Northwest Airlines Boeing 757-251 incident
Boeing 757-251 · Incident: airframe, component or system failure en route
From Detroit Metropolitan Wayne County Airport (DTW) to an unrecorded destination
Event
- NTSB case
- CHI90IA006
- 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
Boeing 757-251
- Aircraft type
- Boeing 757
- 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
- N512US
- Operator
- Northwest Airlines
- Onboard fatalities
- Unknown
- Route
- From Detroit Metropolitan Wayne County Airport (DTW), Detroit, MITo 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
- 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
- Airframe, component or system 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
- Flight control, flap › Inoperative
- Flt control syst, wing flap control cable/rod › Failure, total
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE FLIGHT CREW REPORTED THAT THEY RECEIVED A 'FLAP DISAGREE' MESSAGE DURING THE DESCENT AND APPROACH TO THEIR DESTINATION AIRPORT. WHEN CHECKLIST PROCEDURES WERE NOT SUCCESSFUL IN CORRECTING THE SITUATION, AN UNEVENTFUL 'ABNORMAL FLAP' LANDING WAS PERFORMED. POST-INCIDENT INSPECTION REVEALED A FAILED INBOARD TRAILING EDGE FLAP DRIVE TORQUE TUBE COUPLING. FURTHER INVESTIGATION REVEALED ONE SIMILAR FAILURE, AND EXAMINATION OF THE OPERATING 757 FLEET REVEALED NUMEROUS OCCURRENCES OF EXCESSIVE WEAR ON THE AFT COUPLING OF THE TORQUE TUBE ASSEMBLY. LAB ANALYSIS OF THE WEAR, AND A METALLURGICAL EXAMINATION RESULTED IN THE MANUFACTURER REDUCING THE RECOMMENDED MAINTENANCE INTERVAL AND RECOMMENDING MORE FREQUENT VISUAL INSPECTIONS OF THE COMPONENT.
Probable cause
THE EXTREME WEAR AND EVENTUAL FAILURE OF A TORQUE TUBE IN THE INBOARD TRAILING EDGE FLAP SYSTEM. INSPECTION AND LUBRICATION INTERVALS WERE A FACTOR, AS WAS THE PHYSICAL LOCATION OF THE TORQUE TUBE WITH REFERENCE TO EXTERNAL FACTORS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI90IA006
- Event ID
- 20001213X29555
- Case number
- CHI90IA006
- 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: ef0eacaa5fc2767ac6ccd5e317debb9bd02c0549cf2cc080990b8de1596dc422; retrieved 2026-09-18T19:07:38.942Z.