United Air Lines Boeing 737-924ER 924 accident
Boeing 737-924ER 924 · Accident: turbulence encounter en route
From Denver International Airport (DEN) to Orlando International Airport (MCO)
Event
- NTSB case
- DCA16CA010
- 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
Boeing 737-924ER 924
- Aircraft type
- Boeing 737
- 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
- N69838
- Operator
- United Air Lines
- Onboard fatalities
- Unknown
- Route
- From Denver International Airport (DEN), Denver, COTo Orlando International Airport (MCO), Orlando, FL
- Aircraft age
- About 1 year (built 2014)
- 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 · cruise
- 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
- Turbulence encounter
- 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
- Environmental issues › Conditions/weather/phenomena
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to flight crew statements, possible moderate turbulence was forecasted for portions of the route of flight and they briefed the flight attendants (FA) of the possible turbulence. During the first portion of the flight, several areas of turbulence were encountered. The seatbelt sign was turned on during this time and the captain told the FAs to suspend service and remain seated. The flight crew requested and was cleared to a lower altitude and the turbulence subsided. After the flight was in smooth air for several minutes, the captain advised the FAs they could leave their seats but not use the carts. About five minutes later the flight again encountered moderate to severe turbulence. The captain called the cabin and discovered two FAs in the aft galley had sustained injuries during the encounter but could continue their duties to the destination. After arrival, the FAs were transported to the hospital where one was diagnosed with a tibia plateau fracture.
Probable cause
An inadvertent encounter with clear air turbulence resulting in a serious injury to a flight attendant.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DCA16CA010
- Event ID
- 20151026X81321
- Case number
- DCA16CA010
- 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: investigation status, 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: 620361bac52e9bca21eacc2e4c0ed9f9aae2021725d2c8e26b950215fe091bbb; retrieved 2026-09-16T02:55:30.344Z.