LAX07CA125 · Cessna 172M
Cessna 172M · Accident: total loss of engine power (non-mechanical) en route
From San Gabriel Valley Airport (KEMT) to Stockton Metropolitan Airport (KSCK)
Event
- NTSB case
- LAX07CA125
- 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
- Unknown
- 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 172M
- 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
- N9685Q
- Operator
- Aacit
- Onboard fatalities
- Unknown
- Route
- From San Gabriel Valley Airport (KEMT), El Monte, CATo Stockton Metropolitan Airport (KSCK), Stockton, 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 · descent
- 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 consumption calculations, inaccurate
- Pilot in command › In-flight planning/decision, improper
- Pilot in command › Refueling, not performed
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
After a loss of engine power, the airplane landed short of the runway, collapsing the nose gear and buckling the engine firewall. The pilot departed with both fuel tanks full. His route of flight usually takes 3 hours to fly. He encountered turbulence and strong winds, which had the effect of increasing the flight time to 4 hours. As he lined up for a straight-in approach to the runway, the engine stopped due to fuel exhaustion. The pilot executed a forced landing short of the approach end of runway and collided with the ground and a fence. The pilot stated that the airplane and engine had no mechanical malfunctions. An FAA inspector examined the airplane at the accident scene and confirmed that there was no fuel onboard.
Probable cause
The loss of engine power due to fuel exhaustion resulting from the pilot's inaccurate fuel consumption calculations and failure to refuel while en route.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX07CA125
- Event ID
- 20070508X00531
- Case number
- LAX07CA125
- 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, coordinates. 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: 099df57aec2cd79cc0accfba361fe3426461e612ca1507c09b001fccf196210e; retrieved 2026-09-21T18:32:58.586Z.