NTSB investigations: Cessna 172M, 2002
26 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\") = 2002
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") = 2002
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 CHI03LA040Accident · No injuriesLimited investigationFinal reportCessna 172M · Moline, ILThe pilot's failure to maintain altitude clearance during a base to final turn on approach. Contributing factors to the accident were the night conditions and the trees.NTSB FTW03LA056Accident · No injuriesLimited investigationFinal reportCessna 172M · Vici, OKThe pilot's departure and continued flight into adverse weather conditions. Contributing factors were the icing conditions, and the lack of suitable terrain for the precautionary landing.NTSB LAX03LA033Accident · No injuriesLimited investigationFinal reportCessna 172M · Rosamond, CAThe fatigue failure of left main landing gear strut at the upper fuselage aft attachment hole, which resulted in the collapse of the left main landing gear during the landing roll.NTSB ANC03LA014Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Anchorage, AKThe pilot's failure to adequately remove frost/ice from the airplane which resulted in an inadvertent stall/mush during the takeoff/initial climb.NTSB LAX03LA023Accident · No injuriesLimited investigationFinal reportCessna 172M · Mesquite, NVThe pilot's failure to maintain directional control during takeoff. A contributing factor was the ditch.NTSB MIA03FA007Accident · 2 fatalField investigationFinal reportCessna 172M · Coral Springs, FLThe failure of the dual students and flight instructors on both N9840V and N6101F to see and avoid each other, which resulted in a midair collision.NTSB ATL03LA005Accident · No injuriesLimited investigationFinal reportCessna 172 · Opa Locka, FLThe pilot' inadequate evaluation of weather information, and the selection of the wrong runway that resulted in an attempted takeoff with a tailwind and the subsequent loss of control during takeoff.NTSB IAD02LA095Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Edinburg, VAA loss of engine power for undetermined reasons.NTSB ATL02LA154Accident · No injuriesLimited investigationFinal reportCessna 172M · Enterprise, ALThe pilot's delayed flare on landing that resulted in a hard landing.NTSB IAD02LA082Accident · No injuriesLimited investigationFinal reportCessna 172M · Mount Pocono, PAThe pilot's improper flare, which resulted in a hard landing.NTSB ATL02LA151Accident · No injuriesLimited investigationFinal reportCessna 172M · Dahlonega, GAThe pilot's improper recovery from a bounced landing and failure to maintain directional control resulting in the airplane going off the left side of the runway and colliding with a ditch.NTSB DEN02LA066Accident · No injuriesLimited investigationFinal reportCessna 172M · Hite, UTthe pilot's improper in-flight planning resulting in fuel exhaustion. A factor relating to the accident was the unsuitable terrain encountered during the forced landing attempt.NTSB DEN02LA060Accident · No injuriesLimited investigationFinal reportCessna 172M · Telluride, COthe pilot not maintaining proper aircraft control resulting in a hard landing. Factors contributing to this accident were the high airspeed, the porpoise encountered during the landing, and the pilot's delayed remedial action resulting in the damage to the…NTSB LAX02LA199Accident · No injuriesLimited investigationFinal reportCessna 172M · Saint Johns, AZthe pilot's inadequate compensation for wind conditions resulting in a loss of directional control and collision with terrain. Related factors were the wind gusts, crosswind and soft terrain.NTSB FTW02LA178Accident · No injuriesLimited investigationFinal reportCessna 172M · Kirbyville, TXthe pilot's failure to attain the proper touchdown point. A contributing factor was the loose gravel.NTSB LAX02LA182Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Mountain Ranch, CAthe pilot's inadequate preflight planning/preparation and his in-flight planning/decision resulting in fuel exhaustion and loss of engine power.NTSB SEA02LA093Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Anacortes, WAThe pilot's improper decision to continue his flight after failing to take on fuel at a planned en route refueling stop, which lead to a loss of power from fuel exhaustion while on final approach to his round-robin final destination. Factors include…NTSB LAX02LA153Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Green Valley, AZThe pilot's failure to identify the wind direction, which led to an attempted downwind landing approach that resulted in a hard landing and severe bounce. Also causal was the pilot's failure to promptly retract the flaps during the rejected landing after…NTSB LAX02LA135Accident · No injuriesLimited investigationFinal reportCessna 172M · Avalon, CAThe pilot's inadequate bounced landing recovery technique, which resulted in an inadvertent porpoise.NTSB LAX02LA106Accident · No injuriesLimited investigationFinal reportCessna 172M · Tucson, AZthe pilot's misjudged landing flare and improper bounced landing recovery.NTSB MIA02LA180Accident · No injuriesLimited investigationFinal reportCessna 172M · Kissimmee, FLThe pilot's failure to maintain the proper clearance while taxing the airplane which resulted in the left wing tip colliding with an object and damage to the airplane. A related factor was night conditions.NTSB MIA02LA064Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Marion, SCThe loss of engine power during takeoff/initial climb due to undetermined reasons, resulting in a landing on unsuitable terrain.NTSB FTW02LA082Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Mount Selman, TXthe loss of engine power for an undetermined reason, which resulted in a forced landing. A factor was the lack of suitable terrain for the forced landing.NTSB LAX02LA070Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Payson, AZFailure of the pilot to maintain directional control of the airplane. A contributing factor was the premature raising of the flaps.NTSB FTW02LA067Accident · No injuriesLimited investigationFinal reportCessna 172 · Iraan, TXThe pilot's failure to maintain directional control during landing roll. Contributing factors were the pilot's selection of a downwind runway for landing, the tail wind condition, and his lack of total experience in the type of aircraft.NTSB ATL02LA039Accident · No injuriesLimited investigationFinal reportCessna 172M · Sanford, NCThe pilots failure to maintain directional control during landing roll that resulted in a collision with an airport sign. Factors were wet runway surface and wind gust.