NTSB investigations: Cessna 172N, 2010
23 cases on aircraft the registry lists as Cessna 172N. 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 | 1 |
|---|---|
| 1966 | 2 |
| 1967 | 2 |
| 1975 | 1 |
| 1976 | 2 |
| 1977 | 26 |
| 1978 | 62 |
| 1979 | 81 |
| 1980 | 107 |
| 1981 | 86 |
| 1982 | 91 |
| 1983 | 53 |
| 1984 | 55 |
| 1985 | 40 |
| 1986 | 44 |
| 1987 | 42 |
| 1988 | 47 |
| 1989 | 45 |
| 1990 | 46 |
| 1991 | 57 |
| 1992 | 40 |
| 1993 | 51 |
| 1994 | 43 |
| 1995 | 48 |
| 1996 | 37 |
| 1997 | 40 |
| 1998 | 37 |
| 1999 | 46 |
| 2000 | 35 |
| 2001 | 32 |
| 2002 | 43 |
| 2003 | 32 |
| 2004 | 38 |
| 2005 | 26 |
| 2006 | 23 |
| 2007 | 21 |
| 2008 | 21 |
| 2009 | 20 |
| 2010 | 23 |
| 2011 | 22 |
| 2012 | 14 |
| 2013 | 20 |
| 2014 | 15 |
| 2015 | 10 |
| 2016 | 24 |
| 2017 | 19 |
| 2018 | 14 |
| 2019 | 16 |
| 2020 | 25 |
| 2021 | 15 |
| 2022 | 16 |
| 2023 | 20 |
| 2024 | 13 |
| 2025 | 15 |
| 2026 | 11 |
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 ('2072434'))
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 ('2072434'))
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 ERA11LA071Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Bluffton, SCAn in-flight upset of undetermined origin resulting in a forced landing.NTSB ERA11CA061Accident · No injuriesData collectionFinal reportCessna 172N · Gaithersburg, MDThe student pilot's inadequate use of the rudder, and subsequent loss of directional control.NTSB WPR11CA008Accident · No injuriesData collectionFinal reportCessna 172N · Salem, ORThe pilot's failure to maintain directional control during the landing roll.NTSB CEN11CA004Accident · No injuriesData collectionFinal reportCessna 172N · Wabash, INThe student pilot's failure to maintain proper airspeed during the landing and certificated flight instructor's failure to execute a go-around.NTSB ERA10LA426Accident · Minor injuriesLimited investigationFinal reportCessna 172NA total loss of engine power for undetermined reasons.NTSB ERA10CA392Accident · No injuriesData collectionFinal reportCessna 172N · Elk Creek, VAThe student pilot’s continued visual flight into instrument meteorological conditions, which resulted in an off-airport landing.NTSB ERA10CA402Accident · No injuriesData collectionFinal reportCessna 172N · Perry, GAThe pilot's failure to maintain clearance from a pole while taxiing.NTSB ERA10CA381Accident · No injuriesData collectionFinal reportCessna 172N · Stonington, METhe pilot's failure to maintain directional control during a crosswind landing.NTSB ERA10LA377Accident · No injuriesLimited investigationFinal reportCessna 172N · Waynesboro, VAThe pilot's failure to follow the short-field takeoff procedures published in the Pilot's Operating Handbook.NTSB ANC10CA060Accident · No injuriesData collectionFinal reportCessna 172N · Palmer, AKThe pilot's decision to fly towards rising terrain that exceeded the climb capability of the airplane.NTSB WPR10LA307Accident · 1 fatalLimited investigationFinal reportCessna 172N · Angels Camp, CAThe pilot’s failure to maintain airplane control while maneuvering.NTSB CEN10CA336Accident · No injuriesData collectionFinal reportCessna 172N · Maryland Heights, MOThe pilot's improper flare, which resulted in a hard landing.NTSB ERA10LA322Accident · Serious injuriesLimited investigationFinal reportCessna 172N · West Milford, NJThe student pilot’s control interference which resulted in a landing with a higher than normal airspeed, and the commercial pilot’s failure to initiate a go-around to avoid the runway overrun.NTSB ERA10CA289Accident · No injuriesData collectionFinal reportCessna 172N · Sterling, MAThe pilot’s decision to not continue with the go-around, which resulted in a collision with trees. Contributing to the accident was the pilot’s distraction due to the passenger’s panicked condition.NTSB ERA10LA275Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Plattekill, NYThe pilot's failure to place the fuel selector valve in the appropriate position for takeoff resulting in a partial loss of engine power. Contributing to the accident was the pilot's attempted takeoff at a higher than allowed gross weight.NTSB ERA10CA268Accident · No injuriesData collectionFinal reportCessna 172N · Blue Hill, METhe flight instructor’s inability to maintain directional control while landing with gusting winds.NTSB WPR10LA220Accident · Serious injuriesLimited investigationFinal reportCessna 172N · TamuningThe failure of the pilot to maintain clearance with the airplane’s propeller while hand-propping.NTSB ERA10CA244Accident · No injuriesData collectionFinal reportCessna 172N · Poughkeepsie, NYThe pilot's failure to maintain directional control on the landing rollout.NTSB CEN10CA190Accident · No injuriesData collectionFinal reportCessna 172N · New Hudson, MIThe pilot’s failure to maintain directional control during the landing rollout with gusting winds.NTSB CEN10CA178Accident · No injuriesData collectionFinal reportCessna 172N · Ankeny, IAA total loss of engine power due to fuel exhaustion as a result of the pilot's inadequate in-flight fuel monitoring.NTSB ERA10CA167Accident · No injuriesData collectionFinal reportCessna 172 · Poughkeepsie, NYThe pilot's failure to maintain directional control during the landing flare.NTSB CEN10LA123Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Genoa City, WIA total loss of engine power due to the failure of the bolts that held in place the connecting rods to the engine's No. 3 and No. 4 cylinders as a result of the engine overhaul facility's improper installation of the bolts during a recent overhaul.NTSB CEN10FA101Accident · 2 fatalField investigationFinal reportCessna 172 · Holland, MIThe pilot's decision to take off in known instrument meteorological conditions without instrument currency or recent instrument experience, which led to spatial disorientation resulting in an inadvertent spin. Contributing to the accident was the pilot's lack…