FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Ameriflight Piper PA-31-350 accident

15 Sept 1989 · Ontario, CA, United States

Piper PA-31-350 · Accident: airframe, component or system failure during initial climb

From Ontario International Airport (ONT) to Santa Barbara Municipal Airport (SBA)

Report a problem

Event

NTSB case
LAX89FA314
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
0
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
Charter & commuter
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-31-350

Aircraft type
Piper PA-31
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
N70PE
Operator
Ameriflight
Onboard fatalities
Unknown
Route
From Ontario International Airport (ONT), Ontario, CATo Santa Barbara Municipal Airport (SBA), Santa Barbara, 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 135: Air Taxi & Commuter
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
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

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

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

NTSB narrative

THE PROPELLER SEPARATED FROM THE RIGHT ENGINE DURING THE INITIAL CLIMB. EXAMINATION OF THE WRECKAGE REVEALED THE PROPELLER HUB FRACTURE RESULTED IN ONE OF THE THREE PROPELLER BLADES DETACHING FROM THE HUB. THE REST OF THE PROPELLER HUB THEN SEPARATED STRIKING THE RIGHT FRONT OF THE FUSELAGE. OIL WAS SPREAD ACROSS THE AIRCRAFT NOSE AND WINDSHEILD. THE FUSELAGE RIGHT SIDE DAMAGE INCREASED AERODYNAMIC DRAG. WITNESSES REPORTED THE ENGINE COWLING WAS TORN. THE AIRCRAFT ENTERED A RIGHT TURN AND DIVE. IT IMPACTED THE GROUND IN A NEAR INVERTED ATTITUDE. METALLURGICAL EXAMINATION OF THE FAILED PROP HUB REVEALED METAL FATIGUE EMANATING FROM THE THREADED HOLE FOR THE GREASE FITTING. THE THREADS HAD BEEN DEFORMED BY SHOT PEENING, RESULTING IN INCREASED STRESS CONCENTRATIONS AT THE THREADS.

Probable cause

FAILURE OF THE RIGHT PROPELLER HUB DUE TO METAL FATIGUE WHICH RESULTED IN CATASTROPHIC SEPARATION OF THE PROPELLER. CONTRIBUTING TO THE ACCIDENT WAS DAMAGE DONE TO THE AIRCRAFT AIRFRAME IN FLIGHT BY THE SEPARATING PROPELLER MAKING THE AIRCRAFT UNCONTROLLABLE.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX89FA314
Event ID
20001213X29403
Case number
LAX89FA314
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. 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: be44eb769d80cdcf16f49aa164bdd65e44839df142263146ce3ac34bdff04da5; retrieved 2026-09-18T14:08:04.958Z.