NTSB investigations: Continental C145 series, 2017
14 cases on aircraft whose registry engine model is Continental C145 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 | 68 |
|---|---|
| 1965 | 53 |
| 1966 | 52 |
| 1967 | 54 |
| 1968 | 45 |
| 1969 | 41 |
| 1970 | 21 |
| 1971 | 35 |
| 1972 | 30 |
| 1973 | 34 |
| 1974 | 26 |
| 1975 | 44 |
| 1976 | 29 |
| 1977 | 29 |
| 1978 | 33 |
| 1979 | 27 |
| 1980 | 18 |
| 1981 | 23 |
| 1982 | 13 |
| 1983 | 22 |
| 1984 | 15 |
| 1985 | 17 |
| 1986 | 15 |
| 1987 | 21 |
| 1988 | 16 |
| 1989 | 12 |
| 1990 | 21 |
| 1991 | 17 |
| 1992 | 11 |
| 1993 | 10 |
| 1994 | 8 |
| 1995 | 9 |
| 1996 | 16 |
| 1997 | 18 |
| 1998 | 16 |
| 1999 | 8 |
| 2000 | 7 |
| 2001 | 8 |
| 2002 | 11 |
| 2003 | 11 |
| 2004 | 10 |
| 2005 | 7 |
| 2006 | 9 |
| 2007 | 10 |
| 2008 | 8 |
| 2009 | 15 |
| 2010 | 10 |
| 2011 | 11 |
| 2012 | 8 |
| 2013 | 16 |
| 2014 | 11 |
| 2015 | 11 |
| 2016 | 9 |
| 2017 | 14 |
| 2018 | 8 |
| 2019 | 8 |
| 2020 | 15 |
| 2021 | 7 |
| 2022 | 6 |
| 2023 | 7 |
| 2024 | 12 |
| 2025 | 8 |
| 2026 | 6 |
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\") = 2017
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17012'))
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") = 2017
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17012'))
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 CEN18LA044Accident · No injuriesLimited investigationFinal reportCessna 170B · Harvard, ILThe failure of the universal joint in the pilot-side flight control yoke due to the fatigue fracture of a rivet within the universal joint. Contributing to the universal joint failure was the universal joint design, which was prone to galling wear and seizure.NTSB GAA17CA499Accident · No injuriesData collectionFinal reportCessna 170 · Rochelle, ILThe pilot’s failure to maintain directional control during landing with a tailwind.NTSB GAA17CA489Accident · No injuriesData collectionFinal reportCessna 170 · Axtell, KSThe pilot's exceedance of the airplane's critical angle of attack during a go-around. Contributing to the accident was the pilot's decision to attempt to close a passenger door during a critical phase of flight.NTSB GAA17CA468Accident · Serious injuriesData collectionFinal reportCessna 170 · Moab, UTThe pilot’s improper decision to depart in unfavorable weather conditions, which resulted in a hard, forced landing.NTSB GAA17CA445Accident · No injuriesData collectionFinal reportCessna 170 · San Andreas, CAThe pilot’s improper landing flare during an aborted go-around in gusting wind conditions, which resulted in a hard landing.NTSB GAA17CA426Accident · No injuriesData collectionFinal reportCessna 170 · Friday Harbor, WAThe pilot’s loss of directional control during landing.NTSB GAA17CA399Accident · No injuriesData collectionFinal reportCessna 170B · Pine Bluff, ARThe pilot’s failure to maintain directional control during the landing roll.NTSB GAA17CA382Accident · No injuriesData collectionFinal reportCessna 170 · Alamogordo, NMThe pilot receiving instruction’s failure to maintain directional control during the landing roll and the flight instructor’s delayed remedial action, which resulted in a ground loop.NTSB GAA17CA284Accident · No injuriesData collectionFinal reportCessna 170 · Taos, NMThe pilot’s failure to maintain directional control while landing in gusting crosswind conditions.NTSB ERA17FA155Accident · 4 fatalField investigationFinal reportCessna 170 · Williston, FLThe pilot's failure to maintain adequate airspeed during initial climb in gusty wind conditions, which resulted in the airplane exceeding its critical angle-of-attack and experiencing an aerodynamic stall/spin.NTSB GAA17CA204Accident · Minor injuriesData collectionFinal reportCessna 170 · Death Valley, CAThe pilot’s improper compensation for crosswind conditions during the landing flare and his subsequent failure to maintain directional control during the landing.NTSB GAA17CA141Accident · No injuriesData collectionFinal reportCessna 170 · Wheatland, WYThe flight instructor’s incorrect compensation for the gusting crosswind during the landing roll, which resulted in a loss of directional control and runway excursion.NTSB GAA17CA116Accident · No injuriesData collectionFinal reportCessna 170 · Coeur D'Alene, IDThe pilot’s failure to maintain an appropriate descent rate during approach, which resulted in landing short of the runway threshold.NTSB ERA17CA087Accident · Serious injuriesData collectionFinal reportCessna 170 · Hayden, ALThe pilot’s failure to maintain clearance from trees during the approach.