NTSB investigations: Cessna 170B, 2017
7 cases on aircraft the registry lists as Cessna 170B. 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 | 77 |
|---|---|
| 1965 | 67 |
| 1966 | 61 |
| 1967 | 46 |
| 1968 | 48 |
| 1969 | 31 |
| 1970 | 36 |
| 1971 | 44 |
| 1972 | 35 |
| 1973 | 32 |
| 1974 | 35 |
| 1975 | 35 |
| 1976 | 27 |
| 1977 | 22 |
| 1978 | 28 |
| 1979 | 22 |
| 1980 | 12 |
| 1981 | 16 |
| 1982 | 15 |
| 1983 | 13 |
| 1984 | 16 |
| 1985 | 15 |
| 1986 | 15 |
| 1987 | 17 |
| 1988 | 11 |
| 1989 | 11 |
| 1990 | 10 |
| 1991 | 12 |
| 1992 | 7 |
| 1993 | 13 |
| 1994 | 5 |
| 1995 | 8 |
| 1996 | 17 |
| 1997 | 15 |
| 1998 | 12 |
| 1999 | 11 |
| 2000 | 10 |
| 2001 | 9 |
| 2002 | 11 |
| 2003 | 10 |
| 2004 | 12 |
| 2005 | 9 |
| 2006 | 14 |
| 2007 | 5 |
| 2008 | 3 |
| 2009 | 13 |
| 2010 | 9 |
| 2011 | 4 |
| 2012 | 6 |
| 2013 | 12 |
| 2014 | 11 |
| 2015 | 9 |
| 2016 | 3 |
| 2017 | 7 |
| 2018 | 8 |
| 2019 | 7 |
| 2020 | 7 |
| 2021 | 7 |
| 2022 | 4 |
| 2023 | 6 |
| 2024 | 8 |
| 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.aircraft_model_code IN ('2072306', '2072307'))
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.aircraft_model_code IN ('2072306', '2072307'))
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 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 ERA17FA143Accident · 2 fatalField investigationFinal reportCessna 170B · Edgewater, FLThe Cessna pilot's failure to maintain clearance from the Grumman during the transition to a different formation. Contributing to the accident was the stepped down configuration of the formation flight which was composed of dissimilar aircraft.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.