Fatal NTSB investigations: Cessna 172P
113 cases on aircraft the registry lists as Cessna 172P. 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
| 1981 | 3 |
|---|---|
| 1982 | 4 |
| 1983 | 3 |
| 1984 | 2 |
| 1985 | 3 |
| 1986 | 3 |
| 1987 | 5 |
| 1988 | 10 |
| 1989 | 6 |
| 1990 | 8 |
| 1991 | 8 |
| 1992 | 8 |
| 1993 | 6 |
| 1994 | 2 |
| 1995 | 2 |
| 1996 | 3 |
| 1997 | 3 |
| 1998 | 3 |
| 1999 | 3 |
| 2000 | 3 |
| 2001 | 1 |
| 2002 | 2 |
| 2003 | 5 |
| 2004 | 2 |
| 2005 | 2 |
| 2009 | 1 |
| 2010 | 1 |
| 2012 | 1 |
| 2015 | 3 |
| 2016 | 2 |
| 2021 | 1 |
| 2022 | 2 |
| 2023 | 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 ('2072436'))
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 ('2072436'))
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 ERA23FA323Accident · 2 fatalClass 3 · FieldFinal reportCessna 172 · Pembroke Pines, FLThe flight instructor’s exceedance of the airplane’s critical angle of attack during the initial climb, which resulted in an aerodynamic stall and subsequent rapid descent into terrain.NTSB ERA23FA247Accident · 2 fatalClass 3 · FieldFinal reportCessna 172 · Lake Worth, FLMaintenance personnel’s failure to detect the corroded aileron cable during recent inspections, which resulted in the separation of the aileron control cable and a subsequent loss of airplane control during takeoff.NTSB ERA23FA008Accident · 1 fatalClass 3 · FieldFinal reportCessna 172 · Newport News, VAThe flight instructor’s failure to monitor the student pilot on takeoff and her delayed remedial action to stop him from exceeding the airplane’s critical angle of attack, which resulted in a low altitude aerodynamic stall from which she was unable to recover.NTSB ANC22LA025Accident · 2 fatalClass 3 · LimitedFinal reportCessna 172P · Kekaha, HIThe pilot’s improper decision to continue the visual-flight-rules flight into low visibility conditions, which resulted in controlled flight into terrain.NTSB ANC21FA065Accident · 2 fatalClass 3 · FieldFinal reportCessna 172P · Eagle River, AKAn inflight collision with terrain under unknown circumstances. Contributing to the delayed rescue response was the failure of the emergency locator transmitter (ELT) to activate as designed, and the mechanic’s failure to ensure the correct ELT was installed…NTSB ERA16FA329Accident · 1 fatalField investigationFinal reportCessna 172 · Laytonsville, MDThe pilot/mechanic's failure to maintain airspeed following a loss of engine power, which resulted in the airplane exceeding its critical angle of attack and experiencing an aerodynamic stall. Also causal was the pilot/mechanic's failure to service the engine…NTSB ANC16FA019Accident · 4 fatalField investigationFinal reportCessna 172 · Chugiak, AKThe in-flight collision with one or more large birds (Bald Eagle), which resulted in a loss of airplane control.NTSB ERA15FA351Accident · 1 fatalField investigationFinal reportCessna 172 · Riegelwood, NCThe noncertificated pilot’s failure to maintain adequate clearance from terrain for reasons that could not be determined based on the available evidence.NTSB WPR15FA247Accident · 2 fatalField investigationFinal reportCessna 172P · Townsend, MTThe non-instrument-rated pilot's decision to conduct a cross-country flight over a mountain range in dark night conditions with limited night flight experience, which resulted in a collision with mountainous terrain.NTSB CEN15FA289Accident · 1 fatalField investigationFinal reportCessna 172P · Bartlett, ILThe pilot’s loss of airplane control for reasons that could not be determined because an examination of the airplane did not reveal any preimpact abnormalities.NTSB ERA12FA483Accident · 1 fatalField investigationFinal reportCessna 172P · Plainville, CTThe pilot's failure to maintain the proper glidepath during final approach in visual meteorological conditions, resulting in collision with a berm.NTSB ERA10FA346Accident · 1 fatalField investigationFinal reportCessna 172P · Chesapeake, VAThe airplane's impact with terrain for undetermined reasons following the pilot's report of a flight control malfunction.NTSB ERA10FA029Accident · 1 fatalField investigationFinal reportCessna 172P · Bennington, VTThe pilot’s failure to maintain clearance from terrain during a night approach. Contributing to the accident was the pilot’s non-standard traffic pattern over higher terrain.NTSB MIA06FA007Accident · 1 fatalField investigationFinal reportCessna 172P · La Belle, FLThe student pilot's failure to maintain airspeed during the initial takeoff climb, resulting in an inadvertent stall/spin and uncontrolled descent to ground impact. A contributing factor was the failure of the wing flap control, which resulted in the flaps…NTSB CHI05FA194Accident · 1 fatalField investigationFinal reportCessna 172P · Jackson, WIThe pilot not maintaining aircraft control for undetermined reasons while maneuvering.NTSB SEA05FA013Accident · 1 fatalField investigationFinal reportCessna 172P · Olympia, WAThe pilot's failure to maintain clearance from terrain while maneuvering in known adverse weather conditions. Clouds, rain, high wind, dark night, trees, mountainous terrain and the pilot's inadequate in-flight planning/decision were factors.NTSB DEN04FA119Accident · 2 fatalField investigationFinal reportCessna 172P · Monarch Crest, COthe pilot's failure to maintain airspeed which resulted in a stall, and his decision to conduct flight beyond the performance capability of the aircraft. A contributing factor was the high density altitude, and an inadvertent stall.NTSB CHI03FA151Accident · 2 fatalField investigationFinal reportCessna 172P · Sheboygan, WIThe pilot failed to maintain control of the airplane after encountering instrument meteorological conditions during takeoff. Factors associated with the accident were the low ceiling, fog and lack of instrument rating.NTSB LAX03FA124Accident · 2 fatalField investigationFinal reportCessna 172P · North Las Vegas, NVthe applicant pilot's failure to maintain an adequate airspeed while maneuvering, which resulted in an inadvertent stall/spin.NTSB MIA03FA066Accident · 1 fatalField investigationFinal reportCessna 172P · Osteen, FLThe intentional suicidal act by the pilot-in-command resulting in the in-flight collision with trees then the ground.NTSB DEN03MA035Accident · 5 fatalMajor investigationFinal reportPiper PA-31T · Denver, COBoth pilots' inadequate visual lookout. A contributing factor was the Cheyenne pilot operating the airplane with a known transponder deficiency.NTSB MIA03FA043Accident · 4 fatalField investigationFinal reportCessna 172P · Edgewater, FLThe pilot's inflight loss of control and the pilot's failure to recover from the resultant dive for unknown reasons which resulted in flight beyond the design stress limits of the airplane and subsequent in flight airframe breakup.NTSB SEA03FA013Accident · 2 fatalField investigationFinal reportCessna 172P · Malaga, WAThe pilot's attempted VFR flight into IMC resulting in the aircraft colliding with trees and up sloping terrain. Contributing factors were clouds, trees, and uphill terrain. The pilot’s performance and judgment were likely impaired by the effects of…NTSB IAD02FA037Accident · 4 fatalField investigationFinal reportCessna 172P · Ocean City, MDThe pilot's spatial disorientation, which resulted in his subsequent loss of control of the airplane. A factor was the dark night, over water visual conditions.NTSB FTW01FA058Accident · 2 fatalField investigationFinal reportCessna 152 · Platter, OKthe failure of both pilots to maintain a visual lookout, which resulted in a mid-air collision over a lake. A contributing factor to the accident was the sun glare from the setting sun.NTSB LAX00FA178Accident · 4 fatalField investigationFinal reportCessna 172P · Chester, CAThe pilot's encounter with a wind shear at low altitude, which resulted in a loss of control and a stall/spin. Factors in the accident were the high density altitude and the pilot's lack of experience and training in high density altitude operations. The…NTSB NYC00FA106Accident · 2 fatalField investigationFinal reportCessna 172P · Ballston Spa, NYa loss of control for undetermined reason(s).NTSB CHI00MA066Accident · 3 fatalMajor investigationFinal reportMoravan Z242L · Zion, ILClearance not maintained by the pilot of the other airplane. A factor relating to the accident was the airport control tower's local controller's failure to provide effective sequencing.NTSB NYC00FA058Accident · 1 fatalField investigationFinal reportCessna 172P · Leominster, MAThe student pilot's failure to see and avoid the private pilot's airplane. Factors included the student pilot's non-standard traffic pattern entry, the private pilot's failure to check for other traffic before turning onto final, and the position of the sun…NTSB DEN99FA142Accident · 1 fatalField investigationFinal reportCessna 172P · Grants, NMThe pilot's failure to fly the aircraft at an altitude sufficient to clear surrounding terrain. Factors were: The pilot's in-flight planning and decision making in proceeding into known adverse weather. Low ceiling, rain, lack of total pilot experience, and…NTSB FTW99FA153Accident · 2 fatalField investigationFinal reportMooney M20B · Mesquite, TXThe failure by both pilots to maintain visual lookout. A factor was the inadequate radio communications maintained by both pilots while in the traffic pattern.NTSB LAX99FA036Accident · 2 fatalField investigationFinal reportCessna 172P · Scottsdale, AZthe failure of the solo student pilot in the other aircraft to acquire and maintain separation from this aircraft, which was departing the airport traffic pattern and had been issued as traffic by the local controller. Also causal was the failure of the pilot…NTSB IAD98FA032Accident · 2 fatalField investigationFinal reportCessna 172P · Langley Afb, VAThe pilot's inadvertent VFR flight into IMC conditions, and the subsequent loss of aircraft control due to spatial disorientation. A factor in the accident was the low ceiling.NTSB NYC98FA066Accident · 1 fatalField investigationFinal reportCessna 172P · York, PAThe pilot's failure to maintain airspeed during final approach which resulted in an inadvertent stall/spin.NTSB IAD97FA122Accident · 1 fatalField investigationFinal reportCessna 172P · Airville, PAThe student pilot's failure to maintain adequate airspeed which resulted in a stall/mush and subsequent collision with terrain.NTSB CHI97FA218Accident · 7 fatalField investigationFinal reportCessna 172P · Chicago, ILthe pilots not maintaining visual separation between their airplanes. A factor in this accident was the pilot of the southbound airplane not reporting her position abeam the airport as directed by the ATC controller.NTSB SEA97FA076Accident · 1 fatalField investigationFinal reportCessna 172P · Burlington, WYloss of engine power for undetermined reason(s). The lack of suitable terrain for a forced landing was a related factor.NTSB MIA97FA013Accident · 3 fatalField investigationFinal reportCessna 172P · St. Croixthe pilot's failure to maintain airspeed.NTSB IAD96FA132Accident · 3 fatalField investigationFinal reportCessna 172P · Summersville, WVThe pilot's improper flare, his delay in aborting a landing, and his failure to maintain adequate airspeed, which resulted in a bounced landing and a stall during climb out in an attempt to avoid collision with trees.NTSB MIA96WA058Accident · 5 fatalForeign investigationCessna 172 · Nassau, BahamasNTSB FTW96FA058Accident · 3 fatalField investigationFinal reportCessna 172P · Hallett, OKThe flight instructor's intentional low altitude flight maneuver. Factors were the static wire and the bright night condition.NTSB NYC95FA080Accident · 1 fatalField investigationFinal reportCessna 172P · Naples, NYThe pilot's continued VFR flight into instrument meteorological conditions. Factors contributing to the accident were: the night conditions, fog, low ceiling, and hilly terrain.NTSB FTW95FA050Accident · 2 fatalField investigationFinal reportCessna 172P · Deming, NMThe pilot's failure to maintain sufficient altitude and clearance in moutainous terrain. Factors were rising terrain and gusty, high wind conditions.NTSB FTW94FA155Accident · 2 fatalField investigationFinal reportCessna 172P · Arlington, TXThe pilot's loss of aircraft control for an undetermined reason, while maneuvering in the vicinity of the airport.NTSB SEA94FA014Accident · 2 fatalField investigationFinal reportCessna 172P · Kelso, WAThe pilot's failure to follow the published missed approach procedure. Factors in the accident were: the weather and mountainous terrain.NTSB BFO93LA156Accident · 1 fatalLimited investigationFinal reportCessna 172P · Pembroke, VAThe pilot's failure to maintain proper altitude while manuevering in mountainous terrain.NTSB NYC93FA158Accident · 1 fatalField investigationFinal reportCessna 172N · Lincoln Park, NJThe failure of both pilots to maintain adequate visual lookout while in the airport traffic pattern, which resulted in an in-flight collision.NTSB SEA93FA125Accident · 3 fatalField investigationFinal reportCessna 172P · Enumclaw, WAInadvertent VFR flight into IMC. Factors to the accident were: fog and rain.NTSB LAX93FA160Accident · 4 fatalField investigationFinal reportCessna 172P · Livermore, CAThe pilot's decision to attempt VFR flight into instrument meteorological conditions. Factors that contributed to this accident were: the pilot's lack of recent instrument experience, the rain and high wind conditions in the area.NTSB LAX93FA096Accident · 1 fatalField investigationFinal reportCessna 172P · Sun City, CAThe pilot's decision to initiate VFR flight into instrument meteorological conditions. Factors which contributed to the accident were: the pilot's failure to obtain a weather briefing, the adverse weather, and the mountainous terrain.