Boeing 767 accident near San Bernardino, California, January 10, 2025
On January 10, 2025 at about 2:55 am local time, a 1998 Boeing 767, registered N324UP, was substantially damaged in an accident during landing (flare/touchdown) near San Bernardino, California (San Bernardino Intl airport). It was flown under scheduled airline rules (Part 121). No one was hurt; 3 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
Encounter with windshear during landing which resulted in a tailstrike.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- January 10, 2025 · about 2:55 am local time
- Place
- San Bernardino, California · San Bernardino Intl · map
- Type
- Accident
- Injuries
- No one was hurt; 3 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Boeing 767 34AF, built 1998 · all 767s on the register
- Registration
- N324UP · registry record · serial 27750
- Damage
- Substantial damage
- Flight
- Flight · scheduled airline rules (Part 121)
The NTSB's narrative final · quoted from the NTSB record
United Parcel Service (UPS) flight 2918 experienced a tailstrike while landing on runway 6 at San Bernardino International Airport (SBD), San Bernardino, California. The non-scheduled cargo flight was operated under the provisions of 14 Code of Federal Regulations Part 121. The airplane sustained substantial damage to the underside of the fuselage near the tail. Flight 2918 was originally destined for Ontario International Airport (ONT), Ontario California. After a missed approach at ONT, the flight crew elected to divert to SBD due to fuel state and unfavorable wind conditions at ONT. According to the flight crew, the approach into SBD was stabilized at both 1,000 and 500 ft above ground level (agl). The flight crew further stated that during landing on runway 6, the captain began a normal flare at about 100 ft agl, but he felt the airplane “nose come up and sink rate accelerate” at about 15 ft. The captain stated the airplane contacted the runway “slightly more firmly than usual” but it did not bounce. Once on the runway, the flight crew received an aural windshear warning. Flight data showed the airplane’s pitch attitude reached a maximum of 8.1° at touchdown, sufficient to cause contact between the airplane’s lower fuselage and the runway. Additionally, flight data showed a vertical acceleration of 2.2g, and a windshear warning simultaneous with the touchdown that lasted about 5 seconds. An unscheduled stabilizer trim movement warning occurred immediately after the touchdown. Lastly, an unscheduled stabilizer movement, consistent with the tailstrike event, occurred momentarily about half a second after touchdown. During postlanding rollout, the captain recalled seeing a “tail skid” message on the engine indicating and crew alerting system (EICAS). During postlanding taxi, the first officer was unable to reset the stabilizer trim. Postlanding inspection by the captain revealed substantial damage to the lower fuselage consistent with its contact with the runway. Further inspection of the airplane found damage to the tail skid shock strut and its support assembly as well as the horizontal stabilizer ballscrew actuator (jackscrew), both as a result of the tailstrike. The tail skid damage was consistent with the tail skid message observed on the EICAS by the flight crew. The flight data showed no evidence of a mechanical malfunction that would have contributed to the airplane pitch angle when the airplane touched down on the runway.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Tailstrike during landing (flare/touchdown) defining event
The NTSB's findings
- Aircraft › Aircraft structures › Fuselage › Fuselage main structure › Damaged/degraded
- Environmental issues › Conditions/weather/phenomena › Wind › Windshear › Contributed to outcome
- Environmental issues › Conditions/weather/phenomena › Wind › Windshear › Ability to respond/compensate
- Personnel issues › Experience/knowledge › Knowledge › Knowledge of meteorologic cond › Flight crew
Pilot
- Certificate: airline transport pilot, private
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Flight time: 12,831 hours in all; 2,753 in this make and model; 102 in the last 90 days; 17 in the last 30 days; 4,853 as pilot in command; 1,838 on instruments
- Last flight review: December 20, 2024
- Medical certificate: Class 1 (without waivers/limitations)
- Seat: left
- Injury: no injuries
Pilot
- Certificate: airline transport pilot, military
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Flight time: 4,679 hours in all; 5 in this make and model; 5 in the last 90 days; 5 in the last 30 days; 2,780 as pilot in command; 72 on instruments
- Last flight review: December 17, 2024
- Medical certificate: Class 1 (without waivers/limitations)
- Seat: rgt
- Injury: no injuries
Other crew
- Certificate: airline transport pilot
- Seat: rear
- Injury: no injuries
The aircraft
- Last inspection: continuous airworthiness programme, January 9, 2025
- Maximum gross weight: 408,000 lb
- Seats: 6
- Landing gear: retractable
- Engine 1: Ge CF6-80 SERIES (turbofan); 23,172 hours total
- Engine 2: Ge CF6-80 SERIES (turbofan); 64,645 hours total
- Operator: United Parcel Service CO
The flight
- Departed from: KSDF Louisville KY at 10:32 pm
- Destination: KONT Ontario CA
- Flight plan: IFR
- Runway 06/2, 10,000 ft by 200 ft
- A second pilot was aboard
Weather at the time
- Light: night
- Wind: from 360° at 5 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 66°F (19°C), dew point 0°F (-18°C)
- Altimeter: 30.15 inHg
- Observation at 5:55 pm from KSBD, 13 miles away
Weather report (METAR): METAR KSBD 100155Z 36005KT 10SM CLR 19/M18 A3015=
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 3 |
Photographs from the investigation 5 pictures from the NTSB's docket, as the NTSB released them
Photograph 1 – Lower fuselage damage near tail.
Photograph 2 – Tail skid.
Photograph 3 – Tail skid.
Photograph 4 – Lower fuselage damage near tail.
Photograph 5 – Drain mast damage.The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.
Documents from the investigation the NTSB's docket: the evidence folder behind the report
3 documents, released by the NTSB on October 23, 2025. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | NTSB Form 6120.1 - DCA25LA085 | PDF, 10 pages | View Download |
| 2 | Flight Crew Statements | PDF, 2 pages | View Download |
| 3 | N324UP Damage Photos | PDF, 6 pages · our copy | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
