Delta Air Lines McDonnell Douglas MD-88 incident
McDonnell Douglas MD-88 · Incident: airframe, component or system failure en route
From Hartsfield Jackson Atlanta International Airport (ATL) to Montgomery Regional (Dannelly Field) Airport (MGM)
Event
- NTSB case
- ATL92IA025
- 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
- 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
McDonnell Douglas MD-88
- Aircraft type
- McDonnell Douglas MD-88
- 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
- N908DL
- Operator
- Delta Air Lines
- Onboard fatalities
- Unknown
- Route
- From Hartsfield Jackson Atlanta International Airport (ATL), Atlanta, GATo Montgomery Regional (Dannelly Field) Airport (MGM), Montgomery, AL
- 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
- 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, electric wiring › Shorted
- Electrical system, electric wiring › Undetermined
Approximate · Estimated position: the centre of Atlanta, GA, the place the record names. Not the accident site.
NTSB narrative
SHORTLY AFTER LIFTOFF A PASSENGER IN ROW 18 REPORTED OBSERVING FLAMES COMING FROM THE OVERHEAD AREA ON THE RIGHT SIDE OF THE AIRPLANE. THE FLIGHT ATTENDANT SUPPRESSED THE REPORTED AREA WITH A HALON FIRE EXTINGUISHER AND REPORTED THE INCIDENT TO THE FLIGHT DECK. HOWEVER, THE FLIGHT ATTENDANT DID NOT REPORT SEEING FLAMES. AN EMERGENCY LANDING WAS MADE AT THE DEPARTURE AIRPORT WITHOUT FURTHER INCIDENT. EXAMINATION OF THE OVERHEAD AREA AROUND ROW 18 REVEALED THAT THE CANNON PLUG CONNECTOR ADJACENT TO THE LIGHT ASSEMBLY HAD SHORTED. SUBSEQUENT EXAMINATIONS OF THE CONNECTOR REVEALED THAT PINS IN THE MATING HALVES OF THE CONNECTOR WERE DAMAGED, AND APPEARED TO HAVE OCCURED WHEN A PREVIOUS CONNECTION WAS ATTEMPTED. RESEARCH EFFORTS TO DUPLICATE THE CONNECTOR FAILURE MODE FAILED. A REVIEW OF THE OPERATORS MAINTENANCE RECORDS FAILED TO DISCLOSE IF ANY MAINTANANCE HAD BEEN CONDUCTED IN THE AREA OF THE CONNECTOR. HOWEVER, THE OPERATOR COULD NOT VERIFY THAT THE CONNECTOR AND AFFECTED AREAS WERE NEVER SERVICED DURING A PREVIOUS STOPOVER
Probable cause
A SHORT IN AN ELECTRICAL CONNECTOR WHICH RESULTED IN ITS FAILURE. THE REASON FOR THE SHORT WAS NOT DETERMINED. A FACTOR WAS THE IMPROPER INSTALLATION OF THE CONNECTOR BY AN UNKNOWN MAINTENANCE PERSON.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL92IA025
- Event ID
- 20001212X18411
- Case number
- ATL92IA025
- 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: 43190d81d6e255043b50fd59477eedc3ab4cad6577a3083e62c8ab013138e183; retrieved 2026-09-18T18:50:26.633Z.