FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR24LA296 · Cessna 182C

22 May 2024 · Vernal, UT, United States

Cessna 182C · Accident: fuel starvation on approach

From Bozeman Yellowstone International Airport (KBZN) to Vernal Regional Airport (KVEL)

Report a problem

Event

NTSB case
WPR24LA296
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 182C

Aircraft type
Cessna 182
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
N8580T
Operator
Unknown
Onboard fatalities
Unknown
Route
From Bozeman Yellowstone International Airport (KBZN), Bozeman, MTTo Vernal Regional Airport (KVEL), Vernal, UT
Aircraft age
About 64 years (built 1960)
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
Approach · VFR pattern final
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 starvation
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 › Task performance

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

NTSB narrative

The pilot reported that, while on an approach to land, he set the fuel selector lever to the left tank and maintained a leaned mixture condition with the carburetor heat on; he then performed a brief slip to quickly lose altitude. As the airplane was about 3 miles from the runway, he reduced engine power and extended the flaps to 40°. Before reaching short final, the engine stumbled and lost all power. The pilot was unable to restart the engine and initiated a forced landing onto an open field. During the off-airport landing, the airplane landed hard, which resulted in substantial damage to the engine truss. An examination of the engine did not reveal any anomalies that would have precluded normal operation and that there was no evidence of a breach in the fuel system. Local law enforcement officers who responded to the accident stated that they did not see any fuel in the left tank. The pilot reported that his practice was to switch fuel tanks every 30 minutes to maintain a fuel balance between tanks and used the onboard fuel computer to determine fuel consumption. NTSB fuel performance calculations showed that the calculated fuel consumption from the airplane’s onboard fuel computer was consistent with the pilot’s operating handbook (POH) performance charts for the accident flight. The calculation and the pilot’s recount revealed that he likely departed with 55 gallons onboard and the LEFT fuel tank selected. Fuel calculations showed that after about 2 hours of flight he would have had about 10.5 gallons of fuel in the left tank and 15.5 gallons in the right tank. However, the pilot reported that he also had the left fuel tank selected for the remaining 80 minutes of flight. Additional calculations from available ADS-B data showed that the engine would have consumed approximately 7 gallons in the last 34 minutes of cruise flight and another 8 gallons during the pilot’s subsequent 36 minute descent. At the time of the power loss following the descent, the airplane would have had 0 gallons remaining in the left fuel tank, and 9.5 remaining in the right fuel tank. The pilot’s statement noted that he had planned to switch fuel tanks during the descent, but was delayed as he was not yet established on final approach. The evidence in the investigation showed that had he set the fuel selector lever to BOTH during the descent, as required in the “Before Landing” section of the POH, the engine likely would not have encountered fuel starvation and a loss of power. Thus, the accident was the result of the pilot’s improper in-flight fuel management and delay in configuring the fuel selector for landing as recommended by the airplane manufacturer, which resulted in fuel starvation and a total loss of engine power.

Probable cause

The pilot’s improper in-flight fuel management and delay in configuring the fuel selector for landing as recommended by the manufacturer, which resulted in fuel starvation and a total loss of engine power during the final approach to land.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR24LA296
Event ID
20240906195070
Case number
WPR24LA296
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, 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: 0d4908c0bf55ed025f304ff51c4d9083d3a07f44da7d03503cd32dc3779b16dd; retrieved 2026-09-16T19:14:24.799Z.