Gulfstream Aerospace G-IV incident near Sioux City, Iowa, June 17, 2023
On June 17, 2023 at about 3:59 pm local time, a 1999 Gulfstream Aerospace G-IV, registered N926TT, suffered minor damage in an incident during enroute (change of cruise level) near Sioux City, Iowa. It was a flight of an unrecorded kind under charter and air-taxi rules (Part 135). No one was hurt; 9 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
A No. 2 (right) engine failure due to a spinner fairing separation and subsequent impact with the fan blades that resulted in a midspan fracture of one fan blade. The spinner fairing separated as a result of a fatigue crack that originated from the heat affected zone of a tack weld that secured a spacer to the aft side of the fairing. Contributing to the incident was inadequate spinner fairing inspection procedures that did not require removal of the spinner fairing to inspect the aft side for earlier detection of crack indications.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- June 17, 2023 · about 3:59 pm local time · cases in 2023
- Place
- Sioux City, Iowa · map
- Type
- Incident
- Injuries
- No one was hurt; 9 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Gulfstream Aerospace G-IV, built 1999 · all G-IVs on the register
- Registration
- N926TT · registry record · serial 1372
- Damage
- Minor damage
- Flight
- Flight of an unrecorded kind · charter and air-taxi rules (Part 135)
The NTSB's narrative final · quoted from the NTSB record
The No. 2 (right) engine failure was caused by a spinner fairing separation due to fatigue cracks that originated from the heat affected zone of a tack weld that secured a spacer to the aft side of the fairing. The separated fairing impacted the leading edge of the fan blades and the inner barrel of the fan case and inlet cowl and fractured one fan blade (position 7) at the midspan. The subsequent fan imbalance resulted in severe vibrations that caused an anti-ice air line b-nut connector to back off, the P3 limiter to separate from the fuel flow regulator (FFR) at the mating flange, and a fuel line fracture at the acceleration reset solenoid. The fuel line fracture at the acceleration reset solenoid resulted in a fuel leak that persisted until the airplane landed. There was no evidence of undercowl fire or thermal damage on the engine or nacelle. The flight crew reported temporary difficulty moving the No. 2 engine fuel shutoff cock (SOC) to the closed position and advancing the No. 1 (left) engine throttle from the idle position following the engine failure. The No. 2 engine fuel SOC and No. 1 engine throttle were cycled multiple times, and the associated linkages to the engine were inspected with no indications of binding, deformation, or other anomalies. Rolls-Royce and Gulfstream reviewed their system designs and did not identify an interlock or other mechanism that would have prevented normal operation during the incident flight. The operator was in compliance with the regular spinner fairing inspection interval in accordance with the aircraft maintenance manual (AMM) and the last inspection was performed in October 2022, 542.2 hours before the incident flight. The AMM procedures at the time of the inspection did not include a step to remove the spinner fairing from the nose cone to perform a 360 degree visual inspection. The origin of all Rolls-Royce Tay model spinner fairing crack findings to date has been the heat affected zone of the tack welds that secure spacers to the aft side of the fairing, and therefore, early crack detection would have only been possible if the spinner fairing was removed to inspect the aft side. It is unknown if the crack on the incident spinner fairing had grown to where it was visible on the forward side of the fairing during the October 2022 inspection. The inspection procedures were revised in October 2023 to incorporate removal of the spinner fairing in response to this incident.
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
- Powerplant sys/comp malf/fail during enroute (change of cruise level) defining event
The NTSB's findings
- Aircraft › Aircraft power plant › Engine (turbine/turboprop) › Air inlet section (core eng) › Failure other cases naming the engine
- Aircraft › Aircraft power plant › Engine (turbine/turboprop) › Compressor section › Failure other cases naming the engine
- Aircraft › Aircraft power plant › Engine (turbine/turboprop) › Air inlet section (core eng) › Fatigue/wear/corrosion other cases naming the engine
- Aircraft › Aircraft power plant › Engine fuel and control › Fuel distribution › Failure other cases naming the engine
- Aircraft › Aircraft handling/service › Maintenance/inspections › (general) › Inadequate inspection
The aircraft
- Airframe total time: 16,893.4 hours
- Last inspection: continuous airworthiness programme, June 16, 2023
- Seats: 22
- Landing gear: retractable
- Engine 1: Rolls-Royc TAY 611SER (turbofan); 16,534 hours total
- Engine 2: Rolls-Royc TAY 611SER (turbofan); 15,382 hours total
- Operator: Planet 9 Private Air, LLC
The flight
- Departed from: KPHL Philadelphia PA
- Destination: KSUS Sonoma CA
- Flight plan: IFR
- A second pilot was aboard
Weather at the time
- Light: daylight
- Wind: at 3 knots
- Visibility: 6 statute miles
- Sky: scat at 8,500 ft
- Temperature: 73°F (23°C), dew point 66°F (19°C)
- Altimeter: 29.88 inHg
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 3 | |||
| Passengers | 6 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
5 documents, released by the NTSB on July 31, 2024. 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.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Powerplants Group Chair's Factual Report | PDF, 34 pages | View Download |
| 2 | Powerplants Attachment 1- Rolls-royce Technical Report, TAY611-8 Investigation of Spinner Fairing and Fan Blades, Esn 16870 | PDF, 31 pages | View Download |
| 3 | Flight Data Recorder - Specialist's Factual Report | PDF, 15 pages | View Download |
| 4 | Flight Data Recorder - Specialist's Factual Report - Attachment 1 - Tabular Data | data file | Download |
| 5 | Cockpit Voice Recorder - Specialist's Factual Report | PDF, 6 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N926TT on the register today · the tail number may have moved to another aircraft since
- Gulfstream G-IV Gulfstream IV 357 registered today · the model family and its accident history
- Engine: Rolls-Royc TAY 611SER 260 aircraft carry this series today · as the NTSB recorded it
- Engine: Rolls-Royc TAY 611SER 260 aircraft carry this series today · as the NTSB recorded it
- Philadelphia International · departed from
- Spirit Of St. Louis Airport · bound for
- Accidents and incidents in Iowa 871 since 1982 · 131 in the last ten years
- Iowa 4,513 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/ENG23LA030.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
