FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN24FA248 · Rotorway Scorpion 133

5 Jul 2024 · Andale, KS, United States

Rotorway Scorpion 133 · Accident: mast bumping while maneuvering

From Andale, KS (private airstrip) to an unrecorded destination

Report a problem

Event

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

Rotorway Scorpion 133

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
N51017
Operator
Unknown
Onboard fatalities
Unknown
Route
From Andale, KS (private airstrip)To not recorded
Aircraft age
About 36 years (built 1988)
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
Mast bumping
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

  • Aircraft › Aircraft oper/perf/capability
  • Aircraft › Aircraft propeller/rotor
  • Personnel issues › Action/decision

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

NTSB narrative

The pilot departed from his residence on a local area flight to practice maneuvers in the experimental helicopter. A witness heard a loud “bang” and observed debris separating from the helicopter as it descended to the ground. Surveillance camera audio captured the sound of the helicopter’s experimental engine at a constant high-power setting, followed by a momentary reduction in power. Shortly thereafter, the audio captured multiple impacts and the helicopter came into view inverted, then descended to the ground. A postimpact fire consumed the wreckage. Postaccident examination of the wreckage found that the aft tailboom had separated from the helicopter and was located about 150 yards from the main wreckage. An impact mark consistent with the shape of a main rotor blade was noted at the right side of the tubular structure at the separation area, consistent with a main rotor blade impact. While no mechanical anomalies were found during the airframe and engine examination, the examination was limited due to extensive fire damage. The throttle control cable was found thermally separated from the collective control and the snap-out ball joint was not in the safety position; it was found separated from the carburetor. However, the surveillance audio of the engine’s reduction and increase of rpm before the main rotor’s impact with the tailboom are consistent with an intact throttle control and indicate that the throttle cable likely separated from the carburetor during the impact with terrain. The pilot did not hold a helicopter rating. His last solo endorsement was October 07, 2022, and was valid until January 05, 2023. The accident occurred 18 months after the expiration of the last solo endorsement, and the pilot was not authorized to conduct solo flight operations at the time of the accident. The pilot previously reported that he felt uncomfortable performing autorotations and requested additional training from a flight instructor; however, it was unknown what maneuvers he was performing during the accident flight. Teetering main rotor systems, such as the one on the accident helicopter, are particularly susceptible to main rotor mast bumping during the low-G conditions that result from abrupt forward (nose-down) cyclic inputs. Based on the available evidence the pilot likely applied abrupt control inputs while performing an unknown maneuver, which resulted in main rotor mast bumping during a low-G condition and subsequent main rotor blade contact with and subsequent separation of the tailboom..

Probable cause

The pilot’s abrupt control inputs, which resulted in a low-G condition, main rotor mast bumping, and subsequent severing of the tailboom by the main rotor blades.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN24FA248
Event ID
20240705194615
Case number
CEN24FA248
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: c40d42af175f93d46b070aa5c4042d1237ef4408218f3bf59ade8998dd8de237; retrieved 2026-09-15T08:24:06.130Z.