LAX00LA083 · Cessna 152
Group 3 Aviation Cessna 152 · Accident: total loss of engine power (non-mechanical) en route
From Laughlin Bullhead International Airport (IFP) to Van Nuys Airport (VNY)
Event
- NTSB case
- LAX00LA083
- 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 152
- Aircraft type
- Cessna 152
- 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
- N25573
- Operator
- Group 3 Aviation
- Onboard fatalities
- Unknown
- Route
- From Laughlin Bullhead International Airport (IFP), Bullhead City, AZTo Van Nuys Airport (VNY), Van Nuys, 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 (non-mechanical)
- 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
- Fuel exhaustion
- 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
- Fluid, fuel › Exhaustion
- Pilot in command › Became lost/disoriented, inadvertent
- Pilot in command › Navigation receiver, misread
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot became disoriented after encountering clouds near his destination airport and ran out of fuel while he was in the process of finding a place to land. The aircraft then nosed over after encountering soft soil during the forced landing. The pilot stated that he did not obtain a preflight weather briefing or in-flight weather advisories. The pilot said another pilot in the departure airport terminal obtained a weather briefing and told him the weather was good for now but that conditions would get worse around Los Angeles later in the day. Following departure, the flight was uneventful until he reached the high desert area north of his destination and he found that the coastal mountains between the high desert and his destination were obscured by clouds. He then decided to proceed to a VOR close to his destination in the hopes that the airport would be open. Upon reaching the VOR, the pilot could not find a clear route and elected to return to the high desert area and land at an airport there. He stated that after dialing in the VOR radial to take him to the alternate he became confused over the "TO/FROM" indicator and ended up flying in the wrong direction. When he realized where he was, he believed he did not have enough fuel to fly back over the mountains and was looking for an airport when he ran out of fuel. Review of NWS data disclosed that AIRMET Sierra was in effect at the time of the pilot's departure. The forecast called for occasional ceilings below 1,000 feet and visibility's below 3 miles in the coastal areas. Mountain obscuration in clouds, precipitation, and fog was also predicted for the coastal mountain ranges. The pilot stated that there were no mechanical malfunctions with the airframe or engine. The pilot obtained his private pilot certificate 10 days prior to the accident.
Probable cause
The pilot's misinterpretation of his VOR navigation indicator, which subsequently led to his becoming lost and disoriented while navigating to an alternate airport and resulted in fuel exhaustion. The pilot's failure to obtain either a preflight weather briefing or in-flight weather advisories was a factor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX00LA083
- Event ID
- 20001212X20398
- Case number
- LAX00LA083
- 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: 69127295d8ca206505ef7bbdfb1aaa990aa3b9087b4e9d19d01f08a5b90a63bc; retrieved 2026-09-22T13:18:40.271Z.