NTSB investigations: Cessna 172K
691 cases on aircraft the registry lists as Cessna 172K. 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
| 1967 | 1 |
|---|---|
| 1968 | 3 |
| 1969 | 29 |
| 1970 | 48 |
| 1971 | 66 |
| 1972 | 52 |
| 1973 | 43 |
| 1974 | 40 |
| 1975 | 21 |
| 1976 | 30 |
| 1977 | 29 |
| 1978 | 25 |
| 1979 | 15 |
| 1980 | 12 |
| 1981 | 13 |
| 1982 | 11 |
| 1983 | 6 |
| 1984 | 5 |
| 1985 | 7 |
| 1986 | 6 |
| 1987 | 12 |
| 1988 | 9 |
| 1989 | 5 |
| 1990 | 7 |
| 1991 | 11 |
| 1992 | 4 |
| 1993 | 7 |
| 1994 | 12 |
| 1995 | 6 |
| 1996 | 12 |
| 1997 | 5 |
| 1998 | 6 |
| 1999 | 6 |
| 2000 | 10 |
| 2001 | 5 |
| 2002 | 8 |
| 2003 | 10 |
| 2004 | 7 |
| 2005 | 4 |
| 2006 | 2 |
| 2007 | 8 |
| 2008 | 3 |
| 2009 | 1 |
| 2010 | 4 |
| 2011 | 6 |
| 2012 | 6 |
| 2013 | 5 |
| 2014 | 7 |
| 2015 | 2 |
| 2016 | 6 |
| 2017 | 1 |
| 2018 | 2 |
| 2019 | 8 |
| 2020 | 1 |
| 2021 | 3 |
| 2022 | 4 |
| 2023 | 4 |
| 2024 | 4 |
| 2025 | 4 |
| 2026 | 2 |
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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072430'))
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072430'))
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 CEN26LA167Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Topeka, KSThe student pilot’s failure to maintain situational awareness while taxiing which resulted in a collision with fence poles on either side of a gate which was not intended for airplanes.NTSB CEN26LA094Accident · No injuriesClass 3 · LimitedPreliminary reportCessna 172K · Amery, WIOn January 16, 2026, about 1130 central standard time, a Cessna 172 airplane, N79118, was substantially damaged when it was involved in an accident near Amery, Wisconsin. The pilot was not injured. The airplane was operated as a Title 14 Code of Federal…NTSB ERA25LA361Accident · Minor injuriesClass 3 · LimitedPreliminary reportCessna 172K · Salisbury, CTOn September 20, 2025, about 1733 eastern daylight time, a Cessna 172K, N78938, was substantially damaged when it was involved in an accident near Salisbury, Connecticut. The flight instructor and pilot receiving instruction sustained minor injuries. The…NTSB WPR25FA182Accident · 1 fatalClass 3 · FieldPreliminary reportCessna 172 · Billings, MTOn June 19, 2025, at 1412 mountain daylight time, a Cessna 172K airplane, N79306, was destroyed when it was involved in an accident near Billings, Montana. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations…NTSB ERA25LA112Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Rock Hill, SCThe student pilot’s failure to maintain control of the airplane during an aborded crosswind landing.NTSB WPR25LA082Accident · Serious injuriesClass 3 · LimitedFinal reportCessna 172K · Columbia, CAA partial loss of engine power for undetermined reasons.NTSB ERA25LA087Accident · No injuriesClass 4 · LimitedFinal reportCessna 172K · Southport, NCThe pilot’s loss of aircraft control due to spatial disorientation, and the flight instructor’s inadequate supervision, which resulted in the subsequent overstress of the airplane during recovery.NTSB ERA24LA388Accident · Minor injuriesClass 3 · LimitedFinal reportCessna 172K · Spartanburg, SCMaintenance personnel’s failure to follow the engine manufacturer’s maintenance guidance, which resulted in the assembly of the engine with an obstructed oil passage, a subsequent lack of lubrication to the front main bearing, and a total loss of engine power.NTSB ERA24LA390Accident · Minor injuriesClass 3 · LimitedFinal reportCessna 172K · Fredericksburg, VAThe pilot’s inadequate fuel planning, which resulted in fuel exhaustion and a subsequent total loss of engine power.NTSB ERA24LA241Accident · Minor injuriesClass 3 · LimitedFinal reportCessna 172 · Terryville, CTA total loss of engine power for undetermined reasons.NTSB WPR23LA241Accident · No injuriesClass 3 · LimitedFinal reportCessna 172K · Marana, AZA total loss of engine power due to fuel exhaustion.NTSB WPR23LA114Accident · No injuriesClass 4 · LimitedFinal reportCessna 172K · Ephraim, UTThe pilot’s improper landing flare and loss of directional control.NTSB CEN23LA111Accident · No injuriesClass 4 · LimitedFinal reportCessna 172K · Moline, ILThe student pilot’s failure to maintain directional control during the landing roll in gusting crosswind conditions.NTSB CEN23LA073Accident · No injuriesClass 4 · LimitedFinal reportCessna 172K · Conway, ARThe solo student pilot’s improper landing flare and subsequent improper recovery from a bounced landing.NTSB CEN22LA382Accident · No injuriesClass 4 · LimitedFinal reportCessna 172K · Kahului, HIThe pilot’s inadequate compensation for gusting winds while maneuvering on the ground.NTSB ERA22LA360Accident · No injuriesClass 4 · LimitedFinal reportCessna 172K · Barnstable, MAThe pilot’s failure to attain a proper touchdown point, which resulted in a runway overrun in gusting wind conditions.NTSB ERA22LA267Accident · Serious injuriesClass 4 · LimitedFinal reportCessna 172 · Bluffton, OHThe student pilot’s loss of control during climb after an aborted landing, which resulted in an aerodynamic stall.NTSB CEN22LA155Accident · No injuriesClass 4 · LimitedFinal reportCessna 172K · Plains, TXThe pilot’s failure to maintain control of the airplane during taxi with a strong crosswind.NTSB ERA22LA006Accident · No injuriesClass 4 · LimitedFinal reportCessna 172K · Williston, FLThe pilot’s failure to maintain clearance from terrain on approach which resulted in controlled flight into trees. Contributing to the accident was the flight instructor’s inadequate supervision of the approach path, the dark night conditions and the landing…NTSB WPR21LA364Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Auburn, CAThe student pilot’s inadequate flare which resulted in a hard and bounced landing.NTSB WPR21LA241Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Moose Creek Ranger Station, IDThe pilot’s improper landing flare which resulted in a bounced hard landing and subsequent nose over.NTSB CEN20LA431Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Big Rapids, MIThe airplane’s impact with a deer during takeoff.NTSB CEN20WA011Accident · 2 fatalForeign investigationCessna 172 · San Salvador, El SalvadorNTSB ERA19LA280Accident · No injuriesClass 3 · LimitedFinal reportCessna 172 · Manville, NJA total loss of engine power due to the ingestion of sealant material that had loosened inside the carburetor airbox.NTSB ERA19LA246Accident · Serious injuriesClass 3 · LimitedFinal reportCessna 172 · Jay, FLThe pilot's improper decision to fly over a river at a very low altitude, which resulted in a collision with power lines.NTSB CEN19CA239Accident · No injuriesData collectionFinal reportCessna 172 · Oshkosh, WIThe pilot's improper fuel planning and decision to not divert to a closer airport when the planned flight profile changed, which resulted in a total loss of engine power due to fuel exhaustion.NTSB GAA19CA439Accident · Minor injuriesData collectionFinal reportCessna 172 · Manteo, NCThe pilot's failure to maintain adequate airspeed and his exceedance of the airplane’s critical angle of attack, which resulted in an aerodynamic stall.NTSB GAA19CA362Accident · No injuriesData collectionFinal reportCessna 172 · Tampa, FLThe student pilot's failure to maintain directional control during landing, which resulted in a runway excursion and subsequent nose-over.NTSB GAA19CA193Accident · No injuriesData collectionFinal reportCessna 172 · Pella, IAThe student pilot's failure to maintain the runway heading and the flight instructor's delayed remedial action during landing, which resulted in the instructor landing the airplane in grass left of the runway and a subsequent nose-over.NTSB ERA19LA194Accident · No injuriesClass 3 · LimitedFinal reportCessna 172 · Mount Holly, NJFailure of the pilot's seat back due to a sheared bolt during the landing roll, which resulted in a loss of directional control and runway excursion.NTSB GAA19CA020Accident · No injuriesData collectionFinal reportCessna 172 · Lawrenceville, GAThe student pilot's improper pitch application, which resulted in a hard landing and subsequent fire. Contributing to the accident was the student’s failure to give over the flight controls to the flight instructor when instructed to do so.NTSB GAA19CA014Accident · No injuriesData collectionFinal reportCessna 172 · Stockton, CAThe student pilot's failure to maintain directional control during takeoff.NTSB GAA17CA373Accident · No injuriesData collectionFinal reportCessna 172 · Roseburg, ORAn in-flight collision with a bird during the approach.NTSB CEN17LA006Accident · No injuriesLimited investigationFinal reportCessna 172K · Wilmot, WIA failure of the No. 1 piston pin plug due to corrosion in the cylinder barrel, which resulted in oil contamination, oil starvation to the crankshaft connecting rod bearings, and a subsequent partial loss of engine power.NTSB GAA16CA473Accident · No injuriesData collectionFinal reportCessna 172 · Fulton, MOThe pilot’s improper landing flare and subsequent improper recovery from a bounced landing, which resulted in the airplane porpoising.NTSB GAA16CA413Accident · Minor injuriesData collectionFinal reportCessna 172 · Cross Keys, NJThe pilot's failure to maintain lateral bank control during final approach, which resulted with an impact with a tree and substantial damage to the left and right wings.NTSB CEN16LA309Accident · No injuriesLimited investigationFinal reportCessna 172K · Neenah, WIA loss of engine power due to oil starvation, which resulted from the pilot, who was not a certified airframe and powerplant mechanic, removing the vacuum pump from the engine, and his misconception that he could operate the airplane without the pump.NTSB GAA16CA340Accident · No injuriesData collectionFinal reportCessna 172 · Lumberton, NJThe pilot's hard landing, resulting in a runway excursion and substantial damage to the firewall.NTSB WPR16LA093Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Avalon, CAThe pilot's failure to maintain a proper approach path on landing because he failed to familiarize himself with the airport's unique approach hazards and recommended procedures before the flight. Also causal was the pilot's failure to recognize the airplane's…NTSB ERA15LA318Accident · No injuriesLimited investigationFinal reportCessna 172K · Chiefland, FLThe partial loss of engine power during cruise flight for reasons that could not be determined because a postaccident airframe and engine examination and engine test run revealed no evidence of mechanical malfunctions or failures.NTSB CEN15CA105Accident · No injuriesData collectionFinal reportCessna 172K · Holland, MIThe pilot's loss of control while landing in gusty wind conditions.NTSB CEN15FAMS1Accident · 2 fatalMissing aircraftFinal reportCessna 172K · Lake Pontchartrain, LAThe airplane's collision with water for reasons that could not be determined because the wreckage was not located.NTSB CEN15LA024Accident · Serious injuriesLimited investigationFinal reportCessna 172K · Xenia, OHThe failure of the seat track mechanism, which led the pilot to inadvertently apply aft yoke and lift his feet off the rudder pedals and resulted in a loss of directional control during takeoff.NTSB ERA14FA428Accident · 2 fatalField investigationFinal reportCessna 172 · Selkirk, NYA loss of engine power for reasons that could not be determined because postaccident examination of the airframe and engine did not reveal any anomalies that would have precluded normal operation.NTSB WPR14FA302Accident · 2 fatalField investigationFinal reportCessna 172K · Littlefield, AZThe pilot's failure to maintain airplane control when the airplane encountered high gusting wind while conducting low altitude flight in a narrow canyon, which resulted in an inflight collision with terrain.NTSB ERA14LA158Accident · Minor injuriesLimited investigationFinal reportCessna 172K · Elizabethton, TNThe pilot’s delayed decision to maneuver around rising terrain, which resulted in a collision with trees and terrain. Contributing to the accident was the pilot’s failure to calculate the performance requirements needed to climb over mountainous terrain…NTSB WPR14CA125Accident · No injuriesData collectionFinal reportCessna 172K · Eastsound, WAThe pilot's inadequate flare and failure to maintain aircraft control during landing in gusty wind conditions.NTSB CEN14LA134Accident · No injuriesLimited investigationFinal reportCessna 172K · Milan, ILThe pilot’s delayed use of carburetor heat while operating the airplane in atmospheric conditions conducive to carburetor icing, which resulted in a total loss of engine power due to carburetor icing during a short final approach.NTSB CEN14CA096Accident · Minor injuriesData collectionFinal reportCessna 172K · Concordia, KSThe pilot's failure to maintain a proper glidepath during approach which resulted in the airplane landing long, and his decision to turn off of the runway during the landing roll which resulted in a collision with an earth berm.NTSB WPR14FA078Accident · 2 fatalField investigationFinal reportCessna 172K · Fresno, CAThe pilot’s failure to maintain adequate clearance from trees while on approach, which subsequently led to a loss of airplane control. Also causal was the pilot’s continued operation of the airplane at night with a diagnosed medical condition that degraded…