NTSB investigations: Cessna 172B
5 cases on aircraft the registry lists as Cessna 172B, 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
| 1982 | 1 |
|---|---|
| 1985 | 1 |
| 1991 | 1 |
| 2000 | 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 ('2072406')
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 ('2072406')
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 LAX07CA242Accident · No injuriesData collectionFinal reportCessna 172B · Sisters, ORThe pilot's failure to maintain adequate clearance from trees.NTSB FTW00LA217Accident · Serious injuriesLimited investigationFinal reportCessna 172B · Olney, TXThe pilot's inadequate compensation for wind conditions. A factor was the gusty crosswind.NTSB FTW92LA038Accident · No injuriesLimited investigationFinal reportCessna 172B · Tulsa, OKClearance was not maintained and the airplane struck a wire. A factor was the aircraft had been stolen by two unknown individuals.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 ANC83LA006Accident · No injuriesLimited investigationFinal reportCessna 172 · Near Homer, AKThe pilot decided to land on a gravel bar. He made a touch-and-go, then returned for a full stop landing. During the landing, he decided there was insufficient room to stop. He applied full power to initiate a go-around and saw a log in the takeoff path. The…