Fatal NTSB investigations: Cessna 172F
73 cases on aircraft the registry lists as Cessna 172F. 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 | 7 |
|---|---|
| 1966 | 8 |
| 1967 | 6 |
| 1968 | 3 |
| 1969 | 1 |
| 1970 | 1 |
| 1971 | 4 |
| 1972 | 5 |
| 1973 | 4 |
| 1974 | 2 |
| 1975 | 2 |
| 1976 | 1 |
| 1977 | 4 |
| 1978 | 1 |
| 1981 | 2 |
| 1982 | 1 |
| 1983 | 3 |
| 1989 | 2 |
| 1993 | 1 |
| 1995 | 2 |
| 1996 | 1 |
| 1997 | 1 |
| 1998 | 1 |
| 2001 | 1 |
| 2004 | 1 |
| 2005 | 1 |
| 2006 | 1 |
| 2009 | 1 |
| 2016 | 1 |
| 2018 | 1 |
| 2022 | 1 |
| 2024 | 1 |
| 2025 | 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 ('2072414'))
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 ('2072414'))
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 WPR25FA294Accident · 1 fatalClass 3 · FieldPreliminary reportCessna 172F · Battle Ground, WAOn September 26, 2025, about 1306, Pacific daylight time a Cessna 172F, N8219U, was destroyed when it was involved in an accident near Battle Ground, Washington. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal…NTSB CEN24FA305Accident · 1 fatalClass 3 · FieldFinal reportCessna 172F · Brazoria, TXThe pilot’s failure to attain adequate airspeed for takeoff, which led to the airplane exceeding its critical angle-of-attack and an aerodynamic stall. Contributing to the accident was the pilot’s failure to abort the takeoff after not maintaining directional…NTSB WPR22FA188Accident · 2 fatalClass 3 · FieldFinal reportCessna 172F · Show Low, AZThe pilot’s improper leaning of the engine during an extended period of time, which caused an exhaust valve to become stuck and led to the partial loss of engine power during the accident flight. Contributing to the accident was the pilot’s decision to…NTSB CEN18FA088Accident · 1 fatalField investigationFinal reportCessna 172F · Williamsport, INThe pilot's mismanagement of fuel, which resulted in fuel exhaustion and descent and collision with trees.NTSB WPR16LA138Accident · 3 fatalLimited investigationFinal reportCessna 172 · Brookings, ORThe pilot's spatial disorientation and loss of situational awareness during the departure turn in dark night conditions, which resulted in an in-flight collision with water.NTSB ERA09LA132Accident · 1 fatalLimited investigationFinal reportCessna 172 · Hardin, KYThe pilot's failure to maintain aircraft control and his impairment from illegal drug use.NTSB CHI06FA184Accident · 1 fatalField investigationFinal reportCessna 172F · Brookville, INThe in-flight loss of engine power during cruise flight due to restricted fuel flow and the inadequate preflight the pilot performed. An additional cause was the trees.NTSB DFW05FA082Accident · 1 fatalField investigationFinal reportCessna 172F · Hot Springs, ARA loss of engine power due to the pilot's failure to refuel resulting in fuel starvation. Contributing factors were the lack of suitable terrain for the forced landing, and a shoulder harness restraint system was not installed.NTSB ATL04FA130Accident · 2 fatalField investigationFinal reportCessna 172F · Madisonville, TNThe pilot's failure to maintain airspeed while maneuvering on a touch and go landing resulting in a stall and collision with the ground.NTSB LAX01FA070Accident · 2 fatalField investigationFinal reportCessna 172F · San Luis Obispo, CAThe pilot's failure to maintain a proper climb rate to VFR conditions on-top.NTSB CHI99FA042Accident · 2 fatalField investigationFinal reportCessna 172F · Coleman, WIpilot's failure to maintain clearance from the trees and his intentional flight into IMC conditions. Factors contributing to this accident were the pilot's lack of instrument certification, his becoming lost in the poor weather, his inadequate preparation for…NTSB NYC97FA048Accident · 1 fatalField investigationFinal reportCessna 172F · Conrad, PAVFR flight by the pilot into instrument meteorological conditions (IMC), and spatial disorientation of the pilot, which led to loss of aircraft control, an uncontrolled descent, and subsequent collision with wooded terrain. Factors relating to the accident…NTSB CHI96FA348Accident · 1 fatalField investigationFinal reportCessna 172F · Saint Clair, MNa loss of power due to the engine's #2 cylinder exhaust valve stuck open, and the pilot's failure to maintain airspeed.NTSB BFO95FA050Accident · 1 fatalField investigationFinal reportCessna 172F · Tappahanock, VAThe student pilot's misjudgment of distance/speed during the approach to land, and her failure to go around while there was still sufficient runway remaining. Factors related to the accident were: inadequate supervision by the flight instructor, the student's…NTSB ATL95FA079Accident · 1 fatalField investigationFinal reportCessna 172F · Seneca, SCThe pilot's inadequate visual lookout while maneuvering near utility lines, which resulted in a collision with the wires.NTSB CHI93FA218Accident · 1 fatalField investigationFinal reportCessna 172F · Miami, MOthe pilot's failure to maintain aircraft control.NTSB ATL89FA163Accident · 1 fatalField investigationFinal reportCessna 172F · Vernon, ALImproper maintenance of the spark plugs by the pilot/mechanic which resulted in a partial loss of engine power, and the pilot's failure to clear trees during an emergency landing in an open field resulting in an inadvertent stall.NTSB LAX89FA113Accident · 1 fatalField investigationFinal reportCessna 172F · Safford, AZFailure of the pilot to maintain proper airspeed while on final approach resulting in an aerodynamic stall. Contributing to the accident was the pilot's delayed use of wing flaps.NTSB ATL84FA033Accident · 1 fatalField investigationFinal reportCessna 172F · Brunswick, GAThe acft was observed entering a cloud layer about 500 ft AGL after takeoff. Another witness observed the acft's navigational lights in a circling motion as the acft plunged to the ground.NTSB FTW83FA362Accident · 3 fatalField investigationFinal reportCessna 172F · El Paso, TXTwo plts & 2 passengers departed san angelo, TX, on a x-country flt, one of the plts, who had 95 hrs of flying time, was the pilot-in-command (PIC) for the 1st leg of the x-country to El Paso, TX. On the next leg, the other plt assumed duties as PIC & signed…NTSB ATL83FIG03Accident · 1 fatalFinal reportCessna 172F · Hancock, MDThe aircraft collided with the top two wires of a powerline during a low altitude sight-seeing flight along the potomac river. The pilot stated he was maintaining visual contact with the ground should an emergency landing become necessary. He was staying high…NTSB SEA82FA111Accident · 4 fatalField investigationFinal reportCessna 172F · Oxbow, ORDuring the final approach the aircraft was observed to descend to approximately 50 feet above the river and then execute a pullup and begin a left turn to either reenter a left downwind or reverse the direction of landing. The pilot lost control, the left…NTSB ATL82FA109Accident · 3 fatalClosedCessna 172F · Wolf Pen, WVNTSB ATL81FA075Accident · 1 fatalClosedCessna 172 · Rocky Face, GANTSB NYC79FA012Accident · 3 fatalClosedCessna 172F · Mcadoo, PANTSB DEN77FA054Accident · 3 fatalClosedCessna 172 · Nsalina, UTNTSB NYC77FA075Accident · 1 fatalClosedCessna 172 · Mayfield, NYNTSB CHI77FA061Accident · 1 fatalClosedCessna 172F · Grand Rapids, MINTSB MKC77FA027Accident · 2 fatalClosedCessna 172 · Cedar Rapids, IANTSB FTW76FPM22Accident · 1 fatalClosedCessna 172F · Jenks, OKNTSB CHI76AC034Accident · 2 fatalClosedPiper PA-28 · Salem, MINTSB CHI75ACO57Accident · 1 fatalClosedCessna 172F · Wilmington, OHNTSB LAX75AL023Accident · 2 fatalClosedCessna 172F · Lebec, CANTSB CHI75AC015Accident · 1 fatalClosedCessna 172F · Mayview, ILNTSB LAX74AL035Accident · 2 fatalClosedCessna 172F · Kingman, AZNTSB OAK74AP012Accident · 3 fatalClosedCessna 172F · Weaverville, CANTSB CHI74AC003Accident · 4 fatalClosedCessna 172F · No.Webster, INNTSB IAD73AI005Accident · 2 fatalClosedCessna 172F · Mcclellanville, SCNTSB FTW73AF032Accident · 1 fatalClosedCessna 172F · Cleveland, TXNTSB LAX73AL014Accident · 1 fatalClosedCessna 172F · Salome, AZNTSB CHI72FEG41Accident · 1 fatalClosedCessna 172F · So.Webster, OHNTSB MKC72AK054Accident · 2 fatalClosedCessna 172F · Sioux Falls, SDNTSB LAX72AL050Accident · 2 fatalClosedCessna 172F · Missing AircraftNTSB MIA72FKJ36Accident · 1 fatalClosedCessna 172F · Oneonta, ALNTSB NYC72AN049Accident · 4 fatalClosedCessna 172L · Meyerstown, PANTSB FTW72AF017Accident · 2 fatalClosedCessna 172F · Boerne, TXNTSB DEN72AD014Accident · 2 fatalClosedCessna 172F · Capitan, NMNTSB NYC70AN065Accident · 1 fatalClosedCessna 172 · Missing AircraftNTSB FTW70F0104Accident · 1 fatalClosedCessna 172F · Brinkley, ARNTSB MKC69A0042Accident · 1 fatalClosedCessna 172F · Kennett, MO