The U.S. aircraft register, updated daily
Accidents · NTSB ENG22LA049 · Final report

Bombardier Global 7500 incident near Riyadh, SA, March 31, 2022

On March 31, 2022 at about 7:05 pm local time, a 2021 Bombardier Global 7500, registered N9HVIG, suffered minor damage in an incident during initial climb near Riyadh. It was a personal flight under non-U.S. commercial rules. The NTSB record does not give the injuries. The weather was conditions the NTSB did not record.

The NTSB's probable cause their words, unchanged

An in-flight engine fire resulted from a fuel leak from fuel nozzle No. 18 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.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
March 31, 2022 · about 7:05 pm local time
Place
Riyadh, Saudi Arabia · map
Type
Incident
Injuries
The NTSB record does not give the injuries.
Weather
conditions the NTSB did not record
Aircraft
Bombardier Global 7500, built 2021
Registration
N9HVIG · no longer on the register · serial 70086
Damage
Minor damage
Flight
Personal flight · non-U.S. commercial rules

The NTSB's narrative final · quoted from the NTSB record

Post-event inspection of a GE Aviation Passport 20-19BB1A turbofan engine found light sooting aft of the fuel nozzles, along with minor thermal damage to an air duct thermal sleeve consistent with an undercowl engine fire. This corroborates the pilot’s report of an in-flight engine fire during takeoff climb and during the throttle increases to troubleshoot the fire warning. The engine was removed and sent to GE for evaluation and a fuel system leak check was performed but the source/location of the fuel leak could not be identified. At several fuel nozzle locations, Nos. 12, 14, 16 and 18, the fuel nozzle pigtail-to-fuel manifold b-nut connections were shiny, lacked sooting, and were thought to be possible leak locations. 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 were determined to be insufficient to replicate the fuel leak. A torque check of all the fuel manifold b-nut connections found five 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. Two of the five - Nos. 16 and 18 - were identified as possible leak sources during the initial examination. Detailed analysis of the fuel nozzle No. 18 pigtail-to-fuel manifold b-nut connection revealed evidence of fuel manifold outer diameter surface galling and elliptical and intermediate contact marks indicative of misalignment contact with the fuel manifold female ferrule sealing surface and signs of contaminants and imbedded material (hard particles) on the fuel nozzle male bullnose sealing surface; no other b-nut connection location exhibited this type of surface distress. The source of the hard particle damage could not be positively identified but the observed diagonally orientated abrasive material marks/material removal was consistent with what appears to be a previous repair; there is no record of a repair operation being performed on this specific nozzle. 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 fuel manifold b-nut torque, misalignment between fuel nozzle No. 18 pigtail-to-fuel manifold b-nut connection and sealing surface distress created the conditions, 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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Fire/smoke (non-impact) during initial climb defining event
  2. Engine shutdown during initial climb
  3. Loss of engine power (partial) during initial climb

The NTSB's findings

  • Aircraft › Aircraft power plant › Engine fuel and control › Fuel distribution › Design
  • Personnel issues › Task performance › Maintenance › Installation › Maintenance personnel

The aircraft

  • Landing gear: retractable
  • Engine 1: General Electric Passport 20-1 (turbofan); 0 hours total
  • Engine 2: General Electric Passport 20-1 (turbofan); 0 hours total
  • Operator: Vistajet Ltd

The flight

  • Departed from: OERK Riyadh OF
  • Destination: OMDB Dubai OF
  • A second pilot was aboard

Weather at the time

  • Light: not reported
  • Temperature: 0°F (-18°C), dew point 0°F (-18°C)

Documents from the investigation the NTSB's docket: the evidence folder behind the report

2 documents, released by the NTSB on June 13, 2023. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.