WPR14FA188 · Mooney M20C
Mooney M20C · Accident: controlled flight into terrain/object (CFIT) en route
From Yellowstone Regional Airport (COD) to Joslin Field Magic Valley Regional Airport (TWF)
Event
- NTSB case
- WPR14FA188
- 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
- 2 · 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
- Instrument Meteorological Cond
Mooney M20C
- Aircraft type
- Mooney M20
- 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
- N6704U
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Yellowstone Regional Airport (COD), Cody, WYTo Joslin Field Magic Valley Regional Airport (TWF), Twin Falls, ID
- Aircraft age
- About 51 years (built 1963)
- 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 · cruise
- 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)
- 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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The two pilots were on a multi-leg cross-country trip in the airplane to visit friends and relatives. Both pilots had current medical certificates, and it could not be determined who was acting as pilot-in-command at the time of the accident. The pilot seated in the right front seat had owned the airplane for over 20 years and had accumulated considerable experience flying it. Neither pilot had an instrument rating.
Postaccident review of meteorological information indicated that at the time of the flight's departure, the departure and arrival airports were reporting visual meteorological conditions; however, the initial segment of the flight required flight over mountainous terrain where instrument meteorological conditions (IMC) and mountain obscuration existed. There was no record of either pilot having obtained an official weather briefing before the flight; however, they were most likely aware of the mountain obscuration, as it would have been visible before takeoff and during the initial stages of the flight.
The airplane was equipped with a panel-mounted GPS receiver that was capable of providing minimum safe altitude information along a user-defined flight plan, but it is unknown if the pilots were using this feature. An iPad, which the pilots reportedly used for navigation, was found in the cockpit; however, impact damage to the device prevented determination of what navigation software was installed. Additionally a sectional chart covering the accident area was on board; however, the chart was found stowed in the rear pocket of the left front seat, indicating that the pilots were not using it during the flight.
Radar and weather data revealed that the airplane entered the clouds shortly after takeoff. The flight track began to waver slightly about 7 minutes after takeoff, likely due to the airplane being hand-flown as it entered IMC. The flight track remained generally on course toward the destination airport as the flight progressed, and there was no indication of an attempt to return to the departure airport. The airplane flew through the mountainous terrain at a fairly consistent altitude about 2,500 ft below the maximum elevation figure of 12,500 ft mean sea level shown on the sectional aeronautical chart for the area and eventually struck the side of a mountain about 430 ft below its summit.
The consistency of the airplane's flight track indicates that the pilots most likely intentionally elected to enter IMC in an effort to fly over the mountainous terrain and into the clearer weather beyond. The airplane's altimeter was set to the correct pressure, and postaccident examination did not reveal any anomalies with the airframe or engine that would have precluded normal operation. The investigation was unable to determine why the pilots elected to fly at an altitude below the maximum elevation for the area.
While both pilots had reported histories of significant cardiovascular disease, autopsies and toxicological analysis did not reveal any findings that would have contributed to the accident. Although ethanol was detected in the right-seat pilot's urine, the levels were not sufficient to have caused impairment.
Probable cause
The non-instrument rated pilots’ decision to continue flight into known instrument meteorological conditions over mountainous terrain, which resulted in controlled flight into terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR14FA188
- Event ID
- 20140512X20858
- Case number
- WPR14FA188
- 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: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 8f16a4d59f743b8c41ec7d3ae9b9404b2de6b20b9b527efbd3cc24c285674a5d; retrieved 2026-09-14T17:17:35.691Z.