FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR12FA235 · Cirrus SR20

29 May 2012 · Duck Creek Village, UT, United States

Elite Aviation Cirrus SR20 · Accident: aerodynamic stall/spin while maneuvering

From Mesquite Airport (67L) to Bryce Canyon Airport (BCE)

Report a problem

Event

NTSB case
WPR12FA235
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

Cirrus SR20

Aircraft type
Cirrus SR20
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
N187PG
Onboard fatalities
Unknown
Route
From Mesquite Airport (67L), Mesquite, NVTo Bryce Canyon Airport (BCE), Bryce Canyon, UT
Aircraft age
Not recorded
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 · low-altitude flying
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
Aerodynamic stall/spin
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The airplane collided with remote mountainous terrain in an inverted position during the second leg of a cross-country flight in day visual meteorological conditions. Recorded data recovered from the airplane revealed that about 40 minutes into the flight, the airplane reached its highest recorded altitude of 7,847 feet mean sea level (msl). At this time, the airplane was about 4 miles from a mountain ridge directly ahead, the lowest point of which was 8,470 feet msl, with terrain elevations of more than 9,000 feet msl on both sides. The airplane’s recovered electronic data revealed that the airplane’s stall warning system activated about 3 minutes before the accident and remained on for most of the remaining recorded data. The data indicated that the airplane rolled steeply to the left, briefly recovered and pitched up 10 to 15 degrees, and then rolled to the left in a nearly 67-degree inverted nose-down attitude before impacting terrain. Postaccident calculations indicated that at the time of the accident, the airplane was likely being flown close to the airplane’s stall speed.

The pilot, who had rented the airplane, had extensive rotorcraft/helicopter flight experience but had accumulated only about 160 hours total flight time in fixed wing airplanes, with about 17 hours in the accident airplane make and model. The pilot’s most recent flight in the make and model of the accident airplane took place about 18 months before the accident flight.

Postaccident interviews with personnel from the company that rented the airplane revealed that, on a previous occasion, the pilot had been observed overloading the airplane and was advised that he could not take that much baggage on the flight. The company personnel further stated that on the morning of the accident, after the company fueled the airplane for the pilot’s flight, the pilot taxied the airplane to another area on the airport where he loaded his passengers and baggage. This location was about 1/4 mile away and was not visible from the company’s facility. The calculated density altitude at the time of the accident was 9,287 feet, which would have been detrimental to the airplane’s climb performance, especially if the airplane was overloaded. A postaccident examination of the airframe and engine did not reveal any mechanical anomalies that would have precluded normal operation.

Based on the available information, it is likely that the pilot was unable to maintain sufficient airspeed to climb the airplane over the high terrain, which resulted in an aerodynamic stall. Further, it is likely that a combination of the pilot overloading the airplane before taking off and the high density altitude conditions would have resulted in the airplane’s reduced climb performance. Further, the pilot’s lack of total experience operating fixed wing airplanes in mountainous terrain likely negatively affected his decision to attempt to fly over the mountainous terrain with the given conditions and contributed to the accident.

Probable cause

The pilot's failure to maintain sufficient airspeed and airplane control while maneuvering a heavily loaded airplane over high mountainous terrain in a high density altitude environment. Contributing to the accident was the pilot’s lack of experience operating fixed wing airplanes in such an environment.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR12FA235
Event ID
20120530X50747
Case number
WPR12FA235
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: 0d3451ae24882b58f8c049ac4e11daffb400d2d4492c05596dda6ef85cf6f682; retrieved 2026-09-13T22:24:38.246Z.