NTSB investigations: Cessna 172, 1998
13 cases on aircraft the registry lists as Cessna 172. 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 | 80 |
|---|---|
| 1965 | 77 |
| 1966 | 84 |
| 1967 | 85 |
| 1968 | 65 |
| 1969 | 35 |
| 1970 | 32 |
| 1971 | 37 |
| 1972 | 40 |
| 1973 | 35 |
| 1974 | 35 |
| 1975 | 15 |
| 1976 | 29 |
| 1977 | 25 |
| 1978 | 27 |
| 1979 | 15 |
| 1980 | 21 |
| 1981 | 27 |
| 1982 | 11 |
| 1983 | 6 |
| 1984 | 8 |
| 1985 | 13 |
| 1986 | 8 |
| 1987 | 13 |
| 1988 | 21 |
| 1989 | 15 |
| 1990 | 6 |
| 1991 | 11 |
| 1992 | 12 |
| 1993 | 10 |
| 1994 | 10 |
| 1995 | 9 |
| 1996 | 12 |
| 1997 | 4 |
| 1998 | 13 |
| 1999 | 9 |
| 2000 | 9 |
| 2001 | 9 |
| 2002 | 6 |
| 2003 | 2 |
| 2004 | 2 |
| 2005 | 11 |
| 2006 | 4 |
| 2007 | 9 |
| 2008 | 8 |
| 2009 | 3 |
| 2010 | 4 |
| 2011 | 6 |
| 2012 | 4 |
| 2013 | 7 |
| 2014 | 3 |
| 2015 | 5 |
| 2016 | 3 |
| 2017 | 6 |
| 2018 | 6 |
| 2019 | 6 |
| 2020 | 3 |
| 2021 | 8 |
| 2022 | 4 |
| 2023 | 3 |
| 2024 | 2 |
| 2025 | 5 |
| 2026 | 3 |
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 ('2072402'))
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 ('2072402'))
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 IAD99LA018Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Essex, MDA loss of engine power for undetermined reasons. Factors were the lack of suitable terrain for a forced landing and dark night conditions.NTSB FTW98FA384Accident · 2 fatalField investigationFinal reportCessna 172 · West Jordan, UTThe pilot's failure to maintain proper airport traffic pattern altitude. Factors were night lighting conditions and the unseen static line.NTSB ATL98LA120Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Sewanee, TNThe inadequate visual lookout by the ground pedestrian. A factor was dark night conditions.NTSB ANC98LA131Accident · No injuriesLimited investigationFinal reportCessna 172 · Palmer, AKFatigue of the forward end of the engine crankshaft resulting in separation of the propeller assembly, and the operator's failure to comply with a required maintenance procedure. A factor was uneven terrain.NTSB ATL98LA104Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Ocean Isle Bch, NCThe pilot's inadequate inflight planning that resulted in excessive airspeed and altitude for a full stop landing.NTSB SEA98LA154Accident · 1 fatalLimited investigationFinal reportCessna 172 · Baker City, ORThe pilot's failure to maintain terrain clearance and inadequate in-flight planning/decision. Contributing to the accident was mountain obscuration.NTSB LAX98LA214Accident · No injuriesLimited investigationFinal reportCessna 172 · Flagstaff, AZOil system contamination with an unidentified metal substance that traveled through the oil system and blocked the number 4 main bearing and number 6 connecting rod bearing oil ports, resulting in oil starvation and failure of the engine. The source of the…NTSB ANC98LA071Accident · No injuriesLimited investigationFinal reportCessna 172 · Angoon, AKThe pilot's failure to maintain directional control during the aborted takeoff. A factor associated with the accident was rough and uneven terrain.NTSB ANC98LA065Accident · No injuriesLimited investigationFinal reportCessna 172 · Naknek, AKThe pilot's inadequate compensation for wind conditions. A factor associated with this accident was a crosswind.NTSB CHI98FA165Accident · 2 fatalField investigationFinal reportCessna 172 · S. Sioux City, NEThe pilot's failure to maintain adequate flying airspeed during the climbing left turn resulting in a stall condition. Contributing factors were the gusty, crosswind conditions, and the pilot's excessively tight turn maneuver during the initial climb.NTSB CHI98LA122Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Barrington Hill, ILThe pilot's failure to maintain adequate airspeed which resulted in a stall/mush and subsequent in-flight collision with trees.NTSB MIA98LA065Accident · No injuriesLimited investigationFinal reportCessna 172 · Valkaria, FLthe pilot's inadequate preflight, and subsequent loss of engine power, due to fuel exhaustion, which resulted in a forced landing and impact with trees.NTSB FTW98LA116Accident · No injuriesLimited investigationFinal reportCessna 172 · Laramie, WYThe pilot's improper flare and subsequent improper go-around in that he failed to use compensating elevator control, and his loss of directional control.