NTSB investigations: Cessna 180J, 1999
6 cases on aircraft the registry lists as Cessna 180J. 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
| 1973 | 2 |
|---|---|
| 1974 | 3 |
| 1975 | 4 |
| 1976 | 4 |
| 1977 | 11 |
| 1978 | 14 |
| 1979 | 8 |
| 1980 | 8 |
| 1981 | 6 |
| 1982 | 6 |
| 1983 | 3 |
| 1984 | 2 |
| 1985 | 4 |
| 1986 | 4 |
| 1987 | 2 |
| 1988 | 4 |
| 1989 | 8 |
| 1990 | 2 |
| 1991 | 2 |
| 1992 | 1 |
| 1993 | 4 |
| 1994 | 3 |
| 1995 | 6 |
| 1996 | 1 |
| 1997 | 4 |
| 1998 | 2 |
| 1999 | 6 |
| 2002 | 1 |
| 2003 | 2 |
| 2004 | 2 |
| 2005 | 1 |
| 2006 | 1 |
| 2007 | 1 |
| 2009 | 2 |
| 2010 | 2 |
| 2011 | 3 |
| 2012 | 2 |
| 2013 | 2 |
| 2014 | 2 |
| 2015 | 2 |
| 2016 | 2 |
| 2017 | 1 |
| 2018 | 2 |
| 2019 | 5 |
| 2020 | 1 |
| 2021 | 5 |
| 2022 | 1 |
| 2023 | 3 |
| 2024 | 4 |
| 2025 | 4 |
| 2026 | 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 year(c.\"eventDate\") = 1999
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072622'))
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 year(c."eventDate") = 1999
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072622'))
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 CHI00LA016Accident · No injuriesLimited investigationFinal reportCessna 180J · Pleasant Hills, MOThe pilot's loss of directional control during an aborted takeoff.NTSB SEA99LA137Accident · No injuriesLimited investigationFinal reportCessna 180J · Council, IDThe pilot's inadequate recovery from a bounced landing. Gusting wind conditions and a dirt bank adjacent to the runway edge were factors.NTSB ANC99LA071Accident · No injuriesLimited investigationFinal reportCessna 180J · Palmer, AKThe failure of the pilot to maintain directional control during the water landing.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 ANC99LA042Accident · No injuriesLimited investigationFinal reportCessna 180 · Iliamna, AKThe improper installation of the main landing gear attaching bolt by maintenance personnel, which resulted in total failure of the bolt and collapse of the landing gear.NTSB FTW99LA070Accident · No injuriesLimited investigationFinal reportCessna 180J · Granbury, TXThe loss of engine power due to an undetermined reason. A factor was the power lines crossing the final approach path.