Frontier Airlines Flight 384
Airbus A319-112 · Accident: turbulence encounter en route
From Denver International Airport (DEN) to Fort Lauderdale Hollywood International Airport (FLL)
Event
- NTSB case
- DCA12FA069
- 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-112
- 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
- N951FR
- Operator
- Frontier Airlines
- Onboard fatalities
- Unknown
- Route
- From Denver International Airport (DEN), Denver, COTo Fort Lauderdale Hollywood International Airport (FLL), Fort Lauderdale, FL
- 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
- 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
On May 10, 2012, at 1224 Eastern Daylight Time (EDT) an Airbus 319, registration N951FR, operated by Frontier Airlines as flight 384, encountered turbulence resulting in serious injuries to a flight attendant during descent into the Fort Lauderdale Airport (FLL). The flight was descending through 12,400 feet about 45 miles west of FLL at the time of the encounter. The airplane was not damaged.
The flight crew reported that on initial descent into the Fort Lauderdale area they noticed typical Florida summertime cumulus cloud conditions. About 20 minutes before the event, the Captain appropriately briefed the flight attendants to prepare the cabin for landing early and to be seated after completing the initial clean-up. The flight crew subsequently illuminated the seat belt sign during the descent. The flight attendants were still in the process of preparing the cabin for landing when the turbulence was encountered.
During descent, the airplane passed in and out of cloud formations. The crew described, and CVR data is consistent with, passing out of a cloud and noticing a larger developing cumulus in front of them. The autopilot and autothrust were engaged. The crew reported that the radar did not indicate any echoes ahead of them. The Airbus weather radar system includes a Turbulence detection function, which was not used by the crew. The Airbus flight crew training manual describes effective mode, range, and tilt settings for detecting “wet” (convective) turbulence. As the airplane passed into the cumulus development, the airplane encountered convectively induced turbulence, resulting in a peak vertical acceleration of about +2 G and -0.5 G. The activity was likely developing upwards, possibly below the field of view of the radar, and into the flight path.
As a result of the injuries to the forward flight attendant, the flight crew advised ATC that they had an injured crew member and requested priority handling and for paramedics to meet the airplane on arrival. The ATC approach controller did not forward the request for paramedics. The crew also attempted to contact the company station agents and dispatch, but received no response. The lack of ATC coordination, and lack of company personnel to monitor communications from inbound flights, delayed the arrival of emergency medical personnel to meet the flight.
Probable cause
an inadvertent encounter with convectively induced turbulence developing upwards into the flight path, which was not detected on weather radar as configured by the crew.
Contributing to the delay in emergency medical personnel notification was the incomplete coordination of paramedic response by air traffic control and ineffective communications monitoring by Frontier Airlines.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DCA12FA069
- Event ID
- 20120511X73555
- Case number
- DCA12FA069
- 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: be27f46c13f2777459294db59746d54be33519acb24424fe8c876efb13b6b0e1; retrieved 2026-09-15T18:03:33.052Z.