Airtran Airways Boeing 717-200 incident
Boeing 717-200 · Incident: airframe, component or system failure during landing
From Hartsfield Jackson Atlanta International Airport (ATL) to Minneapolis–Saint Paul International Airport / Wold–Chamberlain Field (MSP)
Event
- NTSB case
- ATL04IA085
- 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
- Incident
- 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
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
- N978AT
- Operator
- AirTran Airways
- Onboard fatalities
- Unknown
- Route
- From Hartsfield Jackson Atlanta International Airport (ATL), Atlanta, GATo Minneapolis–Saint Paul International Airport / Wold–Chamberlain Field (MSP), MINNEAPOLIS, MN
- 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
- Landing · emergency landing after takeoff
- 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
- Airframe, component or system failure
- 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
- Electrical system › Failure, total
Approximate · Estimated position: the centre of Atlanta, GA, the place the record names. Not the accident site.
NTSB narrative
According to the captain, during the climb out from runway 26L at approximately 200 feet, the number 6 display unit on the pilot's instrument panel went blank and the engine alert display left generator off alert displayed. The first officer requested radar vectors from the Atlanta Tower. After contacting the tower the airplane had a complete electrical power failure, and communications with the Atlanta Tower was lost. Emergency electrical power was restored shortly after the electrical failure. The flight attendants advised the captain that there was smoke in the aft part of the cabin area. The captain and first officer "smelled an electrical burning smell", and declared an emergency. The captain returned to the airport and made an emergency landing, and evacuated the airplane on runway 9R. Examination of the Power Conversion Distribution Unit revealed that the tantalum capacitor and the permanent magnet generator input transformer failed. The failed transformer was the apparent source of the smoke in the cabin. No other anomalies were reported by the captain.
Probable cause
The failure of the tantalum capacitor and the permanent magnet generator input transformer which resulted in total electrical system failure.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL04IA085
- Event ID
- 20040323X00357
- Case number
- ATL04IA085
- 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: investigation status, 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: c5ec669f7b7491e4d25f1814cd871cc597850d1c7b68ca71b27be55bb18345a5; retrieved 2026-09-18T15:29:26.806Z.