Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

September 12, 2020 · Piper PA 30 No Series · N7602Y

Billings, MT

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
September 12, 2020
Injury Outcomes
1 injury (1 serious injury)
Location
Billings, MT
Aircraft
Piper PA 30 No Series (1964)
Tail Number
N7602Y
Injuries
Serious
Aircraft Damage
Substantial
NTSB Number
WPR20LA308

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.

NTSB Probable Cause

The pilot’s improper fuel planning, which resulted in a total loss of engine power due to fuel exhaustion.

Full 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.

Flight

Event TypeAccident
Event Time11:43 MDT
Nearest AirportBillings Logan International A (1nm)
Runway28R
Runway Length10518 ft
Runway Width150 ft
Flight Plan FiledIFR
Flight Plan ActivatedYes
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA 30 No Series
Tail NumberN7602Y
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines2
Engine TypeReciprocating
Engine DetailsLycoming · IO-320 SERIES · Reciprocating · 160 | Lycoming · IO-320 SERIES · Reciprocating · 160
Seats4

People & Injuries

Injury Summary1 injury (1 serious injury)
Fatal0
Serious1
Minor0
Uninjured0
Total1
Crew 1Age 67 · First Class · Serious

Conditions

ConditionsVMC
LightDaylight
Wind210° @ 9 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point32 C
Altimeter30.04 inHg
Observation Time11:53
Weather SourceWFAC

Appendix: Source Data