NTSB investigations: Cessna 175
6 cases on aircraft the registry lists as Cessna 175, where the first occurrence was “Hard landing”. 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
| 1987 | 1 |
|---|---|
| 1991 | 1 |
| 1997 | 1 |
| 1999 | 1 |
| 2001 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072502')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 200))
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072502')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 200))
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 LAX01LA235Accident · No injuriesLimited investigationFinal reportCessna 175 · Monterey, CAThe pilot's improper recovery from a bounced landing.NTSB SEA00LA022Accident · No injuriesLimited investigationFinal reportCessna 175 · Garden Valley, IDAn improper in-flight decision by the pilot-in-command to attempt a landing at a confined-area airstrip which was beyond his piloting capabilities, and his subsequent failure to take adequate remedial action upon encountering a downdraft. Related factors were…NTSB FTW97LA318Accident · No injuriesLimited investigationFinal reportCessna 175 · Rock Springs, WYThe delayed landing flare by both student pilot and flight instructor, and the flight instructor's inadequate supervision of the student. Factors were the no flap steep approach at low airspeed.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 ANC87LA132Accident · No injuriesLimited investigationFinal reportCessna 175 · Yellow Jacket, AKThe pilot stated he bounced hard on the gravel runway causing him to lose directional control and the airplane nosed over on its back.