Northwest Airlines Flight 58
McDonnell Douglas DC-10-30 · Accident: in flight encounter with weather en route
From Miami International Airport (MIA) to Amsterdam Airport Schiphol (AMS)
Event
- NTSB case
- DCA02MA029
- 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
McDonnell Douglas DC-10-30
- Aircraft type
- McDonnell Douglas DC-10
- 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
- N234NW
- Operator
- Northwest Airlines
- Onboard fatalities
- Unknown
- Route
- From Miami International Airport (MIA), Miami, FLTo Amsterdam Airport Schiphol (AMS), Amsterdam
- 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
- En route · descent
- 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
- In flight encounter with weather
- 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
- Copilot/second pilot › Aircraft handling, excessive
- Flight attendant › Seat belt
- Flight attendant › Shoulder harness, not used
- Weather condition › Turbulence
Not plotted · Location withheld: coordinates are missing, conflicting, invalid, or have no accepted acquisition method. No substitute location has been invented.
NTSB narrative
A flight attendant was seriously injured when the airplane encountered turbulence while descending from flight level (FL) 350 to FL 340. Flight crew interview statements indicated that they were preparing for turbulence and that they wanted the passengers and flight attendants seated with their seatbelts fastened. However, the flight crew did not advise the lead flight attendant (LFA) of the turbulence level and its anticipated duration nor did they use turbulence codes, as stipulated in Northwest Airlines' Flight Operations Manual. The investigation also revealed that the LFA did not relay the turbulence information to all of the flight attendants, as stipulated in the company's Flight Attendant Manual.
Examination of the restraint system from the injured flight attendant's jump seat indicated that the restraint system did not fail during the turbulence upset. The Safety Board was unable to determine whether the lapbelt was improperly secured by the flight attendant or whether it was inadvertently disengaged during the turbulence upset.
The Safety Board's investigation examined the turbulence and the flight crew's operation of the airplane during the turbulence encounter to evaluate the effects on the airplane occupants. Analysis of the flight data recorder (FDR) data indicates that the turbulence caused substantial vertical and lateral oscillations, which may have made it difficult for the first officer (as the flying pilot) to maintain a constant pitch attitude.
The FDR data showed variations in the airplane's pitch attitude during the turbulence encounter. Despite the airplane's pitch excursions, statements from the flight crew indicate that they were attempting to maintain constant pitch attitudes during the turbulence upset. Nevertheless, FDR data indicate that the large and rapid pitch excursions were primarily a result of control column inputs made by the first officer. The Safety Board's investigation determined that the main pitchover (which likely caused the flight attendant's injuries) occurred as a result of the first officer's control inputs.
Probable cause
The flight attendant's injuries were a result of her unsecured lap belt and shoulder harness for undetermined reasons, and the oscillations of the airplane, which were caused by turbulence and large control column inputs by the first officer. Contributing to the flight attendant's injuries was the failure of the flight crew and the lead flight attendant to follow company procedures regarding dissemination of turbulence information.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DCA02MA029
- Event ID
- 20020322X00387
- Case number
- DCA02MA029
- 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: 3ed1e87ff82926dd4262f801d3a048f3b05f19d3a4dbe4523743a718a07e807e; retrieved 2026-09-18T16:04:25.182Z.