NTSB investigations: Cessna 182N
5 cases on aircraft the registry lists as Cessna 182N, where the first occurrence was “In flight collision with object”. 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
| 1985 | 2 |
|---|---|
| 1987 | 1 |
| 1993 | 1 |
| 1998 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072730')
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\" = 220))
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 ('2072730')
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" = 220))
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 CHI99LA004Accident · No injuriesLimited investigationFinal reportCessna 182N · Genesee, MIthe pilot's failure to maintain directional control and the subsequent failure to attain clearance with the trees during takeoff. Factors associated with the accident were the trees, dark night conditions, and fog which resulted in the lack of visual…NTSB CHI93FA118Accident · 1 fatalField investigationFinal reportCessna 182N · Ludington, MIthe pilot's improper instrument procedures. Related factors are the below approach minima weather conditions, fog and dark night.NTSB CHI87DEP02Accident · 1 fatalFinal reportCessna 182N · Wissota, WIWhile attempting a night landing, by use of car headlights, the aircraft struck wires and descended out of control into the terrain. Witnesses stated that the pilot seemed low during the final approach. The private airport was not lighted.NTSB NYC86FA030Accident · 2 fatalField investigationFinal reportCessna C-182N · Winterport, METhe acft departed bangor under special VFR dur to low ceilings. A witness saw the acft fly under powerlines that crossed a river and disappear behind trees. There was no indication of an accident. 22 day later, the acft was located 150 ft south from the…NTSB DEN85FTE08Accident · Minor injuriesFinal reportCessna 182N · Alamosa, COThe acft contacted trees, a fence and a ditch during a precautionary landing on a dirt road. The plt stated that when approaching his destination, the eng began running rough and he was unable to correct the problem. He then decided to land on the road and…