NTSB investigations: Cessna 172RG, 1983
10 cases on aircraft the registry lists as Cessna 172RG. 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
| 1965 | 1 |
|---|---|
| 1966 | 1 |
| 1970 | 1 |
| 1972 | 1 |
| 1979 | 2 |
| 1980 | 3 |
| 1981 | 11 |
| 1982 | 7 |
| 1983 | 10 |
| 1984 | 11 |
| 1985 | 13 |
| 1986 | 3 |
| 1987 | 10 |
| 1988 | 5 |
| 1989 | 8 |
| 1990 | 9 |
| 1991 | 8 |
| 1992 | 8 |
| 1993 | 6 |
| 1994 | 12 |
| 1995 | 8 |
| 1996 | 8 |
| 1997 | 8 |
| 1998 | 5 |
| 1999 | 7 |
| 2000 | 2 |
| 2001 | 11 |
| 2002 | 6 |
| 2003 | 5 |
| 2004 | 6 |
| 2005 | 5 |
| 2006 | 4 |
| 2007 | 3 |
| 2008 | 10 |
| 2009 | 5 |
| 2010 | 2 |
| 2011 | 3 |
| 2012 | 2 |
| 2013 | 4 |
| 2014 | 2 |
| 2015 | 1 |
| 2016 | 3 |
| 2017 | 4 |
| 2018 | 1 |
| 2019 | 2 |
| 2020 | 1 |
| 2021 | 1 |
| 2022 | 4 |
| 2024 | 1 |
| 2025 | 1 |
| 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\") = 1983
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072438'))
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") = 1983
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072438'))
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 MIA84FA038Accident · 1 fatalField investigationFinal reportCessna 172RG · Cross City, FLWhile in the vicinity of Cross City the plt requested VFR flt following from jacksonville ARTCC. While he was in radio &radar contact, the controller suddenly lost radar contact with the flt. Radar indicated that the acft made a rapid descent from the cruise…NTSB FTW84LA031Accident · No injuriesLimited investigationFinal reportCessna 172RG · Monticello, ARDuring flt, the plt detected smoke in the cabin. Thinking that an electrical malfunction was the source, he secured the electrical master switch & used the battery. A precautionary landing was made at Monticello, AR. During the landing, the right main gear…NTSB CHI83LA286Accident · No injuriesLimited investigationFinal reportCessna 172RG · Dayton, OHThe acft collided with equipment when landing on a closed rwy at night. The plt of N4929V called Dayton approach regarding landing at Dayton general but did not receive info that the fld was closed. Another acft called ATC at about this time, without…NTSB LAX83FUM06Accident · Serious injuriesFinal reportCessna 172RG · San Clemente, CAThe acft crashed on San Clemente island during a fish spotting flt on a dark night. These flts are usually flown at an alt of 1000-2000 ft AGL. A navy witness on the accident island said the ceiling was zero and the visibility about 200 yards at the accident…NTSB MKC83LA099Accident · Minor injuriesLimited investigationFinal reportCessna 172RG · Newton, KSThe aircraft crashed alongside the runway during an attempted go-around. The runway in use was 17 and the wind was from 250 degrees at 15 KTS gusting to 24 KTS. The pilot stated he could not get aligned with the runway so he retracted the landing gear and…NTSB MIA83FA113Accident · 1 fatalField investigationFinal reportCessna 172RG · Gainesville, FLThe acft crashed about 8 miles from the intended destination during weather on a dark night. The plt had gone outbound that afternoon with two passengers who did not return with him because of motion sickness. According to the one of his former instructors…NTSB LAX83LA102Accident · No injuriesLimited investigationFinal reportCessna 172RG · Wenden, AZThe acft drifted off the runway into a plowed area of a private airstrip during landing and nosed over. The private pilot reported that as he began to flare the acft for landing to the west a gust of wind from the north caused the acft to drift southward. The…NTSB CHI83LA081Accident · Serious injuriesLimited investigationFinal reportCessna 172 RG · Green Bay, WIThe acft collided with the ground during an ILS approach. The weather was IMC at the time and an IFR flt plan was filed. The pilot was instrument rated and had received a weather briefing which forecast icing and freezing drizzle. The pilot told the weather…NTSB FTW83LA077Accident · No injuriesLimited investigationFinal reportCessna 172RG · San Angelo, TXThe acft had reached an alt of 3500 ft MSL when the engine started to lose power. The pilot turned back toward his departure airport. The engine then lost all power and the pilot elected to land in a plowed field with landing gear down. When the acft touched…NTSB LAX83LA063Accident · Minor injuriesLimited investigationFinal reportCessna 172RG · Sedona, AZWhile enroute, the plt noticed that he had lost his airspeed indication. Observing the pitot head on the wing with a flashlight, he stated that the flip-up cover was down, covering the ram tube. Unable to maintain proper airspeed, the plt inadvertently…