FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

American Airlines Flight 2516

10 Feb 2023 · Rushville, IN, United States

Boeing 737 823 · Accident: turbulence encounter en route

From Orlando International Airport (MCO) to Chicago O'Hare International Airport (ORD)

Report a problem

Event

NTSB case
DCA23LA170
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
0
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 823

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
N944AN
Onboard fatalities
Unknown
Route
From Orlando International Airport (MCO), Orlando, FLTo Chicago O'Hare International Airport (ORD), Chicago, IL
Aircraft age
About 23 years (built 2000)
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

American Airlines flight 2516 encountered clear air turbulence during decent, while en route to Chicago O’Hare International airport (ORD), Chicago, Illinois. The flight was a regularly scheduled passenger flight from Orlando International Airport (MCO), Orlando, Florida to ORD. As a result of the turbulence, one flight attendant (FA) sustained serious injuries. The aircraft was not damaged, and the flight landed without further incident.

The flight crew reported that while on the VEECK5 arrival at flight level (FL)290, near the top of the decent, air traffic control (ATC) advised of reports of moderate turbulence between FL240 and FL190. ATC suggested the flight begin its decent early to avoid the area, and the flight crew agreed. The flight had previously been smooth, and this was the first turbulence advisory they had received from ATC.

The captain informed the cabin crew to expect moderate turbulence in about 10 minutes and advised them to prepare the cabin for landing and take their seats. The captain made an announcement for the passengers to remain seated. The seatbelt sign was on. While the cabin crew was preparing for landing, the airplane encountered severe turbulence as it descended through FL250.

FA1 reached the forward jumpseat, while FA2 and FA3 reached nearby cabin seats. All 3 had difficulty reaching their seats and trouble securing their seatbelts due to the turbulence. FA4 was lifted up then down to the floor while attempting to reach a seat, injuring her left leg and ankle. She remained on the aisle floor until the turbulence ended, about 2 minutes after it began.

Once FA1 confirmed it was safe to get up, she informed the captain about the injury to FA4 and went to check on the passengers with FA2. FA3 tended to FA4 and made a passenger announcement requesting medical assistance. A nurse who was a passenger on board rendered aid to FA4. The captain advised dispatch of the event and requested medical personnel meet the airplane at the gate. After landing, FA4 was transported to the hospital where she was diagnosed with multiple fractures to her left leg and ankle which required surgery.

A post-accident weather analysis provided by the operator showed strong horizontal and vertical wind shear and gravity waves in the area indicating an environment conducive to clear air turbulence. Preflight weather planning predicted light to moderate turbulence between FL290 to FL360 in the area of the event. While there were no active Significant Meteorological hazards (SIGMETs) over the area of the event, a turbulence SIGMET was in effect between FL290 and FL360 for an area about 20 nautical miles southeast of the event. The Turbulence Auto-PIREP System (TAPS) had generated severe turbulence reports for altitudes between FL276 and FL244 in the hour prior to the event, and one pilot report of severe turbulence between FL200 and FL250 was issued a few minutes after the event.

Probable cause

An encounter with clear air turbulence during descent.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DCA23LA170
Event ID
20230213106723
Case number
DCA23LA170
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: local date, investigation status, cause areas, damage. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2023-02-11.
  • API snapshot SHA-256: ac70ccee883985a965c66333a877b7503656cf85b81c9751c2509ad7a21a929d; retrieved 2026-09-16T17:19:55.683Z.