FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

United Airlines Airbus A319-131 accident

7 Jul 2006 · Masonville, CO, United States

Airbus A319-131 · Accident: in flight encounter with weather en route

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

Report a problem

Event

NTSB case
DEN06LA095
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
Accident
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 A319-131

Aircraft type
Airbus A319
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
N839UA
Onboard fatalities
Unknown
Route
From Jackson Hole Airport (JAC), Jackson, WYTo Denver International Airport (DEN), Denver, CO
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
En route · descent
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
In flight encounter with weather
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None

Cause areas

  • Weather condition › Turbulence, clear air

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The crew reported that the flight had been smooth, the "fasten seatbelt sign" was off, and passengers were allowed to get up and move around the cabin. According to the passenger, she was exiting the aft lavatory when the airplane encountered some turbulence. She stated that she felt as if she was being "jammed" to the floor, and felt her right ankle and leg "go" before she fell to the floor. She sustained serious injury to her right ankle. There were no airmen's meteorological information or significant meteorological information issued for turbulence for the area at the time of the accident. No other injuries were reported and the airplane landed without further incident.

Probable cause

the flight's encounter with unexpected turbulence, which resulted in a passenger sustaining a fractured ankle.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN06LA095
Event ID
20060711X00910
Case number
DEN06LA095
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
  • 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: investigation status, coordinates, damage. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: d96d8958a3c0245f3ff93cf446ceacc46662a55161b24989639aeb337df7f041; retrieved 2026-09-18T14:52:05.980Z.
  • The NTSB's operator name is blank for N839UA; the operator shown is the name the NTSB's other records give its FAA operator code, UALA.