Flight 12 · McDonnell Douglas MD-11
McDonnell Douglas MD-11 · Accident: airframe, component or system failure en route
From Hartsfield Jackson Atlanta International Airport (KATL) to ELGW · London
Event
- NTSB case
- MIA02FA075
- 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
McDonnell Douglas MD-11
- Aircraft type
- McDonnell Douglas MD-11
- 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
- N809DE
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Hartsfield Jackson Atlanta International Airport (KATL), Atlanta, GATo ELGW · London
- 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
- 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
- Minor
Cause areas
- Company maintenance personnel › Maintenance, service bulletin/letter, not performed
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The captain stated he was the pilot flying and the takeoff and climb to the cruise altitude of 33,000 feet was conducted within normal parameters. After level off the relief pilot left the cockpit to begin his rest period. Within a few minutes he observed that the number 2 engine master warning light was illuminated, as well as a level 3 alert on the Engine and Alert Display and a red light on the number 2 fire handle and fuel shutoff lever. The fire bell did not activate. He and the first officer performed the memory and initial action items on the hard card checklists for an engine fire and shutdown the No. 2 engine. In addition, the captain discharged an engine fire bottle. The engine fire light continued to illuminate. The captain then fired a second engine fire bottle. The engine fire light continued to be illuminated. The captain requested that the relief pilot return to the cockpit. He then contacted Air Traffic Control (ATC) and told them that their No. 2 engine was on fire and that they intended to land at the nearest suitable field. ATC responded that Charlotte was 35 miles away with a 10,000 foot runway. He asked for radar vectors and an immediate descent into Charlotte. They were given a lower altitude. The first officer initiated fuel dumping. The relief pilot returned to the cockpit and he asked the relief pilot and the first officer to run the checklists. As they descended the aircraft encountered heavy rain, light hail, and moderate turbulence. In addition, they observed a bright flash to the left of the nose, which might have been a lightning strike. As they completed the descent and approach checklists he told the crew to expect an emergency evacuation upon landing and directed the first officer to so inform the flight attendants. The aircraft was configured for an engine out approach and they reviewed the loss of a second engine procedure. The remainder of the approach, touchdown and landing roll occurred within normal parameters. He brought the airplane to a stop on the runway. The engine fire indication remained illuminated. The relief pilot stated they did not terminate fuel dumping prior to landing. They completed the items on the evacuation checklist. He then ordered an evacuation of the airplane. According to Delta Air Lines representatives, examination of the No. 2 engine by company maintenance personnel found one fire loop chafed through an adjacent cable, an integrated drive generator (IDG) feeder cable, inside the No. 2 engine cowling This allowed a direct 115 volt AC connection between the IDG and the fire detection control unit. The result was an electrical short and complete failure of the detection control unit that was indicated in the cockpit as a fire warning. There was no evidence of fire in the No. 2 engine. Boeing Service Bullettin MD11-71-086 was issued on May 21, 1996. The subject of the service bulletin was "Power Plant - Electrical Harness - Replace/Modify Integrated Drive Generator (IDG) Wire Harness Support Brackets". On May 21, 2001, Boeing elevated the service bulletin to the "Alert" level. Boeing recommended that aircraft operators accomplish the service bulletin within 1 year. According to Delta Air Lines personnel, in November 2001, Delta Air Lines Aircraft Engineering issued a Engineering Order to comply with Alert Service Bulletin MD11-71A086. The Engineering Order stated that all engines should be inspected and modified by November 2002. All three engines on the accident aircraft were inspected and modified in accordance with the Engineering Order on March 3, 2002. On March 28, 2002, the No. 2 engine was changed and the engine installed had not been modified by the Engineering Order.The Delta Airlines descent, approach, and before landing checklists dated June 30, 2000, and which were in use at the time of the accident, required the pilots to check the Engine and Alert Display. When fuel dumping is activated, a message is displayed on the Engine and Alert Display.
Probable cause
The failure of the aircraft operator to comply with, in a timely manner, on the No. 2 engine, Boeing Alert Service Bulletin MD11-71A086, resulting in the integrated drive generator feeder cable chaffing through a fire warning loop and failure of the fire warning system due to electrical damage. This resulted in a continuous indication in the cockpit of a No. 2 engine fire, an emergency descent and landing, and injuries to passengers during the subsequent emergency evacuation of the airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA02FA075
- Event ID
- 20020402X00443
- Case number
- MIA02FA075
- 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. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2002-04-01.
- API snapshot SHA-256: fa5dbaf69fc8302597b38774f6b824e3d69a2b988c7b1053abd6cfce851a6912; retrieved 2026-09-18T16:04:06.943Z.