NTSB investigations: Cessna 172B, 1994
5 cases on aircraft the registry lists as Cessna 172B. 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 | 36 |
|---|---|
| 1965 | 17 |
| 1966 | 15 |
| 1967 | 17 |
| 1968 | 16 |
| 1969 | 11 |
| 1970 | 7 |
| 1971 | 11 |
| 1972 | 5 |
| 1973 | 9 |
| 1974 | 3 |
| 1975 | 5 |
| 1976 | 5 |
| 1977 | 5 |
| 1978 | 6 |
| 1979 | 2 |
| 1980 | 1 |
| 1981 | 4 |
| 1982 | 2 |
| 1983 | 1 |
| 1984 | 1 |
| 1985 | 7 |
| 1986 | 2 |
| 1987 | 1 |
| 1988 | 3 |
| 1989 | 1 |
| 1990 | 4 |
| 1991 | 3 |
| 1992 | 4 |
| 1993 | 1 |
| 1994 | 5 |
| 1995 | 3 |
| 1996 | 1 |
| 1997 | 2 |
| 1998 | 2 |
| 1999 | 5 |
| 2000 | 4 |
| 2001 | 2 |
| 2002 | 1 |
| 2003 | 2 |
| 2004 | 1 |
| 2005 | 3 |
| 2007 | 3 |
| 2010 | 1 |
| 2011 | 1 |
| 2012 | 2 |
| 2013 | 2 |
| 2014 | 1 |
| 2015 | 1 |
| 2016 | 2 |
| 2017 | 1 |
| 2018 | 2 |
| 2021 | 2 |
| 2022 | 1 |
| 2023 | 2 |
| 2026 | 1 |
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\") = 1994
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072406'))
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") = 1994
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072406'))
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 CHI95LA055Accident · No injuriesLimited investigationFinal reportCessna 172 · Allegan, MIthe student pilot's failure to maintain directional control which resulted in the inability to obtain proper runway alignment. Related factors are the student pilot's lack of total flight experience and the snowbank.NTSB FTW95LA062Accident · No injuriesLimited investigationFinal reportCessna 172B · Seguin, TXThe pilot's failure to attain proper touchdown point.NTSB FTW94LA317Accident · No injuriesLimited investigationFinal reportCessna 172B · Poteau, OKThe loss of engine power due to the pilot's delayed use of carburetor heat and the resultant carburetor icing. Factors were the weather condition and the lack of suitable terrain for the forced landing.NTSB NYC94LA112Accident · No injuriesLimited investigationFinal reportCessna 172 · Tinton Falls, NJThe loss of engine power for undetermined reasons.NTSB CHI94LA216Accident · Serious injuriesLimited investigationFinal reportCessna 172B · Shiocton, WIthe pilot's failure to maintain Vso during takeoff. Factors related to the accident was the disregard for performance data and trees.