NTSB investigations: Cessna 172P, 2002
16 cases on aircraft the registry lists as Cessna 172P. 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
| 1969 | 1 |
|---|---|
| 1973 | 1 |
| 1980 | 2 |
| 1981 | 9 |
| 1982 | 30 |
| 1983 | 34 |
| 1984 | 36 |
| 1985 | 32 |
| 1986 | 24 |
| 1987 | 42 |
| 1988 | 39 |
| 1989 | 27 |
| 1990 | 28 |
| 1991 | 39 |
| 1992 | 36 |
| 1993 | 26 |
| 1994 | 22 |
| 1995 | 19 |
| 1996 | 24 |
| 1997 | 25 |
| 1998 | 19 |
| 1999 | 24 |
| 2000 | 21 |
| 2001 | 16 |
| 2002 | 16 |
| 2003 | 25 |
| 2004 | 18 |
| 2005 | 17 |
| 2006 | 9 |
| 2007 | 10 |
| 2008 | 13 |
| 2009 | 9 |
| 2010 | 16 |
| 2011 | 14 |
| 2012 | 12 |
| 2013 | 6 |
| 2014 | 6 |
| 2015 | 12 |
| 2016 | 9 |
| 2017 | 7 |
| 2018 | 10 |
| 2019 | 4 |
| 2020 | 5 |
| 2021 | 7 |
| 2022 | 10 |
| 2023 | 7 |
| 2024 | 9 |
| 2025 | 7 |
| 2026 | 9 |
Where
Latest 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 ('2072436'))
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 ('2072436'))
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 SEA03FA013Accident · 2 fatalField investigationFinal reportCessna 172P · Malaga, WAThe pilot's attempted VFR flight into IMC resulting in the aircraft colliding with trees and up sloping terrain. Contributing factors were clouds, trees, and uphill terrain. The pilot’s performance and judgment were likely impaired by the effects of…NTSB DEN03LA003Accident · No injuriesLimited investigationFinal reportCessna 172P · Broomfield, COthe pilot misjudging the clearance between the airplane and a fixed object during taxi. Contributing factors were the pilot's attention being diverted and sunglare.NTSB CHI02LA280Accident · No injuriesLimited investigationFinal reportCessna 172P · Sturtevant, WIThe proper touchdown point not attained and the approach speed not obtained/maintained by the pilot.NTSB ATL02LA168Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Mocksville, NCThe pilot's failure to maintain airspeed during the takeoff and initial climb which resulted in an inadvertent stall and the subsequent collision with trees.NTSB CHI02LA255Accident · No injuriesLimited investigationFinal reportCessna 172P · Buffalo City, WIThe malfunction of the seat positioning system for undetermined reasons, which resulted in the loss of directional control. A factor to the accident was the descending embankment.NTSB LAX02LA237Accident · No injuriesLimited investigationFinal reportCessna 172P · Creston, CAthe pilot's inadequate in-flight planning/decision, which resulted in fuel exhaustion and loss of engine power. A factor in the accident was the dark night conditions.NTSB LAX02LA241Accident · No injuriesLimited investigationFinal reportCessna 172P · Mesa, AZthe pilot of the other airplane'ss use of an excessive taxi speed and too close of a spacing interval to the Cessna 152, which resulted in an on-ground collision when the Cessna 152 abruptly stopped.NTSB ATL02LA140Accident · No injuriesLimited investigationFinal reportCessna 172P · Merritt Island, FLThe pilot's improper recovery after a bounced landing and improper landing flare which resulted in the airplane colliding with the runway.NTSB CHI02LA102Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Council Bluffs, IAThe student pilot's failure to maintain control of the airplane and the subsequent inadvertent stall. A factor associated with the accident was the student's lack of total experience.NTSB FTW02LA147Accident · No injuriesLimited investigationFinal reportCessna 172P · McKinney, TXthe student pilot's failure to properly recover from a bounced landing which resulted in the airplane porpoising. A contributing factor was the student pilot's improper landing flare which resulted in a bounced landing.NTSB ATL02LA073Accident · No injuriesLimited investigationFinal reportCessna 172P · Pensacola, FLThe pilot's inadequate compensation for a crosswind and his failure to maintain directional control during the landing roll. Contributing to the accident was the pilot's decision to land with a tailwind.NTSB IAD02LA038Accident · No injuriesLimited investigationFinal reportCessna 172P · Ocean City, NJThe pilot's inadequate compensation for wind and his failure to maintain directional control.NTSB IAD02FA037Accident · 4 fatalField investigationFinal reportCessna 172P · Ocean City, MDThe pilot's spatial disorientation, which resulted in his subsequent loss of control of the airplane. A factor was the dark night, over water visual conditions.NTSB NYC02LA070Accident · No injuriesLimited investigationFinal reportCessna 172P · Coatesville, PAThe student pilot's loss of aircraft control which resulted in a hard landing, and the CFI's delayed remedial action. Factors related to the accident were the fatigue cracks which initiated at the attachment hole on the landing gear strut, and the crosswind…NTSB CHI02LA078Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Dowagiac, MIThe pilot's inadequate compensation for the wind conditions that resulted in directional control not being maintained during the landing roll. Factors to the accident were the pilot's inadequate in-flight decision to attempt the landing with a gusting 20 knot…NTSB MIA02LA051Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Levittown, PRthe failure of maintenance personnel to comply with aircraft manufacturer's inspection procedures, resulting in corrosion and separation of the aileron control cable in flight and the subsequent forced landing in a swamp.