JetBlue Airways Airbus A320-232 accident
Airbus A320-232 · Accident: turbulence encounter on approach
From John F. Kennedy International Airport (JFK) to Patrick Leahy Burlington International Airport (BTV)
Event
- NTSB case
- ERA11CA152
- 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 A320-232
- 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
- N706JB
- Operator
- JetBlue Airways
- Onboard fatalities
- Unknown
- Route
- From John F. Kennedy International Airport (JFK), Jamaica, NYTo Patrick Leahy Burlington International Airport (BTV), Burlington, VT
- 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
- Approach · IFR initial approach
- 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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the captain, while on approach at an altitude of approximately 6,000 feet mean sea level, the airplane experienced an encounter with severe turbulence. Two flight attendants struck the aft galley floor and rear passenger door. One flight attendant sustained bruising and the other flight attendant sustained multiple fractured ribs. The airplane continued its approach and landed normally. There was no damage to the airplane.
Probable cause
The airplane's inadvertent encounter with turbulence during the approach, which resulted in serious injury to a flight attendant.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA11CA152
- Event ID
- 20110219X32035
- Case number
- ERA11CA152
- 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, 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: 9bd9ccb6689a1ea33050f06ae8d776fc6bf0f37836710f6dfd4ab08e76e02458; retrieved 2026-09-15T15:49:47.741Z.