FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI03IA066 · Bombardier BD 100-1A10

4 Feb 2003 · Wichita, KS, United States

Bombardier BD 100-1A10 · Incident: fire en route

From Wichita Dwight D. Eisenhower National Airport (ICT) to Wichita Dwight D. Eisenhower National Airport (ICT)

Report a problem

Event

NTSB case
CHI03IA066
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
General aviation
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

Bombardier BD 100-1A10

Aircraft type
Bombardier BD-100
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
C-GJCV
Operator
Unknown
Onboard fatalities
Unknown
Route
From Wichita Dwight D. Eisenhower National Airport (ICT), Wichita, KSTo Wichita Dwight D. Eisenhower National Airport (ICT)
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 91: General Aviation
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
Fire
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 › Inadequate
  • Electrical system, inverter › Fire

Approximate · Estimated position: the centre of Wichita, KS, the place the record names. Not the accident site.

NTSB narrative

The experimental airplane returned from a test flight with evidence of an in-flight inverter fire discovered during a post flight inspection. The test flight was part of a new airplane certification test program and was to evaluate the airplane's audio design/flight deck audio system. The flight crew did not receive any fire warning indications in-flight and neither they or the test crew members noted any smoke or odors associated with burning during the flight. The inverter was located in the aft equipment bay, aft of the rear pressure bulkhead. The area within which the inverter was located was equipped with fire detection and an airplane circuit breaker for the system. The airplane circuit breaker for the inverter was not tripped. Subsequent testing demonstrated that the circuit breaker operated within specification limits.

Inspection of the airplane revealed the presence of hydraulic fluid below and in the inverter tray. Examination of the inverter and fluid susceptibility testing confirmed the presence of Skydrol hydraulic fluid within the inverter. The inverter manufacturer reported that Skydrol intrusion, internal power circuit high voltages, operation at altitude, and drastic changes in temperature may have contributed to material degradation or deterioration or even possible dielectic breakdown, which resulted in the failure mode observed. Following this incident, the manufacturer reported that the inverter design was tested and confirmed that it met the fluid susceptibility requirements of DO-160C for Skydrol. A second examination of the inverter, performed by the United States Air Force Research Laboratory, was documented in a laboratory evaluation report. The failure analysis section of this report states that no root cause of failure could be found and noted that the majority of the thermal damage to the inverter was attributed to Joule heating from a sustained current overload. The examination also revealed the existence of numerous manufacturing deficiencies that would be classified as defects per Joint Industry Standard requirements for soldered electrical and electronic assemblies. The majority of these defects violated cleanliness, conformal coating, and soldering. The inverter manufacturer's FAA approved manufacturing requirements differ from those noted by the Air Force Research Laboratory and are based on its own internal design standards and practices as well as in-house workmanship standards derived from good industry practice and requirements contained in IPC-A-610C, "Acceptability of Electronic Assemblies".

The inverter was part of a cabin outlet system considered non-essential under 14 CFR Part 25, Subpart F. Information contained in Advisory circular 25-10 regarding guidance for installation of miscellaneous, non-required equipment states. that circuit protective devices should be provided such that a fault in the nonrequired system does not cause a failure of a required system. Supplementing this guidance, AC 25-16, "Electrical Fault and Fire Prevention and Protection," states that in cases where internally faulted components will not cause automatic disconnection of their circuit protective devices before causing excess temperatures potentially resulting in fire, these electrical equipment should be provided with adequate backup protection (beyond the aircraft circuit breakers). In addition, the AC states that each installation of an electrical device should be assessed for its potential to generate fire or smoke under failure conditions. The inverter specified for this installation was a TSO-C73 certified article. The applicable TSO addresses short circuit and overload conditions to the extent that inverters continue producing power through these conditions, but it does not require circuit protection when these conditions are encountered. A design analysis of the inverter as installed in the cabin outlet system to consider failure conditions and corresponding hazards such as fire/smoke generation, in accordance with the related provisions of 14 CFR Part 25.1309, had not been performed by the aircraft manufacturer prior to this incident. As a result, additional requirements to address internal inverter circuit protection for this installation were not mandated by the aircraft manufacturer. Subsequent to this incident, a design analysis was performed by the airplane manufacturer. Correspondingly, the inverter manufacturer modified the inverter design to incorporate fuses on the power input lines to interrupt electrical power in the event a short circuit or overload failure condition develops inside the inverter.

Probable cause

The uninterrupted current overload of the cabin outlet system static inverter leading to ignition and sustained fire. The cause of the initiating overload condition could not be determined. Contributing factors were the lack of adequate current overload protection for the static inverter due to a failure to adequately assess fire/smoke hazards of the inverter in this installation and the absence of timely fire annunciation to the flight crew.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI03IA066
Event ID
20030212X00205
Case number
CHI03IA066
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, damage. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2003-02-05.
  • API snapshot SHA-256: b27799fca06f2835737d764e58657476134fb2abb75abcb495612bcad28aaf9f; retrieved 2026-09-22T09:37:08.255Z.