ERA15IA198 · Dassault-Breguet MYSTERE FALCON 900
RLB Holdings Transportation Dassault-Breguet MYSTERE FALCON 900 · Incident: electrical system malfunction/failure en route
From Westchester County Airport (HPN) to Orlando International Airport (MCO)
Event
- NTSB case
- ERA15IA198
- 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
Dassault-Breguet MYSTERE FALCON 900
- Aircraft type
- Dassault Breguet MYSTERE FALCON 900
- 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
- N610RL
- Operator
- RLB Holdings Transportation
- Onboard fatalities
- Unknown
- Route
- From Westchester County Airport (HPN), White Plains, NYTo Orlando International Airport (MCO), Orlando, FL
- Aircraft age
- About 27 years (built 1988)
- 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 · descent
- Defining eventThe 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
- Electrical system malfunction/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
- Aircraft › Aircraft systems
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During the airplane’s descent to its destination airport, the cabin attendant noticed a “weird smell” in the galley area; she checked the appliances but could find nothing wrong with them. She then turned around and opened the area in the galley where they kept the crystal glasses and noticed a “glow behind it,” which was an electrical fire. The pilot extinguished the fire using two halon fire extinguishers, and the airplane incurred minor damage.
Examination of the area behind the crystal storage area revealed sooting, a burnt wiring bundle containing the 28-volt direct current wiring and ground wires for the cabin lighting, and a tripped circuit breaker for the cabin lighting. Two of the insulation bags in the area of the burnt wiring bundle had been fire damaged, and the wires had been routed over the insulation bags instead of directly next to the airplane's structure. The wires were also in contact with or near a soft oxygen line, which had been completely burned through. Examination of the oxygen line revealed no evidence of copper on the exposed coil; thus, the wiring had chafed against itself and not against the soft oxygen line.
During the 26 years between the completion of the airplane and the incident, numerous modifications to the lighting, interior, and galley had been made by several maintenance, repair, and overhaul organizations, which required rerouting and re-securing wiring, as well as removal and replacement of interior panels, partitions, and cabinetry near the fire. The oxygen line and wiring in the area of the fire damage had been changed from the originally specified configuration; it did not conform to the manufacturer's cabin oxygen system drawing or the manufacturer's installation standard. Further, a clamp on the oxygen line near the fire damaged area appeared to be the wrong part number clamp. A spacer and a support in this area were missing, which would have been used to achieve and maintain separation between the oxygen line and wiring.
Postincident examinations of exemplar airplanes revealed that on three of the seven airplanes, the layout of the oxygen line and electrical wiring was in compliance with manufacturer installation standards. However, on the other four airplanes, incorrect routing, spacing, or support was found, which likely occurred during maintenance.
Probable cause
Unknown maintenance personnel’s inadequate securing of a wiring bundle during a maintenance, repair, or modification event, which led to chafing of the wiring bundle, an electrical short and arcing, and a subsequent in-flight fire.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA15IA198
- Event ID
- 20150423X75710
- Case number
- ERA15IA198
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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. 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: 952954bec7f09f902519728b091799eeb6d8411e4cee10d69cfc01f1fd01f4e6; retrieved 2026-09-16T02:15:37.192Z.