Emery Worldwide Airlines Flight 102
McDonnell Douglas DC-8-71F · Incident: airframe, component or system failure on approach
From James M. Cox Dayton International Airport (DAY) to Seattle–Tacoma International Airport (SEA)
Event
- NTSB case
- SEA01IA039
- 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
- Instrument Meteorological Cond
McDonnell Douglas DC-8-71F
- Aircraft type
- McDonnell Douglas DC-8
- 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
- N8084U
- Operator
- Emery Worldwide Airlines
- Onboard fatalities
- Unknown
- Route
- From James M. Cox Dayton International Airport (DAY), Dayton, OHTo Seattle–Tacoma International Airport (SEA), 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
- Approach · IFR final approach
- 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
- Comm/nav equipment, flight management computer(fmc) › Malfunction
- Flight/nav instruments, course indicator › False indication
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
On a coupled instrument landing system (ILS) approach to runway 16R at Seattle-Tacoma International Airport, the aircraft deviated approximately 0.4 nautical mile east of the final approach course. During missed approach, the aircraft flew east of parallel runway 16L and in proximity to an approximately 290-foot-high air traffic control (ATC) tower under construction on the airport. The crew subsequently made a second approach and landing attempt without further incident. The flight crew reported that the incident approach was flown with the autopilot coupled to the #1 NAV, and that all instruments indicated on course and on glide slope during final approach. The crew reported that at decision height, they initiated a missed approach when they did not observe the proper visual cues, and that the tower subsequently informed them that they were left of course. On the second (successful) approach attempt, the first officer hand-flew the approach using the #2 NAV. Visibility at the time was reported as 1/4 statute mile with freezing fog, with a vertical visibility of 100 feet. A post-incident flight inspection of the localizer and glide slope did not disclose any problems with the ILS signal. During post-incident troubleshooting of the aircraft's course deviation circuitry, maintenance personnel discovered a defective relay in the switching matrix for the aircraft's flight management system (FMS), which was installed under an FAA Supplemental Type Certificate. Whenever the area around the FMS switching matrix or the defective relay itself was physically tapped, the captain's course deviation indicator (CDI) was observed to jump. When a replacement relay was installed, this anomaly was not observed. Inflight system testing also disclosed that the autopilot was erratic in pitch, with porpoising about the glide slope. Maintenance personnel subsequently discovered an anomaly during the autopilot pitch computer self test, which was resolved by replacing the fore and aft pitch accelerometers. Maintenance personnel further discovered that by replacing the BNC connectors at NAV 1 and NAV 2, significant improvements in system efficiency were attained. No anomalies with the first officer's CDI indications, or false "on glide slope" indications, were found during any post-incident troubleshooting.
Probable cause
A malfunctioning relay in the aircraft's flight management system (FMS) switching matrix and associated false "on course" indication on the captain's course deviation indicator (CDI), resulting in proper localizer course alignment not being obtained or maintained and subsequent flight in close proximity to the new control tower. The reason for the reported false "on course" indications on the first officer's CDI was not determined. Factors contributing to the incident included low ceiling and obscuration, weak signal received by both localizer receivers due to faulty BNC connectors, and the new control tower.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA01IA039
- Event ID
- 20010207X00412
- Case number
- SEA01IA039
- 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: db9ef6b22b88955ea069c0b8be8ea9469f9ebddacbe35936eb6780f0707e43b9; retrieved 2026-09-18T16:17:31.145Z.