NTSB investigations: Cessna 172M, 2013
20 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\") = 2013
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") = 2013
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 WPR14CA074Accident · No injuriesData collectionFinal reportCessna 172M · Fullerton, CAThe pilot's inadequate landing flare, which resulted in a bounced landing.NTSB ANC14LA011Accident · No injuriesLimited investigationFinal reportCessna 172M · Bethel, AKThe pilot’s decision to abort the takeoff with insufficient runway remaining, which resulted in a runway excursion.NTSB CEN14CA027Accident · Serious injuriesData collectionFinal reportCessna 172M · Raymondville, TXThe operation of an airplane by a non-certificated pilot. Contributing to the accident was his failure to maintain airspeed following a total loss of engine power at low altitude, which resulted in an aerodynamic stall. Also contributing was the pilot's…NTSB WPR14LA023Accident · Minor injuriesLimited investigationFinal reportCessna 172 - M · Hardin, MTA rough-running engine and partial loss of power, which resulted from the pilot’s failure to use carburetor heat appropriately while operating in an area conducive to carburetor icing.NTSB ERA13LA339Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Farmingdale, NJThe airplane’s loss of lift shortly after picking up a banner for reasons that could not be determined because postaccident examinations revealed no anomalies that would have precluded normal operation.NTSB ERA13FA330Accident · 1 fatalField investigationFinal reportCessna 172M · Fredericksburg, VAThe pilot's intentional descent into the ground to commit suicide.NTSB WPR13FA294Accident · 1 fatalField investigationFinal reportCessna 172 · Birdseye, UT***This report was modified on August 18, 2015. Please see the docket for this accident to view the original report.*** The operator's improper installation of a supplemental electrical power supply, which caused a short circuit due to inadequate vibration…NTSB CEN13FA364Accident · 4 fatalField investigationFinal reportCessna 172M · Waterford, MIThe pilot's failure to retract the wing flaps before attempting to take off, due to his lack of familiarity with the airplane make and model, which prevented the airplane from maintaining adequate altitude for takeoff.NTSB ERA13LA311Accident · No injuriesLimited investigationFinal reportCessna 172M · Burlington, VTThe pilot's improper turn down an airport access road while attempting to taxi to a runway. Contributing to the accident was the airport management's failure to install proper signage indicating that an airport access road was prohibited to aircraft.NTSB ERA13LA279Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Louisville, KYThe pilot's failure to set the correct flap position before takeoff and his inadequate preflight planning, which resulted in the operation of the airplane over the maximum allowable gross weight, both of which led to an aerodynamic stall at too low an…NTSB WPR13CA241Accident · No injuriesData collectionFinal reportCessna 172M · Truckee, CAThe pilot’s failure to maintain directional control during the landing roll which resulted in a collision with a tree.NTSB CEN13CA272Accident · No injuriesData collectionFinal reportCessna 172M · Thief River Falls, MNThe pilot’s failure to maintain clearance from the power line while on approach to landing.NTSB CEN13LA249Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Covington, LAThe pilot’s failure to maintain airspeed during a banner towing operation, which resulted in the airplane stalling and landing hard.NTSB WPR13LA224Accident · No injuriesLimited investigationFinal reportCessna 172M · Lakeport, CALoss of engine power during climb due to a failure of the No. 2 piston assembly; the reason for the failure could not be determined because of the extent of damage to the piston assembly.NTSB WPR13FA211Accident · 2 fatalClass 3 · FieldFinal reportCessna 172RG · Calabasas, CAThe failure of the pilots in both aircraft to maintain an adequate visual lookout, which resulted in a midair collision.NTSB ERA13LA194Accident · No injuriesLimited investigationFinal reportCessna 172M · New Castle, VAThe pilot's failure to abort the takeoff after recognizing that the airplane was not accelerating properly, which led to an aerodynamic stall. The reason for the lack of acceleration could not be determined because postaccident examinations did not reveal any…NTSB ERA13CA170Accident · No injuriesData collectionFinal reportCessna 172M · Hendersonville, NCThe student pilot’s failure to maintain control of the airplane during an attempted go-around in gusty tailwind conditions.NTSB WPR13FA138Accident · 1 fatalField investigationFinal reportCessna 172M · Saratoga, WYThe pilot’s decision to attempt flight into approaching adverse weather, which led to his low-level flight, encounter with mountain obscuration and moderate turbulence, and his subsequent loss of airplane control. Contributing to the severity of the pilot’s…NTSB CEN13CA161Accident · No injuriesData collectionFinal reportCessna 172M · Jenison, MIThe pilot's failure to maintain directional control while landing on an ice- and snow-covered runway in crosswind conditions.NTSB WPR13LA113Accident · No injuriesLimited investigationFinal reportCessna 172 · Wilcox, AZThe loss of engine power for reasons that could not be determined because postaccident examination did not reveal any abnormalities that would have precluded normal operation.