FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR24FA313 · Cirrus Design Corp SR22

27 Sept 2024 · Provo, UT, United States

Cirrus Design Corp SR22 · Accident: loss of control in flight while maneuvering

From St George Regional Airport (SGU) to an unrecorded destination

Report a problem

Event

NTSB case
WPR24FA313
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
Ongoing
API-reported fatalities
2 · all aircraft and ground
Ground fatalities
0
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 Design Corp SR22

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
N831AZ
Operator
Michael Cox
Onboard fatalities
Unknown
Route
From St George Regional Airport (SGU), Saint George, UTTo not recorded
Aircraft age
About 23 years (built 2001)
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
Maneuvering
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
Loss of control in flight
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

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

On September 27, 2024, about 1010 mountain daylight time, a Cirrus Design Corp. SR-22, N831AZ, was destroyed when it was involved in an accident near Provo, Utah. The pilot and pilot-rated passenger were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. Review of Air Traffic Control Tower communication recordings revealed that the controller instructed the pilot to enter the airport traffic pattern on downwind for runway 13. They later advised the pilot that there was an airplane on final approach to the runway and to follow that airplane. Shortly after, the pilot reported that the other airplane was in sight and the controller subsequently approved a base turn at the pilot’s discretion. As the accident airplane crossed the approach end of runway 13, the controller told the pilot to go around and that there was an airplane on the runway. The pilot replied that he was going around and that the other airplane was still on the runway. The controller asked the pilot if he was able to turn right to the downwind leg, to which the pilot replied he was able to do so. The controller cleared the pilot to land on runway 13, to which they acknowledged. No further radio transmissions from the pilot were heard. An airport surveillance video showed the first airplane approach runway 13 and perform a touch and go landing. The accident airplane then came into view and about 50 ft above ground level, entered a climb, and veered to the right before going out of view of the camera. Both airplanes appeared to be about 200 ft from each other. Preliminary ADS-B data showed the accident airplane remained within the airport traffic pattern and turned onto the downwind leg at a ground speed of about 110 knots. The data showed that a few moments later, just before the airplane initiated a right turn to the base leg for runway 13, and that the ground speed had decreased to about 80 knots. Shortly after the right turn was initiated, the ADS-B data ended over Utah Lake near the accident site. A witness in another airplane reported that they observed the accident airplane “bank sharply then stall” before it “fell into a rapid descent with 3 rotations.” The witness added that he saw the airplane’s parachute start to deploy just prior to the airplane impacting the water. The airplane came to rest submerged in about 9 ft of water about 2 miles northwest of the approach end of runway 13. The airplane plane was heavily fragmented. All major components of the airplane were recovered from the water with the exception of both flaps, ailerons and the propeller assembly. The wreckage was relocated to a secure facility for further examination.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record WPR24FA313
Event ID
20240927195213
Case number
WPR24FA313
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (5)
  • 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, coordinates. 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: e9c02f1817830fa2210e824c7e9e8ba8475b34ac84df5896c194bc1ec53f0bf0; retrieved 2026-09-15T08:58:33.893Z.
  • Corrected after a review of the NTSB narrative, which states these values explicitly: damage. The narrative states the airplane was destroyed and describes heavy fragmentation after impact with the water.