Delta Air Lines McDonnell Douglas MD-11 incident
McDonnell Douglas MD-11 · Incident: on ground/water collision with terrain/water during landing
From Portland International Airport (PDX) to an unrecorded destination
Event
- NTSB case
- ATL92IA151
- 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
- Incident
- 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
McDonnell Douglas MD-11
- Aircraft type
- McDonnell Douglas MD-11
- 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
- N803DE
- Operator
- Delta Air Lines
- Onboard fatalities
- Unknown
- Route
- From Portland International Airport (PDX), Portland, ORTo not recorded
- Aircraft age
- Not recorded
- 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 · landing roll
- First occurrenceThe 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
- On ground/water collision with terrain/water
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
- Pilot in command › Elevator, improper use of
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE FLIGHT CREW WAS PERFORMING A NORMAL LANDING (MANUAL THROTTLES/AUTO GROUND SPOILER). THEY REPORTED THAT AFTER THE MAIN GEAR HAD TOUCHED DOWN, THE NOSE PITCHED UP 'VIOLENTLY'. SUBSEQUENTLY, THE UNDERSIDE OF THE AIRCRAFT TAIL SCRAPED THE RUNWAY SURFACE. DFDR DATA INDICATED THAT AFTER MAIN GEAR TOUCHDOWN, THE NOSE WAS LOWERED AT AN EXCESSIVE RATE, FOLLOWED BY LARGE, AFT YOKE INPUT TO ARREST THE RATE OF NOSE SINK. THE NOSE GEAR CONTACTED THE RUNWAY WHILE THE AFT YOKE INPUT WAS MAINTAINED, AND THE GROUND SPOILERS EXTENDED TO 60 DEGREES. THE MANUFACTURER STATED THAT WITH THIS SCENARIO, A PITCH UP OF THE NOSE WOULD OCCUR.
Probable cause
THE PILOT IN COMMAND'S IMPROPER USE OF THE AIRCRAFT FLIGHT CONTROLS (ELEVATOR) DURING THE LANDING, WHICH RESULTED IN THE AIRCRAFT TAIL CONTACTING THE RUNWAY SURFACE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL92IA151
- Event ID
- 20001211X15314
- Case number
- ATL92IA151
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: 10c02a500eaeeb513d552acf57cac5ab6a120894b2474b886d5d6a7104b127db; retrieved 2026-09-18T18:45:16.951Z.