NTSB investigations: Cessna 180J
6 cases on aircraft the registry lists as Cessna 180J, 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
| 1988 | 2 |
|---|---|
| 1995 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072622')
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 ('2072622')
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 LAX99FA199Accident · 1 fatalField investigationFinal reportCessna 180J · Wickenburg, AZThe pilot's failure to maintain altitude/clearance from ground obstacles. A factor was the pilot's diverted attention in this accident.NTSB CHI98FA123Accident · 1 fatalField investigationFinal reportCessna 180J · Ashland, WIthe pilot failing to maintain separation from the trees. Factors contributing to this accident were the trees and the pilot being too low in altitude.NTSB SEA96LA014Accident · No injuriesLimited investigationFinal reportCessna 180J · Stanley, IDthe pilot's failure to maintain clearance with obstacles at the end of the takeoff area. His failure to attain sufficient altitude to clear the obstacles was a factor.NTSB CHI95LA090Accident · No injuriesLimited investigationFinal reportCessna 180J · Cotton, MNthe pilot's failure to gain sufficient clearance over the trees during the aborted landing.NTSB ANC89LA016Accident · No injuriesLimited investigationFinal reportCessna 180 · Meshik Lake, AKThe pilot was attempting to takeoff from an unimproved landing area with two hunter-friends. He stated that the aircraft bounced three times, reached an altitude of about four feet, then hit the ten-foot high trees at the departure end of the area and nosed…NTSB ANC89LA001Accident · No injuriesLimited investigationFinal reportCessna 180 · Wasilla, AKDrg arrival to land on a lake at night, the plt began a 180 deg turn from a NE heading at aprx 500' AGL to a final apch on a sw heading. As the acft was in the turn, it began losing altitude rapidly. The plt applied power to stop the descent, but the acft…