NTSB investigations: Cessna 172S, 2002
22 cases on aircraft the registry lists as Cessna 172S. 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
| 1967 | 2 |
|---|---|
| 1970 | 1 |
| 1972 | 1 |
| 1979 | 3 |
| 1987 | 1 |
| 1999 | 2 |
| 2000 | 4 |
| 2001 | 20 |
| 2002 | 22 |
| 2003 | 29 |
| 2004 | 27 |
| 2005 | 28 |
| 2006 | 25 |
| 2007 | 26 |
| 2008 | 31 |
| 2009 | 22 |
| 2010 | 27 |
| 2011 | 20 |
| 2012 | 29 |
| 2013 | 24 |
| 2014 | 18 |
| 2015 | 18 |
| 2016 | 29 |
| 2017 | 24 |
| 2018 | 22 |
| 2019 | 23 |
| 2020 | 18 |
| 2021 | 22 |
| 2022 | 9 |
| 2023 | 13 |
| 2024 | 14 |
| 2025 | 18 |
| 2026 | 14 |
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 ('2072439', '2072442'))
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 ('2072439', '2072442'))
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 NYC03LA032Accident · No injuriesLimited investigationFinal reportCessna 172S · Akron, OHThe pilot's improper flare which resulted in a hard landing.NTSB CHI03LA075Accident · No injuriesLimited investigationFinal reportCessna 172S · Tea, SDThe student pilot's improper flare. The pilot's lack of experience and diverted attention were factors.NTSB CHI03LA015Accident · No injuriesLimited investigationFinal reportCessna 172 · St. Paul, MNThe student pilot failed to maintain directional control. A factor was the runway sign.NTSB SEA02FA185Accident · 2 fatalField investigationFinal reportCessna 172S · Medford, ORTerrain clearance was not maintained during cruise flight. Dark night and mountainous terrain were factors.NTSB CHI02LA291Accident · No injuriesLimited investigationFinal reportCessna 172S · Boyne Falls, MIThe pilot's improper flare during landing.NTSB ATL02LA166Accident · No injuriesLimited investigationFinal reportCessna 172S · Immokalee, FLThe student pilot's improper flare at touchdown resulted in a hard landing while performing an off-airport precautionary landing after the inadvertent activation of the autopilot.NTSB IAD02FA086Accident · 2 fatalField investigationFinal reportCessna 172S · Plainville, CTAn in-flight engine compartment fire of unknown origin, and a loss of engine power for undetermined reasons. Also causal, was the pilot's failure to maintain airspeed during a turn back to the airfield, which resulted in an inadvertent stall and subsequent…NTSB FTW02LA224Accident · Serious injuriesLimited investigationFinal reportCessna 172S · Marietta, OKThe pilot's failure to maintain adequate airspeed which resulted in a stall.NTSB DEN02LA088Accident · No injuriesLimited investigationFinal reportCessna 172S · Englewood, COthe instructor's inadequate supervision of the flight and his premature raising of the flaps, resulting in a hard landing.NTSB MIA02GA137Accident · 3 fatalFinal reportCessna 172S · Tyner, NCThe loss of power for undetermined reasons, and the pilot's failure to maintain airspeed.NTSB MIA02LA112Accident · No injuriesLimited investigationFinal reportCessna 172S · Kill Devil Hill, NCthe pilot's failure to maintain control of the airplane after an attempted aborted landing, and while braking during the landing roll, which resulted in the airplane departing the end of the runway and impacting with a ditch.NTSB LAX02LA192Accident · Minor injuriesLimited investigationFinal reportCessna 172S · Goldfield, NVThe pilot's failure to maintain control of the airplane during a high density altitude takeoff. Contributing factors were the pilot's lack of experience in the type of operation and a wind gust.NTSB LAX02LA184Accident · No injuriesLimited investigationFinal reportCessna 172S · Monterey, CAThe pilot was unfamiliar with the airplane's systems and failed to set the elevator trim in accordance with the published checklist.NTSB MIA02FA104Accident · 1 fatalField investigationFinal reportCessna 172S · Lutz, FLThe suicidal act by the pilot resulting in the in-flight collision with trees then the ground. A contributing factor in the accident was the pilot's depression. Findings in the investigation were the pilot's overdose of zolpidem and citalopram before the…NTSB LAX02LA167Accident · No injuriesLimited investigationFinal reportCessna 172S · Scottsdale, AZthe student pilot's improper recovery from a bounced landing and failure to maintain directional control on the landing roll, which resulted in a collision with a runway sign.NTSB MIA02LA091Accident · No injuriesLimited investigationFinal reportCessna 172S · Daytona Beach, FLthe pilot misjudged the landing flare, resulting in a hard landing, and damage to the airplane.NTSB FTW02LA115Accident · No injuriesLimited investigationFinal reportCessna 172S · Angel Fire, NMThe pilots failure to maintain directional control during the crosswind landing. A contributing factor was the gusting wind condition.NTSB LAX02LA133Accident · No injuriesLimited investigationFinal reportCessna 172S · Phoenix, AZthe pilot flaring the airplane too high above the runway causing a stall and resulting in the hard landing. Factors relating to the accident were the light conditions (dusk) and the pilot's lack of total experience in the type of airplane.NTSB LAX02LA130Accident · No injuriesLimited investigationFinal reportCessna 172S · Palm Springs, CAThe pilot lost directional control and collided with a runway edge light and taxiway sign.NTSB LAX02LA092Accident · Minor injuriesLimited investigationFinal reportCessna 172S · Santa Paula, CAThe pilot's selection of the wrong landing runway due to his failure to correctly interpret wind indicators, which resulted in his landing with a tailwind.NTSB LAX02LA084Accident · No injuriesLimited investigationFinal reportCessna 172S · Glendale, AZThe pilot of the landing airplane failed to maintain directional control resulting in the on-ground collission.NTSB FTW02LA068Accident · No injuriesLimited investigationFinal reportCessna 172S · Sugar Land, TXthe student pilot's failure to maintain directional control during landing.