NTSB investigations: Cessna 172H, MS
7 cases on aircraft the registry lists as Cessna 172H. 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
| 1968 | 1 |
|---|---|
| 1969 | 1 |
| 1972 | 1 |
| 1975 | 1 |
| 1993 | 1 |
| 1995 | 1 |
| 2000 | 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\" = 'MS' 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 ('2072424'))
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" = 'MS' 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 ('2072424'))
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 MIA00LA150Accident · No injuriesLimited investigationFinal reportCessna 172H · Picayune, MSAn in-flight fire in the vicinity of the firewall from an undetermined source. This resulted in a forced landing to an airport and total consumption of the airplane by fire after landing.NTSB MIA95LA109Accident · No injuriesLimited investigationFinal reportCessna 172H · Hattiesburg, MSThe pilot-in-command's improper use of carburetor heat during descent, resulting in a total loss of engine power due to carburetor icing, and subsequent forced landing to unsuitable terrain.NTSB MIA93FA194Accident · 1 fatalField investigationFinal reportCessna 172H · Liberty, MSThe pilot's delayed go-around and failure to retract the flaps in a timely manner. Factors which contributed to the accident were: the pilot's misjudgment of distance and speed which resulted in overshooting the approach, and the existence of power lines…NTSB MIA75AM059Accident · 2 fatalClosedCessna 172H · Olive Branch, MSNTSB MIA73FKQ16Accident · Serious injuriesClosedCessna 172 · Columbus, MSNTSB MIA70A0027Accident · 2 fatalClosedCessna 172H · Philadelphia, MSNTSB MIA68A0091Accident · 2 fatalClosedCessna 172H · Belmont, MS