LAX83LA005 · Beech A36
Eagle Aviation Beech A36 · Accident: total loss of engine power (mechanical failure) en route
From Long Beach International Airport (LGB) to Harry Reid International Airport (LAS)
Event
- NTSB case
- LAX83LA005
- 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 A36
- Aircraft type
- Beechcraft 36
- 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
- N4603A
- Operator
- Eagle Aviation
- Onboard fatalities
- Unknown
- Route
- From Long Beach International Airport (LGB), Long Beach, CATo Harry Reid International Airport (LAS), Las Vegas, NV
- 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
- Engine assembly, crankcase › Failure, total
- Engine assembly, crankcase › Fatigue
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WHILE CRUISING AT 9500 FT MSL, THE ENGINE BEGAN RUNNING ROUGH. THE PILOT DIVERTED TO RIALTO MUNICIPAL AIRPORT FOR A PRECAUTIONARY LANDING. WHILE ON BASE LEG, THE ENGINE QUIT COMPLETELY. FROM THAT POSITION, THE PILOT WAS UNABLE TO REACH THE RUNWAY. THE AIRCRAFT TOUCHED DOWN ABOUT 1/4 MILE SHORT, AND DURING THE LANDING ROLL, IT COLLIDED WITH A DITCH. AN INVESTIGATION REVEALED THAT THE ENGINE CRANKSHAFT HAD FAILED FROM FATIGUE. PREVIOUSLY, THE AIRCRAFT HAD BEEN INVOLVED IN A GEAR-UP LANDING. NO RECORD WAS FOUND TO VERIFY AN INSPECTION OF THE CRANKSHAFT IN ACCORDANCE WITH THE ACCEPTED PRACTICES FOLLOWING A PROPELLER STRIKE.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX83LA005
- Event ID
- 20020917X04837
- Case number
- LAX83LA005
- 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: 4c816bc6eb5b52fbdc47bf29c4962990e0a9263356be4372774a8551cf8f3b60; retrieved 2026-09-24T00:35:17.120Z.