Aviation Crash Map

Airbus A320-211 N331NW

21 October 2007 · Fargo, North Dakota, United States · No injuries

Summary

On 21 October 2007 at about 01:07 local time, a Airbus A320-211 registered N331NW, operated by Northwest Airlines, was involved in an incident near Fargo, North Dakota, United States. 138 people were on board and nobody was injured. The aircraft was slightly damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.

The record

Date
at 01:07
Classification
Incident
Location
Fargo, North Dakota, United States
Nearest airport
Hector International (FAR)
Coordinates
46.9206, -96.8158
Aircraft
Airbus A320-211
Registration
N331NW
Category
Airplane
Engines
2
Operating rule
Part 121: Air Carrier
Phase of flight
Not recorded
Route
Minneapolis → Fargo
Aircraft damage
Minor
Weather
VMC
Light
Night
NTSB number
CHI08IA022

People

Nobody was injured.

On board Died Serious Minor Uninjured
138 0 0 0 138

Probable cause

The failure of the Brake and Steering Control Unit, which allowed the nose landing gear to turn to the 90-degree position.

Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.

Read the full 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.

Quoted verbatim from the NTSB record.

Other Airbus A320 accidents

Date Aircraft Location Operator Outcome Died
17 Jul 2007 Airbus A320-233
PR-MBK
Sao Paulo, Brazil
no coordinates
TAM Linhas Aéreas Fatal 187
10 Oct 2007 Airbus A320-232
N431UA
Chicago, Illinois, United States United Air Lines Inc Minor injuries -
25 Jan 2008 Airbus A320
N462UA
Newark, New Jersey, United States United Airlines Inc No injuries -
24 Jul 2006 Airbus A320
AP-BGV
Islamabad, Pakistan
no coordinates
AirBlue Unknown -
5 Mar 2006 Airbus A320
EC-HUK
Dublin, Ireland
no coordinates
Iberia Lineas Aereas de Espana Unknown -
2 Aug 2006 Airbus A320
B-2369
Shenzhen, China, China
no coordinates
China Southern Airlines Unknown -

All 204 records for this type

Other accidents in this area

Date Aircraft Location Operator Outcome Died
15 Jul 2007 Air Tractor AT-301
N8841S
Lignite, North Dakota, United States - Serious injuries -
16 Jul 2007 Rotorway 162F
CFYAR
Heart, North Dakota, United States - No injuries -
5 Jun 2007 Weatherly 201C
N1246W
Mc Clusky, North Dakota, United States - No injuries -
5 Jun 2007 Aero Commander S2R
N8835Q
Watford City, North Dakota, United States
no coordinates
Taylor Ag Services, Inc. Fatal 1
9 Aug 2007 Snow S-2C
N16535
Hazelton, North Dakota, United States - No injuries -
1 Aug 2007 Beechcraft B60
N529R
Bismark, North Dakota, United States Henry L. Reichert No injuries -

All 170,864 records in United States