NTSB investigations: Cessna R182
12 cases on aircraft the registry lists as Cessna R182, where the first occurrence was “In flight collision with terrain/water”. 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
| 1982 | 1 |
|---|---|
| 1984 | 1 |
| 1985 | 2 |
| 1986 | 1 |
| 1988 | 1 |
| 1993 | 1 |
| 2000 | 1 |
| 2003 | 1 |
| 2006 | 3 |
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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072734')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 230))
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072734')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 230))
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 NYC07LA020Accident · No injuriesLimited investigationFinal reportCessna 182RG · Toms River, NJThe private pilot's failure to attain the proper touchdown point, and the flight instructor's inadequate remedial action, which resulted in a landing short of the runway. A contributing factor was the gusty wind conditions.NTSB SEA06CA177Accident · No injuriesData collectionFinal reportCessna 182RG · Shelton, WAThe pilot's failure to extend the landing gear prior to a practice soft-field landing, and the certified flight instructor's failure to take remedial action. Factors include the pilot's failure to use a checklist.NTSB CHI06CA153Accident · No injuriesData collectionFinal reportCessna R182 · Cooperstown, NDThe pilot's inability to gain sufficient altitude during the aborted landing. Factors associated with the accident were the tailwind, the pilot's selection of the runway used, the wet runway, the roadway, and the corn crop.NTSB NYC03LA093Accident · No injuriesLimited investigationFinal reportCessna R182 · Monticello, NYThe pilot's premature raising of the flaps during the aborted landing. A factor in this accident was the crosswind condition.NTSB DEN01FA003Accident · 1 fatalField investigationFinal reportCessna R-182 · Grants, NMthe pilot's continued VFR flight into IMC during cruise. Contributing factors were the dark night light conditions, and the cloudy weather conditions.NTSB CHI93LA341Accident · No injuriesLimited investigationFinal reportCessna R182 · St Louis, MOthe pilot's delay in lowering the landing gear prior to touchdown.NTSB LAX89FA010Accident · 1 fatalField investigationFinal reportCessna 182R · Salinas, CAThe pilot failed to follow published missed approach procedures. Factors contributing to the accident were the pilot lack of recent experience in type of operation, instrument go-around procedures, and the cloud covered mountainous terrain.NTSB MIA86LA205Accident · No injuriesLimited investigationFinal reportCessna R182 · Jacksonville, FLAfter the plt applied carb heat during the approach sequence, he became concerned about roughness in the eng. At about that same time, the tower cleared him to land behind another acft; however, at 1st, he did not have the other acft in sight & spent several…NTSB NYC85LA066Accident · Minor injuriesLimited investigationFinal reportCessna 182RG · Norfolk, MAThe acft was unintentionally landed with the gear retracted. A CFI and a pvt plt were on board at the time of the accident. The pvt plt in the left seat was flying the acft and on the third landing failed to extend the gear. The CFI in the right seat was…NTSB ATL85FA173Accident · 1 fatalField investigationFinal reportCessna R182 · Seneca, SCDuring flt, the plt was observed to make a low pass over lake keowee near a friend's houseboat. The owner of the houseboat stated that the acft was flying low off his right side when the acft struck the water. Another witness also saw the acft flying at…NTSB ATL85LA033Accident · No injuriesLimited investigationFinal reportCessna 182RG · Charleston, SCPilot landed the aircraft with the landing gear in the up position. Examination of the landing gear after the accident revealed no evidence of mechanical malfunction or failure that would have prevented normal gear operation.NTSB LAX82DA239Accident · No injuriesFinal reportCessna R182 · Fresno, CAWhen the landing gear was extended to demonstrate an approach-to-landing stall, there was no safe indication. The gear was recycled but the nose gear would not extend. All attempts to extend the nose gear, including the use of the emergency extension hand…