FTW00LA045 · Cartercopters CARTERCOPTER CARTERCOPT
Cartercopters CARTERCOPTER CARTERCOPT · Accident: hard landing
From Olney Municipal Airport (ONY) to an unrecorded destination
Event
- NTSB case
- FTW00LA045
- 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
- 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
Cartercopters CARTERCOPTER CARTERCOPT
- 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)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
- 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
- Hard landing
- 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
For the first test flight of the day, the gyroplane's rotor was pre-rotated to 450 rpm, instead of the normal 550 rpm. As the takeoff was initiated, the collective was raised in a 'normal' manner and liftoff was accomplished. According to the pilot, 'within a few seconds into the climb, the control forces began to build, and stick shake began.' The pilot had to use both hands to apply forward cyclic pressure to 'counter' the nose pitching up. The pilot stated that he momentarily removed one hand from the cyclic to reduce power [collective]. At this time, the nose pitched up and power was reapplied to cushion the touchdown. The pilot reported that, 'application of power was not smooth and resulted in a hard landing, causing the blades to hit the rudders.' The pilot reported that after reviewing the flight data, it 'became apparent that had the collective been lowered shortly after liftoff, the rotor RPM would not have dissipated so rapidly, causing the high control forces and blade flapping.'
Probable cause
The pilot's failure to maintain rotor rpm during takeoff, which resulted in a hard landing following the aborted takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW00LA045
- Event ID
- 20001212X20241
- Case number
- FTW00LA045
- 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: bc4f07cfb643078957810946a997f833dc45dd7e935c036fa8c176859323cf99; retrieved 2026-09-22T13:32:27.162Z.