NTSB CAROL · Event
Event WPR20LA308
Aircraft involved
Probable cause & findings
The pilot’s improper fuel planning, which resulted in a total loss of engine power due to fuel exhaustion.
Factual narrative
On September 12, 2020, about 1143 mountain daylight time, a Piper PA-30 airplane, N7602Y, was substantially damaged when it was involved in an accident near Billings Logan International Airport (BIL). The airline transport pilot was seriously injured. The airplane was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 personal flight. The pilot does not recall the accident; however, he recalls that he had an issue with the right engine and had to shut it down. The airplane departed Lake Elmo Airport (21D), St. Paul, Minnesota, and was destined for BIL. According to the FAA, the pilot contacted the BIL air traffic control tower asking for clearance to land on runway 28. In addition, the pilot mentioned that the airplane had one engine “out” but did not share details, nor did he declare an emergency. As the airplane was on short final, the pilot made another radio call to the tower indicating that he lost the second engine. The airplane landed short of the runway against a cliffside. On-scene law enforcement reported that they did not smell fuel at the accident site, nor was fuel present in the fuel tanks. Postaccident examination of the airframe did not reveal any anomalies that would have precluded normal operations. Flight control continuity was established throughout. All of the fuel caps were loose in their filler necks; however, the cap seals were pliable and undamaged. No fuel was present in any of the fuel bladders. The fuel strainers were drained, and a small amount of uncontaminated fuel exited. The strainer bowls were removed, and no anomalies were noted. The fuel selector valve hands were undamaged; they moved freely by hand and exhibited normal detents. The auxiliary pumps would not operate when the switch was in the ON position. The airplane structure near the pumps exhibited extensive damage and the pumps were unable to be examined. Examination of both engines did not reveal any anomalies that would have precluded normal operations. All upper spark plugs were removed and exhibited normal operating wear signatures. All cylinder rocker covers were removed, and the valves were lubricated with a light brown oil. The crankshaft was rotated by hand on both engines; thumb compression was obtained on all cylinders and the valves moved accordingly. In addition, spark was obtained from each ignition lead. The right engine propeller assembly was found in the feathered position, and the spinner exhibited impact damage to one side. One blade was bent about midspan and exhibited multidirectional scuffing near its leading edge. The other propeller blade exhibited damage consistent with recovery. The left engine propeller assembly was found in the low pitch position. One blade was bent aft near the shank and exhibited scuff marks on its cambered side near the leading edge. The other blade was unremarkable. Estimated fuel calculations were completed for full fuel tanks. The accident flight was about 4 hours and 31-minutes long. According to the Piper Twin Comanche Owner’s Handbook, the airplane’s fuel capacity is 84 gallons of usable fuel, and it would have consumed about 77.4 gallons when operated at 75% power. The calculations did not account for variables such as engine leaning, wind, climb, or descent. According to the FAA, the pilot contacted the air traffic control tower at the destination airport and requested clearance to land on runway 28. The pilot mentioned that the airplane had one engine “out” but did not share details, nor did he declare an emergency. As the airplane was on short final, the pilot made another radio call to the tower indicating that he lost the second engine. The airplane landed short of the runway against a cliffside. On scene law enforcement reported that they did not smell fuel at the accident site, nor was fuel present in the unbreeched fuel tanks. Postaccident examination of the airframe and both engines did not reveal any anomalies that would have precluded normal operations. The pilot does not recall the accident; however, he recalls that he had an issue with the right engine and had to shut it down. Estimated fuel calculations were completed assuming the fuel tanks were full and 75% power was used. The airplane would have consumed 77.4 gallons of the 84 usable gallons during the 4.5 hr accident flight. The calculations did not account for variables such as engine leaning, wind, climb, or descent. Taking those variables into account, it is likely that the airplane did not have enough fuel to complete the flight. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- — Aircraft-Fluids/misc hardware-Fluids-Fuel-Fluid management
- — Personnel issues-Task performance-Planning/preparation-Fuel planning-Pilot
Verbatim from NTSB's published report. Source file
NTSB_2020_WPR20LA308.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (fuel exhaustion). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- AOPA Air Safety Institute 2023 · Safety advisor
Safety Advisor: Fuel Awareness
AOPA Air Safety Institute safety advisor on preventing fuel-exhaustion and fuel-starvation accidents in general aviation. Covers pre-flight fuel planning, reserve requirements (14 CFR 91.151, 91.167),…
- NASA NTRS 2019 · Abstract
U.S. Civil Rotorcraft Accidents, 1963 through 1997
The U.S. National Transportation Safety Board (NTSB) has recorded 8,436 rotorcraft accidents during the period mid - 1963 through the end of 1997.
- NASA NTRS 2019 · Contractor Report (CR)
A study of carburetor/induction system icing in general aviation accidents
An assessment of the frequency and severity of carburetor/induction icing in general-aviation accidents was performed. The available literature and accident data from the National Transportation Safet…
- NASA NTRS 2018 · Other
Parachuting to Safety
NASA's Langley Research Center awarded Ballistic Recovery Systems, Inc., three Small Business Innovation Research (SBIR) contracts to research and develop a new, low cost, lightweight recovery system …
Browse the full corpus — academia portal ↗