NTSB investigations: Cessna 182, MT
13 cases on aircraft the registry lists as Cessna 182. 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
| 1965 | 1 |
|---|---|
| 1966 | 2 |
| 1970 | 1 |
| 1974 | 2 |
| 1975 | 1 |
| 1976 | 1 |
| 1979 | 1 |
| 1983 | 1 |
| 1990 | 1 |
| 2009 | 2 |
Where
Latest 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\" = 'MT' 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 ('2072702'))
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" = 'MT' 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 ('2072702'))
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 WPR10FA018Accident · 2 fatalField investigationFinal reportCessna 182 · Pryor, MTThe pilot’s decision to continue flight into an area of low ceilings and low visibility and his failure to maintain clearance from terrain.NTSB WPR09LA179Accident · No injuriesLimited investigationFinal reportCessna 182 · Kalispell, MTA partial loss of engine power during a go-around for undetermined reasons. Contributing to the accident was a fatigue failure of the right main landing gear spring.NTSB DEN90LA153Accident · Minor injuriesLimited investigationFinal reportCessna 182 · Miles City, MTThe failure of the pilot to use carburetor heat during descent for landing, resulting in a loss of power.NTSB DEN83LA181Accident · No injuriesLimited investigationFinal reportCessna 182 · Forsyth, MTThe flt originated at cambridge, id with a planned refueling stop at billings, MT. The plt stated the acft was 'topped off' at cambridge before takeoff. En route, southerly winds were encountered which drifted the acft north, so a refueling stop was made at…NTSB SEA79DTI22Accident · Minor injuriesClosedCessna 182 · Schafer, MTNTSB SEA76FTI33Accident · No injuriesClosedCessna 182 · Seeley Lake, MTNTSB SEA75DTI36Accident · No injuriesClosedCessna 182 · Livingston, MTNTSB SEA75FTI11Accident · No injuriesClosedCessna 182 · Harve, MTNTSB SEA74DTA26Accident · No injuriesClosedCessna 182 · Ekalaka, MTNTSB SEA70FDA15Accident · No injuriesClosedCessna 182 · Joliet, MTNTSB SEA67F0111Accident · No injuriesClosedCessna 182 · Dupuyer, MTNTSB SEA67D0029Accident · Minor injuriesClosedCessna 182 · Three Forks, MTNTSB SEA66F0046Accident · No injuriesClosedCessna 182 · Darby, MT