NTSB investigations: Cessna 170B, 2002
11 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\") = 2002
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") = 2002
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 LAX03LA042Accident · No injuriesLimited investigationFinal reportCessna 170B · Mobile, AZthe pilot's improper compensation for the crosswind conditions at touchdown and failure to maintain proper alignment of the tail wheel equipped airplane during landing, which resulted in a ground loop. The crosswind was a contributory factor.NTSB ANC02LA096Accident · No injuriesLimited investigationFinal reportCessna 170 · Soldotna, AKThe pilot's inadequate recovery from a bounced landing, and his failure to maintain directional control of the airplane. A factor contributing to the accident was the pilot's excessive braking which resulted in a nose over.NTSB LAX02LA245Accident · No injuriesLimited investigationFinal reportCessna 170B · St. Johns, AZthe pilot's selection of the wrong runway for the existing crosswind condition and his subsequent inadequate compensation for the winds, which led to a failure to maintain directional control and a ground loop.NTSB DEN02LA047Accident · No injuriesLimited investigationFinal reportCessna 170B · Rock Springs, WYthe pilot's failure to maintain aircraft control during initial takeoff climb. A contributing factor was the gusty crosswind.NTSB LAX02LA168Accident · No injuriesLimited investigationFinal reportCessna 170B · Show Low, AZThe pilot's improper recovery from a bounced landing resulted in a loss of aircraft control. A factor was a sudden wind shift on final approach.NTSB ANC02LA034Accident · No injuriesLimited investigationFinal reportCessna 170B · North Pole, AKThe separation of the right main landing gear from the airplane during landing. A factor associated with the accident is the unapproved hardware used to attach the main landing gear.NTSB ANC02LA032Accident · No injuriesLimited investigationFinal reportCessna 170B · Anchorage, AKThe failure of the pilot to maintain directional control during takeoff. A factor associated with the accident was an inadvertent ground loop.NTSB LAX02LA159Accident · No injuriesLimited investigationFinal reportCessna 170B · San Diego, CAThe failure of the dual student to maintain directional control of the airplane and the instructor's delayed the remedial action, which resulted in a ground loop. A factor in the accident was the gusting crosswind conditions.NTSB ATL02LA080Accident · No injuriesLimited investigationFinal reportCessna 170B · Ocala, FLThe pilot's failure to maintain directional control on landing roll, resulting in a loss of control/ground loop.NTSB SEA02LA054Accident · Minor injuriesLimited investigationFinal reportCessna 170B · Rainier, WAThe pilot's failure to maintain the proper decent rate on approach. A factor was the trees in close proximity to the airport.NTSB ATL02LA036Accident · Minor injuriesLimited investigationFinal reportCessna 170B · Bellewood, MSThe pilot misjudged the proper touched down point and collided with the ground short of the runway during an attempted landing.