NTSB investigations: Cessna 175, MT
10 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
| 1968 | 1 |
|---|---|
| 1969 | 3 |
| 1971 | 1 |
| 1981 | 1 |
| 1987 | 1 |
| 1988 | 1 |
| 1991 | 1 |
| 2016 | 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\" = 'MT' 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" = 'MT' 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 GAA16CA097Accident · No injuriesData collectionFinal reportCessna 175 · Seeley Lake, MTThe pilot' failure to identify the plowed runway width in dusk and flat light conditions, which resulted in a touchdown left of the runway center, an impact with a snow berm, and a ground loop.NTSB SEA91LA138Accident · Minor injuriesLimited investigationFinal reportCessna C175 · East Glacier, MTThe pilot's failure to maintain sufficient airspeed. Contributing to the accident was: the gusty wind conditions and the pilot's lack of experience in this type of operation.NTSB DEN89LA021Accident · Serious injuriesLimited investigationFinal reportCessna 175 · Fort Peck, MTThe plt enctrd hvy snow at night & turned back to find a nearby landing strip that he was familiar with. He recognized a ranch house associated with the strip, but was unable to find the landing area. He began to circle in hopes that someone would turn on the…NTSB DEN87LA179Accident · Minor injuriesLimited investigationFinal reportCessna 175 · Kalispell, MTThe pvt plt was on a x-country flight. The engine began running rough, made a 'bang' sound and lost partial power. Smoke entered the cockpit, oil pressure was lost and the plt initiated an emergency landing. The acft ldg gr struck powerlines on approach to a…NTSB DEN81DTI04Accident · Minor injuriesClosedCessna 175 · Belgrade, MTNTSB SEA71DTI30Accident · No injuriesClosedCessna 175 · Havre, MTNTSB SEA70D0141Accident · No injuriesClosedCessna 175 · Ryegate, MTNTSB DEN70A0024Accident · 1 fatalClosedCessna 175 · Eureka, MTNTSB SEA69A0049Accident · 3 fatalClosedCessna 175 · Four Buttes, MTNTSB SEA68A0066Accident · 3 fatalClosedCessna 175 · Cascade, MT