Fatal NTSB investigations: Cessna 172G
73 cases on aircraft the registry lists as Cessna 172G. 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
| 1966 | 9 |
|---|---|
| 1967 | 4 |
| 1968 | 3 |
| 1969 | 10 |
| 1970 | 3 |
| 1971 | 5 |
| 1972 | 5 |
| 1973 | 2 |
| 1976 | 3 |
| 1977 | 1 |
| 1978 | 2 |
| 1979 | 1 |
| 1980 | 2 |
| 1981 | 2 |
| 1982 | 2 |
| 1985 | 1 |
| 1986 | 1 |
| 1988 | 2 |
| 1989 | 1 |
| 1991 | 2 |
| 1992 | 2 |
| 1993 | 1 |
| 1995 | 1 |
| 1998 | 1 |
| 2000 | 1 |
| 2015 | 1 |
| 2017 | 1 |
| 2020 | 1 |
| 2023 | 2 |
| 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 c.\"highestInjuryLevel\" = 'Fatal'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072420'))
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 c."highestInjuryLevel" = 'Fatal'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072420'))
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 WPR26FA284Accident · 1 fatalClass 3 · FieldPreliminary reportCessna 172 · Blackfoot, IDOn August 1, 2026, about 2301 mountain daylight time (MDT), a Cessna 172G, N1166F, was substantially damaged when it was involved in an accident near Blackfoot, Idaho. The pilot was fatally injured, and the two passengers sustained serious injuries. The…NTSB WPR24FA057Accident · 3 fatalClass 3 · FieldFinal reportCessna 172G · Independence, ORThe pilot’s decision to continue flight under visual flight rules into instrument meteorological conditions, which resulted in collision with an obstacle while landing.NTSB WPR24FA035Accident · 2 fatalClass 3 · FieldFinal reportCessna 172G · Provo, UTThe pilot's exceedance of the airplane's critical angle of attack during a chandelle maneuver, which resulted in an aerodynamic stall and descent into trees and terrain. Contributing to the accident was the pilot’s decision to maneuver into a canyon and…NTSB WPR21WA062Accident · 1 fatalClass 5 · ForeignCessna 172 · Katale, UgandaNTSB CEN18FA037Accident · 1 fatalField investigationFinal reportCessna 172G · Pittsford, VTThe pilot's decision to continue visual flight into instrument meteorological conditions, which resulted in a loss of control due to spatial disorientation.NTSB ERA15FA203Accident · 1 fatalField investigationFinal reportCessna 172 · Penn Yan, NYThe student pilot's failure to maintain airplane control during the initial climb. Contributing to the accident was the student's inappropriate configuration of the airplane's wing flaps for the initial climb.NTSB ANC00FA110Accident · 1 fatalField investigationFinal reportCessna 172G · Juneau, AKThe pilot's inadvertent stall/mush. A factor in the accident was the pilot's lack of certification.NTSB NYC99FA007Accident · 2 fatalField investigationFinal reportCessna 172G · Bennington, VTThe pilot's VFR flight into IMC. Contributing factors were the pilot's lack of recent experience, mountainous/hilly terrain, and clouds.NTSB LAX95LA101Accident · 1 fatalLimited investigationFinal reportCessna 172G · Pope Valley, CAthe pilot's poor judgment to buzz the lake and his inadequate visual lookout.NTSB ATL93FA059Accident · 3 fatalField investigationFinal reportCessna 172G · Jackson, GAThe pilots inadequate preflight planning and his failure to properly compensate for the wind. A factor was the unfavorable wind condition at the time of take off.NTSB ATL93FA025Accident · 3 fatalField investigationFinal reportCessna 172 · Brownsboro, ALThe pilot failed to evaluate the wind conditions and took off with a tailwind which resulted in the collision with a tree on the departure end of the runway. Factors were dark night and tailwind.NTSB MIA92LA061Accident · 1 fatalLimited investigationFinal reportCessna 172G · Atlantic Ocean (Atlantic Ocean)Loss of engine power due to undetermined reasons.NTSB SEA92FA002Accident · 4 fatalField investigationFinal reportCessna 172G · Miltonfreewater, ORInadequate in-flight planning. Factors to the accident were: mountainous terrain, clearance not maintained, lack of total flight experience, and lack of familiarity with geographical area.NTSB NYC91FA115Accident · 2 fatalField investigationFinal reportCessna 172G · New Bedford, MAThe pilot's improper planning/decision and failure to maintain proper altitude after encountering adverse weather at low altitude. The adverse weather (fog) was a related factor.NTSB ATL89FA182Accident · 3 fatalField investigationFinal reportCessna 172G · Ridgeland, SCImproper planning/decision by the pilot-in-command (PIC), which resulted in an inadvertent stall during takeoff. Factors related to the accident were: the excessive gross weight and improper lift-off by the PIC, the pilot/passenger's improper crew…NTSB MKC88FA124Accident · 1 fatalField investigationFinal reportCessna 172G · Sarcoxie, MOWitnesses at the acdnt site characterized the wx as having a low ceiling with fog. They rprtd they saw the acft 'appear out of clouds' in a steep descent. The acft then began to 'pull up;' however, during recovery from the dive, the acft struck trees &…NTSB LAX88FA161Accident · 4 fatalField investigationFinal reportCessna 172G · Los Banos, CAFailure of the pilot to maintain control of his aircraft to avert a collision with the ground.NTSB FTW86FA086Accident · 1 fatalField investigationFinal reportCessna 172G · Blackwell, OKThe pilot of N5878R, a Cessna 172G, had no previous experience in formation flying. The pilot of N2603E, an Aeronca 7AC, stated he had many hours of formation flying in the military during world war ii and has made an occasional formation flight since that…NTSB CHI85FA316Accident · 1 fatalField investigationFinal reportCessna 172G · Plain City, OHThe plt had just taken off from his pvt strip for the fourth flt of the day when witnesses heard the eng quit. The acft had been flown 3.4 hrs since the last refueling. The acft was being operated on a mixture of avgas and automotive fuel with no STC. The…NTSB DEN83FTE02Accident · 1 fatalFinal reportCessna 172G · Mack, COWhile on a flt from evanston, WY to glenwood, CO, the plt encountered "cloud to ground" conditins & diverted toward grand junction, CO. He stated that due to a nav problem, he radioed grand junction tower to verify his position. Grand junction had no radar &…NTSB ATL83FID01Accident · 1 fatalFinal reportCessna 172G · Boones Mill, VAThe pilot was trying to approach roanoke in weather that obscured the mountain tops. He crashed into a mountain slope at the 2900 foot level. He had contacted roanoke radio but radar contact had not been established. During his weather briefing VFR flight had…NTSB MIA82FA014Accident · 1 fatalClosedCessna 172G · St.Petersburg, FLNTSB MKC81FA042Accident · 2 fatalClosedCessna 172G · Newburg, MONTSB NYC80FA043Accident · 3 fatalClosedCessna 172G · Cape May, NJNTSB LAX80FA032Accident · 2 fatalClosedCessna 172 · Coalinga, CANTSB CHI79FA078Accident · 2 fatalClosedCessna 172G · Brownstown, ILNTSB LAX79FA016Accident · 1 fatalClosedCessna 172G · Cuyamaca, CANTSB FTW79FA001Accident · 1 fatalClosedCessna 172 · Bridgeport, TXNTSB MIA78FA022Accident · 2 fatalClosedCessna 172 · Blairsville, GANTSB IAD76AI078Accident · 1 fatalClosedCessna 172 · St Pauls, NCNTSB FTW76AF103Accident · 3 fatalClosedCessna 172M · Sperry, OKNTSB FTW76AF071Accident · 1 fatalClosedCessna 172 · Marksville, LANTSB OAK74AP017Accident · 1 fatalClosedCessna 172G · Bass Lake, CANTSB IAD74AI013Accident · 1 fatalClosedCessna 188B · Swan Quarter, NCNTSB UNK73X0100Accident · 1 fatalClosedCessna 172L · Lamacaza, CanadaNTSB MKC73AK004Accident · 1 fatalClosedCessna 172 · Tunica, MSNTSB LAX72AL065Accident · 2 fatalClosedCessna 172 · La Mesa, CANTSB CHI72AC071Accident · 3 fatalClosedCessna 172G · Orion, ILNTSB MKC72AK051Accident · 3 fatalClosedCessna 172G · Bartlett, NENTSB FTW72AF039Accident · 1 fatalClosedCessna 172 · Seguin, TXNTSB FTW72AF003Accident · 2 fatalClosedCessna 172 · Sasakwa, OKNTSB OAK71AP040Accident · 2 fatalClosedCessna 172 · Sacramento, CANTSB MKC71AK044Accident · 1 fatalClosedCessna 172G · Marshalltown, IANTSB CHI71AC056Accident · 1 fatalClosedCessna 172G · Chevrolet, KYNTSB SEA71AS029Accident · 1 fatalClosedCessna 172 · Reardan, WANTSB IAD71AI021Accident · 3 fatalClosedCessna 172G · Providence Frg, VANTSB LAX70AL066Accident · 4 fatalClosedCessna 172G · St.Johns, AZNTSB MIA70A0041Accident · 1 fatalClosedCessna 172G · Hazelhurst, MSNTSB IAD70A0030Accident · 2 fatalClosedCessna 172G · Accident, MDNTSB OAK70A0031Accident · 1 fatalClosedCessna 172G · Missing Aircraft