NTSB investigations: Cessna 180, 2000
14 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\") = 2000
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") = 2000
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 ANC01LA023Accident · No injuriesLimited investigationFinal reportCessna 180 · Chugiak, AKThe failure of a mechanic to ensure the throttle linkage was secure. A factor in the accident was the pilot's failure to take remedial action during an emergency landing and overrun.NTSB ANC01LA019Accident · No injuriesLimited investigationFinal reportCessna 180 · Clarks Point, AKThe pilot's excessive application of the brakes during landing roll. Factors associated with the accident were water on the runway, low tire pressure, a sheared tire valve stem, and a fractured landing gear axle.NTSB ANC01LA005Accident · No injuriesLimited investigationFinal reportCessna 180 · Anchorage, AKThe pilot's delay in aborting the takeoff run. A factor associated with the accident was glassy water conditions.NTSB ANC00LA108Accident · 3 fatalLimited investigationFinal reportCessna 180 · Pilot Point, AKThe commercial certificated pilot, an owner of a fishing lodge, departed a remote area of beach with three passengers to return to the lodge. The accident airplane was one of two airplanes transporting lodge guests. The beach was located along an area of…NTSB SEA00LA153Accident · Minor injuriesLimited investigationFinal reportCessna 180 · Challis, IDThe pilot's inadequate compensation for wind conditions. Factors include variable winds during landing.NTSB CHI00LA233Accident · No injuriesLimited investigationFinal reportCessna 180 · Jeffersonville, INThe pilot failed to maintain directional control of the airplane while landing. A factor associated with the accident was the crosswind.NTSB ANC00FA093Accident · 1 fatalField investigationFinal reportCessna 180 · Thorne Bay, AKThe pilot-in-command's inadvertent stalling of the airplane.NTSB CHI00LA190Accident · No injuriesLimited investigationFinal reportCessna 180 · Saint Cloud, MNdirectional control not being maintained by the pilot during landing rollout.NTSB NYC00LA182Accident · No injuriesLimited investigationFinal reportCessna 180 · Jackson Center, PAA seized left brake as reported by the pilot.NTSB ANC00LA072Accident · No injuriesLimited investigationFinal reportCessna 180 · Port Alsworth, AKThe fatigue failure of the left main landing gear leg at the main landing gear axle attachment bolt holes.NTSB LAX00LA177Accident · No injuriesLimited investigationFinal reportCessna 180 · N. Las Vegas, NVThe pilot's inadequate compensation for the existing crosswind condition, and his improper positioning of the flight controls.NTSB SEA00LA049Accident · No injuriesLimited investigationFinal reportCessna 180 · Port Townsend, WAThe pilot's failure to adequately compensate for changing wind conditions during the landing roll in a tailwheel-equipped aircraft. Factors include a variable, shifting wind that changed from a quartering headwind to a quartering tailwind just prior to the…NTSB CHI00LA072Accident · 1 fatalLimited investigationFinal reportCessna 180 · Tower, MNthe passenger not maintaining clearance from the rotating propeller.NTSB ANC00LA026Accident · No injuriesLimited investigationFinal reportCessna 180 · Glennallen, AKThe pilot's selection of an unsuitable landing site on a frozen, snow-covered lake. A factor associated with the accident was an area of drifted snow at the landing site.