LAX93LA338 · Beech 95
Beech 95 · Accident: airframe, component or system failure during initial climb
From Kingman Airport (IGM) to Phoenix Goodyear Airport (GYR)
Event
- NTSB case
- LAX93LA338
- 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
- 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
- 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
Beech 95
- Aircraft type
- Beechcraft 95
- 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
- N9CE
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Kingman Airport (IGM)To Phoenix Goodyear Airport (GYR), Goodyear, AZ
- 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
- 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
- Substantial
Cause areas
- Maintenance, service bulletin/letter › Not performed
- Propeller system/accessories, prop blade retention › Fatigue
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The propeller separated from the left engine after experiencing a propeller blade separation from its hub assembly. The pilot landed, gear-up, in an open area. A metallurgical examination on the separated propeller blade revealed fatigue cracking of its retention screw. The retention screw was the subject of two service bulletins which were issued by the manufacturer on October 23, 1981, and August 27, 1982. These bulletins required replacement of the older retention screws with the newer retention screws at the next overhaul. The recommended overhaul time for this propeller assembly is five calendar years or 2,000 hours, whichever comes first. The engine log book revealed the last recorded propeller overhaul was performed on January 5, 1978.
Probable cause
the fatigue cracking of the propeller blade retention screw. A factor was the maintenance service bulletins for the propeller were not performed on the accident airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX93LA338
- Event ID
- 20001211X13187
- Case number
- LAX93LA338
- 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: 4fad063266c76deef858bf9582ceca10c194393d31fde3486a853763180b9614; retrieved 2026-09-23T01:41:43.523Z.