FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL01LA043 · Globe GC1B

1 Apr 2001 · CHERRY POINT, NC, United States

Globe GC1B · Accident: airframe, component or system failure while maneuvering

From Cherry Point MCAS / Cunningham Field/ (NKT) to CHERRY POINT, NC

Report a problem

Event

NTSB case
ATL01LA043
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

Globe GC1B

Aircraft type
Globe GC1
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
N78321
Operator
Unknown
Onboard fatalities
Unknown
Route
From Cherry Point MCAS / Cunningham Field/ (NKT), CHERRY POINT, NCTo CHERRY POINT, NC
Aircraft age
Not recorded
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
Maneuvering
First occurrenceThe 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
Airframe, component or system failure
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

  • Propeller system/accessories, hub › Fatigue
  • Propeller system/accessories, hub › Fractured

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

A Globe GC1B lost a propeller blade in-flight while maneuvering in the number two position of a formation of three airplanes, a propeller blade separated from the propeller hub assembly. The second propeller blade, along with the hub assembly, subsequently separated from the engine crankshaft. Examination of the recovered propeller hub fracture faces disclosed fatigue cracking. The fatigue fracture propagated until it intersected the outside hub surface. According to McCauley Propeller the fatigue fracture reduced the propeller hub load carrying capacity until it was no longer a sufficient cross section to carry the centrifugal load of the propeller.

Probable cause

Fatigue cracking of the propeller hub that resulted in the in-flight separation of a propeller blade.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL01LA043
Event ID
20010405X00695
Case number
ATL01LA043
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: 91bca4eea76477cf7689eb761ce6bacfe67f8b4817f1333e144311617e651161; retrieved 2026-09-22T12:03:54.629Z.