FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX03FA065 · Piper PA-34-200

11 Jan 2003 · Westlake Village, CA, United States

Aero Club Piper PA-34-200 · Accident: airframe, component or system failure en route

From Van Nuys Airport (VNY) to an unrecorded destination

Report a problem

Event

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

Piper PA-34-200

Aircraft type
Piper PA-34
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
N56484
Onboard fatalities
Unknown
Route
From Van Nuys Airport (VNY), Van Nuys, CATo not recorded
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
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
Destroyed

Cause areas

  • Manufacturer › Acft/equip, inadequate design
  • Propeller system/accessories, hub › Fatigue
  • Propeller system/accessories, hub › Separation

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

NTSB narrative

The airplane collided with ground obstacles during a forced landing when the pilots could not maintain altitude after one propeller blade and part of the propeller hub from the right engine separated in flight. The CFI and the student practiced two simulated engine-out maneuvers. The CFI was reaching for the mixture control for a third simulation when he heard a loud bang. The airplane yawed violently to the right and began to lose altitude. The CFI turned toward his home field, but was having difficulty maintaining altitude. He decided that he would not be able to make it to the airport, and would have to make an off field landing. He landed in the only clear spot that he could see, which was a cemetery. The airplane collided with monuments and a wood chip pile before coming to rest next to a mausoleum. The right propeller hub fractured and separated. Investigators did not recover one blade and the corresponding part of the hub. The hub fractured as a result of fatigue cracking emanating from one of the grease-fitting holes. The fatigue cracking originated in the area of the grease-fitting threads closest to the interior surface of the hub, at the intersection between the grease-fitting hole and the chamfer. No material or manufacturing defect was found that could be identified as the source of the fatigue cracking. The fatigue cracking originated just outside the thread remnants of the grease fitting hole that were plastically deformed during a chamfering process. The grease fitting was located in a region where the wall of the hub was approximately at its thinnest, and where there was a slight change in the profile along the axis of the propeller. These geometrical factors would have led to high stresses at the edges of the hole. Chamfers were retrofitted to the grease-fitting holes by the manufacturer at both the interior and exterior surfaces of the hub in response to fatigue fractures that occurred in three-bladed propellers. This accident was the first occurrence of fatigue emanating from a grease-fitting hole for a two-bladed propeller. The chamfering was apparently introduced in an effort to smooth the stress distribution around the grease-fitting holes. The chamfer at the interior surface should have removed the stress concentration associated with the change in wall profile, but would also have decreased the amount of material in the wall, leading to higher stresses overall. The stress concentration associated with the grease-fitting hole and the chamfer, coupled with the location in a position where the hub wall was very thin, were likely sufficient to initiate fatigue cracking in this case. In more recently manufactured hubs, the grease-fitting holes have been relocated to positions where the hub wall is much thicker.

Probable cause

a fatigue crack in the propeller hub due to the inadequate design location of the grease fitting and the chamfering process.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX03FA065
Event ID
20030124X00107
Case number
LAX03FA065
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: bfc7f079a001d688d815eb6293e7eab4f34d1e19ba9a5e282ec92117e4dd3d29; retrieved 2026-09-21T09:31:54.191Z.