NTSB investigations: Cessna 175, OK
9 cases on aircraft the registry lists as Cessna 175. 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
| 1964 | 1 |
|---|---|
| 1966 | 1 |
| 1967 | 3 |
| 1973 | 1 |
| 1978 | 1 |
| 1994 | 1 |
| 2006 | 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\" = '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 ('2072502'))
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 ('2072502'))
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 DFW06LA060Accident · No injuriesLimited investigationFinal reportCessna 175 · Lindsay, OKThe hard landing was the result of the pilot's failure to maintain adequate airspeed while misjudging the altitude above the runway. Contributing factors were the inadequate quality of the manufacturer's engine-support bracket and the prevailing night…NTSB FTW94FA295Accident · 2 fatalField investigationFinal reportCessna 175 · Oklahoma City, OKImproper maintenance of the engine by unknown person(s), the installation of unapproved parts, and subsequent bearing seizure. The lack of suitable terrain in the forced landing area was a related factor.NTSB FTW78FPM03Accident · No injuriesClosedCessna 175 · Pryor, OKNTSB FTW74AF025Accident · 2 fatalClosedCessna 175 · Wister, OKNTSB FTW68F0364Accident · No injuriesClosedCessna 175 · Mooreland, OKNTSB FTW68D0094Accident · No injuriesClosedCessna 175 · Oklahoma Cty, OKNTSB FTW67F0639Accident · Serious injuriesClosedCessna 175 · Mangum, OKNTSB FTW67D0224Accident · No injuriesClosedCessna 175 · Perry, OKNTSB UNK64X0912Accident · No injuriesClosedCessna 175 · Okla City, OK