United Parcel Service Airbus A300 F4-622R accident
Airbus A300 F4-622R · Accident: tailstrike during landing
From Ontario International Airport (ONT) to an unrecorded destination
Event
- NTSB case
- DCA25LA015
- 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
- Unknown
- 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
Airbus A300 F4-622R
- Aircraft type
- Airbus A300
- 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
- N162UP
- Operator
- United Parcel Service
- Onboard fatalities
- Unknown
- Route
- From Ontario International Airport (ONT), Ontario, CATo not recorded
- Aircraft age
- About 19 years (built 2005)
- 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 oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
On October 29, 2024, about 1155 eastern daylight time, United Parcel Service (UPS) Company flight 2909 sustained a tailstrike while landing at Louisville Muhammad Ali International Airport (SDF), Louisville, KY. According to the flight crew, the captain was the pilot flying, and the first officer (FO) was the pilot monitoring (PM) when they were cleared for the instrument landing system (ILS) approach to runway 17R at SDF. The airplane was in the landing configuration and on a stabilized approach at 1,000 ft. and 500 ft. above ground level (AGL) respectively per company procedure. After the 500 ft stable callout by the PM, the auto pilot was disengaged and the approach continued with a normal descent rate and the autothrottles engaged. At about 20 ft AGL, power was reduced, and the flare was initiated. The touchdown felt normal, and the PM vocalized the spoiler deployment. Subsequently, the thrust reversers were deployed. The airplane bounced; however, due to the deployment of the thrust reversers a go-around was prohibited. The airplane settled back on the runway and was slowed for taxi. During the taxi, air traffic control advised the flight crew of a possible tailstrike. After the tailstrike, the remainder of the landing rollout and taxi were uneventful. A review of flight data recorder data showed that after the initial touchdown due to excessive energy, the airplane bounced followed by a firm landing. As the airplane’s shock absorber rebounded from the firm landing a nose-up control column was applied and the pitch angle began to increase. Simultaneously, the ground spoilers and thrust reversers continued to deploy, which exacerbated the nose-high attitude and resulted in a pitch angle of about 12 degrees. According to Airbus, after touchdown the flight crew should fly the nosewheel smoothly, but without delay on to the runway, and must be ready to counteract any pitch up effect of the ground spoilers and reverse thrust. The tailstrike resulted in abrasion damage along the aft lower fuselage. An inspection revealed substantial damage to the frames.
Probable cause
The pilot’s incorrect pitch attitude during a bounced landing which resulted in a tailstrike.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DCA25LA015
- Event ID
- 20241030195412
- Case number
- DCA25LA015
- 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: investigation status, coordinates, cause areas. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: d973de4d72dcedd57f672aa300afeb3160f54ac81dc3f8f87b192eb3f58e9c42; retrieved 2026-09-16T19:26:02.041Z.