Fatal NTSB investigations: Cessna 172M
246 cases on aircraft the registry lists as Cessna 172M. 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
| 1973 | 2 |
|---|---|
| 1974 | 13 |
| 1975 | 17 |
| 1976 | 17 |
| 1977 | 19 |
| 1978 | 6 |
| 1979 | 16 |
| 1980 | 17 |
| 1981 | 9 |
| 1982 | 10 |
| 1983 | 2 |
| 1984 | 3 |
| 1985 | 4 |
| 1986 | 6 |
| 1987 | 2 |
| 1988 | 3 |
| 1989 | 6 |
| 1990 | 8 |
| 1991 | 6 |
| 1992 | 7 |
| 1993 | 5 |
| 1994 | 3 |
| 1995 | 8 |
| 1997 | 7 |
| 1998 | 6 |
| 2000 | 1 |
| 2002 | 1 |
| 2003 | 2 |
| 2004 | 2 |
| 2005 | 2 |
| 2006 | 1 |
| 2007 | 2 |
| 2008 | 2 |
| 2009 | 1 |
| 2010 | 2 |
| 2011 | 4 |
| 2012 | 1 |
| 2013 | 5 |
| 2014 | 3 |
| 2015 | 1 |
| 2016 | 1 |
| 2017 | 3 |
| 2019 | 1 |
| 2020 | 3 |
| 2021 | 1 |
| 2022 | 1 |
| 2023 | 1 |
| 2024 | 1 |
| 2025 | 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.\"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 ('2072418'))
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 ('2072418'))
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 WPR26FA043Accident · 2 fatalClass 3 · FieldPreliminary reportCessna 172M · Poleta, CAOn November 10, 2025, at about 1515 Pacific standard time, Cessna 172M, N13221, was substantially damaged when it was involved in an accident near Poleta, California. A pilot-rated passenger and a passenger were fatally injured, and the pilot was seriously…NTSB WPR25FA268Accident · 1 fatalClass 3 · FieldPreliminary reportCessna 172M · Fort Morgan, COOn August 31, 2025, about 1040 mountain daylight time, a Cessna 172M, N61657, and an Extra Flugzeugproduktions-UND EA 300/LC, N330AN, were both destroyed when they collided midair near Fort Morgan, Colorado. The pilot and safety pilot of the Cessna received…NTSB ERA24LA114Accident · 1 fatalClass 3 · LimitedFinal reportCessna 172M · Brookwood, ALThe pilot’s failure to see and avoid powerlines while maneuvering at low altitude.NTSB ERA23LA328Accident · 2 fatalClass 3 · LimitedFinal reportCessna 172 · Charlotte Amalie, CBThe pilots’ loss of airplane control due to spatial disorientation. Contributing to the accident was both pilots’ lack of experience in operating in actual instrument meteorological conditions.NTSB WPR22LA371Accident · 1 fatalClass 3 · LimitedFinal reportCessna 172M · Pacific Ocean, CAUndetermined because the airplane and pilot were not located.NTSB WPR22FA022Accident · 1 fatalClass 3 · FieldFinal reportCessna 172 · Ukiah, CAA power interruption due to water-contaminated fuel, which resulted in the student pilot aborting the takeoff and landing hard. Contributing to the accident were a leak in the left fuel tank that allowed water to enter and damage to the fuel tank that…NTSB WPR21LA032Accident · 1 fatalClass 3 · LimitedFinal reportCessna 172 · Billings, MTThe pilot’s failure to maintain the proper descent glide path while on final approach for reasons that could not be determined from available evidence.NTSB WPR20LA203Accident · 4 fatalClass 3 · LimitedFinal reportCessna 172 · Alpine, UTThe pilot’s exceedance of the airplane’s critical angle-of-attack while maneuvering in a canyon, which resulted in a loss of airplane control.NTSB CEN20LA214Accident · 1 fatalClass 3 · LimitedFinal reportCessna 172 · New Washington, INA high velocity descent and impact with terrain for undetermined reasons.NTSB WPR19FA080Accident · 2 fatalClass 2 · FieldFinal reportCessna 172 · Desert Hot Springs, CAThe pilot's inadequate and/or improper preparation for the flight in which he selected an altitude too low to assure terrain clearance and resulted in an impact with terrain in turbulent downdraft conditions.NTSB WPR18FA063Accident · 2 fatalField investigationFinal reportCessna 172M · Ogden, UTThe pilot's failure to maintain clearance from the water while flying over a lake with glassy surface conditions. Contributing to the accident was the pilot's use of three impairing medications.NTSB CEN18FA011Accident · 2 fatalField investigationFinal reportCessna 172M · Ramsey, MNThe pilot's decision to fly along the river at a low altitude contrary to applicable regulations and safety of flight considerations which resulted in the impact with the power lines. Contributing to the accident was the pilot's inability to see the and avoid…NTSB ERA17FA272Accident · 1 fatalField investigationFinal reportCessna 172 · New Milford, CTThe flight instructor's failure to ensure that the wing flaps were properly configured for takeoff, which resulted in an aerodynamic stall and loss of control during the initial climb.NTSB WPR17FAMS2Accident · 3 fatalMissing aircraftFinal reportCessna 172M · Open water, HIUndetermined because the airplane was not located.NTSB WPR15MA243Accident · 5 fatalMajor investigationFinal reportCessna 172M · San Diego, CAThe local controller's (LC) failure to properly identify the aircraft in the pattern and to ensure control instructions provided to the intended Cessna on downwind were being performed before turning Eagle1 into its path for landing. Contributing to the LC's…NTSB CEN15FA083Accident · 1 fatalField investigationFinal reportCessna 172M · Odessa, TXThe pilot’s failure to maintain adequate airspeed while maneuvering at an excessive bank angle at a low altitude, which resulted in an accelerated stall and spin with insufficient altitude for a recovery.NTSB ERA14FA459Accident · 2 fatalField investigationFinal reportCessna 172M · Lancaster, NYThe other airplane pilot’s failure to maintain an adequate visual lookout for known traffic in the fly-in event traffic pattern, which resulted in a midair collision.NTSB WPR14LA230Accident · 1 fatalLimited investigationFinal reportCessna 172M · Laytonville, CAThe pilot’s impairment due to alcohol ingestion, which resulted in his failure to maintain clearance from trees during a low-altitude flyby.NTSB ERA13FA330Accident · 1 fatalField investigationFinal reportCessna 172M · Fredericksburg, VAThe pilot's intentional descent into the ground to commit suicide.NTSB WPR13FA294Accident · 1 fatalField investigationFinal reportCessna 172 · Birdseye, UT***This report was modified on August 18, 2015. Please see the docket for this accident to view the original report.*** The operator's improper installation of a supplemental electrical power supply, which caused a short circuit due to inadequate vibration…NTSB CEN13FA364Accident · 4 fatalField investigationFinal reportCessna 172M · Waterford, MIThe pilot's failure to retract the wing flaps before attempting to take off, due to his lack of familiarity with the airplane make and model, which prevented the airplane from maintaining adequate altitude for takeoff.NTSB WPR13FA211Accident · 2 fatalClass 3 · FieldFinal reportCessna 172RG · Calabasas, CAThe failure of the pilots in both aircraft to maintain an adequate visual lookout, which resulted in a midair collision.NTSB WPR13FA138Accident · 1 fatalField investigationFinal reportCessna 172M · Saratoga, WYThe pilot’s decision to attempt flight into approaching adverse weather, which led to his low-level flight, encounter with mountain obscuration and moderate turbulence, and his subsequent loss of airplane control. Contributing to the severity of the pilot’s…NTSB ERA12FA484Accident · 1 fatalField investigationFinal reportCessna 172M · San Juan, PRMaintenance personnel’s improper lubrication of the right direct aileron control cable and failure to detect the severe corrosion of the cable during a maintenance inspection, which resulted in the in-flight failure of the cable, the pilot’s subsequent…NTSB CEN12LA059Accident · 1 fatalLimited investigationFinal reportCessna 172M · Sturgis, SDThe student pilot’s failure to maintain control of the airplane during takeoff with extended flaps.NTSB ERA11FA493Accident · 1 fatalField investigationFinal reportCessna 172M · Greenville, METhe pilot's failure to maintain adequate airspeed while manuevering at low altitude, which resulted in an aerodynamic stall/spin and subsequent impact with terrain.NTSB ERA11FA467Accident · 2 fatalField investigationFinal reportCessna 172M · Titusville, PAThe flight instructor's improper decision to attempt a visual descent into instrument meteorological conditions while approaching the destination airport, which resulted in an in-flight collision with trees and terrain.NTSB ERA11FA369Accident · 2 fatalField investigationFinal reportCessna 172M · Poughkeepsie, NYThe pilot’s loss of airplane control due to impairment or incapacitation as a result of coronary artery disease in combination with atrial fibrillation. Contributing to the accident was the pilot's failure to report his paroxysmal atrial fibrillation to the…NTSB CEN11LA082Accident · 1 fatalLimited investigationFinal reportCessna 172M · Velma, OKThe pilot’s failure to maintain control of the airplane while maneuvering, which resulted in an inadvertent stall and subsequent impact with terrain. Contributing to the accident was the pilot's relative inexperience in pipeline patrols.NTSB ERA10FA414Accident · 2 fatalField investigationFinal reportCessna 172 · Orange, MAThe pilots did not maintain control of the airplane during a flight in dark night conditions due to spatial disorientation.NTSB WPR09FA316Accident · 2 fatalField investigationFinal reportCessna 172M · Rimrock, WAThe pilot's failure to maintain clearance from trees during a go-around. Contributing to the accident was the pilot's lack of flight experience, and his delayed initiation of a go-around.NTSB LAX08FA190Accident · 3 fatalField investigationFinal reportCessna 172M · Pahala, HIThe pilot's continued visual flight into instrument meteorological conditions and his failure to remain clear of rising terrain while deviating from his planned route of flight. Contributing to the accident were clouds and mountainous terrain.NTSB DFW08FA078Accident · 1 fatalField investigationFinal reportCessna 172M · Gun Barrel City, TXThe pilot's failure to avoid the transmission line. A contributing factor was the pilot's decision to perform a low-level maneuver.NTSB ATL07FA125Accident · 2 fatalField investigationFinal reportCessna 172M · Mansfield, MAThe pilot's improper use of wing flaps during takeoff, which resulted in reduced climb performance and a subsequent stall. Contributing to the accident was the exceedance of the airplane's maximum gross weight.NTSB CHI07LA288Accident · 1 fatalLimited investigationFinal reportCessna 172M · Union Star, MOThe student pilot's failure to maintain adequate airspeed and the subsequent inadvertent stall while buzzing residences. Contributing to the accident was the pilot performing buzzing maneuvers.NTSB SEA07FA012Accident · 1 fatalField investigationFinal reportCessna 172M · Escalante, UTThe pilot's failure to maintain aircraft control. Contributing factors were the pilot's lack of experience of flying on instruments on a dark night and in rainy weather.NTSB SEA05FA125Accident · 2 fatalField investigationFinal reportCessna 172M · Yamhill, ORThe flight instructor's excessive climb and failure to maintain adequate airspeed during an attempted go-around, which resulted in an inadvertent stall and subsequent collision with the ground. Contributing factors were the flight instructor's improper…NTSB MIA05LA046Accident · 1 fatalLimited investigationFinal reportCessna 172M · Orlando, FLThe failure of the CFI to initiate a precautionary landing after noticing zero oil pressure with corresponding oil temperature increase, resulting in total loss of engine power due to oil exhaustion. A contributing factor in the accident was the failure of…NTSB IAD04LA036Accident · 1 fatalLimited investigationFinal reportCessna 172M · Brownville Junc, METhe pilot's continued visual flight into instrument meteorological conditions, which resulted in the airplane's controlled flight into rising terrain. Factors included the instrument meteorological conditions and the rising terrain.NTSB NYC04FA171Accident · 1 fatalField investigationFinal reportCessna 172M · Brookville, OHThe student pilot's control interference while the flight instructor was maneuvering to avoid a tree, which resulted in a failure to maintain airspeed and a stall/mush.NTSB ATL03FA142Accident · 1 fatalField investigationFinal reportCessna 172M · Perry, GAThe pilot inadequate preflight inspection of the airplane, and also causal was his failure to detect water-contaminated fuel which resulted in a loss of engine power and his failure to maintain adequate airspeed which resulted in an stall.NTSB FTW03FA184Accident · 2 fatalField investigationFinal reportCessna 172M · McAllen, TXThe pilot's failure to recover from a bounced landing which resulted in a loss of control. Contributing factors were the gusty winds.NTSB MIA03FA007Accident · 2 fatalField investigationFinal reportCessna 172M · Coral Springs, FLThe failure of the dual students and flight instructors on both N9840V and N6101F to see and avoid each other, which resulted in a midair collision.NTSB CHI00FA129Accident · 3 fatalField investigationFinal reportCessna 172M · Cornell, WIthe pilot not maintaining aircraft control and the stall/spin he encountered. A factor was the extended flaps.NTSB FTW99FA006Accident · 1 fatalField investigationFinal reportCessna 172M · Oklahoma City, OKSuicide.NTSB ATL99WA010Accident · 4 fatalForeign investigationCessna 172M · Freeport, BahamasNTSB CHI98FA274Accident · 1 fatalField investigationFinal reportCessna 172M · Brooklyn, MIThe proper touchdown point was not attained and the visual lookout not being maintained by the pilot-in-command. Contributing factors to the accident were the unmarked static and transmission wires.NTSB IAD98FA072Accident · 1 fatalField investigationFinal reportCessna 172M · Hebron, CTThe pilot's failure to obtain a weather briefing which resulted in inadvertent flight into instrument meteorological conditions, and his failure to maintain control of the airplane due to spatial disorientation. Factors in this accident were low ceilings and…NTSB ANC98FA048Accident · 2 fatalField investigationFinal reportCessna 172M · Palmer, AKThe pilot's intentional flight into known adverse weather conditions. Contributing factors were the terrain induced turbulence, clouds, the pilot's overconfidence in his abilities, and mountainous terrain conditions.NTSB LAX98FA066Accident · 2 fatalField investigationFinal reportCessna 172M · Chandler, AZThe pilot's intentional flying at a low altitude and failure to see and avoid the power lines during dusk conditions.