NTSB investigations: Cessna 182C
5 cases on aircraft the registry lists as Cessna 182C, 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
| 1983 | 2 |
|---|---|
| 1987 | 1 |
| 1991 | 1 |
| 1997 | 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 ('2072708')
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 ('2072708')
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 NYC97LA141Accident · No injuriesLimited investigationFinal reportCessna 182 · Springfield, KYthe pilot's misjudgment of distance and speed, and his delay in aborting the landing. Factors relating to the accident were: the pilot's failure to attain a proper touchdown point for landing, and proximity of the fence to the runway.NTSB BFO91LA025Accident · 1 fatalLimited investigationFinal reportCessna 182C · Bonnyman, KYThe pilot's failure to maintain adequate obstacle clearance. Contributing was inadequate altitude.NTSB ATL88LA042Accident · Minor injuriesLimited investigationFinal reportCessna 182C · Hazel Green, ALThe airplane hit a tree and crashed about 300 yds short of the rwy while on final appch to land. The plt indicated that he became preoccupied with the airspeed indicator and allowed the airplane to descend below the proper glide path. The plt had less than 1…NTSB SEA83FA187Accident · 3 fatalField investigationFinal reportCessna 182C · Near Elk River, IDThe acft collided with trees and crashed into heavily wooded area at about 4000 ft MSL. The purpose of flight was to look for game or areas for hunting in a pre-hunting game spotting trip. The acft first impacted a large 200 ft tree about 85 ft below its top.…NTSB NYC83LA225Accident · No injuriesLimited investigationFinal reportCessna 182C · New Salem, MAThe acft collided with high tension wires while flying at about 100 ft AGL. The plt landed in the water and all 4 occupants evacuated safely. The ditching was controlled but the acft nosed over after impact. The passengers said they had no trouble until they…