NTSB investigations: Cessna 172G, 1989
9 cases on aircraft the registry lists as Cessna 172G. 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
| 1965 | 2 |
|---|---|
| 1966 | 67 |
| 1967 | 81 |
| 1968 | 41 |
| 1969 | 35 |
| 1970 | 27 |
| 1971 | 32 |
| 1972 | 22 |
| 1973 | 21 |
| 1974 | 14 |
| 1975 | 11 |
| 1976 | 14 |
| 1977 | 11 |
| 1978 | 11 |
| 1979 | 7 |
| 1980 | 5 |
| 1981 | 9 |
| 1982 | 5 |
| 1983 | 6 |
| 1984 | 4 |
| 1985 | 4 |
| 1986 | 6 |
| 1987 | 8 |
| 1988 | 8 |
| 1989 | 9 |
| 1990 | 7 |
| 1991 | 10 |
| 1992 | 9 |
| 1993 | 4 |
| 1994 | 5 |
| 1995 | 8 |
| 1996 | 6 |
| 1997 | 6 |
| 1998 | 5 |
| 1999 | 7 |
| 2000 | 4 |
| 2001 | 2 |
| 2002 | 6 |
| 2003 | 4 |
| 2005 | 2 |
| 2006 | 3 |
| 2007 | 2 |
| 2010 | 2 |
| 2011 | 1 |
| 2012 | 1 |
| 2013 | 2 |
| 2015 | 4 |
| 2017 | 3 |
| 2018 | 6 |
| 2019 | 3 |
| 2020 | 1 |
| 2021 | 6 |
| 2022 | 3 |
| 2023 | 3 |
| 2024 | 3 |
| 2025 | 5 |
| 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 ('2072420'))
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 ('2072420'))
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 NYC90LA037Accident · Serious injuriesLimited investigationFinal reportCessna 172G · Uxbridge, MAIce in the fuel strainer, which restricted fuel flow & resulted in fuel starvation, and the pilot inadvertently stalled the airplane, when he abruptly maneuvered it to avoid a transmission wire during a forced landing.NTSB CHI90LA037Accident · No injuriesLimited investigationFinal reportCessna 172G · Savoy, ILImproper planning/decision by the pilot, which resulted in his inability to maintain control of the aircraft. A factor related to the accident was: the adverse wind condition.NTSB MKC89LA183Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Barnesville, MNThe pilot's failure to insure that the aircraft contained an adequate fuel supply to complete the flight.NTSB FTW89LA144Accident · No injuriesLimited investigationFinal reportCessna 172G · Mckinney, TXTotal failure of the engine assembly/rocker arm/tappet shaft.NTSB ATL89FA182Accident · 3 fatalField investigationFinal reportCessna 172G · Ridgeland, SCImproper planning/decision by the pilot-in-command (PIC), which resulted in an inadvertent stall during takeoff. Factors related to the accident were: the excessive gross weight and improper lift-off by the PIC, the pilot/passenger's improper crew…NTSB MIA89LA199Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Forest, MSFailure of the pilot to maintain runway alignment and partial loss of power from water in the fuel. Contributing factors were: uneven runway, pilot's improper recovery from a bounced landing, a gusty crosswind condition, and trees.NTSB SEA89LA078Accident · No injuriesLimited investigationFinal reportCessna 172 · Lynden, WAThe pilot delayed in aborting the landing and failed obtain or maintain sufficient airspeed to keep the aircraft from mushing after lift-off. Factors related to the accident were: obstructions near the approach end of the runway, failure of the pilot to…NTSB ATL89LA102Accident · No injuriesLimited investigationFinal reportCessna 172G · Coolidge, GAFuel contamination of an unknown origin, failure of company maintenance personnel to locate and remove all contamination, continued operation of the aircraft by the pilot after the cause of a known engine problem was not determined, and subsequent fuel…NTSB DEN89LA053Accident · No injuriesLimited investigationFinal reportCessna 172 · Cheyenne, WYImproper planning/decision by the pilot. Factors related to the accident were the high wind and gusts, which he was unable to compensate for.