NTSB investigations: Cessna 172S, 2014
18 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\") = 2014
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") = 2014
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 ERA15CA056Accident · No injuriesData collectionFinal reportCessna 172S · Sarasota, FLThe student pilot's failure to maintain airplane control during the initial climb, resulting in a runway excursion and substantial damage to the engine firewall. The student pilot's lack of overall flying experience was a factor.NTSB ERA15FA046Accident · 1 fatalField investigationFinal reportCessna 172 · Hinton, VAThe flight instructor’s decision to conduct a night training flight in mountainous terrain without conducting or allowing the student to conduct appropriate preflight planning and his lack of situational awareness of the surrounding terrain altitude, which…NTSB WPR15LA025Accident · No injuriesLimited investigationFinal reportCessna 172S · Santa Monica, CAThe separation of a section of a propeller blade due to fatigue cracking. Contributing to the accident was the operator’s failure to comply with the manufacturer’s maintenance and inspection instructions.NTSB WPR15CA028Accident · No injuriesData collectionFinal reportCessna 172 - S · Hawthorne, CAThe pilot's improper flare which resulted in a loss of aircraft control and subsequent hard landing.NTSB WPR15LA014Accident · Serious injuriesLimited investigationFinal reportCessna 172S · Big Bear, CAA partial loss of engine power for reasons that could not be determined because postaccident examination of the airframe and engine did not reveal any anomalies that would have precluded normal operation.NTSB WPR15CA004Accident · Minor injuriesData collectionFinal reportCessna 172S · Sedona, AZThe pilot's failure to maintain airplane control during the landing roll out.NTSB ERA14CA452Accident · No injuriesData collectionFinal reportCessna 172S · Naples, FLThe student pilot's improper landing flare, which resulted in a hard landing. Contributing to the accident was the pilot's self-induced pressure to land due to the deteriorating weather conditions.NTSB WPR14CA351Accident · No injuriesData collectionFinal reportCessna 172S · Santa Ynez, CAThe student pilot's inadequate flare and loss of aircraft control during landing, which resulted in multiple bounces.NTSB ERA14CA317Accident · Minor injuriesData collectionFinal reportCessna 172S · Orlando, FLThe flight instructor's failure to maintain control while taxiing in a strong gusty wind.NTSB CEN14CA322Accident · No injuriesData collectionFinal reportCessna 172S · Knox, INThe student pilot's use of excessive back pressure on the flight controls during an attempted go around that induced a stall and loss of control.NTSB ERA14FA283Accident · 2 fatalField investigationFinal reportCessna 172S · Daytona Beach, FLA partial loss of engine power during the initial climb after takeoff for reasons that could not be determined due to the postaccident condition of the wreckage. Contributing to the accident was the pilots' decision to turn back to the airport, which led to…NTSB ERA14CA273Accident · No injuriesData collectionFinal reportCessna 172S · Harrisburg, PAThe pilot's failure to compensate for wind conditions during landing, which resulted in a hard landing.NTSB WPR14CA163Accident · No injuriesData collectionFinal reportCessna 172S · Everett, WAThe pilot's failure to maintain directional control during a takeoff, which resulted in the airplane veering off the runway surface and colliding with a sign.NTSB CEN14CA191Accident · No injuriesData collectionFinal reportCessna 172S · Albuquerque, NMThe student pilot's improper flare that resulted in a bounced landing.NTSB CEN14CA187Accident · No injuriesData collectionFinal reportCessna 172 · Larimore, NDFailure of the pilot to attain and maintain sufficient control inputs to compensate for the crosswind. Contributing to the accident was the flight instructor's failure to adequately monitor the pilot and the flight.NTSB ERA14CA127Accident · Minor injuriesData collectionFinal reportCessna 172S · Caldwell, NJThe pilot's failure to maintain directional control while landing.NTSB ERA14CA124Accident · No injuriesData collectionFinal reportCessna 172S · Mansfield, MAThe student pilot's failure to maintain an adequate approach glide path, which resulted in a collision with a snow bank.NTSB ERA14CA109Accident · No injuriesData collectionFinal reportCessna 172S · Immokalee, FLThe student pilot's improper landing flare, which resulted in a hard landing.