FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Flight 859 · Boeing MD-11

19 Sept 2004 · Memphis, TN, United States

Boeing MD-11 · Accident: hard landing

From Oakland San Francisco Bay Airport (KOAK) to Frederick W. Smith International Airport (KMEM)

Report a problem

Event

NTSB case
DCA04MA082
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

Boeing MD-11

Aircraft type
Boeing 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
N601FE
Operator
Unknown
Onboard fatalities
Unknown
Route
From Oakland San Francisco Bay Airport (KOAK), Oakland, CATo Frederick W. Smith International Airport (KMEM), Memphis, TN
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 · flare/touchdown
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
Hard landing
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

  • Flightcrew › Recovery from bounced landing, improper

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The approach to landing was normal, and the crew stated that the touchdown was firm but not categorized as a hard landing. The airplane pitched up and bounced after touchdown and the captain became concerned that the airplane would porpoise. The speed had decreased to 107 knots, and reverse thrust had been initiated. The captain elected to conduct a go-around maneuver, and rotated the airplane to a nose high attitude of about 12 degrees prior to achieving sufficient airspeed and a positive rate of climb. The rear fuselage of the airplane contacted the runway for about 3,000 to 4,000 feet causing substantial damage to the airframe. The airplane lifted off, and the crew completed a second landing on runway 36R without further incident. Boeing training material and FedEx guidance states that "after reverse thrust is initiated, a full stop landing must be made. Do not attempt a go-around." Additionally, the FedEx tailstrike awareness training states that "the [pilot flying] must not exceed 10 degrees of pitch or retract the landing gear until the aircraft is safely airborne with a positive rate of climb."

Probable cause

The pilot's over-rotation during a go-around maneuver initiated because of a bounced landing. The go-around maneuver was initiated at a low speed and high pitch angle, and after reverse thrust was selected, contrary to Boeing and FedEx training guidance.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DCA04MA082
Event ID
20041209X01953
Case number
DCA04MA082
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: 3b9029dceb72feb26a5e507a6f936998a76beca2e3b9360582dafb8d32a82dc2; retrieved 2026-09-18T15:16:17.349Z.