# NTSB WPR20LA128: Piper PA31T, N926K, Billings, MT, April 20, 2020 - Type: NTSB accident investigation - Classification: Accident · Fatal · Class 3 · Limited · Final report - Date: April 20, 2020, 09:50 local (15:50 UTC) - Place: Billings, MT - Coordinates: 45.816944, -108.589164 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=45.8169&lon=-108.5892&mi=10 - Phase of flight: [Initial climb](https://openairdocs.org/ntsb-phases/350) (OpenAirDocs' grouping) - Defining event: [Initial climb: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) - Highest injury: Fatal - Injuries: 1 fatal - Status: Completed - Report: Approved by Office Director - Investigation class: Class 3 - NTSB office: Western Pacific Region - Parties: Piper Aircraft, Hartzell Propeller, FAA-FSDO - NTSB case key (mKey): 101183 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR20LA128 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/101183/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=101183 - Page: https://openairdocs.org/ntsb/WPR20LA128 ## Probable cause The degraded airplane performance after takeoff for reasons that could not be determined from available evidence. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: climb rate](https://openairdocs.org/ntsb-findings/01062035): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Piper PA-31T1, 1 case](https://openairdocs.org/ntsb-findings/01062035/cases.md?model=7103126), [All aircraft, 265 cases](https://openairdocs.org/ntsb-findings/01062035/cases.md) - [Not determined](https://openairdocs.org/ntsb-findings/05000000): Not determined › Not determined · Unknown/Not determined (probable cause); cases with it: [Piper PA-31T1, 3 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md?model=7103126), [All aircraft, 2,247 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Initial climb: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) (defining event); cases with it: [Piper PA-31T1, 1 case](https://openairdocs.org/ntsb-events/490/sequence.md?model=7103126), [All aircraft, 1,309 cases](https://openairdocs.org/ntsb-events/490/sequence.md) ## Analysis Air traffic control communications revealed that the pilot requested to take off from the departure runway so that he could perform traffic pattern work and return for a landing on the left adjacent runway. Shortly after takeoff and while departing to the west, the pilot was instructed twice to enter the left traffic pattern, with no response. Radar data showed the airplane departing the runway and remaining on runway centerline heading for the length of the flight. The airplane climbed to about 100 ft above ground level and the airplane’s groundspeed increased to 81 knots soon after departure then decreased to 70 knots before dropping off radar. Witnesses reported seeing the airplane depart the airport at a low climb rate and slow airspeed. Shortly after, the airplane flew out of view and a column of smoke was seen on the horizon. Accident site documentation identified symmetrical propeller strikes on the ground consistent with the airplane impacting the ground in a shallow, nose-up, wings level attitude. Examination of the airframe and both engines did not reveal any evidence of a preaccident mechanical failure or malfunction that would have precluded normal performance to allow for sufficient airspeed and climb rate after takeoff. Both the engines exhibited damage signatures consistent with the engines producing symmetrical power at impact. The pilot’s most recent flight in the accident airplane was 2 months before the accident. The pilot was reported to have problems with understanding the accident airplane’s avionics system; however, it is unknown if he was having these problems during the accident flight. Review of the pilot’s medical history revealed no significant medical concerns or conditions that could pose a hazard to flight. ## Factual narrative The airplane was manufactured in 1980. The airplane was a multiengine, all-metal, low-wing, with a retractable tricycle landing gear configuration. It was equipped with two 550-shaft-horsepower Pratt and Whitney turbine engines. The last inspection was completed on November 25, 2019, at an airplane total time of 4,696 hours of operation. On April 20, 2020, about 0950 mountain daylight time, a Piper PA-31T1 airplane, N926K, was destroyed when it was involved in an accident about 1 1/2 miles west of Billings Logan International Airport (BIL), Billings, Montana. The airline transport pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 local flight. According to air traffic control information, the pilot requested to taxi to runway 28L for takeoff, perform pattern work at BIL, and return to land on runway 28R. After the pilot held short of runway 28L, the controller cleared the pilot for takeoff with instructions to extend the upwind leg. Shortly after takeoff and while departing to the west, the pilot was instructed twice to enter the left traffic pattern for runway 28R, with no response. A subsequent attempt was made to establish communication, with no response. Video from a security camera shows a column of smoke west of the airport about 1.5 minutes after the airplane departed. Radar data showed the airplane departing runway 28L and remaining on runway centerline heading for the length of the flight. The airplane’s altitude climbed to about 100 ft above ground level and the airplane’s groundspeed increased to 81 knots soon after departure, and then decreased to 70 knots before dropping off radar near the accident site. Witnesses located near the departure end of runway 28L watched the airplane through a window. The airplane was lower than normal with its gear not retracted as it neared the end of the runway. All the witnesses moved outside to watch as the airplane flew away from their location. One of the witnesses stated that the airplane had a “slow descent trajectory and a slight-nose up attitude.” The airplane passed over a hill and out of view. None of the witness reportedly saw the accident sequence but saw the column of smoke rising from the accident site. Another witness who was sitting in his vehicle near the accident site saw the airplane pass about 250 ft in front of his position. He reported the airplane’s wings were level, and the landing gear was up when it struck the ground. He lost sight of the airplane as it flew into a nearby coulee. The 64-year-old pilot held an airline transport pilot certificate with rating for multiengine land, single engine land and single engine sea. His most recent first-class Federal Aviation Administration (FAA) airman medical certificate was issued on dated May 22, 2019. At that time, he had reported 12,955 total hours of flight experience and 65 hours in last 6 months. The pilot’s logbooks were not located during the investigation. The pilotcompleted a flight review in the accident airplane in December 2019. According to the flight instructor who conducted the flight review, the pilot seemed “unnerved” by the airplane’s avionics. The flight instructor reported that the pilot was a good pilot but did have to spend some extra time with him with the avionics. Additional training specific to the accident airplane was completed on January 25, 2020. The pilot had flown the airplane eight times in the last three weeks before it was put into scheduled maintenance. The pilot’s last flight before maintenance was on February 13, 2020. While the airplane was down for maintenance, the pilot performed 4 hours of aircraft familiarization in the accident airplane with one of the fixed based operator’s (FBO) employees. This training included weight and balance review, sample loading, and flight log and aircraft time verification in the avionics system. Additional to the training, the pilot had an hour of avionics run-up checks by himself. The airplane had been returned to service on February 29, 2020. The engines were shipped to the manufacturer where examinations were conducted on both engines with the FAA conducting the federal oversight. According to the manufacturer, the examination did not reveal any evidence of any pre-impact mechanical anomalies that would have precluded normal operation. The rotational scoring on the compressor and power turbines of both engines are consistent with the engines producing symmetrical power at the time of the impact. Ground scars found near the top of a coulee consisted of the airplane’s fuselage impact mark and symmetrical propeller strikes consistent with the airplane impacting the ground in a shallow, nose-up, wings-level attitude. The airplane continued about 410 ft over the coulee and about 75 ft down the side before impacting the terrain where a postimpact fire ensued. All major structural components of the airplane were located within the debris field. Figure 1-Accident site, initial ground impact marks. The FAA and a representative from Piper Aircraft Company responded to the accident site, and onsite photographic documentation was accomplished. An airframe examination was performed at the accident site and the wreckage was recovered to a secured facility. ## Aircraft - Registration: [N926K](https://openairdocs.org/deregistered/N926K-2021-01-30), registration cancelled 2021-01-30, S/N 31T8004046, built 1980 (OpenAirDocs) - Reported make and model: Piper PA31T (1) - Registry model: [Piper PA-31T1](https://openairdocs.org/model/piper-pa-31t1) (registry code 7103126) (OpenAirDocs) - Registry engine: [Pratt & Whitney PT6A series](https://openairdocs.org/engine/pratt-whitney-pt6a-series) (registry code 52032, turbo-prop) (OpenAirDocs) - Category: Airplane - Serial number: 31T8004046 - Year built: 1980 - Airframe hours: 4696 - Engines: Pratt & Whitney PT6A-11 550 horsepower turbo prop; Pratt & Whitney PT6A-11 550 horsepower turbo prop - Damage: Destroyed - Fire: On-Ground - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: November 25, 2019 - Departed: BIL, Billings, MT - Destination: BIL, Billings, MT - Airport: BIL, Billings Logan Intl, runway 28L, 3,800 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 64; injuries: fatal; airline transport, commercial; airplane ratings: single-engine land, single-engine sea, multi-engine land; instrument ratings: airplane; medical: class 1, with waivers/limitations; seat: left; toxicology performed; flight hours: 12,955 total ## Weather - Conditions: Visual (VMC), Day - Wind: 290° at 14 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 57 °F, dew point 28 °F - Altimeter: 29.97 inHg - Observed at: KBIL, 2 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 20200420001119A](https://openairdocs.org/incident/20200420001119A), Apr 20, 2020: Piper PA-31T1, Billings, MT, Destroyed, 1 fatal. Following departure the pilot failed to gain sufficient altitude for normal flight - impacted ground just over 1.4 miles from departure end of runway. Post… ## Docket (15 files) The files NTSB released with the investigation on November 10, 2022, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=101183. 121 MB in all. - Faa-witness statement synopsis (item 1, PDF, 2 pages, 124 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13259992&FileExtension=pdf&FileName=N926K%20-%20Witness%20Statement%20Synopsis_Redacted-Rel.pdf - Faa-interview with flight instructor (item 2, PDF, 1 page, 99 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=14382233&FileExtension=pdf&FileName=Email%20FAA%20Interview%20with%20CFI_Redacted-Rel.pdf - Hartzell propeller-teardown report (item 3, PDF, 32 pages, 7.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13259456&FileExtension=pdf&FileName=WPR20LA128%20Propeller%20Teardown%20Report%20200420%20-%20FINAL_Redacted-Rel.pdf - P&w accident/incident report (item 4, PDF, 90 pages, 16.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=14686071&FileExtension=pdf&FileName=10234%2010239%20RF20-042%20Billings%20Montana%20NTSB%20docket%20version-Rel.pdf - Edwards jet center fuel invoice (item 5, PDF, 1 page, 69 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=14728653&FileExtension=pdf&FileName=Edwards%20Jet%20Center%20Fuel%2020200227_Redacted-Rel.pdf - Edwards jet center fuel testing record (item 6, PDF, 2 pages, 4.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=14381822&FileExtension=pdf&FileName=Edwards%20Jet%20Center%20Fuel%20SUMP%20Records_Redacted-Rel.pdf - Pilot's previous flights in N926K (item 7, PDF, 1 page, 403 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=14381832&FileExtension=pdf&FileName=Lloyd%27s%20flights-Rel.pdf - Maintenance logbook-last inspection entry (item 8, PDF, 1 page, 2.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=14384613&FileExtension=pdf&FileName=Mx%20Logbook-Last%20Inspection%20Entry_Redacted-Rel.pdf - Statement of party representatives to NTSB investigation-hartzell (item 9, PDF, 14 pages, 680 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=14599605&FileExtension=pdf&FileName=Party%20Form-Hartzell_Redacted-Rel.pdf - Statement of party representatives to NTSB investigation-piper (item 10, PDF, 1 page, 126 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13260002&FileExtension=pdf&FileName=Piper%20Party%20Form_Redacted-Rel.pdf - Release of aircraft wreckage, NTSB form 6120.15 (item 11, PDF, 1 page, 125 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=14692610&FileExtension=pdf&FileName=Retention-Release-of-Wreckage-Form%20FMR%20Aviation_Redacted-Rel.pdf - Toxicological report (item 12, PDF, 1 page, 219 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=14599633&FileExtension=pdf&FileName=2020_053_001tox%20redacted-Rel.pdf - Photo array-courtesy of the FAA (item 13, PDF, 10 pages, 5.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=14382073&FileExtension=pdf&FileName=Photo%20Array-FAA-Rel.pdf - Video (item 14, MP4, 84.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=14382650&FileExtension=mp4&FileName=Video%204_Billings%20Flying%20Servivce%20Security%20Cam%20-%20%2020200422%20_time%20-%201605_35-Rel.mp4 - Memorandum of record-autopsy report summary (item 15, PDF, 1 page, 66 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=14746984&FileExtension=pdf&FileName=MOR%20Autopsy-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.