NTSB investigations: Cessna 180, 1990
15 cases on aircraft the registry lists as Cessna 180. 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
| 1964 | 61 |
|---|---|
| 1965 | 58 |
| 1966 | 61 |
| 1967 | 61 |
| 1968 | 32 |
| 1969 | 47 |
| 1970 | 44 |
| 1971 | 33 |
| 1972 | 38 |
| 1973 | 34 |
| 1974 | 35 |
| 1975 | 39 |
| 1976 | 29 |
| 1977 | 27 |
| 1978 | 20 |
| 1979 | 24 |
| 1980 | 29 |
| 1981 | 23 |
| 1982 | 17 |
| 1983 | 16 |
| 1984 | 14 |
| 1985 | 8 |
| 1986 | 9 |
| 1987 | 14 |
| 1988 | 14 |
| 1989 | 10 |
| 1990 | 15 |
| 1991 | 13 |
| 1992 | 14 |
| 1993 | 11 |
| 1994 | 6 |
| 1995 | 13 |
| 1996 | 11 |
| 1997 | 8 |
| 1998 | 12 |
| 1999 | 10 |
| 2000 | 14 |
| 2001 | 4 |
| 2002 | 7 |
| 2003 | 10 |
| 2004 | 5 |
| 2005 | 13 |
| 2006 | 12 |
| 2007 | 9 |
| 2008 | 12 |
| 2009 | 7 |
| 2010 | 12 |
| 2011 | 10 |
| 2012 | 8 |
| 2013 | 9 |
| 2014 | 6 |
| 2015 | 7 |
| 2016 | 4 |
| 2017 | 8 |
| 2018 | 9 |
| 2019 | 5 |
| 2020 | 5 |
| 2021 | 2 |
| 2022 | 7 |
| 2023 | 6 |
| 2024 | 7 |
| 2025 | 5 |
| 2026 | 9 |
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\") = 1990
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072602'))
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") = 1990
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072602'))
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 CHI91LA024Accident · No injuriesLimited investigationFinal reportCessna 180 · Northwood, NDPoor in-flight planning and decision, unsuitable terrain selected by the PIC.NTSB ANC91LA009Accident · No injuriesLimited investigationFinal reportCessna 180 · Anchorage, AKThe pilot-in-command's failure to maintain directional control of the airplane during the landing roll.NTSB ANC91LA004Accident · No injuriesLimited investigationFinal reportCessna 180 · Anchorage, AKThe pilot's failure to maintain directional control. Contributing to the accident was the excessive taxi speed and inadequate maintenance on the brakes by the pilot.NTSB SEA90LA184Accident · No injuriesLimited investigationFinal reportCessna 180 · Enterprise, ORThe pilot's failure to maintain directional control of the aircraft during landing.NTSB ANC90LA156Accident · No injuriesLimited investigationFinal reportCessna 180-A · Lime Village, AKThe pilot-in-command's failure to understand the performance data during takeoff. Contributing to the accident was the unsuitable terrain not being identified by the pilot-in-command.NTSB LAX90LA301Accident · No injuriesLimited investigationFinal reportCessna 180 · Calexico, CAThe aircraft's encounter with unfavorable wind, a dust devil, that rendered the aircraft uncontrollable.NTSB FTW90LA163Accident · No injuriesLimited investigationFinal reportCessna 180 · Saint Joseph, LAThe pilot's failure to maintain directional control and his use of excessive braking.NTSB CHI90FA235Accident · 1 fatalField investigationFinal reportCessna 180 · Howell, MIThe pilot's failure to maintain adequate clearance above terrain while maneuvering during takeoff. A factor in the accident was the pilot's attempt to display the aircraft's performance.NTSB LAX90LA344Accident · No injuriesLimited investigationFinal reportCessna 180 · Tucson, AZThe pilot's failure to maintain adequate distance from a MD-80'S jet exhaust.NTSB NYC90LA174Accident · Minor injuriesLimited investigationFinal reportCessna 180 · Hilltown, PAThe pilot receiving training misjudged the airplane's distance from the runway and altitude above the trees. In addition, the CFI failed to provide adequate supervision.NTSB MKC90LA137Accident · Minor injuriesLimited investigationFinal reportCessna 180 · Goddard, KSFuel starvation due to a loose fuel strainer screen. A factor related to this accident was lack of suitable terrain for a forced landing.NTSB LAX90LA207Accident · Minor injuriesLimited investigationFinal reportCessna 180 · Colusa, CAThe pilot's failure to maintain directional control during touchdown.NTSB LAX90LA149Accident · No injuriesLimited investigationFinal reportCessna 180 · Soledad, CAPilot's failure to maintain directional control during takeoff. Contributing factors were the gusty wind and the crosswind conditions.NTSB ANC90LA037Accident · No injuriesLimited investigationFinal reportCessna 180 · Fairbanks, AKImproper installation of the gear axle (use of improper bolts & the wrong number of shims), which resulted in a subsequent failure and loss of control during the landing roll.NTSB FTW90LA066Accident · No injuriesLimited investigationFinal reportCessna 180 · Portland, TXThe pilot's inadequate compensation for wind conditions, which resulted in a failure to attain a flare during the landing. The unfavorable wind conditon was a related factor.