FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Northwest Airlines Douglas DC-9-32 incident

5 May 1994 · Memphis, TN, United States

Douglas DC-9-32 · Incident: total loss of engine power (mechanical failure) during takeoff

From an unrecorded airport to Phoenix Sky Harbor International Airport (PHX)

Report a problem

Event

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

Douglas DC-9-32

Aircraft type
Douglas DC-9
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
N986US
Onboard fatalities
Unknown
Route
From not recordedTo Phoenix Sky Harbor International Airport (PHX), Phoenix, AZ
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
Takeoff · roll/run
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
Total loss of engine power (mechanical failure)
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

  • Combustion assembly, outer casing › Fatigue

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

NTSB narrative

DURING TAKEOFF, AN UNCONTAINED FAILURE OF THE LEFT ENGINE OCCURRED. AN EXAMINATION REVEALED A FATIGUE FRACTURE THROUGH A REAR FLANGE BOLT HOLE OF THE COMBUSTION CHAMBER OUTER CASE, AT THE THREE O'CLOCK POSITION OF THE ENGINE. THE ENGINE HAD BEEN INSPECTED IN ACCORDANCE WITH AN APPLICABLE AIRWORTHINESS DIRECTIVE; HOWEVER, THE FRACTURE OCCURRED 2,060 CYCLES PRIOR TO THE NEXT SCHEDULED INSPECTION. ADDITIONAL INSPECTION REQUIREMENTS RESULTED FROM THE EXAMINATIONS OF THE ENGINE AND THE FRACTURE.

Probable cause

THE FATIGUE FRACTURE OF THE COMBUSTION CHAMBER OUTER CASE. A FACTOR WAS THE MANUFACTURER'S INADEQUATE INSPECTION CRITERIA.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL94IA097
Event ID
20001206X01206
Case number
ATL94IA097
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: 41d87901737b16ee23dfb82b7b08807fcc53a0a1fbaf5d77bc8dbbe2e137545c; retrieved 2026-09-18T18:16:30.559Z.