NTSB CAROL · Event
Event CHI97IA072
Registry · N93S
FAA Aircraft Registry record.
Make / Model
CESSNA 750
Year of manufacture
2002
Engine
ALLISON AE3007C SER
Seats / Engines
12 seats · 2 engines
Last airworthiness date
20020621
ADS-B equipped
Yes — Mode-S ACE4E0
Registrant of record
TEN THREE LLC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
the cross tie relay shorted resulting in a fire in the left main electrical equipment rack.
Factual narrative
On February 20, 1997, at 0645 central standard time, a McDonnell Douglas DC-9-15, N93S, operated as Northwest Airlines Flight 219, from Minneapolis, Minnesota, to Kansas City, Missouri, experienced an electrical fire during cruise. None of the four crewmembers nor the 32 passengers were injured. The airplane sustained minor damage. The 14 CFR Part 121 flight diverted to the Des Moines International Airport, Des Moines, Iowa, without further incident. The flight had departed from Minneapolis, Minnesota, at 0556. Visual meteorological conditions prevailed and an IFR flight plan was filed. The pilot reported that takeoff and climb were "normal." The flight crew leveled the airplane at flight level 310. They noted the "instrument lights flicker twice followed by a loud pop. The first officer noticed flames coming from the jumpseat area just above the locking device. Smoke and fumes filled the cockpit." The crew donned their oxygen masks and turned off both generators and the battery switch. "The flames went out and the smoke did not get any worse." They flew with a flashlight for one minute and then turned the emergency power switch on. A flight attendant reported that the smoke was limited to the cockpit and first class galley with only minor smoke in the main cabin. The flight crew declared an emergency and diverted to Des Moines. The smoke cleared during the descent. The flight crew flew an ILS approach with ASR backup. Fire and rescue crews met the airplane at the runway and escorted it to the gate. Passengers deplaned via the jetway. Examination of the airplane revealed soot tracks from the aft, interior side of the left main equipment rack near the left forward cabin door. The interior of the rack was soot covered. The cross tie relay, four other relays installed in the equipment bay below the cross tie relay, and associated wire bundles were charred. The most severe, black soot patterns were located near the cross tie relay. Visual examination of all charred and soot covered wire bundles revealed no evidence of chaffing, heat concentration, or prefire insulation failures. The cross tie relay, fuse links, generator controllers, and four charred relays were retained for subsequent examination and the airplane was released to Northwest Airlines. Retained components were examined on February 26, 1997 at the Northwest Airlines maintenance facilities, Minneapolis, Minnesota. Both generator controls functioned normally during a standard bench test. Examination of the other four relays revealed superficial exterior charring. The fuse links on the cross tie relay were charred and melted. The left A phase and the right C phase links measured continuity with an ohm meter. The other four links were melted and open. The cross tie relay, part number 914F567-4 exhibited severe charring and burning around the arc box assembly. Both coils measured open with an ohm meter. The arc box contained charred debris and a silver track was melted between all three phases on the right side of the relay contactor. The inter-phase barriers were fragmented. The viton seals were installed. The relay was latched in the closed position. Northwest Airlines' records indicated the relay had 35,160 hours total time and 7,775 hours since overhaul. Northwest Airlines' allowable time between overhaul (TBO) is 14,000 hours for the relay installed in a vertical or horizontal orientation, based on an OPSPEC Reconciliation from December 2, 1981 after a merger. Westinghouse service bulletin 75-703 revised June 1977 suggests a 14,000 hour TBO for the relay when it is mounted in a vertical orientation as a generator, auxiliary power, or external power relay and a 7,000 hour TBO when it is mounted in a horizontal orientation as a cross tie relay. The service bulletin states "the cross tie relays must be cleaned and overhauled at 7,000 hours maximum." In addition, the service bulletin specifies the addition of viton seals on the inter-phase barriers "for the purpose of preventing migration of the metallic dust through the barriers, thereby establishing a low dielectric path between the phases." McDonnell Douglas All Operator Letter AOL 9-1120B specifies a recommended TBO of 7,000 hours for relay. The letter does not specify vertical or horizontal orientation. Examination of the relay overhaul/component maintenance manual revealed no specification for inspection of the arc box during overhaul. Parties to the investigation were the Federal Aviation Administration, Northwest Airlines, Air Line Pilots Association, Douglas Aircraft Company, and Sundstrand Aerospace. There was an electrical fire during cruise flight at FL310. The flight crew extinguished the flames by turning off both generators and the battery switch. The flight diverted to Des Moines, Iowa, where it landed without further incident. Inspection of the airplane revealed the cross tie relay along with four other relays and their associated wiring in the left main equipment rack near the left forward cabin door were charred. Investigation revealed the fire was a result of a phase-to-phase short in the cross tie relay arc box. The short resulted from relay contact wear products (metal dust) migrating through the arc box. The relay manufacturer recommended a 7,000 hour time between overhaul (TBO) for this relay when it is used as a cross tie relay. The aircraft manufacturer recommended a 7,000 hour TBO regardless of how the relay is used. The operator used a 14,000 hour TBO, based on an FAA approved TBO reliability program for the relay installed in a vertical or horizontal orientation. The failed relay had a total of 7,775.26 hours since overhaul. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1997_CHI97IA072.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (stall, maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2023 · Conference paper
The Value of Strong Partnerships to Build a Successful Aviation Maintenance Career Pathway Program for Transitioning Military Service Members
The aerospace industry is competing with other industries for a qualified workforce, and many of those competing industries are investing heavily in creating workforce development pipelines.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- NASA NTRS 2026 · Conference Paper
Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
- Semantic Scholar 2025 · Article (Applied Sciences)
Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
Low-Resource Automatic Speech Recognition Domain Adaptation – A Case-Study in Aviation Maintenance
With timeliness and efficiency being critical in the aviation maintenance industry, the need has been growing for smart technological solutions that optimize and streamline the different underlying ta…
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
A New Trajectory in UAV Safety: Leveraging Reinforcement Learning for Distance Maintenance Under Wind Variations
In the field of aviation, safety is a critical cornerstone, and the operation of Unmanned Aerial Vehicle (UAV) systems is deeply connected with this principle.
Browse the full corpus — academia portal ↗