NTSB investigations: Cessna 172F, OK
13 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 | 4 |
|---|---|
| 1966 | 1 |
| 1967 | 2 |
| 1976 | 2 |
| 1979 | 1 |
| 1992 | 1 |
| 2005 | 1 |
| 2006 | 1 |
Where
Latest 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\" = 'OK' 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" = 'OK' 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 DFW06CA164Accident · Serious injuriesData collectionFinal reportCessna 172F · Marietta, OKThe pilot's improper weather evaluation. Contributing factors were the strong tailwind and the high density altitude.NTSB DFW05LA067Accident · No injuriesLimited investigationFinal reportCessna 172F · Sallisaw, OKA loss of engine power for undetermined reasons. A contributing factor was the lack of suitable terrain for the forced landing.NTSB FTW92LA074Accident · Minor injuriesLimited investigationFinal reportCessna 172F · Mc Alester, OKInadvertent stall. A factor was a total power loss due to fuel exhaustion.NTSB FTW79FPJ13Accident · No injuriesClosedCessna 172 · Minco, OKNTSB FTW77FPJ01Accident · No injuriesClosedCessna 172 · Oklahoma City, OKNTSB FTW76FPM22Accident · 1 fatalClosedCessna 172F · Jenks, OKNTSB FTW68D0015Accident · No injuriesClosedCessna 172 · Ponca City, OKNTSB FTW67F0441Accident · No injuriesClosedCessna 172 · Oklahoma Cy, OKNTSB FTW67F0022Accident · No injuriesClosedCessna 172F · Bethany, OKNTSB FTW66A0043Accident · 3 fatalClosedDouglas C-124 · Tulsa, OKNTSB FTW66F0385Accident · No injuriesClosedCessna 172 · Tulsa, OKNTSB FTW66D0126Accident · No injuriesClosedCessna 172 · Chickasha, OKNTSB FTW66F0046Accident · No injuriesClosedPiper PA-22 · Okmulgee, OK