Fatal NTSB investigations: Continental 0-300 series, 2016
3 cases on aircraft whose registry engine model is Continental 0-300 series. 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 | 4 |
|---|---|
| 1965 | 2 |
| 1966 | 11 |
| 1967 | 8 |
| 1968 | 9 |
| 1969 | 4 |
| 1970 | 4 |
| 1971 | 2 |
| 1972 | 2 |
| 1973 | 4 |
| 1974 | 1 |
| 1976 | 4 |
| 1977 | 2 |
| 1978 | 8 |
| 1979 | 8 |
| 1980 | 6 |
| 1981 | 9 |
| 1982 | 5 |
| 1983 | 4 |
| 1984 | 1 |
| 1985 | 5 |
| 1986 | 3 |
| 1987 | 1 |
| 1988 | 2 |
| 1989 | 6 |
| 1991 | 1 |
| 1992 | 4 |
| 1993 | 3 |
| 1994 | 1 |
| 1995 | 4 |
| 1996 | 4 |
| 1997 | 1 |
| 1999 | 2 |
| 2000 | 2 |
| 2001 | 4 |
| 2002 | 3 |
| 2003 | 3 |
| 2004 | 6 |
| 2005 | 8 |
| 2006 | 4 |
| 2007 | 3 |
| 2008 | 3 |
| 2009 | 3 |
| 2010 | 5 |
| 2011 | 1 |
| 2012 | 2 |
| 2013 | 2 |
| 2014 | 1 |
| 2015 | 3 |
| 2016 | 3 |
| 2017 | 4 |
| 2018 | 1 |
| 2019 | 4 |
| 2020 | 4 |
| 2021 | 1 |
| 2022 | 5 |
| 2023 | 5 |
| 2024 | 1 |
| 2025 | 2 |
| 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\") = 2016
AND c.\"highestInjuryLevel\" = 'Fatal'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17022'))
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") = 2016
AND c."highestInjuryLevel" = 'Fatal'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17022'))
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 ANC17FA003Accident · 1 fatalField investigationFinal reportCessna 172 · Palmer, AKThe student pilot's exceedance of the airplane's critical angle of attack during a steep climbing turn following a touch-and-go landing, which resulted in an aerodynamic stall at too low of an altitude to recover.NTSB WPR16LA138Accident · 3 fatalLimited investigationFinal reportCessna 172 · Brookings, ORThe pilot's spatial disorientation and loss of situational awareness during the departure turn in dark night conditions, which resulted in an in-flight collision with water.NTSB ERA16FA161Accident · 2 fatalField investigationFinal reportCessna 172 · Westmoreland, NYThe pilot's decision to takeoff on the grass runway given the conditions at the time; his excessive aft control input during the takeoff roll, which resulted in the aft fuselage contacting the runway surface; and his failure to attain sufficient airspeed and…