NTSB investigations: Cessna 195, CO
7 cases on aircraft the registry lists as Cessna 195. 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
| 1964 | 2 |
|---|---|
| 1968 | 1 |
| 1969 | 1 |
| 1987 | 1 |
| 1994 | 1 |
| 2000 | 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.\"eventStateOrRegion\" = 'CO' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2073102'))
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."eventStateOrRegion" = 'CO' AND c."eventCountry" = 'USA'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2073102'))
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 DEN00FA127Accident · 4 fatalField investigationFinal reportCessna 195 · Aspen, COthe pilot's poor in-flight decision to fly up a valley with rapidly rising terrain, which resulted in the airplane colliding with the terrain due to its climb performance being exceeded. A contributing factors was the high, rapidly rising, mountainous terrain.NTSB FTW94LA066Accident · No injuriesLimited investigationFinal reportCessna 195 · Watkins, COThe loss of directional control by the pilot rated passenger. A factor was inadequate supervision by the pilot in command.NTSB DEN87LA239Accident · Minor injuriesLimited investigationFinal reportCessna 195 · Colorado Sprgs, COThe plt stated that after he lndd to pick up a pax, he engaged the control lock fm habit, but did not shut dwn the eng. He got clnc to taxi back to the rwy & takeoff, but 'forgot to release control lock.' The Cessna 195 has a combination control lock and…NTSB DEN69D0243Accident · No injuriesClosedCessna 195 · Greeley, CONTSB DEN69D0131Accident · No injuriesClosedCessna 195 · Broomfield, CONTSB UNK64X2093Accident · No injuriesClosedCessna 170A · Durango, CONTSB UNK64X0342Accident · 4 fatalClosedCessna 195 · Winter Park, CO