The U.S. aircraft register, updated daily
Accidents · NTSB WPR19FA154 · Final report

Cirrus SR22 accident near Grover, Utah, May 24, 2019

On May 24, 2019 at about 5:16 pm local time, a 2006 Cirrus SR22, registered N809SR, was destroyed in an accident during enroute near Grover, Utah. It was a personal flight under general aviation rules (Part 91). 2 people were killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's encounter with moderate to severe icing conditions during cruise flight, which resulted in structural icing and a subsequent loss of control. Contributing to the accident was the pilot’s decision to continue a flight route through known moderate to severe icing conditions.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
May 24, 2019 · about 5:16 pm local time
Place
Grover, Utah · map
Type
Accident
Injuries
2 people were killed.
Weather
visual conditions (good weather)
Aircraft
Cirrus SR22 Undesignat, built 2006 · all SR22s on the register
Registration
N809SR · no longer on the register · serial 2129
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot departed on an instrument flight rules cross-country flight and climbed to a cruise altitude of 14,000 ft mean sea level (msl). About 30 minutes into the flight, he requested a climb to 16,000 ft msl. Radar data indicated that over the next several minutes, the airplane climbed to 14,500 ft, then began an increasingly rapid descent as its groundspeed decayed from about 111 knots (kts) to about 64 kts before radar contact was lost. Witnesses reported that they heard the airplane and looked up to see it descending nose down like a corkscrew before it impacted terrain. Postaccident examination of the airframe and engine did not reveal any anomalies that would have precluded normal operation. AIRMET Zulu for moderate icing conditions was valid for the area of the accident site at the time of the accident, and an atmospheric sounding supported the likely formation of moderate rime and mixed-type icing in the area. The sounding also indicated the potential for supercooled large droplet icing formation near the top of the cloud layer near 15,000 ft msl. Satellite imagery depicted cumulus and cumulus congestus type clouds with vertical development over the flight track and accident site, and weather radar imagery depicted the airplane entering an area of light-to-moderate intensity echoes just before radar contact was lost. Immediately before and after the accident, two other aircraft operating at similar altitudes reported encountering light clear to mixed icing conditions. The pilot had received preflight weather information containing the relevant forecasts and advisories. In addition, the airplane was equipped with a TKS ice protection system, but it was heavily fragmented during the accident sequence and the investigation was unable to determine if the system was activated or working at the time of the accident. It is likely that, during the last minutes of the flight, the airplane encountered moderate-to-severe icing conditions, which adversely affected the airplane's handling characteristics and likely resulted in a loss of control.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Structural icing during enroute defining event
  2. Loss of control in flight during enroute (change of cruise level)
  3. Collision with terrain or object (not controlled flight into terrain) during enroute (change of cruise level)

The NTSB's findings

  • cause Environmental issues › Conditions/weather/phenomena › Temp/humidity/pressure › Conducive to structural icing › Effect on operation
  • factor Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • Environmental issues › Conditions/weather/phenomena › Temp/humidity/pressure › Conducive to structural icing › Decision related to condition

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 930 hours in all
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: unk
  • Injury: fatal

The aircraft

  • Airframe total time: 2,672 hours
  • Last inspection: 100-hour inspection, April 16, 2019; 36 hours since
  • Seats: 4
  • Landing gear: fixed
  • Engine: Continental Motors IO-550-N (piston); 0 hours total
  • Fire on the ground

The flight

  • Departed from: CNY Moab UT at 4:42 pm
  • Destination: HND Las Vegas NV
  • Flight plan: IFR

Weather at the time

  • Light: daylight
  • Wind: from 170° at 6 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 59°F (15°C), dew point 36°F (2°C)
  • Altimeter: 30.04 inHg
  • Observation at 5:55 pm from HVE, 30 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

13 documents, released by the NTSB on January 21, 2021. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.