Final NTSB investigations: Cartercopters CARTERCOPTER
6 cases on aircraft the registry lists as Cartercopters CARTERCOPTER. Aircraft are matched to the registry by N-number and event date, checked against the reported serial number, make and model, so older matches can be wrong.
Cases per year
| 1999 | 1 |
|---|---|
| 2000 | 1 |
| 2001 | 2 |
| 2003 | 1 |
| 2005 | 1 |
Where
Open the mapLatest cases
Query with SQL
duckdb -csv -c "SELECT c.\"ntsbNumber\", c.\"eventDate\", c.\"eventType\", c.\"eventCity\", c.\"eventStateOrRegion\", a.n_number, a.\"aircraftMake\", a.\"aircraftModel\", c.\"highestInjuryLevel\", c.\"totalFatal\", c.\"completionStatus\", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c.\"mKey\" AND a.position = 1
WHERE c.\"completionStatus\" = 'Completed'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('05606CO'))
ORDER BY c.\"eventDate\" DESC, c.\"ntsbNumber\" DESC"Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.
SELECT c."ntsbNumber", c."eventDate", c."eventType", c."eventCity", c."eventStateOrRegion", a.n_number, a."aircraftMake", a."aircraftModel", c."highestInjuryLevel", c."totalFatal", c."completionStatus", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c."mKey" AND a.position = 1
WHERE c."completionStatus" = 'Completed'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('05606CO'))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESCRun it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
NTSB DFW05CA163Accident · No injuriesData collectionFinal reportCarterCopter CarterCopter · Olney, TXThe pilot's inability to maintain control of the gyrocraft during a forced landing as a result of a loss of cyclic and collective control. Contributing factors were the sheared propeller drive pulley bolts, broken wire on the co-pilots cyclic boost control…NTSB FTW03LA125Accident · No injuriesLimited investigationFinal reportCarterCopter Prototype · Olney, TXThe pilot's failure to extend the landing gear. A factor was his diverted attention.NTSB FTW01LA108Accident · No injuriesLimited investigationFinal reportCartercopters Cartercopter · Olney, TXthe pilot's failure to maintain directional control during the takeoff initial climb. Contributory factors were the pilot's lack of experience with the aircraft and the soft terrain.NTSB FTW01LA086Accident · No injuriesLimited investigationFinal reportCartercopters Cartercopter · Olney, TXthe pilot's failure to maintain rotor rpm, which resuted in the main rotor contacting the tail during landing.NTSB FTW01LA040Accident · No injuriesLimited investigationFinal reportCartercopter Model 1 · Olney, TXThe pilot's delay in lowering the collective during a run-on landing, which resulted in a runway overrun. A factor was the muddy terrain.NTSB FTW00LA045Accident · No injuriesLimited investigationFinal reportCartercopters Cartercopter · Olney, TXThe pilot's failure to maintain rotor rpm during takeoff, which resulted in a hard landing following the aborted takeoff.