Mesa Airlines Bombardier Inc CL600-2D24 accident
Bombardier Inc CL600-2D24 · Accident: turbulence encounter en route
From Savannah Hilton Head International Airport (SAV) to Charlotte Douglas International Airport (CLT)
Event
- NTSB case
- ERA11CA327
- 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
Bombardier Inc CL600-2D24
- Aircraft type
- Bombardier CL600
- 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
- N929LR
- Operator
- Mesa Airlines
- Onboard fatalities
- Unknown
- Route
- From Savannah Hilton Head International Airport (SAV), Savannah, GATo Charlotte Douglas International Airport (CLT), Charlotte, NC
- 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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The captain stated that he briefed the flight attendants prior the flight that it would be bumpy since they were flying around thunderstorms. While descending through 15,000 feet, the airplane encountered moderate turbulence for several seconds. According to a flight attendant, they were informing the passengers of their gates for the next connection in the destination terminal when the airplane encountered the turbulence. One of the flight attendants sustained a serious injury while the other was not injured. The airplane was not damaged and landed uneventfully at the destination airport.
Probable cause
The inadvertent in-flight encounter with turbulence, resulting in an injury to a cabin attendant.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA11CA327
- Event ID
- 20110607X73034
- Case number
- ERA11CA327
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: local date, investigation status, coordinates, damage. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2011-06-06.
- API snapshot SHA-256: 24e5182d84f93d5b1b3a803f586e4f9458b05d07c9e26388592311585471fabf; retrieved 2026-09-15T16:15:32.995Z.
- Corrected after a review of the NTSB narrative, which states these values explicitly: departure. Typo in city name; airport code SAV is Savannah, GA.