AirTran Airlines Flight 426
Douglas DC-9-32 · Accident: in flight encounter with weather en route
From Hartsfield Jackson Atlanta International Airport (ATL) to Chicago Midway International Airport (MDW)
Event
- NTSB case
- DCA98MA045
- 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
- Instrument Meteorological Cond
Douglas DC-9-32
- Aircraft type
- Douglas DC-9
- 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
- N948VV
- Operator
- AirTran Airlines
- Onboard fatalities
- Unknown
- Route
- From Hartsfield Jackson Atlanta International Airport (ATL), Atlanta, GATo Chicago Midway International Airport (MDW), Chicago, IL
- 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
- 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
- Substantial
Cause areas
- Flightcrew › Flight into known adverse weather, attempted
Approximate · Estimated position: the centre of Calhoun, GA, the place the record names. Not the accident site.
NTSB narrative
The properly certificated and qualified flight crew received flight release documents containing weather information from airline dispatch that was incomplete and did not contain pertinent Convective SIGMETs and a tornado watch bulletin. However, the flight crew stated that before departure, they looked at a computerized weather display and observed a line of adverse weather conditions along their intended route of flight. During initial climb after takeoff, the flight crew noticed that they were approaching a line of thunderstorms. The captain initially planned to fly around this line but noticed a 10-mile gap in the line that was depicted on the airplane's on-board weather radar display. The captain decided to fly through the gap, which he could also see when he looked outside of the airplane. The first officer did not challenge his decision. Both flight crewmembers stated that the weather radar was functioning normally. It is unknown exactly what was depicted on the aircraft radar. Radar and weather data indicate that the airplane penetrated an extreme weather echo (VIP level 6) that likely contained a severe thunderstorm, hail, and severe to extreme turbulence. The thunderstorm top was above 45,000 feet. Neither the flight attendants nor the passengers received an adequate or timely briefing to remain seated and to prepare for the possibility of turbulence. The aft flight attendant and a passenger were seriously injured during the turbulence encounter. Hail shattered the front windshield and damaged the pitot system, radome, wings, tail, and engines. The flight crew successfully performed an emergency landing at a nearby airport. The investigation revealed that the captain had been involved in two other air carrier incidents involving adverse weather conditions. It also revealed that the airline lacked adequate training and guidance regarding hazardous weather interpretation and avoidance, as well as adequate procedures to notify flight attendants about potential turbulence. According to FAA guidance, flight crews should avoid intense or extreme level radar echoes by at least 20 miles. This guidance also instructs pilots that such echoes should be separated by at least 40 miles before flight is attempted between the echoes.
Probable cause
The failure of the flight crew to maintain adequate separation from hazardous meteorological conditions. Factors contributing to the accident were: (1) the failure of AirTran Airlines to provide adequate crewmember training and guidance regarding hazardous weather encounters; (2) the failure of the flight crew to provide an adequate and timely briefing to the flight attendants regarding turbulence; and (3) the presence of hail and turbulence.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DCA98MA045
- Event ID
- 20001211X10040
- Case number
- DCA98MA045
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: investigation status. 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: 634119334ee19ce01cdb35079e47c382d21dec72d637ec78debd3a8d9c5eb15a; retrieved 2026-09-18T17:09:50.324Z.
- Corrected after a review of the NTSB narrative, which states these values explicitly: operator. The NTSB narrative names the operator: "the failure of AirTran Airlines to provide adequate crewmember training and guidance regarding hazardous weather encounters"