DEN00LA079 · Green GTX-SE-FI
Green GTX-SE-FI · Accident: loss of control in flight while maneuvering
From Gillette, WY (no airport) to an unrecorded destination
Event
- NTSB case
- DEN00LA079
- 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
Green GTX-SE-FI
- Aircraft type
- Green GTX-SE-FI
- 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
- N2411V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Gillette, WY (no airport)To not recorded
- 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
- First occurrenceThe 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
- Pilot in command › Aircraft control, not possible
- Pilot in command › Airspeed, excessive
- Pilot in command › Pull-up, abrupt
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Witnesses said the experimental amateur-built gyrocopter (or gyroplane) was flying low and the engine sounded like it was 'racing,' or 'sputtering,' then 'the rotors come apart in the air.' There was no evidence of the rotor blades separating in flight, but there was evidence that the blades had struck the vertical stabilizer and rudder, severing the tail boom. Two blades of the 4-blade propeller were shattered. The pilot's close friend (who assisted the pilot in building the gyrocopter) said if the pilot was flying at high speed and was to suddenly increase the angle of attack and abruptly move the cyclic control aft, the main rotor blades could conceivably strike the tail boom. The accident site was near abruptly rising terrain. On a previous occasion, the pilot accelerated to a high ground speed before increasing the angle of attack for liftoff. The rotor blades struck the runway and were damaged to the extent that they had to be replaced.
Probable cause
The pilot's abruptly pulling the nose up at an excessive airspeed, resulting in the rotor blades striking the vertical stabilizer and a subsequent loss of aircraft control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN00LA079
- Event ID
- 20001212X20804
- Case number
- DEN00LA079
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 91c6a3acbafa386b2774bbbf4fb828bb34552bea284a725c36b956029bbf0008; retrieved 2026-09-20T21:16:01.686Z.