NTSB investigations: Cessna 172S, MN
12 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
| 2000 | 1 |
|---|---|
| 2002 | 1 |
| 2003 | 2 |
| 2006 | 1 |
| 2009 | 2 |
| 2011 | 1 |
| 2017 | 1 |
| 2020 | 1 |
| 2022 | 1 |
| 2023 | 1 |
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 c.\"eventStateOrRegion\" = 'MN' AND c.\"eventCountry\" = 'USA'
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 c."eventStateOrRegion" = 'MN' AND c."eventCountry" = 'USA'
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 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 ERA23FA001Accident · 3 fatalClass 3 · FieldFinal reportCessna 172S · Hermantown, MNThe pilot’s loss of airplane control due to spatial disorientation during initial climb in dark night and low instrument meteorological conditions, which resulted in a descent into terrain. Contributing to the accident was the pilot’s fatigue due to a long…NTSB CEN21LA083Accident · Serious injuriesClass 4 · LimitedFinal reportCessna 172 · Glencoe, MNA bystander’s inadvertent contact with the propeller while the engine was running.NTSB GAA18CA085Accident · No injuriesData collectionFinal reportCessna 172 · Park Rapids, MNThe student pilot’s improper landing flare, which resulted in the propeller striking the ground.NTSB CEN11CA624Accident · No injuriesData collectionFinal reportCessna 172S · Bemidji, MNThe student pilot's improper flare, which resulted in a hard landing.NTSB CEN09LA579Accident · Minor injuriesLimited investigationFinal reportCessna 172S · Park Rapids, MNThe pilot's failure to maintain a proper climb rate during a night takeoff.NTSB CEN09LA586Accident · No injuriesLimited investigationFinal reportCessna 172S · Duluth, MNThe pilot's failure to maintain aircraft control during landing, resulting in a hard landing and a propeller strike with the ground.NTSB CHI07CA027Accident · Serious injuriesData collectionFinal reportCessna 172S · Warroad, MNThe propeller striking the individual who was positioning the propeller in anticipation of hand-propping the engine.NTSB CHI03FA284Accident · 3 fatalField investigationFinal reportCessna 172S · Lake Elmo, MNBoth pilots failed to maintain adequate visual lookout and did not maintain clearance from the other aircraft.NTSB CHI03LA061Accident · No injuriesLimited investigationFinal reportCessna 172 · Lakeville, MNThe pilot's inadequate removal of ice and snow during the airplane preflight, and the subsequent loss of control due to the airplane being covered with ice.NTSB CHI03LA015Accident · No injuriesLimited investigationFinal reportCessna 172 · St. Paul, MNThe student pilot failed to maintain directional control. A factor was the runway sign.NTSB CHI01IA047Incident · No injuriesIncident investigationFinal reportCessna 172S · St. Cloud, MNthe fatigue failure of the propeller blade during the initial takeoff climb. The failure was a result of a material defect, which occurred during the manufacturing process and the manufacturers failure to detect the defect.