Cessna 182R
NTSB investigations · 109
Matched to the registry by N-number and event date, newest first.
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_aircrafts.parquet' a JOIN 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c ON c.\"mKey\" = a.case_mkey
WHERE a.aircraft_model_code IN ('2072731')
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_aircrafts.parquet' a JOIN 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c ON c."mKey" = a.case_mkey
WHERE a.aircraft_model_code IN ('2072731')
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 MKC84LA104Accident · No injuriesLimited investigationFinal reportCessna 182 · Lincoln, NEDuring landing roll on the runway with crosswind conditions and restricted visibility due to ice on the windshield the acft slid left on the ice and collided with a snow bank, damaging the propeller and the right wing tip.NTSB LAX84FA142Accident · 3 fatalField investigationFinal reportCessna 182R · Yorba Linda, CAThe acft was seen to descend in a near-vertical high speed descent out of the clouds and disappear into a canyon. A search party found the acft on the floor of the canyon. The acft had departed an arpt 18 miles away on a VFR x-country flight. Investigation…NTSB MKC84FA002Accident · 4 fatalField investigationFinal reportCessna 182R · Springfield, MOAt 2346 CDT, Kansas city center provided the 2251 CDT Springfield wx & advsed the plt to expect vectors for an apch to rwy 1. Vectors were provided until 0006;50 CDT, when center advised that radar contact was lost, 3 mi south of the outer marker compass…NTSB LAX83LA229Accident · Minor injuriesLimited investigationFinal reportCessna 182R · Duckwater, NVThe acft collided with the terrain after descending to 600 ft AGL and encountering a weather phenomenon which prompted an airspeed decay and uncommanded loss of altitude. Two other acft in the flt of 3 experienced the same phenomenon to a lesser degree…NTSB FTW83FA226Accident · 4 fatalField investigationFinal reportCessna 182R · New Braunfels, TXAt 2006 CDT, before departing san antonio, TX, the plt obtained a wx breifing. At that time, he was advised to expect VFR conditions on his flt to san marcos, TX, but IFR conditions were expected when he planned to return at about midnight. The plt flew to…NTSB LAX83FA188Accident · 2 fatalField investigationFinal reportCessna 182RII · Casa Grande, AZThe acft collided with a lone mountain while in straight & level flight.NTSB FTW83LA130Accident · No injuriesLimited investigationFinal reportCessna 182R · Flatonia, TXThe acft collided with a power line while the plt was making a low apch over a private strip. The top 3 inches of the vertical stabilizer was cut off. The plt did not realize the acft was damaged & landed without further incident.NTSB CHI82DA193Accident · No injuriesFinal reportCessna 182 · Tracy, MNThe pilot reported that during a normal landing, the left main gear axle failed and he was unable to control the aircraft. The aircraft went off the runway and the nose gear collapsed when it encountered soft mud.NTSB MKC81FA039Accident · 1 fatalClosedCessna 182 · New Virginia, IA
Back to Cessna 182R