Airbus Industrie A320United Air Lines
Jackson, WY, USA · 2008-02-26·N442UA
What happened
NTSB summary, verbatimThe flight crew reported that prior to the approach into KJAX, the captain performed an approach briefing which included that the Mu readings indicated "good" breaking; it was determined that if the airplane did not touchdown in the first 2,000 feet of runway, they would perform a go around. The touchdown was "firm" and the captain believed it was within the first 2,000 feet of runway. The deceleration was normal until the airplane reached about 80 knots when it started to slide. The captain then applied maximum manual braking and the airplane started to slide toward the right side of the runway. The airplane exited the end of the runway and came to rest in the snow. The runway friction measurements taken before and after the incident were all above 0.45, which according to the Aeronautical Information Manual, is above the level when braking action would start to deteriorate. Therefore, the airplane braking performance was not deteriorated by the runway conditions. There were no faults logged in the maintenance systems that were relevant to the antiskid or brake systems, however, the inboard (IB) and outboard (OB) tachometer wires on the left main landing gear (LMLG) were found to be cross connected. With the wires crossed connected, when the IB tire began to skid (stop rotating) the Brake Steering and Control Unit (BSCU) would have commanded a reduction in the hydraulic pressure to the OB brake, instead of the IB brake, causing a loss of braking on the OB wheel. At the same time, the BSCU would have continued to command an increase in hydraulic pressure to the IB brake, causing it to fully skid and fail. Therefore, when the captain applied full manual braking, the braking action on the LMLG was almost fully lost while the right MLG braking remained normal, resulting in the airplane veering to the right and exiting the runway. A review of the maintenance documents and practices showed that there were no specific inspections required when the landing gear and wiring harnesses were received to ensure they were routed to the correct axle. Additionally, installation documents did not specify the exact wire number connector that needed to be installed on each tachometer for a given position. Finally, a proper functional check should have identified the cross connected tachometers, even though maintenance personnel indicated no discrepancies when tested. After the incident, United Airlines took numerous actions to prevent similar incidents from reoccurring.
Photographs
1the aircraft, and what the investigators foundProbable cause
the Board's determinationthe loss of braking action on the left main landing gear due to the cross connection of the wheel speed tachometer wires that was caused by inadequate maintenance performed on the airplane during the installation of the main landing gear.
Occurrence sequence
1 stepsNTSB coding · CICTT taxonomy- 1 · Landing-landing rollSys/Comp malf/fail (non-power)defining event
Findings
3 causal · 0 contributing- CAUSEPersonnel issues › Task performance › Maintenance › Installation — Maintenance personnel
- CAUSEAircraft › Aircraft systems › Landing gear system › Landing gear brakes system — Related maintenance info
- CAUSEAircraft › Aircraft systems › Landing gear system › Landing gear brakes system — Incorrect service/maintenance
Sequence of events
3 timed eventsfrom the FDR factual report · claude-fable-5-1 (in-session)- 20:07:40-21:15:40 MSTflightp.7Entire flight covered by the 'a' plots (basic, autopilot, autothrust, brakes, engines, flight controls, spoilers, warnings)
- 21:13:30-21:15:15 MSTlandingp.7Last 105 seconds of FDR data covered by the 'b' plots (approach, landing and runway excursion)
- 21:14:47-21:15:15 MSTrunway excursionp.7Last 27 seconds of FDR data covered by the 'c' plots (departure from the right side of runway 19)
NTSB analysis
from the final reportThe flight crew reported that prior to the approach into KJAX, the captain performed an approach briefing which included that the Mu readings indicated "good" breaking; it was determined that if the airplane did not touchdown in the first 2,000 feet of runway, they would perform a go around. The touchdown was "firm" and the captain believed it was within the first 2,000 feet of runway. The deceleration was normal until the airplane reached about 80 knots when it started to slide. The captain then applied maximum manual braking and the airplane started to slide toward the right side of the runway. The airplane exited the end of the runway and came to rest in the snow. The runway friction measurements taken before and after the incident were all above 0.45, which according to the Aeronautical Information Manual, is above the level when braking action would start to deteriorate. Therefore, the airplane braking performance was not deteriorated by the runway conditions. There were no faults logged in the maintenance systems that were relevant to the antiskid or brake systems, however, the inboard (IB) and outboard (OB) tachometer wires on the left main landing gear (LMLG) were found to be cross connected. With the wires crossed connected, when the IB tire began to skid (stop rotating) the Brake Steering and Control Unit (BSCU) would have commanded a reduction in the hydraulic pressure to the OB brake, instead of the IB brake, causing a loss of braking on the OB wheel. At the same time, the BSCU would have continued to command an increase in hydraulic pressure to the IB brake, causing it to fully skid and fail. Therefore, when the captain applied full manual braking, the braking action on the LMLG was almost fully lost while the right MLG braking remained normal, resulting in the airplane veering to the right and exiting the runway. A review of the maintenance documents and practices showed that there were no specific inspections required when the landing gear and wiring harnesses were received to ensure they were routed to the correct axle. Additionally, installation documents did not specify the exact wire number connector that needed to be installed on each tachometer for a given position. Finally, a proper functional check should have identified the cross connected tachometers, even though maintenance personnel indicated no discrepancies when tested. After the incident, United Airlines took numerous actions to prevent similar incidents from reoccurring.