NTSB investigations: Cessna 175, LA
8 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
| 1965 | 2 |
|---|---|
| 1966 | 1 |
| 1969 | 1 |
| 1984 | 1 |
| 1994 | 1 |
| 1997 | 1 |
| 2004 | 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\" = 'LA' 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" = 'LA' 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 FTW04LA229Accident · No injuriesLimited investigationFinal reportCessna 175 · De Ridder, LAThe partial loss of engine power for undetermined reasons. A contributing factor was the lack of suitable terrain for the forced landing.NTSB FTW98LA039Accident · No injuriesLimited investigationFinal reportCessna 175 · Arnaudville, LAa cracked fuel line, which allowed air to enter the line and lead to fuel starvation and loss of engine power. A related factor was: the lack of suitable terrain for a forced landing.NTSB FTW94LA109Accident · No injuriesLimited investigationFinal reportCessna 175 · Leesville, LAThe loss of engine power for undetermined reasons. A factor was the lack of suitable terrain for a forced landing.NTSB FTW85LA062Accident · Minor injuriesLimited investigationFinal reportCessna 175 · Bastrop, LAPlt stated that on preflight a small amount of water was drained from each wing tank. Also, the main fuel strainer was drained and fuel tanks were topped off (17 gals added). At about 500 ft AGL on initial climb, the engine quit and restart attempts were…NTSB FTW70D0043Accident · No injuriesClosedCessna 175 · Flora, LANTSB FTW67A0059Accident · 2 fatalClosedCessna 175 · Alexandria, LANTSB FTW66D0049Accident · No injuriesClosedCessna 175 · Bastrop, LANTSB UNK65X1423Accident · No injuriesClosedCessna 175 · Abbeville, LA