NTSB investigations: Cessna 182, IN
6 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 |
|---|---|
| 1972 | 1 |
| 1982 | 2 |
| 1998 | 1 |
| 1999 | 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\" = 'IN' 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" = 'IN' 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 CHI00LA031Accident · No injuriesLimited investigationFinal reportCessna 182 · Shelbyville, INthe inadequate preflight planning by the pilot and the exhaustion of usable fuel. A factor was the drainage ditch encountered on landing.NTSB CHI98LA365Accident · Minor injuriesLimited investigationFinal reportCessna 182 · Wheatfield, INthe pilot's failure to apply carburetor heat when the engine lost power. Factors associated with the accident were the carburetor icing conditions which prevailed, the low altitude at which the loss of power occurred, and the soybean crop in which the…NTSB ATL82DA194Accident · Minor injuriesFinal reportCessna 182 · Madison, INThe pilot reported that he experienced a gradual loss of power on a dark night. The terrain was hilly and covered with trees, and reportedly, the pilot elected to land upwind on the Ohio river. After ditching, the occupants egressed and swam to shore, but the…NTSB CHI82DA133Accident · No injuriesFinal reportCessna 182 · Brazil, INThe pilot elected to land on the grass adjacent to a paved runway. While on landing roll the landing gear contacted the edge of a paved taxiway that ran perpendicular to the runway. The aircraft nosed over and came to rest inverted.NTSB CHI73FEA14Accident · No injuriesClosedCessna 182 · Tipton, INNTSB CHI66F0073Accident · Minor injuriesClosedCessna 182 · Indianapolis, IN