Controlled Flight Into Terrain · NTSB WPR20FA063

Cessna TR182 — Billings, MT

4 fatal High-time pilotNight
DateJanuary 12, 2020
LocationBillings, MT
AircraftCessna TR182
Purpose of flightPersonal
ConditionsNight · Visual Meteorological Cond
Phase / occurrenceEnroute Controlled flight into terr/obj (CFIT)
Pilot age69
Pilot total time13,800 hrs · High time
Time in typeUnknown
Fatalities4

Probable cause

The pilot’s failure to maintain clearance due to poor decision making in selecting an unsafe altitude during cruise flight.

NTSB findings

  • Personnel issues-Action/decision-Info processing/decision-Decision making/judgment-Pilot
  • Personnel issues-Psychological-Attention/monitoring-Monitoring environment-Pilot
  • Personnel issues-Task performance-Use of equip/info-Use of equip/system-Pilot
  • Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Altitude-Not attained/maintained
  • Environmental issues-Physical environment-Object/animal/substance-Tower/antenna (incl guy wires)-Response/compensation
  • Environmental issues-Conditions/weather/phenomena-Light condition-Dark-Effect on operation

What happened

The pilot departed with three passengers to the northwest on a flight at night, without any clouds and good visibility at the pilot’s planned cruise altitudes. The airplane leveled off about 4,792 ft mean sea level (msl) and maintained a similar altitude and height above terrain between 1,400 ft and 2,100 ft above ground level (agl) for most of the flight. The terrain elevation increased in the airplane’s final 40 seconds of flight. The airplane was about 65 ft agl (4,809 ft msl) when it impacted a tower. All occupants were fatally injured, and the airplane was destroyed.

Postaccident examination of the airplane and engine revealed no mechanical malfunctions or anomalies that would have precluded normal operation. The airplane’s primary flight display (PFD) reported barometric altitude adjustable by altimeter setting, and its two multifunction displays (MFDs) reported GPS altitude based on satellite geometry. The flight data showed that the barometric altitude (shown on the PFD) about the time of the accident was 207 ft higher than the GPS altitude (displayed on the MFD at the center of the instrument panel). The pilot, who was also a certified flight instructor, had every opportunity to observe the difference between the GPS and barometric altitudes during his instrument scan. The airplane’s relatively consistent cruise flight altitude during the accident leg suggests that autopilot was engaged. It is unclear from available evidence whether the pilot would have used barometric altitude or GPS altitude to set the autopilot or whether the MFD provided a terrain alert before the accident occurred. However, data from previous flights showed that the pilot had extensive knowledge of the area and had intentionally circumvented this tower at a similar altitude during a flight a few days prior.

The tower did not meet the Federal Aviation Administration’s (FAA) 200-ft minimum height requirement to be lit or placed on an aviation chart. However, the FAA sectional chart, which was available to the accident pilot for this flight, showed the height of the plateau beneath the tower. The pilot instead relied on the MFD terrain map for topographical features and obstacles. A review of the terrain map before the accident flight or during cruise flight would have led a conscientious pilot to maintain a safe distance from terrain by climbing to a higher cruise altitude, consistent with the minimum safety altitudes provided in Federal Aviation Regulations. Thus, despite having a preexisting knowledge of the area topography and obstacles, the pilot exercised poor decision making in operating at a cruise altitude less than the minimum safe altitudes specified in regulations.

An editorial "what led to it / how to avoid it" analysis for this accident is generated separately and will appear here.

View the official NTSB docket →