FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Northwest Airlines Flight 985

17 Mar 2001 · Detroit, MI, United States

Airbus Industrie A320-200 · Accident: loss of control in flight during takeoff

From Detroit Metropolitan Wayne County Airport (DTW) to Miami International Airport (MIA)

Report a problem

Event

NTSB case
CHI01FA104
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
Instrument Meteorological Cond

Airbus Industrie A320-200

Aircraft type
Airbus A320
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
N357NW
Onboard fatalities
Unknown
Route
From Detroit Metropolitan Wayne County Airport (DTW), Detroit, MITo Miami International Airport (MIA), Miami, FL
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
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
Loss of control in flight
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

  • Pilot in command › Aborted takeoff, delayed
  • Pilot in command › Porpoise/pilot-induced oscillation, inadvertent

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The Airbus A320 contacted the runway and the terrain during takeoff on runway 3C (8,500 feet by 200 feet, wet) at the Detroit Metropolitan Wayne County Airport. An emergency evacuation was made during which time the emergency evacuation slide on the 2 left (2L) door failed to deploy. The captain reported that during the initial takeoff run, he held half forward pressure until reaching 80 knots. He reported that up to this point, everything was normal. He stated he released forward stick pressure by about 100 knots and the nose of the airplane began lifting off the ground with neutral stick, which was not normal. He reported he applied about half forward stick and the nose came back down. He reported that at 120 knots the nose again began to rise with one half to one quarter stick input. He then pushed the stick forward to the forward stop and the nose came up at a rapid rate. The captain reported that his attention was focused outside the airplane and he did not hear the first officer call V1. He reported that he felt the airplane was going to stall so he pulled the power off and aborted the takeoff. The captain stated that he was trained not to perform high-speed aborted takeoffs, but he felt the airplane would have been uncontrollable if the takeoff continued. The captain stated the thrust reversers were deployed and he initially thought there was enough runway remaining to stop. He assumed the autobrakes activated, but he pressed on the brakes anyway. He reported the airplane was not decelerating and it departed the end of the runway at a high speed. The captain reported that deceleration was rapid once the airplane departed the paved surface and the engines flamed out during the ground roll. Post accident inspection of the airplane revealed the horizontal stabilizer trim was set to negative 1.7 (units of trim), when it should have been set at positive 1.7. The first officer stated he set the trim while on the taxiway. The captain did not notice the improper trim setting during the cross check which was part of the taxi checklist. Further investigation revealed the operator procedures were to set the trim using units instead of percentage of mean aerodynamic chord as recommended by the manufacturer. In addition, it was discovered that the manner in which the units of trim were displayed on the trim control wheel, on the electronic centralized aircraft monitoring system (ECAM), and in the aircraft communications addressing and reporting system (ACARS) were not consistent. As a result the Safety Board issued Safety Recommendations A-02-06 and A-02-07. Post accident examination of the 2L slide/raft that did not deploy revealed an improper chamfer on the telescopic girt bar which attaches the slide/raft to the airplane structure. This allowed the slide/raft to detach from the airplane when the 2L door was opened. As a result the Safety Board issued Safety Recommendations A-01-27 and A-01-28. Being a fly-by wire airplane, the Airbus A320 has two sources of control lag in the pitch control. One is the latency between the pilot's input and the elevator movement through the elevator aileron control (ELAC) computer and the other is the rate limit of the elevator. Examination of the digital flight data recorded data for this accident revealed the pilot changed the pitch input faster than the elevator system would respond and saturation occurred in the rate at which the elevator surface could respond to the inputs. This resulted in pilot inducted oscillations (PIO) during the takeoff roll.

Probable cause

The pilot induced oscillations and the delay in aborting the takeoff. Factors associated with the accident were the first officer used an improper trim setting and the captain did not identify and correct the setting during the taxi checklist, and the wet runway conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI01FA104
Event ID
20010319X00608
Case number
CHI01FA104
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
  • 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, coordinates. 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: 3c45ea7b54b6f77f7975c6559cba5469d7777dc4aa77fa9ae1d8ebf35b046091; retrieved 2026-09-18T16:15:42.048Z.
  • The NTSB's operator name is blank for N357NW; the operator shown is the name the NTSB's other records give its FAA operator code, NWAA.