United Parcel Service Flight 2918
Boeing 767 34AF · Accident: tailstrike during landing
From Louisville Muhammad Ali International Airport (KSDF) to Ontario International Airport (KONT)
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- DCA25LA085
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- Airline
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Boeing 767 34AF
- Aircraft type
- Boeing 767
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N324UP
- Operator
- United Parcel Service
- Onboard fatalities
- Unknown
- Route
- From Louisville Muhammad Ali International Airport (KSDF), Louisville, KYTo Ontario International Airport (KONT), Ontario, CA
- Aircraft age
- About 27 years (built 1998)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 121: Air Carrier
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · flare/touchdown
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Tailstrike
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft structures
- Environmental issues › Conditions/weather/phenomena
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
Encounter with windshear during landing which resulted in a tailstrike.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DCA25LA085
- Event ID
- 20250114199538
- Case number
- DCA25LA085
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: local date, investigation status, coordinates, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2025-01-10.
- API snapshot SHA-256: 6ed100bb920efde00f3d14ae558d2503fb063280f60a0be90d0972a29b5aa021; retrieved 2026-09-16T19:35:47.702Z.