FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR20FA065 · Cessna T310 P

15 Jan 2020 · Roy, UT, United States

Cessna T310 P · Accident: fuel related on approach

From Skypark Airport (BTF) to Ogden Hinckley Airport (OGD)

Report a problem

Event

NTSB case
WPR20FA065
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
1 · 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 T310 P

Aircraft type
Cessna 310
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
N5805M
Onboard fatalities
Unknown
Route
From Skypark Airport (BTF), Bountiful, UTTo Ogden Hinckley Airport (OGD), Ogden, UT
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
Approach
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 related
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 › Aircraft oper/perf/capability
  • Aircraft › Fluids/miscellaneous hardware
  • 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 was conducting a personal flight to relocate the twin-engine airplane back to his home base following maintenance. A leak check on the left-wing tip fuel tank was also performed prior to the flight. About 2 1/2 gallons of fuel was added to the tank to perform the leak check. According to a witness, the pilot did not refuel the airplane prior to the accident flight. Another witness reported hearing popping sounds as the airplane approached the destination airport and thought that one of the engines was trying to restart while it flew overhead. The witness also stated that the landing gear and flaps were extended. A third witness saw that the airplane was in a yaw to the left and appeared to be struggling to stay airborne. Subsequently, the airplane’s left wing dropped, the airplane momentarily stabilized, and the left wing dropped again, banking the airplane further to the left. The airplane continued to the left when the nose dropped and was soon out of view.

Postaccident examination of the airplane revealed that the left propeller blades exhibited minimal rotational signatures, which is consistent with the left engine producing low-to-no power at the time of impact. The visual evidence indicated the left propeller was not feathered at the time of impact, which was counter to procedures indicated for operating with one engine inoperative during flight. The right propeller blades showed evidence of the engine operating at mid-to-low power at the time of impact. Examination of the airframe and engines revealed no evidence of preaccident mechanical malfunctions or anomalies that would have precluded normal operation. It is likely that during the flight, the left-wing tip fuel tank’s remaining fuel was exhausted, resulting in the loss of power to the left engine. Available evidence suggests that the left engine shut down during flight due to fuel starvation, resulting in the airplane yawing to the left with a decrease in performance followed by banking left.

The pilot was known to land the airplane on a single engine on multiple occasions. He was also described as not likely to declare a flight emergency because of the paperwork involved. It is likely after he lost power to the left engine, the pilot continued his approach to his destination without declaring an emergency. As the flight continued there was a loss of airspeed, which resulted in the airplane entering multiple aerodynamic stalls, which precipitated the final left turn toward the accident site.

Probable cause

The pilot’s inadequate preflight fuel planning and fuel management, which resulted in a total loss of power to the left engine due to fuel exhaustion. Also causal was the pilot's failure to follow the one-engine inoperative checklist and maintain the airplane's minimum controllable airspeed by properly configuring the airplane, which resulted in a loss of airplane control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR20FA065
Event ID
20200115X85405
Case number
WPR20FA065
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: 2038ae0cab280ae75b37123555ddd794cf2f48f43e2dc91e0c98165f6cc13457; retrieved 2026-09-15T07:10:43.499Z.