NTSB investigations: Cessna 172E, 1983
8 cases on aircraft the registry lists as Cessna 172E. 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 | 52 |
|---|---|
| 1965 | 50 |
| 1966 | 32 |
| 1967 | 28 |
| 1968 | 25 |
| 1969 | 19 |
| 1970 | 24 |
| 1971 | 18 |
| 1972 | 14 |
| 1973 | 7 |
| 1974 | 9 |
| 1975 | 5 |
| 1976 | 10 |
| 1977 | 8 |
| 1978 | 8 |
| 1979 | 4 |
| 1980 | 7 |
| 1981 | 5 |
| 1982 | 7 |
| 1983 | 8 |
| 1984 | 7 |
| 1985 | 5 |
| 1986 | 6 |
| 1987 | 8 |
| 1988 | 4 |
| 1989 | 3 |
| 1990 | 5 |
| 1991 | 5 |
| 1992 | 3 |
| 1993 | 3 |
| 1995 | 5 |
| 1996 | 4 |
| 1997 | 4 |
| 1998 | 2 |
| 1999 | 4 |
| 2000 | 1 |
| 2001 | 3 |
| 2002 | 2 |
| 2003 | 3 |
| 2004 | 6 |
| 2006 | 3 |
| 2007 | 4 |
| 2009 | 4 |
| 2010 | 3 |
| 2012 | 2 |
| 2013 | 1 |
| 2015 | 1 |
| 2016 | 2 |
| 2018 | 1 |
| 2019 | 5 |
| 2021 | 3 |
| 2024 | 1 |
| 2025 | 1 |
| 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\") = 1983
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072412'))
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") = 1983
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072412'))
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 MKC84LA030Accident · No injuriesLimited investigationFinal reportCessna 172 · Hampton, IAOn his fourth touch and go landing the pilot added power for the go-around and the aircraft drifted off the left side of the runway. The left main gear hit a snowbank and the aircraft flipped over landing upside down in the snow. The winds at macon city, IA…NTSB CHI84LA012Accident · No injuriesLimited investigationFinal reportCessna 172E · Cincinnati, OHThe acft collided wih a pole and mail boxes during a forced landing after fuel exhaustion. The pilot was unalbe to find blur ash arpt and asked for assistance from Cincinnati approach. When the arpt was located after over 6 hours of flt time,the acrt ran out…NTSB FTW83FA441Accident · 3 fatalField investigationFinal reportCessna 172E · Leesville, LAEarlier in the day the four occupants of the acft had been reported to the sheriff's dept as being drunk at a lounge near zwolle,LA. After landing at the Leesville arpt the acft ran off the asphalt bending both ends of the prop blades. The occupants attempted…NTSB CHI83LA399Accident · Minor injuriesLimited investigationFinal reportCessna 172E · Columbia Sta., OHAccording to the non-rated plt, he was on downwind to land when he applied carburetor heat, then the eng RPM began to decrease. He stated that he pushed the throttle forward, but got no response from the eng. He further stated that the acft continued to lose…NTSB ATL83LA345Accident · Minor injuriesLimited investigationFinal reportCessna 172E · Middlebourne, WVThe plt reported that en route, the eng began to run rough. Reportedly, he applied carburetor heat, full rich mixture & full throttle, but was unable to significantly increase the power. He circled for a short time, then made an emergency landing. An exam of…NTSB ATL83FA224Accident · Serious injuriesField investigationFinal reportCessna 172 · Mocksville, NCN5722T, a Cessna 172, and N3452J, a Cessna 150, collided over the approach end of runway 09 while both acft were on short final approach. Both acft impacted the runway and came to rest about 280 ft east of runway 09 threshold.NTSB LAX83LA218Accident · Serious injuriesLimited investigationFinal reportCessna 172E · Gila Bend, AZThe student plt departed livermore, CA at an undetermined time. He reported that his destination was tucson, AZ. En route stops were made at bakersfield & banning, CA. After refueling at banning, he departed on a unspecified & undetermined route. He stated…NTSB CHI83LA177Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Youngstown, OHThe pilot stated that during a landing, the left wing was caught by the wind and the aircraft drifted to the right. A go-around was initiated but the aircraft struck a runway light and a runway distance marker and nosed over.