NTSB investigations: Cessna 172, 1984
8 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\") = 1984
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") = 1984
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 ATL85FA060Accident · 1 fatalField investigationFinal reportCessna 172 · Hamilton, ALInitiated night flt into area of forecast and observed marginal VFR conditions. Expected to encounter 1200 ft ceiling. Plt stated to fss briefer he would go as FAR as he could. Encountered area of patchy grnd fog, reduced visibility, no horizon ahead. Elected…NTSB MIA85LA005Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Miles City, FLThe acft collided with heavy brush and the ground during a takeoff from a wet sod rwy. The plt reported that the rwy hadbeen furrowed by wild hogs and he and his 13 year old son had tried to repair the damage prior to takeoff. A takeoff wasattempted using…NTSB NYC84FNC09Accident · 1 fatalFinal reportCessna 172 · Pownal, MEPrior to the accident, witnesses observed the acft making several low passes & maneuvering. During the last maneuver, the acft entered a dive & collided with trees before the plt recovered. Trees were broken or damaged over an area of about 200 ft. no…NTSB LAX84IA448Incident · No injuriesIncident investigationFinal reportCessna 172 · Redding, CAPlt briefed pax on use of brakes so he could hand prop acft. Plt stated, the acft 'got away from the passenger' when the engine started. Acft contacted a parked acft and a hangar before stopping.NTSB SEA84LA161Accident · No injuriesLimited investigationFinal reportCessna 172 · Moscow, IDThe acft ran off the rwy into tall wet weeds during a landing on a private agricultural airstrip. The plt said a x-wind caused the swerve. A weather reporting station 6 NM away reported the wind as 7 KTS with no gusts. The plt landed to thenorth and the…NTSB SEA84LA116Accident · No injuriesLimited investigationFinal reportCessna 172 · Stewart Island, WAThe plt landed to the west on a wet grass strip with 1/4 inch of standing water. He said he had no traction & the acft slid off the end between 2 trees, damaging both wings. He also said the wind was 090 deg at 5 KTS gusting 15 KTS.NTSB LAX84LA289Accident · No injuriesLimited investigationFinal reportCessna 172 · Montague, CAAn improper ldg flare by the dual student plt caused the acft to balloon to 15 to 20 ft AGL. The CFI called for power, but the student delayed adding power & raised the nose. At the sound of the stall warning horn, a go-around was called for by the CFI &…NTSB FTW84LA223Accident · No injuriesLimited investigationFinal reportCessna 172 · Allen, OKThe pilot stated that he could not climb enough to clear the trees at the end of the airport. The left wing hit a tree then the right wing hit a pwr line and utility pole. The acft then crashed into the ground. The plt had about 400 hours in this make and…