NTSB investigations: Cessna R172K, 1989
12 cases on aircraft the registry lists as Cessna R172K. 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 | 1 |
|---|---|
| 1976 | 1 |
| 1977 | 6 |
| 1978 | 16 |
| 1979 | 10 |
| 1980 | 12 |
| 1981 | 6 |
| 1982 | 10 |
| 1983 | 7 |
| 1984 | 5 |
| 1985 | 5 |
| 1986 | 6 |
| 1987 | 4 |
| 1988 | 7 |
| 1989 | 12 |
| 1990 | 4 |
| 1991 | 3 |
| 1992 | 3 |
| 1993 | 5 |
| 1994 | 4 |
| 1995 | 2 |
| 1996 | 5 |
| 1997 | 4 |
| 1998 | 3 |
| 1999 | 5 |
| 2000 | 2 |
| 2001 | 3 |
| 2002 | 5 |
| 2003 | 6 |
| 2004 | 1 |
| 2005 | 1 |
| 2006 | 3 |
| 2007 | 2 |
| 2008 | 6 |
| 2009 | 3 |
| 2010 | 1 |
| 2011 | 4 |
| 2012 | 1 |
| 2014 | 1 |
| 2015 | 3 |
| 2016 | 3 |
| 2017 | 2 |
| 2018 | 1 |
| 2019 | 4 |
| 2020 | 2 |
| 2021 | 1 |
| 2022 | 2 |
| 2023 | 1 |
| 2024 | 1 |
| 2025 | 1 |
| 2026 | 2 |
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\") = 1989
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072431'))
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") = 1989
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072431'))
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 CHI89LA186Accident · No injuriesLimited investigationFinal reportCessna 172 · Ypsilanti, MIThe failure of the plt to maintain directional control during the takeoff ground roll. Rain softened terrain adjacent to the runway surface is a contributing factor to the accident.NTSB FTW89LA162Accident · No injuriesLimited investigationFinal reportCessna 172K · Midlothian, TXThe failure of the pilot to compensate for the crosswind condition, which resulted in a loss of directional control and collision with a tree.NTSB ANC89LA181Accident · 4 fatalLimited investigationFinal reportCessna R172K · Anchorage, AKUndetermined.NTSB NYC89LA192Accident · No injuriesLimited investigationFinal reportCessna R172K · Griswold, CTImproper flare by the pilot, and his failure to attain adequated airspeed for an aborted landing (go-around), which resulted in a loss of aircraft control.NTSB CHI89LA161Accident · No injuriesLimited investigationFinal reportCessna R172K · Vincennes, INThe pilot had excessive airspeed, misjudged the landing distance, and did not go around. Contributing factors were: the pilot misread wind information and selected the wrong runway. Also, the tailwind and ditch were considered to be contributing factors.NTSB CHI89LA141Accident · No injuriesLimited investigationFinal reportCessna R172K · Wisconsin Dells, WIFailure of the pilot to insure the oil filler cap was properly secured when he serviced the aircraft before takeoff, and subsequent loss of oil and oil exhaustion. The tree was considered to be a contributing factor.NTSB FTW89LA131Accident · Minor injuriesLimited investigationFinal reportCessna 172K · Blanco, TXInadequate in-flight planning/decisions by not identifying the wind direction along with the failure to maintain airspeed. Contributing to the accident was the tailwind, wires and trees.NTSB LAX89LA216Accident · No injuriesLimited investigationFinal reportCessna 175K · Bagdad, AZTotal loss of engine power due to undetermined reasons.NTSB FTW89FA073Accident · 4 fatalField investigationFinal reportCessna 172XP · Hondo, TXThe pilot's decision to depart into known adverse weather and his lack of instrument training and experience.NTSB NYC89LA109Accident · No injuriesLimited investigationFinal reportCessna 172XP · Vineland, NJThe pilot's misjudgement of speed & distance during landing which resulted in the proper touchdown point to be exceeded. The runway conditions were contributing factors.NTSB NYC89LA082Accident · No injuriesLimited investigationFinal reportCessna R172K · Ballston Spa, NYWorn connecting rod bearing(s), and failure of the #1 connecting rod. A factor related to the accident was: the lack of suitable terrain for an emergency landing.NTSB MIA89LA061Accident · Minor injuriesLimited investigationFinal reportCessna R172K · Margate, FLFailure of the engine driven oil pump due to foreign object(s), which resulted in oil starvation and subsequent engine failure. Factors related to the accident were: dark night and trees in the emergency landing area.