NTSB investigations: Cessna 170B, 1998
12 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\") = 1998
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") = 1998
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 FTW98FA411Accident · 2 fatalField investigationFinal reportCessna 170B · Weatherford, TXThe pilot's failure to maintain obstacle clearance.NTSB LAX98LA287Accident · No injuriesLimited investigationFinal reportCessna 170B · San Jose, CAThe pilot's inadequate compensation for the existing crosswind condition and failure to maintain directional controlNTSB ANC98LA142Accident · No injuriesLimited investigationFinal reportCessna 170B · Port Alsworth, AKThe solo student pilot's excessive application of brakes during taxi from landing. Factors associated with the accident were the pilot's selection of unsuitable terrain for a precautionary landing, rough terrain, and the fuel leak from the fuel tank vent.NTSB ANC98LA121Accident · Minor injuriesLimited investigationFinal reportCessna 170B · Arctic Village, AKThe pilot's inadequate compensation for wind conditions. Factors associated with the accident were variable, and gusty wind conditions.NTSB SEA98LA131Accident · Serious injuriesLimited investigationFinal reportCessna 170B · Hailey, IDThe pilot-in-command's failure to maintain directional control during takeoff. Contributing factors were the pilot-in-command's failure to follow procedures by the improper use of the flaps, high density altitude conditions, crosswind conditions and the tree.NTSB NYC98LA133Accident · No injuriesLimited investigationFinal reportCessna 170B · Oneonta, NYThe separation of the left rudder cable. A factor was chafing of the cable.NTSB ANC98LA050Accident · No injuriesLimited investigationFinal reportCessna 170B · Russian Mission, AKThe pilot's inadequate compensation for wind conditions while landing. A factor associated with the accident was the presence of a tailwind condition.NTSB FTW98LA251Accident · No injuriesLimited investigationFinal reportCessna 170B · Los Alamos, NMThe pilot's inadequate compensation for the wind conditions. Contributing factors were the crosswinds, the fence, and the ditch.NTSB IAD98LA066Accident · Minor injuriesLimited investigationFinal reportCessna 170B · Wadsworth, OHThe flight instructor's failure to maintain control of the airplane which resulted in his intentional ground loop. A factor in the accident was the flight instructor's lack of currency in tailwheel airplanes.NTSB ANC98LA041Accident · No injuriesLimited investigationFinal reportCessna 170B · Kenai, AKA failure of the number six cylinder rod bearing and connecting rod cap for undetermined reasons. Factors in the accident were snow covered terrain that was unsuitable for a forced landing.NTSB ANC98LA028Accident · No injuriesLimited investigationFinal reportCessna 170B · Dillingham, AKThe pilot-in-command's decision to relinquish controls to the student pilot in the left seat during practice landings, and the pilot-in-command's failure to maintain directional control. A factor contributing to this accident was the pilot-in-command's lack…NTSB MIA98LA057Accident · No injuriesLimited investigationFinal reportCessna 170 · Orlando, FLfailure of the the left brake to operate, due to a bad o-ring; and subsequent failure of the pilot to maintain directional control of the airplane during landing rollout, resulting in a ground loop and subsequent on-ground encounter with terrain.