FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Airtran Airways Flight 163

27 Aug 2009 · Inverness, FL, United States Possible conflict

Boeing 717-200 · Accident: turbulence encounter en route

From Tampa International Airport (TPA) to Hartsfield Jackson Atlanta International Airport (ATL)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
ERA09LA488
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
Instrument Meteorological Cond

Boeing 717-200

Aircraft type
Boeing 717
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
N994AT
Onboard fatalities
Unknown
Route
From Tampa International Airport (TPA), Tampa, FLTo Hartsfield Jackson Atlanta International Airport (ATL), Atlanta, GA
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 · climb to cruise
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
  • Personnel issues › Task performance

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

NTSB narrative

The scheduled passenger flight was climbing through 25,000 feet when it encountered convective turbulence in daytime instrument meteorological conditions. A flight attendant, who was servicing the aft cabin, sustained leg and ankle fractures when her service cart became airborne and struck her in the leg. Both the flight and cabin crew members stated that the turbulence was unexpected. The National Weather Service (NWS) had issued multiple, sequential warnings of significant meteorological activity (SIGMETs) regarding the potential for thunderstorms and turbulence along the flight's planned route. The operator's dispatch department provided the flightcrew with a SIGMET that was valid until about one hour before the scheduled departure time. Contrary to operator and regulatory requirements, the dispatch department did not provide the flight crew with updated, current information, which included two new SIGMETs, one of which was issued an hour before the scheduled departure time, and all of which were similar in content and coverage area. The flight crew did not check with dispatch to determine whether any SIGMETS were current for the planned departure time. None of the air traffic controllers who handled the flight prior to the event relayed any hazardous weather information to the flight, despite their requirement to do so.

Correlation of meteorological and flight path data indicated that the turbulence encounter occurred when the airplane penetrated a continuous line of thunderstorms that was present in the SIGMET coverage area. Strong radar echoes, indicative of potential turbulence, were detected below the airplane's altitude by ground-based weather radar. Review of the operator's flight and cabin crew guidance revealed that the procedures incorporated some of the latest industry strategies for mitigating turbulence hazards, but did not provide the flight attendants with the recommended level of autonomy when it came to decisions about when to provide service, or how to prioritize tasks, in the event of turbulence. Although hindered by the failure of the dispatch department to provide them with current SIGMETs, given the previous SIGMET and forecast for significant thunderstorms along the route, and atmospheric activity that was likely readily detectable by the airplane's onboard weather radar, the flightcrew could have anticipated the turbulence, and the flight attendants could have either been instructed to remain seated, or been provided with sufficient information to decide on their own, until the airplane was clear of the hazard area.

Probable cause

The flight crew's encounter with convective turbulence. Contributing to the accident was the failure of the operator's dispatch department to provide the flightcrew with current adverse weather information along the planned route of flight. Also contributing was the failure of the flightcrew to provide relevant forecast information to the cabin crew, and their failure to detect and avoid the existing convective conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA09LA488
Event ID
20090828X61756
Case number
ERA09LA488
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: c8c1981f342c26bbc4eeed46dc6a11df82773cd5aa88ecbe78c56396f7d856e5; retrieved 2026-09-15T12:51:48.856Z.