LAX93LA356 · Cessna 182A
Cessna 182A · Accident: total loss of engine power (mechanical failure) en route
From Ryan Field (RYN) to Royan-Médis Airport (RYN)
Event
- NTSB case
- LAX93LA356
- 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 182A
- Aircraft type
- Cessna 182
- 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
- N6336B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Ryan Field (RYN), RYAN FIELD, AZTo Royan-Médis Airport (RYN)
- 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)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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 › Fatigue
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING A LOCAL VFR FLIGHT, THE ENGINE LOST POWER. THE PILOT TRIED TO LAND ON AN ASPHALT SURFACED ROAD, BUT WAS UNABLE TO REACH THE ROADWAY. DURING THE FORCED LANDING, THE AIRPLANE COLLIDED WITH TREES ON UNEVEN DESERT TERRAIN AND WAS DAMAGED. AN EXAMINATION OF THE ENGINE REVEALED THAT THE CRANKSHAFT HAD FAILED FORWARD OF THE NUMBER ONE JOURNAL. THE FRACTURED SURFACES DISPLAYED BEACH MARKS CONSISTENT WITH FATIGUE. THERE WAS NO EVIDENCE THAT THE ENGINE HAD SUSTAINED ANY HIGH TEMPERATURE DISTRESS OR LACK OF LUBRICATION. THE ENGINE HAD ACCRUED ABOUT 4434 HOURS SINCE NEW AND ABOUT 1110 HOURS SINCE IT WAS OVERHAULED ON 12/10/87.
Probable cause
FAILURE OF THE CRANKSHAFT DUE TO FATIGUE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX93LA356
- Event ID
- 20001211X13432
- Case number
- LAX93LA356
- 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: 46ade1bd743116f820da5ec2e13018a2d53f09c378f6de96cfb0e9742062ddf8; retrieved 2026-09-21T14:08:41.975Z.