The U.S. aircraft register, updated daily
Accidents · NTSB WPR21LA032 · Final report

Cessna 172 accident near Billings, Montana, October 31, 2020

On October 31, 2020 at about 1:05 am local time, a 1975 Cessna 172, registered N124TW, was substantially damaged in an accident during approach (VFR pattern final) near Billings, Montana (Billings Logan International A airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot’s failure to maintain the proper descent glide path while on final approach for reasons that could not be determined from available evidence.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
October 31, 2020 · about 1:05 am local time · cases in 2020
Place
Billings, Montana · Billings Logan International A · cases near this airport · map
Type
Accident
Injuries
1 person was killed.
Weather
visual conditions (good weather)
Aircraft
Cessna 172 M, built 1975 · all 172s on the register
Registration
N124TW · no longer on the register · serial 17265696
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot departed on the last leg of a multi-leg cross-country flight during dark night conditions. Air traffic control communications indicate he reported encountering wind shear, turbulence and difficulties continuing the flight at night with strong headwinds. The pilot also reported that he was not able to climb to an altitude to safely navigate mountainous terrain and needed to divert to another airport. During the approach the pilot was unable to identify the runway from other flashing lights that were likely part of a planned memorial procession and light display that was lined up near the airport. The controller gave the pilot a position report and the pilot reported that he thought he had the airport in sight. The controller advised the pilot to maneuver as necessary and to maintain an altitude of 4,500 ft mean sea level (msl) or higher. After some maneuvering the pilot reported that he did not have the runway in sight. The controller then requested that he pass over the top of the airport and the pilot replied he had the runway in sight. During the approach the pilot impacted trees and terrain about 3/4 mile from the runway. The accident site examination revealed that the airplane impacted a large tree and then terrain which was located along the runway centerline. Branches surrounding the large tree revealed propeller strike marks, suggesting an undetermined amount of engine power during the accident sequence. The postaccident examination of the airframe and engine revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. An airplane performance study revealed that airspeed and airplane attitude information estimated from automatic dependent surveillance-broadcast equipment and winds aloft data indicate that the airplane impacted a tree and terrain while in a controlled descent and that an aerodynamic stall was not likely a factor. The airplane was operating at altitudes between 7,000 and 11,000 ft msl for most of the 2 hour 6-minute accident flight, and it was night for the last 30 minutes with the airplane largely operating between 4,000 and 9,000 ft msl. The pilot’s severe cardiovascular disease placed him at increased risk of an acute cardiac event such as ischemia or arrhythmia that can cause sudden incapacitating symptoms and leave no evidence at autopsy. Whether the pilot was impaired or incapacitated by his cardiac disease or some other medical condition at the time of the accident could not be determined by this investigation. However, whether the cause of the airplane’s behavior was due to an incapacitating medical condition, distraction, wind shear, or some other factor is not known from the available operational information.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Unknown or undetermined during approach (VFR pattern final) defining event

The NTSB's findings

  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Descent/approach/glide path › Not attained/maintained
  • Not determined › Not determined › (general) › (general) › Unknown/Not determined

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 851 hours in all; 51 in the last 90 days
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: fatal

The aircraft

  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-320 (piston); 0 hours total

The flight

  • Departed from: KSHR Sheridan WY at 4:52 pm
  • Flight plan: none
  • Runway 25, 5,501 ft by 75 ft

Weather at the time

  • Light: night
  • Wind: from 250° at 12 knots
  • Visibility: 10 statute miles
  • Sky: a few clouds at 9,000 ft
  • Temperature: 57°F (14°C), dew point 28°F (-2°C)
  • Altimeter: 29.60 inHg

Weather report (METAR): SPECI KBIL 310117Z 24014KT 10SM FEW090 FEW130 SCT200 14/M02 A2960 RMK AO2 T01391022=

Injuries

FatalSeriousMinorNone
Flight crew1

Photographs from the investigation 10 pictures from the NTSB's docket, as the NTSB released them

The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.

Documents from the investigation the NTSB's docket: the evidence folder behind the report

20 documents, released by the NTSB on March 16, 2023. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

#DocumentWhat it is
1 Security Video video View Download
2 Photo Array-google Earth Flight Track Images PDF, 5 pages · our copy View Download
3 Photo Array-accident Site, Courtesy of the FAA PDF, 5 pages · our copy View Download
4 ADS-B Raw Data PDF, 62 pages · our copy View Download
5 NTSB Wreckage Examination Summary PDF, 8 pages · our copy View Download
6 Record of Memorandum B Nimmick PDF, 1 page · our copy View Download
7 Fuel Receipt PDF, 1 page · our copy View Download
8 Statement of Party Representatives to NTSB Investigation-textron Aviation PDF, 1 page · our copy View Download
9 Statement of Party Representatives to NTSB Investigation-lycoming PDF, 11 pages · our copy View Download
10 Weather Factual Report PDF, 23 pages · our copy View Download
11 Weather Attachment 1 PDF, 1 page · our copy View Download
12 Weather Attachment 2 PDF, 7 pages · our copy View Download
13 Weather Attachment 3 PDF, 642 pages · our copy View Download
14 Weather Attachment 4 spreadsheet · our copy Download
15 FAA Accident Package ATC Transcript Excerpt PDF, 5 pages · our copy View Download
16 Airplane Performance Study PDF, 14 pages · our copy View Download
17 Toxicology Report PDF, 1 page · our copy View Download
18 Memorandum of Record-autopsy Report Summary PDF, 1 page · our copy View Download
19 NTSB Medical Factual Report PDF, 3 pages · our copy View Download
20 Release of Aircraft Wreckage, NTSB Form 6120.15 PDF, 1 page · our copy View Download

The same docket at the NTSB.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/WPR21LA032.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.