ERA20LA132 · Cessna 310 I
Cessna 310 I · Accident: fuel starvation en route
From Rocky Mount Wilson Regional Airport (RWI) to Zephyrhills Municipal Airport (ZPH)
Event
- NTSB case
- ERA20LA132
- 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 310 I
- 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
- N8080M
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Rocky Mount Wilson Regional Airport (RWI), Rocky Mount, NCTo Zephyrhills Municipal Airport (ZPH), Zephyrhills, FL
- Aircraft age
- About 56 years (built 1964)
- 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 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 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 a cross-country flight with both of the multiengine airplane’s main and auxiliary fuel tanks filled to capacity. Data recovered from an electronic flight instrumentation system (EFIS) showed that the airplane departed and climbed to cruise altitude. About 45 minutes into the flight, fuel ceased being drawn from the main fuel tanks and began being drawn from the auxiliary fuel tanks. This continued for about 30 minutes until the quantity of fuel in the auxiliary tanks was exhausted, as indicated by both the fuel quantity parameters for those tanks and the fuel flow parameters for both engines. About the time the engines began losing power, the pilot contacted air traffic control and was provided with radar vectors to the nearest airport. Witnesses who heard the airplane flying shortly before the accident described that the rpm of both engines were increasing and decreasing, as if the engines were being starved of fuel. The airplane subsequently impacted trees and terrain about ¼-mile from the runway at the diversion airport.
Examination of the wreckage at the accident revealed that all four fuel tanks had sustained damage during the impact and that there was fuel on the ground beneath the wreckage. Additional examination of the airframe and both engines revealed no evidence of any preimpact mechanical malfunctions or failures, and that the fuel selectors for both engines were positioned to the auxiliary fuel tanks. Based on this information, and the recorded data, it is likely that the pilot departed on the accident flight with the main fuel tanks selected, and that about 45 minutes into the flight, transitioned the fuel selectors to the auxiliary fuel tanks. After the available supply of fuel in those tanks had been exhausted, the pilot failed to reselect the main fuel tanks. This resulted in fuel starvation to both engines and a subsequent total loss of engine power.
Probable cause
The pilot’s fuel mismanagement during flight, resulting in a total loss of engine power due to fuel starvation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA20LA132
- Event ID
- 20200322X70700
- Case number
- ERA20LA132
- 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: 10538b488be5a3b47a009feddd666084482fadfa57badde8ad07959af5e91a3b; retrieved 2026-09-15T07:12:55.180Z.