LAX98LA183 · Cessna 172H
Cessna 172H · Accident: total loss of engine power (non-mechanical) en route
From Bakersfield, CA to 068
Event
- NTSB case
- LAX98LA183
- 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 172H
- Aircraft type
- Cessna 172
- 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
- N2573L
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Bakersfield, CATo 068
- 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; 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
- Pilot in command › Aircraft preflight, improper
- Pilot in command › Fuel supply, inadequate
- Pilot in command › In-flight planning/decision, improper
- Pilot in command › Precautionary landing, not performed
- Pilot in command › Refueling, not performed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The day before the pilot's flight he checked his airplane and determined that its right fuel tank was full of fuel, and the left tank was 'down 2 to 3 gallons.' The following morning a preflight inspection was performed, no fuel was added, and the pilot took off from Mariposa, California. After flying about 1:20 hours, the pilot landed at Bakersfield and ate lunch. Thereafter, he took off for a return flight to Mariposa. En route, the pilot cruised at 6,500 feet msl and overflew Fresno, a community with several airports. The pilot observed the airplane's fuel gauges, switched tanks, and continued heading toward Mariposa. About 35 miles past Fresno, all engine power was lost. A ground-based witness heard the pilot transmit a distress call indicating that he was out of fuel. The pilot attempted to make a forced landing on a highway, but on approach collided with trees. No evidence of any preimpact mechanical malfunction or failure was found during an examination of the airplane. Fuel system continuity was established, with no ruptures evident to any line or tank. The FAA reported that the amount of fuel observed remaining in the fuel tanks was less than 1 gallon and was in the unusable range. A few drops of fuel were observed in the gascolator. The pilot stated that the accident could have been prevented had he refueled (before departure) at Bakersfield.
Probable cause
Fuel exhaustion due to the pilot's inadequate preflight planning, and improper in-flight decision not to make a precautionary landing for additional fuel.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX98LA183
- Event ID
- 20001211X10346
- Case number
- LAX98LA183
- 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: c9b41404efd6cd2c75a7b5e466933325eecf2abb96063a256b897a8daf7a24b7; retrieved 2026-09-21T11:30:37.548Z.