Northwest Airlines Flight 1432
Airbus Industrie A320-211 · Incident: airframe, component or system failure during landing
From Minneapolis–Saint Paul International Airport / Wold–Chamberlain Field (MSP) to Hector International Airport (FAR)
Event
- NTSB case
- CHI08IA022
- 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
- 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
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 Hector International Airport (FAR), Fargo, ND
- 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
- Landing · landing roll
- 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
- Landing gear, nose gear › Malfunction
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
Shortly after departure, the flightcrew received a Brake and Steering Control Unit (BSCU) channel 2 fault message. Upon reaching 10,000 feet, the crew reset the BSCU per the cockpit operational manual (COM); however, the BSCU channel 2 fault returned and they could not turn off the auto brakes, nor could they change the brake setting from “Maximum.” The crew confirmed that they had “yellow” brake pressure (alternate brakes and parking brake), and believed that they would be landing with alternate brakes. Because turning the antiskid and nosewheel steering to the “Off” position would also turn off maximum braking, they discussed landing with the antiskid and nosewheel steering selected “Off” if necessary. When the crew extended the landing gear during the first approach, they received a landing gear shock absorber fault indication and the auto throttles and autopilot turned off. The crew then contacted air traffic control (ATC) and requested a climb to assess the situation. The captain stated that the landing gear remained down and the flaps were raised. The first officer continued to perform the procedures in the COM and contacted maintenance control to inform them of the landing gear shock absorber fault. The autopilot and auto throttles remained inoperative.
The flight crew then requested and received vectors to final approach. The captain stated that they set the flaps to full and completed the landing checklist. He stated that they planned to keep the brake pressure low during the landing and continue the landing roll with manual braking until they came to a stop. They then intended to turn the nosewheel steering on and taxi to the gate. The captain stated they anticipated an uneventful landing and did not advise ATC of the situation. After landing, the crew felt a vibration when the nosewheel touched down and ATC informed them of flames near the nose gear. The airplane came to rest on the runway with the nose gear strut turned 90 degrees to the direction of landing. The lower half of both the nose gear tire and wheel assembly was ground away due to runway contact. The nose gear was the only part of the airplane that sustained damage.
Postincident examination and testing of the nose landing gear systems revealed an unidentified and intermittent failure of an integrated circuit on the BSCU monitor board. This failure most likely resulted in frozen BSCU System 1 analog and discrete outputs. If the BSCU System 1 commands had frozen, the BSCU System 2 would have been able to detect the System 1 failure but would not have been able to take control. As a result of this incident, the aircraft and the nose gear manufacturers established a program intended to increase the reliability of the BSCU. Each issued a service bulletin for modification of the BSCU software and both the Federal Aviation Administration and European Aviation Safety Agency issued Airworthiness Directives that made compliance with the service bulletin mandatory.
Probable cause
The failure of the Brake and Steering Control Unit, which allowed the nose landing gear to turn to the 90-degree position.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI08IA022
- Event ID
- 20071023X01634
- Case number
- CHI08IA022
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2007-10-21.
- API snapshot SHA-256: 6b0ee9528a7441c9418f4cce405cb029e00002c2e90ede8897114ea179c50646; retrieved 2026-09-18T14:40:56.837Z.