FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR21LA032 · Cessna 172 M

30 Oct 2020 · Billings, MT, United States

Cessna 172 M · Accident on approach

From Sheridan County Airport (KSHR) to an unrecorded destination

Report a problem

Event

NTSB case
WPR21LA032
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
1 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Cessna 172 M

Aircraft type
Cessna 172
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N124TW
Operator
Donald C Nimmick · private individual
Onboard fatalities
Unknown
Route
From Sheridan County Airport (KSHR), Sheridan, WYTo not recorded
Aircraft age
About 45 years (built 1975)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach · VFR pattern final
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Unknown or undetermined
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Not determined › Not determined

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

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.

Probable cause

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR21LA032
Event ID
20201031102218
Case number
WPR21LA032
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: local date, investigation status, cause areas. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2020-10-31.
  • API snapshot SHA-256: 80b6fde015834f91455b846ccd1d7920a296d6dcb2c41670fc87ec7a639c42de; retrieved 2026-09-15T07:21:53.138Z.