NTSB investigations: Cessna 172, 1982
11 cases on aircraft the registry lists as Cessna 172. 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 | 80 |
|---|---|
| 1965 | 77 |
| 1966 | 84 |
| 1967 | 85 |
| 1968 | 65 |
| 1969 | 35 |
| 1970 | 32 |
| 1971 | 37 |
| 1972 | 40 |
| 1973 | 35 |
| 1974 | 35 |
| 1975 | 15 |
| 1976 | 29 |
| 1977 | 25 |
| 1978 | 27 |
| 1979 | 15 |
| 1980 | 21 |
| 1981 | 27 |
| 1982 | 11 |
| 1983 | 6 |
| 1984 | 8 |
| 1985 | 13 |
| 1986 | 8 |
| 1987 | 13 |
| 1988 | 21 |
| 1989 | 15 |
| 1990 | 6 |
| 1991 | 11 |
| 1992 | 12 |
| 1993 | 10 |
| 1994 | 10 |
| 1995 | 9 |
| 1996 | 12 |
| 1997 | 4 |
| 1998 | 13 |
| 1999 | 9 |
| 2000 | 9 |
| 2001 | 9 |
| 2002 | 6 |
| 2003 | 2 |
| 2004 | 2 |
| 2005 | 11 |
| 2006 | 4 |
| 2007 | 9 |
| 2008 | 8 |
| 2009 | 3 |
| 2010 | 4 |
| 2011 | 6 |
| 2012 | 4 |
| 2013 | 7 |
| 2014 | 3 |
| 2015 | 5 |
| 2016 | 3 |
| 2017 | 6 |
| 2018 | 6 |
| 2019 | 6 |
| 2020 | 3 |
| 2021 | 8 |
| 2022 | 4 |
| 2023 | 3 |
| 2024 | 2 |
| 2025 | 5 |
| 2026 | 3 |
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\") = 1982
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072402'))
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") = 1982
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072402'))
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 LAX83LA029Accident · No injuriesLimited investigationFinal reportCessna 172 · Alamo, NVAfter takeoff from a desert road the acft settled & struck a yucca tree.NTSB FTW82DA374Accident · Minor injuriesFinal reportCessna 172 · Vain, OKThe pilot and his passenger took off on a local flight and flew over a runway that they were constructing in their pasture. The pilot stated that he was in slow flight over the runway. Both occupants received concussions in the accident and could not recall…NTSB FTW82DA224Accident · No injuriesFinal reportCessna 172 · Duncan, OKThe student pilot was practicing touch-and-go landings in winds from the southeast at 10 gusting 15 KTS. Just prior to landing, the aircraft encountered a gust of wind, then touched down hard. The engine fire wall was buckled and two tires blew out.NTSB LAX82DA197Accident · No injuriesFinal reportCessna 172 · Fresno, CAThe acft landed hard, bounced, veered left & collided with a parked acft. The CFI recognized that the approach speed wastoo slow & waited too long before taking over. A deliberate turn was made to avoid residences.NTSB ATL82DA097Accident · No injuriesFinal reportCessna 172 · Brook Haven, MSThe pilot visually checked the fuel level before takeoff and estimated that he had 15 to 16 gallons remaining. Since the flight was planned for 30 to 45 minutes, no fuel was added. However, after flying for 30 to 35 minutes, the engine lost power. The pilot…NTSB DEN82FA038Accident · 3 fatalField investigationFinal reportCessna 172 · 3nm East Of Mar, UTWitnesses in the vicinity of the accident at the approximate time of the accident stated that blizzard like weather conditions existed, that the snow fall was dense & the wind was variable & gusting. The wreckage was located atop a mountain at approximately…NTSB FTW82DA068Accident · No injuriesFinal reportCessna 172 · Kingfisher, OKThe student pilot stated he read the wind direction as coming from the south and landed accordingly. The aircraft landed downwind, the nose wheel dug in and collapsed, and the aircraft nosed over.NTSB FTW82DA057Accident · No injuriesFinal reportCessna 172 · Navajo Dam, NMThe pilot landed at an unattended airport on what he thought to be approximately 2 inches of snow. It turned out to be 8 inches and the aircraft turned over on landing.NTSB SEA82FYK07Accident · 1 fatalFinal reportCessna 172 · Lapine, ORWhen the pilot landed at lakeview,OR,he checked the weather but reported to his passenger that although the weather was bad he did not want to stay in lakeview. The aircraft departed lakeview, following a highway, when the weather conditions continued to…NTSB FTW82DA039Accident · No injuriesFinal reportCessna 172 · Fruit Vale, TXThe pilot stated that during the approach he was momentarily blinded by the sun. The aircraft collided with the top wire on a fence at the end of the runway pulling it down onto the runway.NTSB NYC82DA016Accident · No injuriesFinal reportCessna 172 · Galeton, PAAfter takeoff from the original departure point, the pilot flew to a local airport and landed on runway 28. The runway was covered with snow and the winds were from 270 degrees at 10 knots. After landing, the pilot taxied back for takeoff. While in a right…