NTSB investigations: Cessna 182P, WV
8 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
| 1978 | 1 |
|---|---|
| 1982 | 1 |
| 1983 | 1 |
| 1997 | 1 |
| 2003 | 1 |
| 2010 | 1 |
| 2022 | 1 |
| 2024 | 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\" = 'WV' 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" = 'WV' 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 ERA25LA014Accident · Serious injuriesClass 4 · LimitedFinal reportCessna 182 · South Charleston, WVThe pilot’s decision to continue landing after encountering a strong tailwind, which resulted in a loss of control and subsequent runway excursion.NTSB ERA23LA098Accident · No injuriesClass 4 · LimitedFinal reportCessna 182P · Ethel, WVThe pilot’s failure to maintain directional control during landing, which resulted in a runway excursion.NTSB ERA10LA296Accident · Serious injuriesLimited investigationFinal reportCessna 182P · Rainelle, WVThe pilot's failure to adequately assess the runway conditions prior to attempting a takeoff and his failure to abort the takeoff in a timely manner resulting in an on-ground collision with trees.NTSB NYC03LA054Accident · 1 fatalLimited investigationFinal reportCessna 182P · So. Charleston, WVThe pilot's failure to perform a go-around prior to touchdown. Factors in the accident were the rising terrain and tail wind.NTSB NYC98FA016Accident · 1 fatalField investigationFinal reportCessna 182P · Morgantown, WVThe loss of engine power due to carburetor ice and the pilot's failure to follow ATC instructions during the emergency descent.NTSB ATL83FIJ02Accident · Serious injuriesFinal reportCessna 182P · Bluefield, WVThe plt reported that he began an ILS approach to the mercer county arpt. He stated that he planned to descend to 3200 ft MSL, then execute a missed approach & return to abington, VA. The arpt elevation was 2857 ft MSL. He stated that he remembered glancing…NTSB ATL82DA069Accident · Minor injuriesFinal reportCessna 182P · Huntington, WVAccording to the pilot the engine failed after liftoff at about the 3500 foot point down the runway at approximately 300 feet AGL. The runway has 1000 feet of overrun and the aircraft came to rest near the runup area for runway 12. The aircraft had not been…NTSB IAD79FIJ02Accident · No injuriesClosedCessna 182P · Fayetteville, WV