FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR09LA340 · Bender Kitfox

7 Jul 2009 · Valencia, CA, United States

Bender Kitfox · Accident: part(s) separation from aircraft en route

From Whiteman Airport (WHP) to Whiteman Airport (WHP)

Report a problem

Event

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

Bender Kitfox

Aircraft type
Bender KITFOX
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
N926JB
Operator
Unknown
Onboard fatalities
Unknown
Route
From Whiteman Airport (WHP), Los Angeles, CATo Whiteman Airport (WHP), Los Angeles, CA
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
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
  • Not determined › Not determined

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

NTSB narrative

The pilot reported that he was flying back to the airport when the experimental airplane began to shake violently, which was accompanied by a loud noise. The propeller blades departed the airplane and the engine subsequently experienced an overspeed, followed by a loss of power. During a forced landing, the airplane encountered a ditch and spun 90 degrees. Metallurgical examinations of the blades could not determine the method of failure. Tests and calculations indicate that the engine could not rotate fast enough to liberate the blades unless their strength had been degraded in some way. Several possible sources of such degradation were observed, but none of them could be conclusively identified as the cause of the event. The strength of the blades was provided by the wood of the propeller, and the fractures in the wood of the three blades appeared similar, making no obvious difference to identify the initial separation. The blades were found very close to one another, suggesting that they were liberated at nearly the same point of rotation during a single revolution of the propeller. Assuming one blade had accumulated enough damage to initiate the event, the resulting unbalanced vibration was sufficient to eject the other two blades, in the process creating fractures similar to those on the damaged blade. The measured gap between hub halves was less than the expected gap for new, correctly installed blades. Such over-clamping of the hub is one problem that has apparently occurred in the past due to improper torquing. It is possible that the hub had previously been over-clamped to a greater degree, with subsequent adjustment leading to an under-clamped condition. Looseness in this area can lead to fatigue cracking, because it allows for the variations in stresses from repetitive loads to be maximized on the components being connected. Bird impact was ruled out, but the blade might have been struck by debris picked up during takeoff. Although there was no staining or other signs of degradation in the wood, one blade had an area that was susceptible to moisture due to a manufacturing defect, which could have allowed the decrease in the stiffness and strength of wood structures and may have played a role in liberating the blades.

Probable cause

The failure and separation of a propeller blade for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR09LA340
Event ID
20090714X11848
Case number
WPR09LA340
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: 3f2d2ba6bfccc6f5f11963dcdef6a295737ce45d08f56aaf8972b948730624eb; retrieved 2026-09-15T11:50:36.865Z.