NTSB investigations: Cessna 182Q, MO
8 cases on aircraft the registry lists as Cessna 182Q. 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
| 1981 | 2 |
|---|---|
| 1983 | 1 |
| 1988 | 1 |
| 1991 | 1 |
| 2000 | 1 |
| 2013 | 1 |
| 2015 | 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\" = 'MO' 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 ('2072732'))
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" = 'MO' 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 ('2072732'))
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 CEN16FA037Accident · 1 fatalField investigationFinal reportCessna 182Q · Richmond, MOThe airplane's impact with trees and terrain during an off-airport forced landing in dark night conditions following a partial loss of engine power. The reason for the partial loss of engine power could not be determined because postaccident examination did…NTSB CEN14CA040Accident · No injuriesData collectionFinal reportCessna 182Q · Braggadocio, MOThe pilot's failure to maintain directional control during landing rollout, which resulted in a runway excursion and the airplane nosing over.NTSB CHI00LA252Accident · No injuriesLimited investigationFinal reportCessna 182Q · Warsaw, MOInadequate maintenance and the pilot's failure to maintain airspeed which resulted in failure of the carburetor and an inadvertent stall.NTSB CHI92LA057Accident · No injuriesLimited investigationFinal reportCessna 182 · Point Lookout, MOFailure of the pilot to attain the proper touchdown Point and maintain directional control of the aircraft. A factor related to the accident was: a go-around was not performed by the pilot.NTSB MKC88LA165Accident · No injuriesLimited investigationFinal reportCessna 182Q · St. Louis, MOThe plt said that during a night takeoff roll, he noticed an inoperative airspeed indicator, and elected to abort the takeoff. Unable to stop in the remaining distance, the acft ran off the end of the runway onto the grass overrun collapsing the nose wheel.…NTSB MKC83LA105Accident · No injuriesLimited investigationFinal reportCessna 182Q · Springfield, MOThe acft went off the runway, collapsed the nose gear and nosed over during landing. The pilot was unable to extend the flaps and tried to land on a 3800 foot runway. There was a 7003 foot runway 8 NM west of the landing site. The pilot also had a tailwind of…NTSB MKC82FCA04Accident · No injuriesClosedCessna 182Q · Eunice, MONTSB MKC81FCG47Accident · No injuriesClosedCessna 182 · Osage Beach, MO