NTSB investigations: Cessna 172S, 2005
28 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\") = 2005
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") = 2005
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 LAX06FA059Accident · 1 fatalField investigationFinal reportCessna 172S · Hana, HICollision with mountainous terrain for undetermined reasons.NTSB DEN06FA023Accident · 1 fatalField investigationFinal reportCessna 172S · Pinon, NMthe pilot's failure to maintain control of the airplane for undetermined reasons.NTSB ATL06CA025Accident · No injuriesData collectionFinal reportCessna 172S · Mobile, ALThe pilot's improper landing flare, which resulted in a hard landing.NTSB DEN06CA022Accident · No injuriesData collectionFinal reportCessna 172S · Lawrence, KSthe student pilot's improper decision to continue taxiing through the field. Contributing factor's include student pilot's failure to maintain control during the takeoff roll and the drainage ditch masked by snow.NTSB NYC06LA026Accident · Minor injuriesLimited investigationFinal reportCessna 172S · Laurel, DEThe pilot's improper decision to takeoff from an unimproved field, and his subsequent failure to abort the takeoff prior to collision with a sign and an embankment. Factors in the accident were his improper soft field technique, and the dark night conditions.NTSB DFW05CA253Accident · No injuriesData collectionFinal reportCessna 172S · Batesville, TXThe pilot's failure to maintain clearance from the tree. A contributing factor was the gusty winds.NTSB DEN05CA145Accident · No injuriesData collectionFinal reportCessna 172S · Cedar City, UTthe student pilot's failure to maintain aircraft control during the landing. Factors contributing to the accident were the improper flare and improper recovery from a bounced landing.NTSB LAX05CA302Accident · No injuriesData collectionFinal reportCessna 172S · Show Low, AZthe pilot's selection of a downwind runway for landing and his inadequate compensation for the strong and gusty quartering tail wind conditions, which resulted in a tail strike during landing.NTSB MIA05CA156Accident · No injuriesData collectionFinal reportCessna 172-S · Kendall-Tamiami, FLThe pilot's failure to recover from a bounced landing which resulted in damage to the airplane.NTSB LAX05CA299Accident · No injuriesData collectionFinal reportCessna 172S · San Manuel, AZThe pilot's misjudged flare during a touch-and-go landing.NTSB IAD05LA130Accident · No injuriesLimited investigationFinal reportCessna 172S · Kutztown, PAThe pilot's failure to attain a proper touchdown point as a result of the airplane's excessive airspeed. A factor was the partial loss of engine power due to a seized exhaust valve.NTSB ATL05LA156Accident · No injuriesLimited investigationFinal reportCessna 172S · Opa Locka, FLA loss of engine power for undetermined reasons.NTSB ATL05CA153Accident · No injuriesData collectionFinal reportCessna 172S · Savannah, GAThe instructor's inadequate supervision and failure to maintain directional control, resulting in an on ground collision with terrain.NTSB IAD05CA120Accident · No injuriesData collectionFinal reportCessna 172S · White Plains, NYThe pilot's improper recovery from a bounced landing.NTSB MIA05FA140Accident · 4 fatalField investigationFinal reportCessna 172S · Key West, FLThe failure of the pilot-in-command to maintain directional control of the airplane during the dark, night flight over water, resulting in the uncontrolled descent and in-flight collision with the water. A contributing factor in the accident was the pilot's…NTSB LAX05CA275Accident · No injuriesData collectionFinal reportCessna 172S · Edwards AFB, CAthe pilot's misjudged flare and inadequate recovery technique from the subsequent bounces.NTSB IAD05CA104Accident · No injuriesData collectionFinal reportCessna 172S · Charlottesville, VAThe student pilot's improper flare which resulted in a hard landing.NTSB MIA05LA129Accident · Minor injuriesLimited investigationFinal reportCessna 172S · Glen Saint Mary, FLThe separation of a plastic sleeve off the idle stop of the servo fuel injector for undetermined reasons resulting in decreased fuel flow and subsequent total loss of engine power.NTSB LAX05LA199Accident · No injuriesLimited investigationFinal reportCessna 172M · Carlsbad, CAthe other pilot's inadequate visual lookout and failure to maintain separation while taxiing.NTSB IAD05FA067Accident · 4 fatalField investigationFinal reportCessna 172S · Brooklyn, NYThe pilot's failure to maintain adequate airspeed, which resulted in an inadvertent stall and subsequent impact with terrain.NTSB CHI05CA124Accident · No injuriesData collectionFinal reportCessna 172S · Port Huron, MIThe pilot not performing a go-around and misjudging the flare leading to a hard landing.NTSB MIA05CA121Accident · No injuriesData collectionFinal reportCessna 172SP · Clearwater, FLThe pilot's improper flare and recovery from a bounced landing.NTSB LAX05CA137Accident · No injuriesData collectionFinal reportCessna 172S · Gallup, NMthe pilot's premature liftoff and inadequate remedial action, which resulted in the airplane inadvertently recontacting the runway.NTSB MIA05LA083Accident · No injuriesLimited investigationFinal reportCessna 172S · Palm Beach, FLThe flight crews inadvertent encounter with turbulence in clouds while being vectored by ATC while operating in instrument meteorological conditions. A factor in the accident was the ATC personnel's (ARTCC) inadequate weather avoidance assistance.NTSB LAX05LA118Accident · No injuriesLimited investigationFinal reportCessna 172S · Thermal, CAthe student pilot's inadequate compensation for the crosswind conditions and failure to maintain directional control.NTSB LAX05CA082Accident · No injuriesData collectionFinal reportCessna 172S · Coalinga, CAthe pilot's inadequate recovery from a bounced landing, and his failure to abort the landing.NTSB LAX05LA073Accident · 1 fatalLimited investigationFinal reportCessna 172SP · Casa Grande, AZthe pilot's inadvertent encounter with a rotating propeller. Contributing factors were the dark night conditions and the pilot's fatigued condition.NTSB MIA05CA048Accident · No injuriesData collectionFinal reportCessna 172SP · Clewiston, FLThe pilot's failure to maintain directional control during landing rollout which resulted in the airplane veering off the runway and colliding into an airport sign.