WPR22FA053 · Russell W Dyer VORTEX
Russell W Dyer VORTEX · Accident: loss of control in flight en route
Event
- NTSB case
- WPR22FA053
- 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
Russell W Dyer VORTEX
- Aircraft type
- Russell W Dyer VORTEX
- Category
- Helicopter
- 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
- N425RD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 2 years (built 2019)
- 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 · cruise
- 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
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
A witness reported seeing the gyroplane flying straight and level about two miles from the departure airport. The witness reported the gyroplane then tumbled tail over nose three times before he lost sight of it below the tree line. The gyroplane sustained substantial damage when it impacted the heavily vegetated terrain. The smell of fuel was present at the accident site and there was no evidence of a wire or bird strike. Additionally, there were no reports of downed power lines or power outages in the accident area. Examination of the gyroplane revealed no evidence of any preaccident mechanical malfunctions or failures that would have precluded normal operation. The gyroplane was equipped with a horizontal stabilizer that remained intact. The engine was likely producing power at the time of the accident, because two of its propeller blades contacted the main rotor blades during the accident sequence. The main rotor blades sustained minimal damage, consistent with the gyroplane entering a low-rotor-rpm state for undetermined reasons before ground impact. According to the Federal Aviation Administration (FAA), FAA-H-8083-21, Chapter 21, Gyroplane Emergencies, if rotor force is rapidly removed, some gyroplanes may pitch forward abruptly into a power pushover event and if not corrected can continue to tumble and become irreversible.
Probable cause
The pilot’s loss of control for reasons that could not be determined and the delayed remedial action to recover from the power pushover event.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR22FA053
- Event ID
- 20211203104342
- Case number
- WPR22FA053
- 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: b180b65ed7d4f73c7fa4ecbff49c5afc472d78d3018dddc53ff0b38474a7cffa; retrieved 2026-09-15T07:38:05.095Z.