NTSB investigations: Cessna 172M, 2004
18 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\") = 2004
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") = 2004
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 NYC05LA002Accident · Serious injuriesLimited investigationFinal reportCessna 152 · Harrison, OHThe Cessna 152 pilot's improper traffic pattern procedure and improper radio communication, which resulted in a mid-air collision with a Cessna 172. A factor in the accident was both pilots' failure to maintain an adequate visual lookout.NTSB NYC05CA003Accident · No injuriesData collectionFinal reportCessna 172M · Eliot, METhe pilot's inadequate in-flight planning decision, which resulted a loss of engine power due to fuel exhaustion.NTSB DEN04LA147Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Provo, UTthe pilot's premature liftoff which resulted in failure to attain airspeed which resulted in a stall.NTSB CHI04LA283Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Houstonia, MOThe fatigue failure of the piston end of the connecting rod and the pilot's failure to maintain aircraft control during the forced landing.NTSB NYC04LA211Accident · No injuriesLimited investigationFinal reportCessna 172M · Medina, OHThe partial loss of engine power due to inadequate maintenance and by failure to comply with service instruction for low engine compression.NTSB IAD04LA036Accident · 1 fatalLimited investigationFinal reportCessna 172M · Brownville Junc, METhe pilot's continued visual flight into instrument meteorological conditions, which resulted in the airplane's controlled flight into rising terrain. Factors included the instrument meteorological conditions and the rising terrain.NTSB CHI04CA209Accident · Minor injuriesData collectionFinal reportCessna 172M · Sublette, KSThe student pilot's inadequate compensation for the crosswind condition, and her failure to maintain aircraft control during landing. Factors contributing to the accident included the student pilot's unsuccessful recovery from the bounced landings and the…NTSB NYC04FA171Accident · 1 fatalField investigationFinal reportCessna 172M · Brookville, OHThe student pilot's control interference while the flight instructor was maneuvering to avoid a tree, which resulted in a failure to maintain airspeed and a stall/mush.NTSB ANC04IA078Incident · No injuriesIncident investigationFinal reportCessna 172M · Aniak, AKThe pilot's inadequate in-flight planning/decision which resulted in fuel exhaustion and the loss of engine power.NTSB ATL04LA167Accident · No injuriesLimited investigationFinal reportCessna 172M · Winston Salem, NCThe pilot's failure to maintain clearance from the fence post, while taxing which resulted in a collision.NTSB FTW04LA145Accident · No injuriesLimited investigationFinal reportCessna 172 · Levelland, TXThe student pilot's failure to maintain directional control and his inadequate compensation for the winds.NTSB SEA04LA096Accident · No injuriesLimited investigationFinal reportCessna 172M · Vernonia, ORThe instructor pilot's misjudgment of speed and distance and his failure to execute a go-around resulting in an overrun of the runway.NTSB CHI04LA104Accident · No injuriesLimited investigationFinal reportCessna 172M · New Munster, WIVisual lookout not maintained by the pilots of both airplanes.NTSB SEA04LA049Accident · No injuriesLimited investigationFinal reportCessna 172M · Eltopia, WARemedial action delayed during the takeoff roll. Factors include rough/uneven terrain.NTSB NYC04CA072Accident · No injuriesData collectionFinal reportCessna 172 · West Dover, VTThe pilot's failure to maintain aircraft control, and his failure to perform a go-around. Factors were wind gusts and the pilot's lack of flight experience.NTSB NYC04CA064Accident · No injuriesData collectionFinal reportCessna 172M · Cumberland, MDThe pilot's inadequate compensation for the crosswind while landing. A factor was the crosswind.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 ANC04LA020Accident · No injuriesLimited investigationFinal reportCessna 172 · Girdwood, AKThe pilot's delay in aborting the takeoff, which resulted in an overrun and collision with a snowbank. A factor in the accident was an inoperative airspeed indicator.