FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR22FA184 · Bruce R Prouse M24 ORION PLUS

22 May 2022 · Cape Girardeau, MO, United States

Bruce R Prouse M24 ORION PLUS · Accident: loss of control in flight on approach

From an unrecorded airport to Sioux Falls, SD

Report a problem

Event

NTSB case
WPR22FA184
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
1 · 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

Bruce R Prouse M24 ORION PLUS

Aircraft type
Bruce R Prouse M24
Category
Gyroplane
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
N590DM
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo Sioux Falls, SD
Aircraft age
Built the same year (2022)
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
Approach · VFR pattern downwind
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
Substantial

Cause areas

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

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

NTSB narrative

The pilot was ferrying a gyroplane from Gulf Shores, Alabama, to his home in South Dakota. He made an overnight stopover in Cape Girardeau, Missouri, as part of his planned route of flight. The following morning he requested progressive taxi instructions from air traffic control to the assigned departure runway. After he taxied to the runway he departed to the northwest, consistent with what he told the controller. However, shortly into his climb, he reported to the controller that he wanted to return to the airport and the controller cleared him to land on his departure runway. The gyroplane flew the airport traffic pattern back to the runway to land; however, during the downwind leg the gyroplane rapidly descended to the ground following a loud crack that was heard by a witness at the airport. Postaccident examination of the gyroplane revealed no preimpact mechanical anomalies or malfunctions with the airframe or engine that could have precluded normal operation. Data retrieved from an onboard recording system suggests that the engine performance was unremarkable and consistent with the throttle movements throughout the final moments of the flight. Paint transfer marks on the rotor blades suggested that the main rotor contacted the horizontal stabilizer right winglet in the final moments of the accident flight, which was likely the source of the “crack” sound heard by the witness. The postaccident examination revealed evidence of severe blade flapping from a partial bend of the teetering stop of one of the main rotor blades and rotor contact with the horizontal stabilizer, which is typically due to a several-second low g or zero rotor load condition that slows the autorotation speed of the rotor. This condition was likely the result of the 270° hard left roll before the gyroplane rapidly descended and impacted the ground. Without the ability to maintain a load on the rotor in the full roll over, the rotor would have slowed and began severe flapping. The investigation was unable to determine the reason for such a severe control input (hard left roll) based on the available evidence. The evidence does indicate distress in the pilot’s voice and that he had opened his door at some point during the flight. There was no damage to the door latches and the door was found at the same distance from the main wreckage as the right horizontal stabilizer (about 170 ft). As a door annunciation would have informed the pilot if the door was not properly latched on takeoff, it is likely that this occurred in flight, and was possibly intentional if the pilot anticipated a hard landing. The accident was the result of the pilot’s failure to maintain controlled flight, which resulted in a hard left roll, excessive blade flapping, and a subsequent inflight separation of the right horizontal stabilizer.

Probable cause

The pilot’s failure to maintain controlled flight, which resulted in a hard left roll, excessive blade flapping and a subsequent in-flight separation of the right horizontal stabilizer.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR22FA184
Event ID
20220522105112
Case number
WPR22FA184
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, cause areas. 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: 139e119171e412c6e4043cf4eea7185c306ff017a8decb783ce993dec32b16c5; retrieved 2026-09-15T07:44:36.141Z.