NTSB investigations: Cessna 182P, AR
9 cases on aircraft the registry lists as Cessna 182P. 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
| 1974 | 1 |
|---|---|
| 1975 | 1 |
| 1977 | 1 |
| 1978 | 1 |
| 1983 | 1 |
| 1989 | 1 |
| 1996 | 1 |
| 2005 | 1 |
| 2011 | 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.\"eventStateOrRegion\" = 'AR' 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 ('2075816'))
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" = 'AR' 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 ('2075816'))
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 CEN11CA255Accident · No injuriesData collectionFinal reportCessna 182P · Humnoke, ARThe pilot's improper fuel management, which resulted in a loss of engine power due to fuel exhaustion.NTSB DFW05CA130Accident · Serious injuriesData collectionFinal reportCessna 182P · Lowell, ARThe instructor's inadequate supervision and the second pilot's inadequate planning/decision to assure adequate takeoff performance to clear obstacles. Contributing factors were the prevailing quartering tailwind, the pilots selection of the wrong runway, and…NTSB FTW96LA188Accident · No injuriesLimited investigationFinal reportCessna 182P · Fordyce, ARthe pilot's failure to initiate a timely go-around. A factor was the pilot's misjudgment of distance and speed during the approach.NTSB MKC90LA007Accident · No injuriesLimited investigationFinal reportCessna 182 · Hasty, ARThe engine failure due to fuel starvation resulting from the collapse at the fuel cell. The fact that the forced landing was made in dark night conditions was a factor.NTSB FTW83LA227Accident · No injuriesLimited investigationFinal reportCessna 182P · Lonoke, ARThe eng quit after takeoff. The acft crashed in a wheat field while returning to the arpt. The carb was found full of water. The acft salvage operator reported finding a large quantity of water in the bladder-type fuel cells.NTSB FTW78DPG13Accident · No injuriesClosedCessna 182P · Waldron, ARNTSB FTW77DPG52Accident · No injuriesClosedCessna 182 · Waldron, ARNTSB FTW75DPG41Accident · No injuriesClosedCessna 182P · Harrison, ARNTSB FTW74DPG57Accident · No injuriesClosedCessna 182 · Jonesboro, AR