NTSB investigations: Cessna 172G, 1992
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\") = 1992
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") = 1992
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 ATL93FA025Accident · 3 fatalField investigationFinal reportCessna 172 · Brownsboro, ALThe pilot failed to evaluate the wind conditions and took off with a tailwind which resulted in the collision with a tree on the departure end of the runway. Factors were dark night and tailwind.NTSB LAX93LA040Accident · Serious injuriesLimited investigationFinal reportCessna 172G · Williams, AZThe partial loss of engine power due to a stuck exhaust valve on the number two cylinder and the pilot's inability to climb the aircraft above the trees surrounding the airport. A factor in the accident was the effects of the high density altitude on the…NTSB NYC92LA182Accident · No injuriesLimited investigationFinal reportCessna 172H · New Cumberland, WVThe pilot's improper takeoff procedures and his lack of understanding of airplane performance which resulted in an aborted takeoff with insufficient runway to stop and the subsequent collision with a fence. Factors related to the accident were; the pilot's…NTSB LAX92LA311Accident · No injuriesLimited investigationFinal reportCessna 172 · Elko, NVThe pilot's failure to maintain adequate altitude over the terrain, and his failure to maintain sufficient airspeed. The mountainous terrain was a factor.NTSB LAX92LA286Accident · No injuriesLimited investigationFinal reportCessna 172G · Tonopah, NVThe failure of the pilot to adequately identify and compensate for the existing tailwind conditions, and, his failure to initiate a go around when he became aware of being high with a fast ground speed.NTSB LAX92LA248Accident · No injuriesLimited investigationFinal reportCessna 172L · Safford, AZThe airplane colliding with animals which ran on to the runway during the pilot's takeoff roll. A factor in this accident was the pilot not being able to take remedial action and avoid the animals.NTSB SEA92LA059Accident · No injuriesLimited investigationFinal reportCessna 172G · Billings, MTThe pilot's failure to maintain directional control. A factor was the crosswind.NTSB MIA92LA061Accident · 1 fatalLimited investigationFinal reportCessna 172G · Atlantic Ocean (Atlantic Ocean)Loss of engine power due to undetermined reasons.NTSB ATL92LA035Accident · Minor injuriesLimited investigationFinal reportCessna 172G · Millen, GAThe pilot's failure to properly use carburetor heat during icing conditions which resulted in the formation of carburetor ice and subsequent loss of engine power.