WPR19FA084 · Cirrus SR22 Undesignat
Cirrus SR22 Undesignat · Accident: VFR encounter with IMC en route
From Craig Moffat Airport (CAG) to Joslin Field Magic Valley Regional Airport (TWF)
Event
- NTSB case
- WPR19FA084
- 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
- Visual Meteorological Cond
Cirrus SR22 Undesignat
- Aircraft type
- Cirrus SR22
- 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
- N917SR
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Craig Moffat Airport (CAG), Craig, COTo Joslin Field Magic Valley Regional Airport (TWF), Twin Falls, ID
- Aircraft age
- About 14 years (built 2005)
- 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 · descent
- 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
- VFR encounter with IMC
- 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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The noninstrument-rated pilot departed on a visual flight rules (VFR) 336 nautical mile (nm) cross-country flight to the northwest in a direct path toward the destination airport. Shortly after departure, the pilot advised air traffic control that he would be diverting to the south for weather; a cold front was passing over the route of flight, in which both VFR and instrument meteorological conditions (IFR) prevailed. About 1 hour and 27 minutes into the flight, the controller suggested to the pilot that in order to circumvent the weather, he fly from his present position southwest to an alternate airport, where he could then turn north to his destination; at this time the alternate airport was about 154 nm southwest of his position. The pilot subsequently advised the controller that he was “…going north to go under [the] deck in about 50 miles. Over the next several minutes, the airplane descended, followed by the controller advising the pilot that he was going in and out of radar contact. The controller provided the pilot a heading to the previously advised alternate airport which was reported as VFR. The pilot arrived at the alternate airport terminal area about 25 minutes after his decision to divert. Witnesses reported that the weather was below VFR minimums, with a solid ceiling of 200 ft above ground level, and visibility between 1/4 and 1/2 mile with snow. They also reported hearing the pilot click his microphone several times to activate the pilot-controlled runway lights. The pilot stated that if he could see the runway he could land, to which one of the witnesses informed the pilot that the runway lights were on. There were no further communications with the pilot. Onboard recorded data revealed that for about the last 10 minutes of flight, the pilot entered the airport terminal area south of the airport on a westerly heading at an altitude of 9,000 ft msl. He subsequently made a 90° right turn toward the north, followed by multiple right and left turns over the airport area at altitudes of between 7,100 ft msl to 7,800 ft msl; the airport elevation was 6,259 ft msl. The pilot then proceeded toward the northeast in a climbing right turn, most likely to proceed eastbound toward a more favorable airport. At this time, it was estimated that the pilot had about 2 hours of fuel remaining, an adequate fuel supply to divert back to the east about 80 nm where a myriad of airports were located that were operating under VFR conditions. However, in an attempt to ascend over a ridgeline to the east of more than 10,750 ft msl, upon reaching an altitude of about 9,400 ft msl, the airplane entered a descending right turn at a rate of descent of about 6,400 ft per minute and an indicated airspeed of about 210 kts, which is consistent with a high rate of descent. As icing was present in the area at the time of the accident, airframe icing most likely precipitated the stall, followed by entering the right spin and subsequent impact with terrain about 3.4 nm northeast of the airport at an altitude of about 6,929 ft msl. The airplane was not authorized for flight into known icing conditions. Postaccident examination of the airframe and engine revealed no mechanical anomalies that would have precluded normal operation. The diversion airport’s ASOS visibility sensor was reporting visibilities which were inaccurate for weeks leading up to the accident, as well as on the day of the accident. The ASOS was scheduled to be repaired that day; however, the technician who was to perform the maintenance was unable to do so due to the weather conditions. Because snowfall intensity reporting was dependent on the visibility observation, inaccurate visibility reporting likely resulted in an unrepresentatively low reported snowfall intensity on the day of the accident. Although the erroneous visibility information provided by the ASOS may have contributed to the pilot’s decision to divert to the airport, as a noninstrument-rated pilot, it remained incumbent upon the pilot to maintain VFR conditions while maneuvering in an attempt to land. Had the pilot been aware of the impending instrument meteorological conditions that he was about to encounter he might have diverted to an airport with better conditions. According to Flight Services, neither they nor any third-party vendors had any contact with the accident pilot.
Probable cause
The pilot’s decision to continue the visual flight rules flight into instrument meteorological conditions and icing conditions which resulted in a high rate of descent and impact with terrain. Contributing to the accident was the inaccurate weather reporting from the airport weather reporting facility.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR19FA084
- Event ID
- 20190216X92232
- Case number
- WPR19FA084
- 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. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2019-02-16.
- API snapshot SHA-256: 2413632ce60e12cd429e4989c7fc1279510c7aa46d5bed8d7af8f00e81f069d4; retrieved 2026-09-15T06:54:23.016Z.