Nose gear damage following landing due to system failures

Casualties unknown • Fargo, ND, US

A flight crew experienced multiple system faults during flight, leading to a nose gear malfunction and runway contact upon landing.

What happened

Shortly after departure, the flight crew of an Airbus A320 (registration not provided) received a Brake and Steering Control Unit (BSCU) channel 2 fault message. After reaching 10,000 feet, the crew attempted to reset the BSCU according to the cockpit operational manual; however, the channel 2 fault returned. This prevented the crew from turning off the auto brakes or changing the brake setting from "Maximum." The crew confirmed they had "yellow" brake pressure, utilizing alternate brakes and the parking brake, and prepared to land using this configuration.

Because disabling the antiskid and nosewheel steering would also disable maximum braking, the crew discussed landing with these systems in the "Off" position if necessary. During the first approach, while extending the landing gear, the crew received a landing gear shock absorber fault indication, which caused the auto throttles and autopilot to disconnect. The captain reported that the landing gear remained down and flaps were raised. The first officer followed manual procedures and notified maintenance control of the shock absorber fault.

After receiving vectors for final approach, the crew set the flaps to full and completed the landing checklist. The plan was to maintain low brake pressure during landing and use manual braking to bring the aircraft to a stop before re-engaging nosewheel steering to taxi to the gate. The crew did not notify air traffic control of their specific situation. Upon touchdown, the crew felt a vibration, and air traffic control reported seeing flames near the nose gear. The aircraft came to rest on the runway with the nose gear strut turned 90 degrees from the direction of landing. The lower half of both the nose gear tire and wheel assembly was ground away due to contact with the runway. There were no injuries and the nose gear was the only part of the aircraft that sustained damage.

The investigation

Post-incident examination and testing of the nose landing gear systems identified an unidentified, intermittent failure of an integrated circuit on the BSCU monitor board. This failure most likely caused the BSCU System 1 analog and discrete outputs to freeze. While BSCU System 2 could detect the System 1 failure, it was unable to take control of the system.

Probable cause

An unidentified and intermittent failure of an integrated circuit on the BSCU monitor board caused System 1 outputs to freeze, preventing the secondary system from taking control.

Frequently asked questions

What happened in the 2007-10-21 Airbus Industrie A320-211 accident near Fargo, ND?

A flight crew experienced multiple system faults during flight, leading to a nose gear malfunction and runway contact upon landing.

What aircraft was involved and where did it happen?

The accident on 2007-10-21 involved a Airbus Industrie A320-211, registration N331NW, operated by Northwest Airlines, at Fargo, ND.

What was the probable cause of the accident?

An unidentified and intermittent failure of an integrated circuit on the BSCU monitor board caused System 1 outputs to freeze, preventing the secondary system from taking control.

Investigation report by the U.S. National Transportation Safety Board (NTSB) historical archive. Original record: https://carol.ntsb.gov/event/20071023X01634. This page is a structured re-presentation; facts and quotes are in the National Transportation Safety Board (NTSB), United States.

Loading the flight search…