Aviation Crash Map

Cessna 182C N8580T

22 May 2024 · Vernal, Utah, United States · No injuries

Summary

On 22 May 2024 at about 16:30 local time, a Cessna 182C registered N8580T was involved in an accident near Vernal, Utah, United States. 3 people were on board and nobody was injured. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.

The record

Date
at 16:30
Classification
Accident
Location
Vernal, Utah, United States
Nearest airport
Vernal Regional Airport (VEL)
Coordinates
40.4361, -109.5114
Aircraft
Cessna 182C
Registration
N8580T
Category
Airplane
Year built
1960
Engines
1
Operator
Not recorded
Operating rule
Part 91: General Aviation
Purpose of flight
Personal
Phase of flight
Not recorded
Route
Bozeman → Vernal
Aircraft damage
Substantial
Weather
VMC
Light
Day
NTSB number
WPR24LA296

People

Nobody was injured.

On board Died Serious Minor Uninjured
3 0 0 0 3

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.

Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.

Read the full 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.

Quoted verbatim from the NTSB record.

Other Cessna 182 accidents

Date Aircraft Location Operator Outcome Died
31 Aug 2024 Cessna 182D
N9020X
Coopersville, Michigan, United States - Unknown -
6 Jul 2024 Cessna 182
LZ-SDB
Sapareva Banya, Bulgaria
no coordinates
- No injuries -
8 Jun 2024 Cessna 182
N3304R
Telford, Tennessee, United States - Serious injuries -
18 Jul 2024 Cessna 182
N8523T
Zephyrhills, Florida, United States - No injuries -
18 Mar 2024 Cessna 182
PT-JUN
Manuel Urbano, Brazil - Unknown -
22 Aug 2024 Cessna 182
N7529N
Shelter Island, New York, United States - No injuries -

All 6,261 records for this type

Other accidents in this area

Date Aircraft Location Operator Outcome Died
10 Feb 2024 Piper PA-32R-301T
N989SR
Spanish Fork, Utah, United States - Minor injuries -
21 Apr 2024 Schleicher Alexander Gmbh & ASH 26 E
N644CC
Heber, Utah, United States - No injuries -
24 Jul 2024 Piper PA-34-220T
N134MG
Roy, Utah, United States CSA Aircraft Leasing LLC Serious injuries -
28 Oct 2024 Cirrus SR20
N27WF
St. George, Utah, United States - No injuries -
27 Jul 2024 Boeing 737
N853DN
Salt Lake City, Utah, United States Delta Air Lines Inc No injuries -
29 Jul 2024 Burkhart Grob Flugzeugbau G103 TWIN ASTIR
N8485W
Huntsville, Utah, United States - No injuries -

All 170,864 records in United States