NTSB investigations: Cessna 172B, OR
8 cases on aircraft the registry lists as Cessna 172B. 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
| 1966 | 1 |
|---|---|
| 1967 | 1 |
| 1968 | 1 |
| 1985 | 2 |
| 2000 | 1 |
| 2007 | 1 |
| 2013 | 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\" = 'OR' 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 ('2072406'))
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" = 'OR' 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 ('2072406'))
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 WPR13LA378Accident · No injuriesLimited investigationFinal reportCessna 172B · Sisters, ORA loss of engine power during cruise flight for reasons that could not be determined because the engine was not properly preserved to prevent corrosion after the wreckage was recovered from the lake.NTSB LAX07CA242Accident · No injuriesData collectionFinal reportCessna 172B · Sisters, ORThe pilot's failure to maintain adequate clearance from trees.NTSB SEA00LA168Accident · No injuriesLimited investigationFinal reportCessna 172B · Sunriver, ORThe pilot's improper decision to continue the takeoff after the aircraft failed to climb or accelerate immediately after the initial liftoff. Factors were inadequate preflight planning, to include the pilot's failure to calculate takeoff performance data,…NTSB SEA86LA005Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Medford, ORThe acft collided with rocky terrain during an attempted forced landing following a loss of pwr. A witness reported seeing the acft in a steep descending left turn at an alt of aprx 100 ft AGL. The descent continued until the left wing contacted the terrain.…NTSB SEA85LA143Accident · No injuriesLimited investigationFinal reportCessna 172B · Imbler, ORDuring takeoff from a field (off arpt), the acft failed to clear a fence. The pilot then attempted to abort the takeoff, but the acft hit a bale of hay & nosed over. The plt's last medical certificate was dated 9/2/82.NTSB SEA68F0290Accident · No injuriesClosedCessna 172 · Bend, ORNTSB SEA68D0202Accident · No injuriesClosedCessna 172 · Vernonia, ORNTSB SEA66D0272Accident · No injuriesClosedCessna 172 · Heppner, OR