FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

United Air Lines Airbus Industrie A320 incident

25 Feb 2008 · Jackson, WY, United States

Airbus Industrie A320 · Incident: system/component malfunction/failure (non-power) during landing

From Denver International Airport (DEN) to Jackson Hole Airport (JAC)

Report a problem

Event

NTSB case
DCA08IA044
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

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
N442UA
Onboard fatalities
Unknown
Route
From Denver International Airport (DEN), Denver, COTo Jackson Hole Airport (JAC), Jackson, WY
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
Defining eventThe 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
System/component malfunction/failure (non-power)
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

  • Aircraft › Aircraft systems
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The 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.

Probable cause

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

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DCA08IA044
Event ID
20080312X00305
Case number
DCA08IA044
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2008-02-26.
  • API snapshot SHA-256: 870990051ca192d73426e14b629e4557664fa4232430344131fb5d0c69b4ce75; retrieved 2026-09-15T09:25:33.047Z.