FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

World Airways Flight 8278

28 Apr 2005 · Anchorage, AK, United States

McDonnell Douglas MD-11 · Incident: airframe, component or system failure en route

From Osan Air Base to Seattle–Tacoma International Airport (KSEA)

Report a problem

Event

NTSB case
ANC05IA064
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

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
N277WA
Onboard fatalities
Unknown
Route
From Osan Air BaseTo Seattle–Tacoma International Airport (KSEA), Seattle, WA
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, installation, inadequate

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

NTSB narrative

The flight crew was conducting an international passenger flight under Title 14, CFR Part 121, when they smelled and saw smoke in the cockpit. The pilot declared an emergency, and diverted to the nearest airport, where the airplane landed without incident. According to the flight crew, just prior to the smell and smoke, there was a crew change that required the cockpit security door to be opened and closed. An examination of the security door by maintenance personnel and the National Transportation Safety Board (NTSB) investigator-in-charge (IIC) revealed an excess length of wiring, which provides power to the electrically locking security door, was laying atop the door's metal-encased, unshielded, locking solenoid inside the doorframe. Several of the wires were encased in a plastic anti-chafe mesh. A portion of the mesh was melted, and had the smell of burnt plastic. During a discussion with the IIC, a mechanic said he had seen similar doors overheat when the door and frame were misaligned, prohibiting full extension of the locking bolt. The cockpit door was modified in accordance with Supplemental Type Certificate (STC) ST01391LA, which meets the FAA's requirements for a reinforced cockpit door. The door uses a "demand access" electrically operated door latching solenoid. The door manufacturer issued an addendum to the airplane manufacturer's maintenance manual. The addendum includes removal, installation, and system tests of the striker/solenoid unit. The installation section does not specifically address the issue of securing excess wiring located above the striker/solenoid within the doorframe. The installation instructions do contain a "caution," referencing the need for the security bolt to engage fully. Failure of the bolt to fully engage will cause the solenoid to remain energized and overheat. Construction of the striker/solenoid assembly is such that the metal-encased electrical coil of the unshielded solenoid is the upper-most portion of the assembly within the doorframe. The installation includes a warning light that illuminates if the solenoid does not shut off. The crew did not report seeing the warning light in-flight, and the light and locking mechanism functioned properly during subsequent tests on the ground; it was not tested in-flight. The conversion of the door was completed on March 21, 2003. Prior to the incident, the new security door had been in service about 16,416 flight hours, and 1170 cycles. FAA Advisory Circular (AC) 65-15A, Chapter 11, covers practices and procedures for the installation and maintenance of aircraft electrical wiring. The AC notes that practices and procedures outlined in this section are general recommendations, and are not intended to replace the manufacturer's instructions. Chapter 11, page 441, Slack in Wiring Bundles, states: "Single wires or wire bundles should not be installed with excessive slack." Page 442, Routing and Installations, states: "All wires and wire groups should be routed and installed to protect them from: (2) high temperatures."

Probable cause

The inadequate installation of the cockpit security door locking device, which resulted in smoke in the cockpit during normal cruise, and a precautionary landing. A factor associated with the incident was the manufacturer's insufficiently defined installation instructions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC05IA064
Event ID
20050518X00630
Case number
ANC05IA064
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, coordinates. 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: 5bc45d48ed6c757fa244834d059b86eea0b4f5eb3c86cfc28e56e4e5e45195c1; retrieved 2026-09-18T15:03:04.973Z.