FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX87DUJ10 · Cessna 188B

28 Aug 1987 · POSTON, AZ, United States

Cessna 188B · Accident: total loss of engine power (mechanical failure) during initial climb

From an unrecorded airport to S 4

Show on map Search Wikipedia NTSB source dataset
Report a problem

Event

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

Cessna 188B

Aircraft type
Cessna 188
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
N8275G
Onboard fatalities
Unknown
Route
From not recordedTo S 4
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 137: Agricultural
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
Total loss of engine power (mechanical 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

  • Engine assembly, crankshaft › Failure, total
  • Other maintenance personnel › Maintenance, overhaul, improper
  • Propeller system/accessories, blade › Fatigue
  • Propeller system/accessories, blade › Separation

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

NTSB narrative

JUST AFTER LIFTOFF ONE PROPELLER BLADE SEPARATED FROM THE HUB NEAR THE OUTBOARD END OF THE ASSOCIATED FERRULE FITTING WHICH INDUCED A FAILURE OF THE CRANCKSHAFT. THE PILOT MADE A FORCED LANDING, OVERRAN THE RUNWAY END AND NOSED OVER. METALLURGICAL ANALYSIS INDICATED THAT THE FAILURE WAS DUE TO A FATIGUE FRACTURE WITH MULTIPLE ORIGIN POINTS CAUSED BY A SCRATCH. THE ANALYSIS ALSO SUGGESTED THAT ALL BUT THE FIRST THREE FERRULE THREADS HAD BEEN REWORKED IN A POST MANUFACTURE HAND GRINDING PROCESS IN ACCORDANCE WITH A MCCAULEY SERVICE BULLETIN SPECIFYING A HAND GRINDING REWORK TO REMOVE SHARP THREADS IN THE FERRULE, WHICH HAD BEEN SHOWN TO PRODUCE PRIOR FATIGUE FRACTURES. IN THE AREA OF THE FATIGUEFRACTURE, THE FIRST THREE THREADS OF THE FERRULE WERE FOUND WITH SHARP EDGES. MAINTENANCE RECORDS DID NOT SHOW THE TOTALTIME ON THIS PROPELLER SINCE MAJOR OVERHAUL.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record LAX87DUJ10
Event ID
20001213X31825
Case number
LAX87DUJ10
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1987-08-29.
  • API snapshot SHA-256: abe70fcdb61cc3e149e838debdc5117b388c24d476c12c821b95ec7cfa592f7b; retrieved 2026-09-23T12:15:58.064Z.