NTSB investigations: Cessna 172M, 2006
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\") = 2006
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") = 2006
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 DFW07CA046Accident · No injuriesData collectionFinal reportCessna 172M · Houston, TXThe pilot's failure to compensate for the existing wind conditions during the landing roll resulting in a loss of control. A contributing factor was the crosswind.NTSB NYC07CA019Accident · No injuriesData collectionFinal reportCessna 172M · Wakefield, VAThe student pilot's failure to maintain control during the landing. A factor to the accident was the wind gusts.NTSB SEA07FA012Accident · 1 fatalField investigationFinal reportCessna 172M · Escalante, UTThe pilot's failure to maintain aircraft control. Contributing factors were the pilot's lack of experience of flying on instruments on a dark night and in rainy weather.NTSB SEA06CA181Accident · No injuriesData collectionFinal reportCessna 172M · Moab, UTThe pilot's failure to obtain current NOTAMS which resulted in an on-ground collision with a construction berm while landing.NTSB ANC06CA127Accident · No injuriesData collectionFinal reportCessna 172 · Healy, AKThe pilot's failure to maintain adequate altitude/clearance while maneuvering, which resulted in an in-flight collision with terrain. Factors associated with the accident were rising terrain, and the pilot's low altitude flight.NTSB LAX06CA253Accident · Serious injuriesData collectionFinal reportCessna 172M · Gasquet, CAthe pilot's selection of a runway favoring tailwind conditions, his delayed decision to go around, and his failure to attain and maintain an adequate airspeed during the aborted landing. Contributing factors were the tailwind and wind shear conditions…NTSB LAX06CA252Accident · No injuriesData collectionFinal reportCessna 172M · San Andreas, CAthe student pilot's improper soft-field takeoff technique and failure to obtain and maintain an adequate airspeed, which resulted in a stall mush. The certificated flight instructor's inadequate supervision of the maneuver was also causal.NTSB ATL06CA116Accident · No injuriesData collectionFinal reportCessna 172M · Augusta, GAThe pilot's improper flare on landing with excessive altitude resulting in a hard landing.NTSB CHI06CA227Accident · No injuriesData collectionFinal reportCessna 172M · Cahokia, ILThe pilot's inadequate flare. A factor was the night light conditions.NTSB SEA06CA103Accident · No injuriesData collectionFinal reportCessna 172M · Hamilton, MTThe pilot's inadequate compensation for the wind conditions during the landing roll which resulted in his failure to maintain directional control. Factors included variable winds and gusty crosswinds.NTSB ANC06LA049Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Tuluksak, AKThe pilot's inadvertent stall/mush during takeoff-initial climb, which resulted in an in-flight collision with trees and terrain. Factors associated with the accident were the pilot's excessive loading of the airplane, his inadequate preflight planning, and a…NTSB ATL06CA065Accident · No injuriesData collectionFinal reportCessna 172 M · Griffin, GAThe pilot's failure to achieve the proper touchdown point, which resulted in an overrun of the runway, collision with an embankment, and subsequent nose over.NTSB MIA06CA083Accident · No injuriesData collectionFinal reportCessna 172M · Vero Beach, FLThe pilot's failure to maintain directional control while executing a go-around in gusty conditions which resulted in the airplane veering off the runway, colliding with a ditch and nosing over.NTSB ATL06CA057Accident · No injuriesData collectionFinal reportCessna 172M · Newnan, GAThe student pilot's failure to maintain directional control on the landing roll out, resulting in the airplane veering off the right side of the runway and colliding with an airport runway sign.NTSB SEA06CA082Accident · No injuriesData collectionFinal reportCessna 172 · Aurora, ORThe student pilot's misjudgment of the landing flare resulting in a hard landing. A related factor was the crosswind.NTSB LAX06CA117Accident · No injuriesData collectionFinal reportCessna 172M · Prescott, AZthe pilot's inadequate compensation for the crosswind conditions and his failure to maintain directional control.NTSB LAX06CA115Accident · No injuriesData collectionFinal reportCessna 172M · Murrieta, CAa partial loss of engine power resulting from the student pilot's mismanagement of the mixture control.NTSB DEN06CA033Accident · No injuriesData collectionFinal reportCessna 172M · Denver, COthe pilot's failure to align the airplane's nose into the direction of the wind while performing the pre-takeoff checklist. A contributing factor was the gusty wind conditions.