WPR20FA063 · Cessna TR182
Marginal Aviation Cessna TR182 · Accident: controlled flight into terrain/object (CFIT) en route
From Big Horn County Airport (00U) to Roundup Airport (RPX)
Event
- NTSB case
- WPR20FA063
- 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
- 4 · 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 TR182
- Aircraft type
- Cessna 182
- 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
- N736YU
- Operator
- Marginal Aviation
- Onboard fatalities
- Unknown
- Route
- From Big Horn County Airport (00U), Hardin, MTTo Roundup Airport (RPX), Roundup, MT
- Aircraft age
- About 42 years (built 1978)
- 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
- En route
- 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
- Controlled flight into terrain/object (CFIT)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tower/antenna (incl guy wires)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Physical environment
- Personnel issues › Action/decision
- Personnel issues › Psychological
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
The pilot’s failure to maintain clearance due to poor decision making in selecting an unsafe altitude during cruise flight.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR20FA063
- Event ID
- 20200112X30726
- Case number
- WPR20FA063
- 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, coordinates, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2020-01-12.
- API snapshot SHA-256: 170f85ead18b1a3552e97c7fa9e2ed8670031680163aa2a1daf3f4efc7b00a71; retrieved 2026-09-15T07:10:38.057Z.