FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

American Airlines McDonnell Douglas MD-82 accident

3 Aug 2003 · Charlotte, NC, United States

McDonnell Douglas MD-82 · Accident: in flight encounter with weather en route

From LaGuardia Airport (LGA) to Tampa International Airport (TPA)

Report a problem

Event

NTSB case
MIA03LA155
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

McDonnell Douglas MD-82

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
N7527A
Onboard fatalities
Unknown
Route
From LaGuardia Airport (LGA), New York City, NYTo Tampa International Airport (TPA), Tampa, 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 · cruise
First occurrenceThe 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
In flight encounter with weather
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

  • Pilot in command › Clearance, not maintained
  • Pilot in command › Seat belt sign, not selected

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The MD-82 encountered turbulence in the vicinity of Charlotte, North Carolina, and one passenger received serious injuries. The captain stated that the ride had been smooth, and there had been occasional light chop. He further stated that the seat belt sign was off, and approximately 7 people were standing at the time of the incident, including the three flight attendants. He said the flight was at FL310, in night visual meteorological conditions, with stars and ground lights visible, and that radar showed a clear flight path, with a significant line of storms approximately 30 miles east of their course. According to the captain, about 2207,the airplane entered instrument meteorological conditions and quickly encountered moderate chop, followed by a very sharp jolt. He said he had immediately turned on the fasten seatbelt sign after the first jolt, and they then received two more sharp jolts. He said that rain and Saint Elmo's were present, and he turned the airplane to the right, back towards where they had last seen ground lights and then informed FAA Air Traffic Control Jacksonville Center of the turn and ride condition. In about 30 seconds, he said the ride became smooth with some light chop, and they entered visual meteorological conditions again. The NTSB examined radar and weather data pertinent to the flight, and the data revealed that when the accident airplane's flight path for the period of the flight was overlaid with infrared satellite imagery, about 2145, there was an isolated thunderstorm with an estimated cloud top of about 36,000 feet in the vicinity of GLOVR intersection. In addition, additional data at 2202, and 2215, showed that the thunderstorm cloud tops had gotten higher, and the thunderstorms had expanded outward and moved northeast along the airplane's track. Digital Doppler weather radar data for Greer, South Carolina, when evaluated with respect to the turbulence times, showed reflectivity echoes in the vicinity of the turbulence location, and the reflectivity’s varied from VIP level 1 (very light) to VIP level 5 (intense). Reflectivity cross sections of radar data along the flight track showed the maximum radar tops which the flight penetrated to be about 40,000 feet. Examination of the airplane's Flight Data Recorder provided data that showed altitude changes, and fluctuations in vertical and lateral acceleration, consistent with other information. Both the NTSB Meteorological, and Flight Data Recorder Factual Group Chairman's reports, have added as attachments.

Probable cause

The pilot-in-command's failure to sufficiently deviate to avoid known weather, and his failure to activate the seatbelt sign to ensure flight attendants and passengers were seated, which resulted in a passenger receiving serious injuries when the flight encountered turbulence.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA03LA155
Event ID
20030812X01306
Case number
MIA03LA155
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates, damage. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2003-08-04.
  • API snapshot SHA-256: b7de1b3164f9948fa787ad5d44ad790efbc4170fefc1bf1d68dccb24dfd7a97e; retrieved 2026-09-18T15:43:12.168Z.