NTSB investigations: Cessna 172N, 2009
20 cases on aircraft the registry lists as Cessna 172N. 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
| 1965 | 1 |
|---|---|
| 1966 | 2 |
| 1967 | 2 |
| 1975 | 1 |
| 1976 | 2 |
| 1977 | 26 |
| 1978 | 62 |
| 1979 | 81 |
| 1980 | 107 |
| 1981 | 86 |
| 1982 | 91 |
| 1983 | 53 |
| 1984 | 55 |
| 1985 | 40 |
| 1986 | 44 |
| 1987 | 42 |
| 1988 | 47 |
| 1989 | 45 |
| 1990 | 46 |
| 1991 | 57 |
| 1992 | 40 |
| 1993 | 51 |
| 1994 | 43 |
| 1995 | 48 |
| 1996 | 37 |
| 1997 | 40 |
| 1998 | 37 |
| 1999 | 46 |
| 2000 | 35 |
| 2001 | 32 |
| 2002 | 43 |
| 2003 | 32 |
| 2004 | 38 |
| 2005 | 26 |
| 2006 | 23 |
| 2007 | 21 |
| 2008 | 21 |
| 2009 | 20 |
| 2010 | 23 |
| 2011 | 22 |
| 2012 | 14 |
| 2013 | 20 |
| 2014 | 15 |
| 2015 | 10 |
| 2016 | 24 |
| 2017 | 19 |
| 2018 | 14 |
| 2019 | 16 |
| 2020 | 25 |
| 2021 | 15 |
| 2022 | 16 |
| 2023 | 20 |
| 2024 | 13 |
| 2025 | 15 |
| 2026 | 11 |
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\") = 2009
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072434'))
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") = 2009
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072434'))
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 ERA10LA055Accident · No injuriesLimited investigationFinal reportCessna 172 · Luray, VAThe pilot's premature rotation and liftoff and her subsequent failure to recognize and correct for the influence of ground effect on the airplane's takeoff performance.NTSB WPR10CA007Accident · No injuriesData collectionFinal reportCessna 172N · San Diego, CAThe pilot’s improper flare and inadequate recovery from a bounced landing.NTSB ERA09CA539Accident · Minor injuriesData collectionFinal reportCessna 172 · Factoryville, PAThe flight instructor's delayed decision to take control of the airplane and execute a missed approach. Contributing to the accident was the lack of communication between the certificated flight instructor and the pilot receiving instruction.NTSB ERA09LA517Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Hillsville, VAThe total loss of engine power for an undetermined reason.NTSB ERA09CA430Accident · No injuriesData collectionFinal reportCessna 172N · Manassas, VAThe student pilot’s failure to maintain directional control during takeoff.NTSB ERA09LA399Accident · No injuriesLimited investigationFinal reportCessna 172N · Rochester, MAAn engine vibration as reported by the pilot, for undetermined reasons.NTSB CEN09CA373Accident · Serious injuriesData collectionFinal reportCessna 172N · Marysville, OHThe pilot's inability to maintain directional control of the airplane during the landing roll for undetermined reasons.NTSB ERA09CA301Accident · No injuriesData collectionFinal reportCessna 172N · Tunkhannock, PAThe pilot's failure to attain the proper touchdown point while landing with a tailwind.NTSB WPR09FA248Accident · 3 fatalField investigationFinal reportCessna 172N · Long Beach, CAThe failure of both pilots to see and avoid each other's aircraft.NTSB WPR09LA245Accident · No injuriesLimited investigationFinal reportCessna 172N · Desert Center, CAA partial loss of engine power due to low compression from an obstructed intake valve. Contributing to the accident was the pilot’s decision to shut down the engine while in flight.NTSB CEN09CA292Accident · No injuriesData collectionFinal reportCessna 172N · Springdale, ARThe student pilot's failure to maintain control of the airplane during the landing roll and subsequent go-around.NTSB CEN09CA253Accident · No injuriesData collectionFinal reportCessna 172N · Roanoke, TXThe partial loss of engine power due to a failure of the throttle control rod-end to carburetor arm hardware. A contributing factor was the pilot's decision to fly the airplane without a current annual inspection.NTSB WPR09CA182Accident · No injuriesData collectionFinal reportCessna 172S · Snohomish, WAAn in-flight collision with a crow.NTSB WPR09LA149Accident · 1 fatalLimited investigationFinal reportCessna 172N · Oceanside, CAA loss of aircraft control for undetermined reasons.NTSB CEN09CA187Accident · No injuriesData collectionFinal reportCessna 172N · Carlisle, ARThe student pilot's improper recovery from a bounced landing.NTSB CEN09CA181Accident · No injuriesData collectionFinal reportCessna 172N · Broomfield, COThe pilot and airplane's inability to compensate for the unforecasted gusting wind conditions.NTSB CEN09LA182Accident · No injuriesLimited investigationFinal reportCessna 172N · Johnson County Exec Airport, KSFailure of the pilot of the Cessna 172S to ensure the taxiway was clear prior to initiating the turn. Contributing to the accident was the failure of the pilot of the Cessna 172N to obtain taxi clearance prior to entering the movement area.NTSB CEN09CA229Accident · No injuriesData collectionFinal reportCessna 172 · Manhattan, KSThe pilot's improper recovery from a bounced landing.NTSB WPR09LA122Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Big Bear Lake, CAThe pilot's failure to maintain clearance from terrain while maneuvering in a ravine. Contributing to the accident was the pilot's decision to continue flight in an area that exceeded the climb rate capabilities of the airplane.NTSB ANC09LA018Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Atmautluak, AKThe pilot's failure to maintain adequate airspeed while landing in gusty winds, which resulted in an aerodynamic stall; his improper aircraft weight calculations; and his operation of the airplane over the allowable gross weight limit.