NTSB investigations: Cessna 175, AR
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 |
|---|---|
| 1965 | 1 |
| 1967 | 1 |
| 1980 | 1 |
| 1994 | 1 |
| 1995 | 3 |
| 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\" = 'AR' 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" = 'AR' 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 CEN16FA210Accident · 1 fatalField investigationFinal reportCessna 175 · Pine Bluff, ARA loss of engine power during cruise flight for reasons that could not be determined because a test run of the engine did not reveal any mechanical malfunctions or anomalies that would have precluded normal operation. Contributing to the accident were the…NTSB FTW96LA032Accident · No injuriesLimited investigationFinal reportCessna 175 · Deer, ARThe pilot's selection of a downwind runway for landing. Factors were the tailwind and the pilot's misinterpretation of the wind conditions.NTSB FTW96LA018Accident · No injuriesLimited investigationFinal reportCessna 175 · Batesville, ARthe pilot's failure to maintain control of the airplane during landing.NTSB FTW95LA210Accident · No injuriesLimited investigationFinal reportCessna 175 · Malvern, ARThe pilot's failure to maintain directional control. A factor was the pilot's lack of recent experience.NTSB FTW94LA080Accident · Serious injuriesLimited investigationFinal reportCessna 175 · Paris, ARFailure by the pilot in command to have annual maintenance inspections performed on the aircraft.NTSB FTW80FPG41Accident · No injuriesClosedCessna 175 · Sherrill, ARNTSB FTW68F0174Accident · No injuriesClosedCessna 175 · Little Rock, ARNTSB FTW66F0020Accident · No injuriesClosedCessna 175 · Chester, ARNTSB UNK64X3508Accident · No injuriesClosedCessna 175 · Pettigrew, AR