FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX96LA117 · Cessna 172P

16 Feb 1996 · RAYMOND, CA, United States

Royal Aviation Cessna 172P · Accident: total loss of engine power (non-mechanical) en route

From John Wayne Orange County International Airport (SNA) to O68 · Mariposa, CA

Report a problem

Event

NTSB case
LAX96LA117
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 172P

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
N53115
Onboard fatalities
Unknown
Route
From John Wayne Orange County International Airport (SNA), Santa Ana, CATo O68 · Mariposa, 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 › Fuel supply, not verified

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot reported that the aircraft was en route over low rolling foothills when the engine quit. The aircraft firewall and nose gear was damaged during the forced landing on a road. Examination of the aircraft by a A&P mechanic revealed that the fuel system was intact. Only residual fuel was found in the fuel tanks. Following recovery of the aircraft, the engine was started using the airframe systems; it accelerated to power smoothly with normal magneto drops observed. The pilot stated the aircraft is rented full of fuel by the FBO and during the preflight inspection put her fingers in the filler port and felt fuel at a level about 1 inch below the top of the filler neck. The pilot noted that the fuel gages in this aircraft historically read something less than full when the tanks are filled and the gage reading on start of between 3/4 and full seemed normal. Cessna Aircraft reported that the tanks must be filled to the top of the filler neck to obtain a 20 gallon usable fuel level. A fuel level at the bottom of the filler neck equals 18 usable gallons and each inch in fuel level below that is equal to about 2 gallons of fuel. The difference between the takeoff time and the accident is 3 hours 22 minutes according to FAA ATC communication tapes. The Safety Board calculated the expected fuel usage using both the aircraft performance charts in the Cessna POH, and specific fuel flow figures provided by Lycoming for an engine operated at full rich condition. With the stated allowances for engine start, taxi and takeoff, the Safety Board calculated that 28.4 gallons of fuel would be used when the engine was leaned and the aircraft flown according to the manual. In the full rich condition, 33.4 gallons of fuel would be required.

Probable cause

The pilot's failure to verify the quantity of fuel onboard the aircraft prior to departure, which resulted in fuel exhaustion.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX96LA117
Event ID
20001208X05285
Case number
LAX96LA117
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1996-02-17.
  • API snapshot SHA-256: ec673508f209f7762e9b61719cd67e569e3c0b4837a183b329c6bf4a2be56d6c; retrieved 2026-09-22T22:48:59.460Z.