WPR23LA241 · Cessna 172K
Cessna 172K · Accident: fuel exhaustion en route
From Inyokern Airport (IYK) to Ryan Field (RYN)
Event
- NTSB case
- WPR23LA241
- 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
- Event fatalities
- Unknown
- 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 172K
- 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
- N84385
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Inyokern Airport (IYK), Inyokern, CATo Ryan Field (RYN), Tucson, AZ
- Aircraft age
- About 54 years (built 1969)
- 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
- Defining eventThe 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
- 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
- Aircraft › Fluids/miscellaneous hardware
- Personnel issues › Psychological
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot departed on the cross-country flight with an estimated 38 gallons of fuel onboard. While enroute, the pilot deviated from the direct route to his destination, which increased his enroute time and distance. Flight track data revealed that the airplane arrived near the planned fuel stop, but the pilot stated that he diverted to another airport when he could not activate the runway lights at his intended fuel stop. After travelling for about 3 hours, 46 minutes, a total of about 467 miles, and about 5 miles short of the airport intended to be his second fuel stop, the engine lost total power about the time that the pilot stated that the fuel quantity gauges had “dropped all the way to basically nothing.” The pilot reported that there were no mechanical malfunctions or failures that would have precluded normal operation but suspected that the airplane may have developed a fuel leak. Postaccident examination revealed no evidence of a fuel leak. Based on the available information, it is likely that the loss of power was the result of fuel exhaustion. The Owner’s Manual Cruise and Range Performance Chart revealed that with 38 gallons of fuel, the accident flight’s distance and time enroute were within the chart limits; however, the accident flight consisted mostly of low altitude maneuvering flight that were not addressed by the Owner’s Manual. Field sobriety testing of the pilot was conducted at the scene of the accident, with no determination of impairment being made by law enforcement at that time. Toxicological testing of the pilot’s blood indicated that the pilot likely had used a cannabis product, cocaine, amphetamine, and MDMA. Although his use of these controlled substances conveyed significant risk of impairment, available evidence was insufficient to determine the precise timing of his substance use, specific impairing effects during the accident flight, or whether such effects contributed to the accident.
Probable cause
A total loss of engine power due to fuel exhaustion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR23LA241
- Event ID
- 20230626192461
- Case number
- WPR23LA241
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, cause areas. 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: 80e5fc5b2d60d7c7e5103cfcd9754c45c9601b7cefe12f5dd5bcb5edcb4b5b3d; retrieved 2026-09-16T17:46:33.524Z.