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

April 20, 2020 · Piper PA31T 1 · N926K

Billings, MT

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
April 20, 2020
Injury Outcomes
1 injury (1 fatality)
Location
Billings, MT
Aircraft
Piper PA31T 1 (1980)
Tail Number
N926K
Injuries
Fatal
Aircraft Damage
Destroyed
NTSB Number
WPR20LA128

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.

NTSB Probable Cause

The degraded airplane performance after takeoff for reasons that could not be determined from available evidence.

Full Narrative

HISTORY OF FLIGHTOn 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. PERSONNEL INFORMATIONThe 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 pilot completed 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. AIRCRAFT INFORMATIONThe 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. AIRPORT INFORMATIONThe 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. WRECKAGE AND IMPACT INFORMATIONGround 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. TESTS AND RESEARCHThe 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.

Flight

Event TypeAccident
Event Time09:50 MDT
Nearest AirportBillings Logan Intl (1nm WNW)
Runway28L
Runway Length3800 ft
Runway Width75 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireGrd
Aircraft ExplosionGrd

Aircraft

AircraftPiper PA31T 1
Tail NumberN926K
Aircraft CategoryAir
DamageDestroyed
Operating RulePart 91
Engine TypeTurboprop
Engine DetailsPratt & Whitney · PT6A-11 · Turboprop · 550 | Pratt & Whitney · PT6A-11 · Turboprop · 550

People & Injuries

Injury Summary1 injury (1 fatality)
Fatal1
Serious0
Minor0
Uninjured0
Total1
Crew 1Age 64 · First Class · Fatal

Conditions

ConditionsVMC
LightDaylight
Wind290° @ 14 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point57 / 28 C
Altimeter29.97 inHg
Observation Time15:53
Weather SourceWFAC

Appendix: Source Data