NTSB investigations: Cessna 182J
5 cases on aircraft the registry lists as Cessna 182J, 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
| 1999 | 2 |
|---|---|
| 2001 | 1 |
| 2002 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072722')
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 ('2072722')
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 CHI05FA017Accident · 2 fatalField investigationFinal reportCessna 182J · Springfield, MOThe pilot's failure to maintain a proper altitude and his failure to maintain obstacle clearance while turning to reverse direction on final approach. A factor associated with the accident was the night lighting conditions which existed at the time of the…NTSB CHI02LA146Accident · No injuriesLimited investigationFinal reportCessna 182J · Galesville, WIThe pilot failed to maintain clearance with the wires while on final approach. Factors associated with the accident were the low altitude, the downdraft, and the wires which the airplane contacted.NTSB SEA01LA170Accident · 1 fatalLimited investigationFinal reportCessna 182J · Gold Beach, ORThe pilot's failure to attain proper alignment while on final approach and clearance from trees. The pilot's lack of total experience in this type of mountain flying operation was a factor.NTSB CHI99FA190Accident · 1 fatalField investigationFinal reportCessna 182J · Satanta, KSthe preflight planning/preparation and the missed approach not performed by the pilot. The obstruction clearance not maintained by the pilot was an additional cause. Contributing factors were the low ceiling and the fog.NTSB MIA99LA094Accident · No injuriesLimited investigationFinal reportCessna 182J · Franklin, NCThe failure of the pilot to maintain directional control of the airplane on final approach resulting in the in-flight collision with trees and the ground.