FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN17LA333 · Gulfstream American Corp AA 5B B

28 Aug 2017 · Carbondale, IL, United States

Gulfstream American Corp AA 5B B · Accident: part(s) separation from aircraft en route

From Bowman Field (LOU) to Wiley Post Airport (PWA)

Report a problem

Event

NTSB case
CEN17LA333
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
Accident
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

Gulfstream American Corp AA 5B B

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
N28005
Operator
Unknown
Onboard fatalities
Unknown
Route
From Bowman Field (LOU), Louisville, KYTo Wiley Post Airport (PWA), Oklahoma City, OK
Aircraft age
About 39 years (built 1978)
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
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
Part(s) separation from aircraft
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft propeller/rotor
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The private pilot reported that, about 1 1/2 hours after departure and in cruise flight about 6,700 ft mean sea level, he felt a "jolt" as if the airplane had impacted an object. The pilot realized that the propeller was missing, initiated an emergency descent, and attempted to land at a nearby airport. Unable to glide to the airport, he decided to perform a forced landing to a field. During the forced landing, the airplane impacted trees and terrain and came to rest upright. Propeller sections and components were located about 9 miles from the accident site.

Material examination of the propeller revealed that the propeller fractured due to fatigue that initiated adjacent to two of the propeller attachment bolt holes. Fretting contact damage was observed at the primary fatigue initiation location. The contact damage appeared to be associated with the movement between the forward bulkhead and the propeller at the edges of the attachment bolt clamping locations, and some of the fretting contact damage likely preceded crack initiation in the propeller. Fatigue cracks were present in the forward bulkhead outboard of each of the propeller attachment holes. The symmetric nature of the cracks at all 6 holes and the locations of fatigue initiation at the forward and aft sides of the bulkhead suggest that the fatigue in the forward bulkhead could be associated with a rotational torque vibration in the spinner. Possible sources for high rotational torque vibration include looseness in the spinner attachment at the aft bulkhead or an engine issue that produced excessive rotational impulses.

Excessive clamping force from the attachment bolts may have also contributed to the initiation of fatigue cracks in the forward bulkhead. Excessive clamping force could have warped the forward bulkhead adjacent to the clamped area, leading to higher stresses in areas around the attachment holes where fatigue cracking was observed. The analysis of deposits from the threaded area within the crankshaft lug pieces suggested lubricant may have been present on the attachment bolt threads that should have been installed dry. The use of lubricant at installation would have reduced the frictional resistance to the applied torque, leading to higher than expected clamping force on the attachment bolts.

Crack arrest marks that appeared to coincide with flight cycles were observed on the fracture surface. One of the crack arrest marks would have a very high probability of detection by fluorescent penetrant inspection (FPI); however, the presence of red deposits in the attachment holes and dowel holes suggest that red dye (visible) penetrant was used at some time on the propeller. The manufacturer recommends against using visible dye penetrant and indicates that the use of visible dye penetrant could prevent crack detection during subsequent FPI inspections.

Probable cause

The failure of the propeller due to fatigue as a result of improper installation by unknown maintenance personnel at some point during the life of the propeller.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN17LA333
Event ID
20170830X83648
Case number
CEN17LA333
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: 08f5b4e68381b7765d3cb24ccee732afac1dc3042b2d59ad4cc4f0c72b5a72a0; retrieved 2026-09-16T05:46:52.493Z.