FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR24FA053 · Beauchamp Norm KITFOX 5

8 Dec 2023 · Eloy, AZ, United States

Beauchamp Norm KITFOX 5 · Accident: powerplant system/component malfunction/failure during initial climb

From Eloy Municipal Airport (E60) to Ryan Field (RYN)

Report a problem

Event

NTSB case
WPR24FA053
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
1 · 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

Beauchamp Norm KITFOX 5

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
N66180
Operator
Unknown
Onboard fatalities
Unknown
Route
From Eloy Municipal Airport (E60), Eloy, AZTo Ryan Field (RYN), Tucson, AZ
Aircraft age
About 19 years (built 2004)
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
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
Powerplant system/component malfunction/failure
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft propeller/rotor
  • Organizational issues › Development
  • Organizational issues › Management
  • Personnel issues › Action/decision

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

NTSB narrative

Shortly after takeoff, during the airplane’s initial climb, a witness just below the airplane’s flight path heard the airplane “go quiet” before he saw white pieces fall from the airplane. The airplane continued to maintain a level flight attitude and he looked away. When he looked up again, he saw the airplane rapidly descending in a nose-down attitude before it struck the ground in the field across from his house and burst into flames. The airplane was not trailing smoke or vapors at any time before impact.

Postaccident examination revealed that one of the airplane’s propeller blades had released from the hub in flight but its collar detached from the root and remained within the hub. The second blade root remained in the hub and its blade had broken off at impact. Examination of that remaining blade root revealed wear and fracture features consistent with the blade sliding outboard in the hub grip as the initiating event. This outboard movement likely caused an imbalance that led to vibration, wear, and release of the opposing blade followed by airframe vibrations so extreme that the airplane became uncontrollable before it rapidly descended to the ground. The initial movement of the blade was due to insufficient retention force between the blade root and the hub. Despite extensive thermal damage, no additional issues with the engine or airframe were found that would have precluded normal operation.

The pilot had upgraded the experimental amateur-built airplane with a Lycoming four-cylinder, 160-horsepower, direct-drive aircraft engine and, about 8 flight hours before the accident, he installed a two-blade ground-adjustable uncertified composite propeller. The design of the propeller was such that the blade was retained in the hub by frictional clamping forces. The propeller blade root incorporated a collar, comprised of non-structural epoxy and a fiber layup orientation that did not provide for adequate strength in the spanwise plane. The collar was therefore only a positional reference locating the blade within the hub rather than a mechanical interlocking feature to help retain the blade if the frictional clamping forces of the hub were exceeded.

Further examination revealed multiple voids and resin-starved regions within the retained blade root. These anomalies would have lowered the stiffness of the blade root, requiring more blade root deformation to achieve the required hub clamping pressure. The risk of cracking and crushing of the fiber plies was therefore increased, as was the subsequent loss of hub clamping pressure during operation. The liberated blade also exhibited a large, elongated void near its leading edge, which could also compromise blade root stiffness, frictional retention, and reduce the pullout force.

The manufacturer of the propeller advised the pilot that although the propeller had been used with engines up to 170 horsepower, these were automotive engines and no data was available for the Lycoming engine. The automotive engine would have been fitted with a propeller speed reduction unit (PSRU). Although the accident engine’s power rating was comparable, it was direct drive and as such the propeller likely exhibited torsional excitation forces more extreme than if it had been installed on an engine with a PSRU.

The propeller manufacturer did not make installation and proper bolt torque information available on its website, nor did it readily publish inspection and maintenance information. Evidence suggests that, if available, this information was not provided to the pilot with the propeller assembly. It is possible that with proper maintenance guidance, the pilot would have detected the impending failure before the accident.

Several factors, therefore, could have contributed to the insufficient retention, including blade root design, blade manufacturing, engine application, and propeller installation and maintenance. Because of the multiple factors at play and their potential interaction, it was not possible to rule any of these out as contributing to the blade’s separation.

Probable cause

The separation of a propeller blade during the initial climb due to insufficient blade retention forces. Contributing to the accident was the propeller blade retention design, manufacturing defects that prevented the propeller from achieving adequate grip forces, the pilot’s decision to use the propeller with an untested engine combination, and the lack of initial and ongoing maintenance documentation provided to the pilot by the manufacturer.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR24FA053
Event ID
20231208193499
Case number
WPR24FA053
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, cause areas. 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: 88b00fe397ddf057ee4368111f3f7d286071fdf7a625d0520678bc6a36e07d1a; retrieved 2026-09-15T08:09:03.760Z.