Northwest Airlines Flight 352
Airbus Industrie A320-211 · Incident: loss of control in flight on approach
From Minneapolis–Saint Paul International Airport / Wold–Chamberlain Field (MSP) to Ronald Reagan Washington National Airport (DCA)
Event
- NTSB case
- CHI95IA138
- 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
Airbus Industrie A320-211
- 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
- N331NW
- Operator
- Northwest Airlines
- Onboard fatalities
- Unknown
- Route
- From Minneapolis–Saint Paul International Airport / Wold–Chamberlain Field (MSP), Minneapolis, MNTo Ronald Reagan Washington National Airport (DCA)
- 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
- Approach · VFR pattern final
- 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
- None
Cause areas
- Company/operator management › Information, disregarded
- Company/operator management › Unsafe/hazardous condition, not identified
- Pilot in command › Flight controls, excessive
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT REPORTED THAT DURING THE VISUAL APPROACH TO RUNWAY 18, THE AIRPLANE ENTERED UNCOMMANDED ROLLS. A GO-AROUND WAS PERFORMED. ACCORDING TO THE PILOT, ON THE SECOND APPROACH THE AIRPLANE ONCE AGAIN EXPERIENCED AN UNCOMMANDED ROLL. THE AIRPLANE WAS LANDED. FDR DATA SHOWS THE ROLL OSCILLATIONS WITH A MAX ROLL OF 15.5 DEGREES. DURING THIS TIME THE SIDE STICK WAS BEING MOVED BACK AND FORTH TO ITS FULL TRAVEL LIMITS. THE AIRPLANE MOVEMENTS AND THE PILOT'S ACTIONS ARE CONSISTENT WITH PILOT INDUCED OSCILLATIONS (PIO). THE AIRPLANE WAS BEING LANDED IN CONF 3 (20 DEGREES OF FLAPS) WHICH MAKES THE HANDLING CHARACTERISTICS OF THE AIRPLANE 'MORE CRISP'. IN 1993 AIRBUS PUBLISHED A TEMPORARY REVISION TO THE AIRPLANE'S FLIGHT CREW OPERATING MANUAL STATING THE AIRPLANE SHOULD NOT BE LANDED IN ADVERSE WEATHER CONDITIONS (GUSTY WINDS AND TURBULENCE) IN CONF 3 DUE TO THE POSSIBILITY OF PIO. NORTHWEST AIRLINES HAD NOT INCORPORATED THIS INFORMATION IN THEIR OPERATING MANUALS.
Probable cause
the pilot's excessive use of the flight controls during the landing approach, the company's disregard of information provided by the airplane manufacturer, and the company's failure to identify a potentially hazardous conditions based on the information provided by the airplane manufacturer. Factors associated with the incident were the gusty wind conditions and the pilot's failure to land with full flaps.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI95IA138
- Event ID
- 20001207X03253
- Case number
- CHI95IA138
- 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, damage. 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: 735b01c8956364ec579dea07451e5fe118974fc8787adb4d900014f0aa4383c3; retrieved 2026-09-18T18:01:28.464Z.
- The NTSB's operator name is blank for N331NW; the operator shown is the name the NTSB records it doing business as.