NTSB investigations: Cessna 172M, IN
37 cases on aircraft the registry lists as Cessna 172M. 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
| 1973 | 3 |
|---|---|
| 1974 | 1 |
| 1975 | 2 |
| 1976 | 2 |
| 1977 | 4 |
| 1978 | 2 |
| 1979 | 3 |
| 1980 | 3 |
| 1981 | 1 |
| 1982 | 2 |
| 1985 | 1 |
| 1987 | 1 |
| 1988 | 1 |
| 1989 | 1 |
| 1996 | 2 |
| 1997 | 1 |
| 1998 | 1 |
| 1999 | 1 |
| 2004 | 1 |
| 2014 | 1 |
| 2017 | 1 |
| 2020 | 1 |
| 2026 | 1 |
Where
Latest 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 c.\"eventStateOrRegion\" = 'IN' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072418'))
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 c."eventStateOrRegion" = 'IN' AND c."eventCountry" = 'USA'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072418'))
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 CEN26LA322Accident · Minor injuriesClass 3 · LimitedPreliminary reportCessna 172M · Hanover, INOn September 16, 2026, about 1905 eastern daylight time, a Cessna 172M airplane, N9909Q, was substantially damaged when it was involved in an accident near Hanover, Indiana. The pilot and passenger sustained minor injuries. The airplane was operated as a…NTSB CEN20LA214Accident · 1 fatalClass 3 · LimitedFinal reportCessna 172 · New Washington, INA high velocity descent and impact with terrain for undetermined reasons.NTSB CEN17LA082Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Hobart, INThe pilot's failure to abort the landing when he recognized the airplane was traveling too fast, which resulted in impact with trees off the end of the runway.NTSB CEN14CA155Accident · No injuriesData collectionFinal reportCessna 172M · South Bend, INThe pilot involved and the phase of flight when the damage was incurred were not determined.NTSB CHI04LA062Accident · No injuriesLimited investigationFinal reportCessna 172M · Jeffersonville, INThe pilot selecting a closed runway for landing and the collapse of the nose landing gear. Factors were the pilot's failure to obtain NOTAM information and the snowbank across the closed runway.NTSB CHI99LA336Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Daleville, INA loss of engine power for undetermined reasons.NTSB CHI98LA149Accident · No injuriesLimited investigationFinal reportCessna 172M · Elkhart, INthe pilot's disorientation that led him to believe he was on the active runway. A factor was the pilot's inattentiveness.NTSB CHI98LA040Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Salem, INthe pilot's misjudgment of distance and altitude, while on final approach to land at night. Factors relating to the accident included: an undetermined electrical malfunction, inoperative flaps, darkness, the pilot not using the landing light, and the…NTSB CHI96LA143Accident · No injuriesLimited investigationFinal reportCessna 172 · Terre Haute, INthe pilot's improper planning/decision, which resulted in his inadequate compensation (or inability to compensate) for the wind condition. The high/gusty wind condition was a related factor.NTSB CHI96LA103Accident · No injuriesLimited investigationFinal reportCessna 172 · Valparaiso, INthe pilot's continued flight into adverse weather. Factors were the low ceilings, icing conditions, airframe ice, and the muddy field.NTSB CHI89LA118Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Indianapolis, INFuel contamination from a deteriorating part in the carburetor. The trees and improper maintenance/servicing of the aircraft were probable contributing factors.NTSB CHI88DEX04Accident · No injuriesFinal reportCessna 172M · Alexandria, INAircraft experienced intermittent engine operation while on final, followed by complete engine failure on landing rollout. Pilot noticed smoke entering cockpit during restart attempt. Aircraft was evacuated by pilot and three passengers. There was an engine…NTSB CHI87LA103Accident · No injuriesLimited investigationFinal reportCessna 172M · Shelbyville, INThe plt's original destn was lexington, KY, however between bluefield, KY and lexington, he amended his destn to indianapolis, IN. The plt stated that fuel consumption was calculated as 7.1 gph, but he did not take into consideration the Cessna 172 time/fuel…NTSB CHI85LA243Accident · No injuriesLimited investigationFinal reportCessna 172 M · Decatur, INThe pilot landing rnwy 36 winds were 210 degrees, 12 knots gusts 18 knots stalled out high onthe wet on the wet sod runway the nose wheel dug in and then broke off the acft then nosed over inverted.NTSB CHI82DA189Accident · No injuriesFinal reportCessna 172 · Evansville, INThe pilots of two Cessna 172 aircraft, N73616 and N2986U, were flying in formation while on a cross-country flight. N73616 contacted Evansville approach and was cleared to intercept the 030 degree radial, outbound from Evansville, IN. As a turn was made to…NTSB CHI82DA094Accident · No injuriesFinal reportCessna 172 · Clarksville, INThe pilot reported that the wind was blowing at 12 knots when he took off on a local flight. However, when he returned to land, it was from 270 degrees at about 30 knots. While landing on runway 18, the aircraft veered off the left side of the runway into…NTSB CHI82FA007Accident · 4 fatalClosedCessna 172 · Kokomo, INNTSB CHI80FEX36Accident · No injuriesClosedCessna 172M · Brownsburg, INNTSB CHI80FET23Accident · Minor injuriesClosedCessna 172M · Woodburn, INNTSB CHI80FEX20Accident · No injuriesClosedCessna 172M · Bloomington, INNTSB CHI80FET03Accident · No injuriesClosedCessna 172M · Mentone, INNTSB CHI79DEX40Accident · No injuriesClosedCessna 172 · Delphi, INNTSB CHI79DEX30Accident · Minor injuriesClosedCessna 172 · Anderson, INNTSB CHI79FET07Accident · No injuriesClosedCessna 172M · Gary, INNTSB CHI78DEX12Accident · No injuriesClosedCessna 172 · Kokomo, INNTSB CHI77FEX36Accident · Serious injuriesClosedCessna 172M · Spencer, INNTSB CHI77DEX31Accident · No injuriesClosedCessna 172 · Boonville, INNTSB CHI77FET09Accident · No injuriesClosedCessna 172M · Kendallville, INNTSB CHI77FEX11Accident · No injuriesClosedCessna 172M · Elwood, INNTSB CHIMMFET05Accident · No injuriesClosedCessna 172M · Hobart, INNTSB CHI77FA001Accident · 1 fatalClosedCessna 172M · Hagerstown, INNTSB CHI75FEA15Accident · No injuriesClosedCessna 172M · Greenwood, INNTSB CHI75DET14Accident · No injuriesClosedCessna 172I · Michigan City, INNTSB CHI74DEA24Accident · No injuriesClosedCessna 172 · Shelbyville, INNTSB CHI74DEA19Accident · No injuriesClosedCessna 172 · Terre Haute, INNTSB CHI73DEA34Accident · No injuriesClosedCessna 172 · Mt.Vernon, INNTSB CHI73AEA30Accident · Minor injuriesClosedCessna 172M · Lafayette, IN