Fatal NTSB investigations: Cessna 175B
9 cases on aircraft the registry lists as Cessna 175B. 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 |
| 1970 | 1 |
| 1978 | 1 |
| 1981 | 1 |
| 1983 | 1 |
| 1993 | 1 |
| 2002 | 1 |
| 2005 | 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.\"highestInjuryLevel\" = 'Fatal'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072506'))
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."highestInjuryLevel" = 'Fatal'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072506'))
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 DFW05FA240Accident · 3 fatalField investigationFinal reportCessna 175B · Cleveland, TXThe pilot's failure to maintain airspeed resulting in an inadvertent stall/spin. A contributing factor was the low altitude.NTSB SEA02FA171Accident · 1 fatalField investigationFinal reportCessna 175B · Arlington, WAA partial loss of engine power for undetermined reasons during the initial climb, followed by the pilot's failure to maintain airspeed while maneuvering. Impairing drugs found in the pilot's system at the time of the accident were a factor.NTSB LAX93FA297Accident · 2 fatalField investigationFinal reportCessna 175B · Blythe, CAThe pilot's failure to see and avoid the cable due to drug impairment. Factors which contributed to the accident were: the pilot's intentional buzzing, his ostentatious display, and his failure to maintain an adequate altitude over the river.NTSB LAX84FA005Accident · 1 fatalField investigationFinal reportCessna 175B · Burbank, CARelatives expected the plt to return home on the evening of 10/4/83. When he did not return, relatives report the acft was overdue. The acft was found where it collided with a mountain at an elevation of about 3580 ft, 10 mi north of the destination arpt.…NTSB SEA82FA002Accident · 1 fatalClosedCessna 175B · Springfield, IDNTSB IAD79FA016Accident · 1 fatalClosedCessna 175B · Rileyville, VANTSB CHI70FBJ31Accident · 1 fatalClosedCessna 175B · Birch Run, MINTSB DIA69A0042Accident · 1 fatalClosedCessna 175 · Linville Falls, NCNTSB MKC69A0033Accident · 2 fatalClosedCessna 175B · Custer, SD