LAX86FA207 · Cessna P210N
Cessna P210N · Accident: total loss of engine power (mechanical failure) en route
From E69 · Payson, AZ to Zamperini Field (TOA)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- LAX86FA207
- 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 P210N
- Aircraft type
- Cessna 210
- 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
- N55MM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route Possible conflict
- From E69 · Payson, AZTo Zamperini Field (TOA), Torrance, 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
- 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
- Other maintenance personnel › Maintenance, alignment, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WHILE ENROUTE FROM CINCINNATI, OH (LUK), TO TORRANCE, CA, THE AIRPLANE EXPERIENCED A TOTAL ENGINE POWER LOSS ABOUT 10 MILES SOUTH OF LONG BEACH AIRPORT (LGB), LONG BEACH, CA. THE PILOT ATTEMPTED TO LAND AT LGB BUT THE ACFT ALT WAS INSUFFICIENT. THE ACFT CRASHED ON A GOLF COURSE LOCATED ABT 1/4 MILE EAST OF THE ARPT. THE INVESTIGATION DISCLSD THE NO. 2 PISTON HAD MELTED DUE TO EXTREME HIGH TEMP DISTRESS AND THE CON ROD FRACTURED IN OVERLOAD. THE ENGINE WAS INSTALLED AT LUK ON MAY 2, 1986 AND HAD ACCUM 125 FLT HRS. METALLURGICAL EXAM DISCLSD MISALIGNMENT OF THE CON ROD AND PISTON/CYLINDER BARREL.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX86FA207
- Event ID
- 20001213X33579
- Case number
- LAX86FA207
- 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: 1dffa07db0a8f889b1f320ba1ba0b040ea5000551bb32a600a9ee3a553000176; retrieved 2026-09-21T16:59:25.963Z.