FTW01LA040 · Cartercopter MODEL 1
Cartercopter MODEL 1 · Accident: overrun during landing
From Olney Municipal Airport (ONY) to an unrecorded destination
Event
- NTSB case
- FTW01LA040
- 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
Cartercopter MODEL 1
- Aircraft type
- Cartercopter MODEL 1
- 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 · landing roll
- 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
- Overrun
- 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 › Lowering of collective, delayed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was performing a short test flight in an experimental prototype gyroplane. After a low level, low airspeed flight down runway centerline, the pilot executed a run-on landing at 30 MPH about 300 feet from the departure end of the runway. The aircraft slowed to about 20 MPH as it rolled off of the runway surface, and onto a muddy field. Subsequently, the nose landing gear collapsed, allowing a 4-foot x 4-foot long section of nose boom to dig into the mud. The aircraft then pitched down about the nose as the main rotor impacted the ground. After the rotor impact, the aircraft rolled to the right, and the right wing impacted the ground. The aircraft sustained structural damage to the right wing, rudder, and main rotor. Skid marks, found about 150 feet forward of the original touch down point, and correlating to the aircraft's landing gear/tires, were observed on the runway. The designer and manufacturer of the prototype, monitored the entire flight with on-board parameter recording devices. These data suggested that the pilot did not lower the collective enough for the brakes to be effective.
Probable cause
The pilot's delay in lowering the collective during a run-on landing, which resulted in a runway overrun. A factor was the muddy terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW01LA040
- Event ID
- 20001226X45486
- Case number
- FTW01LA040
- 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: e9b90e9b7d8d21cce0dc6a4c769d99a676374d0d7590a25e68a374f5dd53d5f8; retrieved 2026-09-22T12:17:11.898Z.