NTSB investigations: Cessna 172F, MS
7 cases on aircraft the registry lists as Cessna 172F. 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
| 1965 | 1 |
|---|---|
| 1966 | 1 |
| 1967 | 1 |
| 1970 | 1 |
| 1984 | 1 |
| 1985 | 1 |
| 2001 | 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 ('2072414'))
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 ('2072414'))
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 ATL01LA026Accident · Serious injuriesLimited investigationFinal reportCessna 172 F · Greenwood, MSAn in-flight fire for undetermined reasons. Finding: A factor is the maintenance modification was performed by company personnel prior to the flight.NTSB ATL86LA022Accident · No injuriesLimited investigationFinal reportCessna 172F · Hazelhurst, MSDuring cruise flight the engine experienced a loss of power and the pilot applied carb heat. The engine operated normally with the carb heat on and when it was turned off the engine again ran rough. The pilot again turned on the carb heat and the engine ran…NTSB ATL84LLT05Accident · Minor injuriesFinal reportCessna C-172F · Pascagoula, MSThe plt ditched the acft after a complete loss of power. The acft fuel system was damaged during the recovery process and a complete evaluation could not be made.NTSB MIA71FKQ17Accident · No injuriesClosedCessna 172F · Valley Park, MSNTSB MIA67F0379Accident · No injuriesClosedCessna 172F · Port Gibson, MSNTSB MIA66F0487Accident · No injuriesClosedCessna 172 · Tchula, MSNTSB MIA66D0239Accident · No injuriesClosedCessna 172 · Tchula, MS