FTW01LA086 · Cartercopters Cartercopter
Cartercopters Cartercopter · Accident during landing
From Olney Municipal Airport (ONY) to an unrecorded destination
Event
- NTSB case
- FTW01LA086
- 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
- 0 · 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
Cartercopters Cartercopter
- Aircraft type
- Cartercopters CARTERCOPTER
- 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
- N121CC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Olney Municipal Airport (ONY), Olney, TXTo 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
- Landing · flare/touchdown
- 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
- Miscellaneous/other
- 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
- Pilot in command › Rotor RPM, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
A design change was made to the main rotor pitch system of the experimental prototype gyroplane prior to the accident flight. The change incorporated an increase to the main rotor pitch with the collective in the down position. The flight was to takeoff from the runway, climb to 50 feet, fly along the runway, and land on the departure end of the runway. After lift off from the runway, about 5 feet, "a severe out of track condition" was noted and the fuselage rolled left. The pilot immediately reduced the throttle to abort the takeoff and attempted to level the aircraft. In order to level the aircraft prior to touchdown, the pilot had to increase the collective to keep the aircraft airborne until the roll could be corrected. The airspeed had increased to 60 mph, "which was too high [an] airspeed for the collective position and rotor rpm." The rotor exceeded the flapping limits and struck the tail and pusher propeller on landing. The pilot stated that the accident could have been prevented by "improved and more visible rotor rpm and blade flapping indication."
Probable cause
the pilot's failure to maintain rotor rpm, which resuted in the main rotor contacting the tail during landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW01LA086
- Event ID
- 20010329X00664
- Case number
- FTW01LA086
- 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: 590a217def10c86914da8b2a16b583c99a75ae1bfc6a44d3b27f5ebd27fa0762; retrieved 2026-09-22T12:04:47.529Z.