# NTSB WPR20LA308: Piper PA 30, N7602Y, Billings, MT, September 12, 2020 - Type: NTSB accident investigation - Classification: Accident · Serious injuries · Class 3 · Limited · Final report - Date: September 12, 2020, 11:43 local (17:43 UTC) - Place: Billings, MT - Coordinates: 45.649333, -108.38076 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=45.6493&lon=-108.3808&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach: Fuel exhaustion](https://openairdocs.org/ntsb-events/192) - Highest injury: Serious injuries - Injuries: 1 serious - Status: Completed - Report: Approved by Office Director - Investigation class: Class 3 - NTSB office: Western Pacific Region - Parties: Piper Aircraft, Federal Aviation Administration - NTSB case key (mKey): 101981 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR20LA308 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/101981/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=101981 - Page: https://openairdocs.org/ntsb/WPR20LA308 ## Probable cause The pilot’s improper fuel planning, which resulted in a total loss of engine power due to fuel exhaustion. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Fluids: fuel](https://openairdocs.org/ntsb-findings/01071010): Aircraft › Fluids/misc hardware · Fluid management (probable cause); cases with it: [Piper PA-30, 14 cases](https://openairdocs.org/ntsb-findings/01071010/cases.md?model=7103002), [All aircraft, 1,695 cases](https://openairdocs.org/ntsb-findings/01071010/cases.md) - [Planning/preparation: fuel planning](https://openairdocs.org/ntsb-findings/02061030): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Piper PA-30, 5 cases](https://openairdocs.org/ntsb-findings/02061030/cases.md?model=7103002), [All aircraft, 719 cases](https://openairdocs.org/ntsb-findings/02061030/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Enroute-cruise: Loss of engine power (partial)](https://openairdocs.org/ntsb-events/342); cases with it: [Piper PA-30, 12 cases](https://openairdocs.org/ntsb-events/342/sequence.md?model=7103002), [All aircraft, 1,858 cases](https://openairdocs.org/ntsb-events/342/sequence.md) - [Approach: Fuel exhaustion](https://openairdocs.org/ntsb-events/192) (defining event); cases with it: [Piper PA-30, 3 cases](https://openairdocs.org/ntsb-events/192/sequence.md?model=7103002), [All aircraft, 804 cases](https://openairdocs.org/ntsb-events/192/sequence.md) - [Approach: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341); cases with it: [Piper PA-30, 11 cases](https://openairdocs.org/ntsb-events/341/sequence.md?model=7103002), [All aircraft, 3,820 cases](https://openairdocs.org/ntsb-events/341/sequence.md) - [Approach: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Piper PA-30, 37 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7103002), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis 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. ## 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. ## Aircraft - Registration: [N7602Y](https://openairdocs.org/deregistered/N7602Y-2021-10-18), registration cancelled 2021-10-18, S/N 30-672, built 1964 (OpenAirDocs) - Reported make and model: Piper PA 30 (No Series) - Registry model: [Piper PA-30](https://openairdocs.org/model/piper-pa-30) (registry code 7103002) (OpenAirDocs) - Registry engine: [Lycoming IO-320 series](https://openairdocs.org/engine/lycoming-io-320-series) (registry code 41509, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 30-672 - Year built: 1964 - Airframe hours: 4736 - Engines: Lycoming IO-320 SERIES 160 hp reciprocating; Lycoming IO-320 SERIES 160 hp reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, May 15, 2020 - Departed: 21D, St. Paul, MN - Destination: Same as departure - Flight plan: IFR - Airport: KBIL, Billings Logan International Airport, runway 28R, 10,518 × 150 ft, asphalt - Equipment: ADS-B ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 67; injuries: serious; commercial, airline transport; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 1, with waivers/limitations; last flight review March 23, 2020; seat: left; restraint: lap only; flight hours: 18,024 total, 820 in this make and model, 15 in the last 90 days, 15 in the last 30 days, 0 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 210° at 9 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 75 °F, dew point 32 °F - Altimeter: 30.04 inHg - Icing: Clear - Observed at: BIL, 1 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20200912012809A](https://openairdocs.org/incident/20200912012809A), Sep 12, 2020: Piper PA-30, Billings, MT, Substantial damage. Inbound to bil, pilot reported one engine operation. Following clearance to land and on short final the pilot declared emergency with loss of second engine.… ## Other investigations on N7602Y (2) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB MIA67A0011](https://openairdocs.org/ntsb/MIA67A0011), Jul 22, 1966: Piper PA-30 (N7602Y), Gordo, AL, destroyed, 2 fatal - [NTSB MIA66F0225](https://openairdocs.org/ntsb/MIA66F0225), Aug 13, 1965: Piper PA-30 (N7602Y), Birmingham, AL, substantial damage ## Docket (10 files) The files NTSB released with the investigation on June 22, 2022, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=101981. 214 MB in all. - Pilot/operator aircraft accident report, NTSB form 6120.1 (item 1, PDF, 9 pages, 11.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=11989576&FileExtension=pdf&FileName=6120%20printed_Redacted-Rel.pdf - Airframe and engine examination observations (item 2, PDF, 9 pages, 5.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=12218106&FileExtension=pdf&FileName=WPR20LA308%20Wreckage%20Examination%20Summary%20Report2-Rel.pdf - Record of conversation - local law enforcement regarding fuel (item 3, PDF, 1 page, 119 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=11991294&FileExtension=pdf&FileName=ROC%20leo%20regarding%20fuel-Rel.pdf - Air traffic control recording (item 4, WAV, 176 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=11991541&FileExtension=wav&FileName=Distribution%201-Rel.wav - Radar tabular data - ADS-B (item 5, CSV, 16.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=12217095&FileExtension=csv&FileName=20200912_AA443D_435515491_ADSB-Rel.csv - Google earth - adsb data (item 6, KMZ, 952 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=12217763&FileExtension=kmz&FileName=20200912_AA443D_435515491-Rel.kmz - Estimated fuel burn calculations (item 7, PDF, 2 pages, 115 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=11551242&FileExtension=pdf&FileName=ROM%20fuel%20calculations-Rel.pdf - Statement of party representatives to NTSB investigation (item 8, PDF, 1 page, 177 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=11552186&FileExtension=pdf&FileName=party%20form%20piper_Redacted-Rel.pdf - Release of aircraft wreckage, NTSB form 6120.15 (item 9, PDF, 1 page, 513 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=12245746&FileExtension=pdf&FileName=Wreckage%20Release%20N7602Y_Redacted-Rel.pdf - On scene photos (item 10, PDF, 3 pages, 2.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=11553826&FileExtension=pdf&FileName=on%20scene%20photos-Rel.pdf From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.