Mirasol Sky Bombardier Inc BD-700-2A12 incident
Bombardier Inc BD-700-2A12 · Incident: fire/smoke (non-impact) during initial climb
From PBI · West Palm Beach, FL to Teterboro Airport (TEB)
Event
- NTSB case
- ENG22LA020
- 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
- Event fatalities
- Unknown
- 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
- Charter & commuter
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Unknown
Bombardier Inc BD-700-2A12
- Aircraft type
- Bombardier BD-700
- 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
- N63RP
- Operator
- Mirasol Sky
- Onboard fatalities
- Unknown
- Route
- From PBI · West Palm Beach, FLTo Teterboro Airport (TEB), Teterboro Airport, NJ
- Aircraft age
- About 1 year (built 2021)
- 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 135: Air Taxi & Commuter
- 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
- Initial climb
- 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
- Fire/smoke (non-impact)
- 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
- Aircraft › Aircraft power plant
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
Post-event inspection of a GE Aviation Passport 20-19BB1A turbofan engine found light thermal distress on the outside of the engine core compartment near the top of the engine from the 10:00 to 11:00 o’clock position, aft looking forward, and localized discoloration on the inside of the core cowls in the general location of fuel nozzle No. 16 location consistent with an undercowl engine fire. This corroborates the pilot’s report of an in-flight engine fire during takeoff climb. The fuel nozzle No. 16 location appeared shiny, lacked the sooting that neighboring fuel nozzle pigtail-to-fuel manifold b-nut connections exhibited; therefore, it was considered a possible fuel leak location. The engine was removed and sent to GE for evaluation; a fuel system leak check was performed but the source/location of the fuel leak could not be identified. The fuel pressure and nitrogen check pressure used during the leak tests were well below the fuel pressure the engine experienced during the event and was determined to be insufficient to replicate the leak.
A torque check of all the fuel manifold b-nut connections found four locations, all located on the left fuel manifold, which had very low torque values, less than 200 inch-pounds, when compared to the other b-nut connection locations and the required installation torque of 285 inch-pounds nominal. One of the four low torque locations was fuel nozzle No. 16 that was identified as a possible leak source during the initial examination. Detailed analysis of the fuel nozzle No. 16 pigtail-to-fuel manifold b-nut connection revealed evidence of galling and intermediate contact marks consistent with and indicative of misalignment and relative movement within the connection; none of the other low torque b-nut connection locations exhibited this type of surface distress.
Since the post-event fuel system leak checks performed by GE could not induce a fuel leak, the exact location/source of the fuel leak could not be determined by testing and observations. However, the combination of low torque, misalignment between fuel nozzle No. 16 pigtail-to-fuel manifold b-nut connection, and sealing surface distress created the conditions by which there was insufficient sealing allowing fuel to leak during high engine power and high fuel pressures. No other fuel nozzle locations had this combination of factors that would have allowed a fuel leak.
Probable cause
An in-flight engine fire resulted from a fuel leak from fuel nozzle No. 16 pigtail-to-fuel manifold b-nut connection that contacted hot engine parts and ignited. Contributing to the manifold fuel leak was the misalignment between fuel manifold female ferrule and fuel nozzle male bullnose sealing surfaces coupled with distress of the ferrule sealing surface.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ENG22LA020
- Event ID
- 20220413104937
- Case number
- ENG22LA020
- 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, coordinates, cause areas, 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: 4d3ec082659097c782deb508c36023e1abd5c48b26d30c9bb005538449cd9583; retrieved 2026-09-16T15:07:47.338Z.