NTSB investigations: Cessna 195, 2004
4 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 | 22 |
|---|---|
| 1965 | 8 |
| 1966 | 11 |
| 1967 | 6 |
| 1968 | 6 |
| 1969 | 12 |
| 1970 | 3 |
| 1971 | 8 |
| 1972 | 3 |
| 1973 | 3 |
| 1974 | 5 |
| 1975 | 7 |
| 1976 | 6 |
| 1977 | 6 |
| 1978 | 2 |
| 1979 | 5 |
| 1980 | 1 |
| 1982 | 2 |
| 1983 | 2 |
| 1984 | 2 |
| 1985 | 2 |
| 1986 | 4 |
| 1987 | 1 |
| 1988 | 3 |
| 1989 | 2 |
| 1990 | 3 |
| 1991 | 2 |
| 1992 | 4 |
| 1993 | 1 |
| 1994 | 1 |
| 1995 | 2 |
| 1997 | 1 |
| 1998 | 3 |
| 1999 | 1 |
| 2000 | 2 |
| 2001 | 1 |
| 2002 | 2 |
| 2003 | 2 |
| 2004 | 4 |
| 2005 | 2 |
| 2006 | 2 |
| 2007 | 2 |
| 2008 | 3 |
| 2009 | 2 |
| 2010 | 2 |
| 2011 | 1 |
| 2012 | 1 |
| 2013 | 1 |
| 2015 | 3 |
| 2016 | 2 |
| 2017 | 1 |
| 2019 | 1 |
| 2021 | 1 |
| 2022 | 2 |
| 2023 | 1 |
| 2024 | 1 |
| 2025 | 1 |
| 2026 | 2 |
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 year(c.\"eventDate\") = 2004
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 year(c."eventDate") = 2004
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 MIA05FA035Accident · 2 fatalField investigationFinal reportCessna 195 · Kilmichael, MSThe pilot's ostentatious display, flying at low altitude, resulting in collision with a static wire power line, in-flight loss of control, and collision with terrain. A factor in the accident was sun glare.NTSB LAX04LA199Accident · No injuriesLimited investigationFinal reportCessna 195 · Riverside, CAthe pilot's failure to maintain directional control, resulting in a veer off the runway and collision with terrain.NTSB SEA04LA070Accident · No injuriesLimited investigationFinal reportCessna 195 · Everett, WAThe pilot's failure to maintain directional control of the aircraft as a result of a locked main gear brake during the landing roll. An inadvertent ground loop was a factor.NTSB CHI04LA083Accident · No injuriesLimited investigationFinal reportCessna 195 · Manitowoc, WIThe Cessna 195 pilot's failure to maintain clearance from the Cessna 177RG while taxiing to the ramp after landing. A contributing factor was the restricted forward visibility (blind spot) of the Cessna 195 due to the engine cowling. An additional factor was…