NTSB investigations: Cessna 172S, 2023
13 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\") = 2023
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") = 2023
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 ERA24LA033Accident · Minor injuriesClass 3 · LimitedFinal reportCessna 172S · Orlando, FLA partial loss of engine power during initial climb after takeoff for undetermined reasons.NTSB CEN23LA421Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Midland, TXThe student pilot’s improper landing flare, which resulted in a hard, bounced landing, and the nose landing gear collapse.NTSB CEN23LA430Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · West Bend, WIThe pilot’s inadequate landing flare that resulted in a hard landing and impact with the runway.NTSB CEN23LA348Accident · Minor injuriesClass 4 · LimitedFinal reportCessna 172 · Philadelphia, PAThe pilot receiving instruction’s failure to maintain control during a go-around. Contributing to the accident was the flight instructor’s inadequate supervision of the flight.NTSB CEN23LA354Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Clewiston, FLThe student pilot’s improper landing flare, which resulted in a hard landing on the nose landing gear. Contributing to the accident was the flight instructor’s inadequate supervision of the student pilot.NTSB WPR23LA298Accident · No injuriesClass 4 · LimitedFinal reportCessna 152 · Long Beach, CAThe flight instructor’s inattention during ground operations, which resulted in unintentional movement of the airplane and ground collision with another airplane.NTSB WPR23LA253Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Novato, CAThe pilot's failure to maintain directional control of the airplane during the landing roll for a touch and go, which resulted in a collision with terrain.NTSB WPR23LA199Accident · No injuriesClass 3 · LimitedFinal reportCessna 172S · Casa Grande, AZAn in-flight separation of the throttle linkage, which resulted in a loss of throttle control. Contributing to the accident was maintenance personnel’s failure to follow the maintenance manual inspection procedure for the throttle cable assembly.NTSB CEN23LA175Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Brookings, SDThe student pilot’s failure to maintain pitch and directional control during the takeoff roll. Contributing to the accident, was the student pilot’s delay in relinquishing control of the airplane and the instructor's delayed reaction before the loss of…NTSB WPR23FA172Accident · 1 fatalClass 3 · FieldFinal reportCessna 172S · Los Angeles, CAThe pilot’s failure to maintain clearance with the hilly terrain resulting from his loss of situational awareness due to the deteriorating weather conditions as he descended to approach his destination airport.NTSB CEN23LA159Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Fredericksburg, TXThe pilot’s failure to maintain airplane control during an attempted go-around resulting in abnormal contact with the runway pavement and a runway excursion.NTSB CEN23LA122Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Princeton, MNThe pilot’s failure to maintain directional control during the takeoff roll. Contributing to the accident, was the runway condition combined with a right crosswind.NTSB CEN23LA102Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Limon, COThe pilot’s failure to maintain directional control during the takeoff roll.