NTSB investigations: Cessna 172M, 2010
15 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
| 1972 | 3 |
|---|---|
| 1973 | 24 |
| 1974 | 59 |
| 1975 | 82 |
| 1976 | 104 |
| 1977 | 99 |
| 1978 | 92 |
| 1979 | 80 |
| 1980 | 59 |
| 1981 | 50 |
| 1982 | 53 |
| 1983 | 34 |
| 1984 | 35 |
| 1985 | 34 |
| 1986 | 38 |
| 1987 | 29 |
| 1988 | 28 |
| 1989 | 38 |
| 1990 | 37 |
| 1991 | 36 |
| 1992 | 31 |
| 1993 | 37 |
| 1994 | 24 |
| 1995 | 29 |
| 1996 | 23 |
| 1997 | 35 |
| 1998 | 30 |
| 1999 | 22 |
| 2000 | 22 |
| 2001 | 30 |
| 2002 | 26 |
| 2003 | 24 |
| 2004 | 18 |
| 2005 | 16 |
| 2006 | 18 |
| 2007 | 16 |
| 2008 | 24 |
| 2009 | 14 |
| 2010 | 15 |
| 2011 | 13 |
| 2012 | 18 |
| 2013 | 20 |
| 2014 | 20 |
| 2015 | 9 |
| 2016 | 10 |
| 2017 | 19 |
| 2018 | 14 |
| 2019 | 13 |
| 2020 | 16 |
| 2021 | 8 |
| 2022 | 24 |
| 2023 | 12 |
| 2024 | 14 |
| 2025 | 12 |
| 2026 | 8 |
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\") = 2010
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 year(c."eventDate") = 2010
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 CEN11LA082Accident · 1 fatalLimited investigationFinal reportCessna 172M · Velma, OKThe pilot’s failure to maintain control of the airplane while maneuvering, which resulted in an inadvertent stall and subsequent impact with terrain. Contributing to the accident was the pilot's relative inexperience in pipeline patrols.NTSB CEN10CA576Accident · No injuriesData collectionFinal reportCessna 172M · Belle Plaine, MNThe pilot's loss of directional control due to an encounter with soft terrain while landing.NTSB CEN10CA562Accident · Minor injuriesData collectionFinal reportCessna 172M · Point Lookout, MOThe pilot receiving instruction's failure to attain the proper touchdown point and execute a go-around and the CFI’s delayed remedial action, which resulted in a runway overrun.NTSB ERA10FA414Accident · 2 fatalField investigationFinal reportCessna 172 · Orange, MAThe pilots did not maintain control of the airplane during a flight in dark night conditions due to spatial disorientation.NTSB WPR10FA384Accident · Minor injuriesField investigationFinal reportCessna 172 · Roche Harbor, WAThe pilot’s failure to attain an adequate climb airspeed due to his use of flaps for takeoff, and his selection of a runway, which resulted in an uphill, and possibly downwind, takeoff and subsequent collision with a known obstacle. Contributing to the…NTSB CEN11CA018Accident · Minor injuriesData collectionFinal reportCessna 172M · Newton, KSThe pilot’s inadequate flare, which resulted in a hard landing.NTSB WPR10CA382Accident · No injuriesData collectionFinal reportBoeing PT-13B · Santa Rosa, CAThe failure of the pilot of another airplane to maintain clearance while taxiing.NTSB WPR10CA323Accident · No injuriesData collectionFinal reportCessna 172M · Twin Falls, IDThe student pilot's improper landing flare.NTSB OPS10IA090Incident · No injuriesIncident investigationFinal reportBoeing 737-7H4 · Burbank, CAThe improper separation procedures by air traffic control.NTSB CEN10CA212Accident · No injuriesData collectionFinal reportCessna 172M · Coldwater, KSThe pilot's failure to compensate for gusting crosswinds resultuing in the loss of directional control while landing.NTSB CEN10CA199Accident · Serious injuriesData collectionFinal reportCessna 172 · Lawton, OKThe private pilot's failure to maintain adequate airspeed, which resulted in a stall, and the failure of both pilots to initiate a go-around. Contributing to the severity of both pilots' injuries was the lack of available shoulder harnesses.NTSB ERA10CA181Accident · No injuriesData collectionFinal reportCessna 172M · Connelsville, PAA total loss of engine power due to fuel exhaustion due to the pilot's failure to refuel.NTSB CEN10CA158Accident · No injuriesData collectionFinal reportCessna 172M · Waupaca, WIThe student pilot's failure to maintain directional control while taking off in gusting winds.NTSB ANC10LA013Accident · No injuriesLimited investigationFinal reportCessna 172M · Bethel, AKThe pilot's failure to maintain directional control of the airplane during takeoff.NTSB WPR10LA115Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Joshua Tree, CAThe certified flight instructor's decision to continue visual flight into deteriorating weather, which resulted in his inadvertent encounter with instrument meteorological conditions and subsequent failure to maintain clearance with terrain.