NTSB investigations: Cessna 170
4 cases on aircraft the registry lists as Cessna 170, where the first occurrence was “In flight collision with object”. 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
| 1985 | 1 |
|---|---|
| 1989 | 1 |
| 1990 | 1 |
| 2007 | 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 ('2072302')
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\" = 220))
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 ('2072302')
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" = 220))
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 ANC07CA043Accident · No injuriesData collectionFinal reportCessna 170 · Anchorage, AKThe pilot's failure to maintain clearance from trees while landing, and his selection of an unsuitable landing site, which resulted in an in-flight collision with a tree and an on-ground encounter with brush.NTSB MIA91LA021Accident · No injuriesLimited investigationFinal reportCessna 170 · Patillas, PRThe accident was failure of the non certificated pilot to lower the flaps to the correct position for takeoff and failure to abort the takeoff due to insufficient acceleration.NTSB ATL89LA136Accident · No injuriesLimited investigationFinal reportCessna 170 · Orwell, OHThe pilot's decision to takeoff on unsuitable terrain, which resulted in his inability to attain sufficient airspeed to clear the fence(s) near the end of the runway. Factors related to the accident were: the soft runway/terrain conditions & the fence.NTSB MIA85LA109Accident · No injuriesLimited investigationFinal reportCessna 170 · Newberry, FLThe plt stated that he was having eng problems so he landed on a road, repaired the problem, & upon attempting to takeoff the acft first struck power lines then collided with trees. Investigation revealed that the plts initial eng problem was a clogged fuel…