NTSB investigations: Cessna 172P, 1991
39 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
| 1969 | 1 |
|---|---|
| 1973 | 1 |
| 1980 | 2 |
| 1981 | 9 |
| 1982 | 30 |
| 1983 | 34 |
| 1984 | 36 |
| 1985 | 32 |
| 1986 | 24 |
| 1987 | 42 |
| 1988 | 39 |
| 1989 | 27 |
| 1990 | 28 |
| 1991 | 39 |
| 1992 | 36 |
| 1993 | 26 |
| 1994 | 22 |
| 1995 | 19 |
| 1996 | 24 |
| 1997 | 25 |
| 1998 | 19 |
| 1999 | 24 |
| 2000 | 21 |
| 2001 | 16 |
| 2002 | 16 |
| 2003 | 25 |
| 2004 | 18 |
| 2005 | 17 |
| 2006 | 9 |
| 2007 | 10 |
| 2008 | 13 |
| 2009 | 9 |
| 2010 | 16 |
| 2011 | 14 |
| 2012 | 12 |
| 2013 | 6 |
| 2014 | 6 |
| 2015 | 12 |
| 2016 | 9 |
| 2017 | 7 |
| 2018 | 10 |
| 2019 | 4 |
| 2020 | 5 |
| 2021 | 7 |
| 2022 | 10 |
| 2023 | 7 |
| 2024 | 9 |
| 2025 | 7 |
| 2026 | 9 |
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 year(c.\"eventDate\") = 1991
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 year(c."eventDate") = 1991
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 SEA92FA026Accident · 7 fatalField investigationFinal reportCessna 172P · Snohomish, WAA visual lookout was not maintained.NTSB ATL92LA028Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Ramseur, NCThe pilot's improper compensation for the wind conditions. The gusty crosswind was a factor in the accident.NTSB CHI92LA033Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Marquette, MIFlight into known adverse weather conditions by the pilot, which resulted in airframe (wing) icing and the inability to maintain altitude. The adverse weather conditions and darkness were related factors.NTSB LAX92LA039Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Williams, AZThe pilot's failure to maintain visual lookout.NTSB CHI92FA020Accident · Serious injuriesField investigationFinal reportCessna 172P · Zion, ILWater contamination of the fuel, and the pilot's inadequate preflight of the aircraft. Factors related to the accident were: darkness and obstructions (trees & transmission lines) in the emergency landing area.NTSB CHI92LA008Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Maple Lake, MNThe loss of engine power for an undetermined reason.NTSB NYC91FA246Accident · 2 fatalField investigationFinal reportCessna 172P · West Chicago, ILThe pilot's improper in-flight decision to return to the airport following a loss of engine power at a low altitude. The pilot failed to maintain airspeed which resulted in an inadvertent stall at an altitude insufficient for recovery. Factors contributing to…NTSB LAX91LA389Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Hesperia, CAA stuck exhaust valve due to the operator's non compliance with a manufacturers recommended service bulletin on the engine. Contributing to the accident was the lack of suitable terrain for a safe landing.NTSB ANC91FA132Accident · 3 fatalField investigationFinal reportCessna 172 · Eklutna Lake, AKThe pilot's failure to maintain terrain clearance. Contributing to the accident was the high terrain.NTSB NYC91LA210Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Sandusky, OHThe pilot initiated an emergency landing when the engine RPM went to zero due to a broken tachometer cable. He did not attain the proper touchdown point and overran the end of the runway.NTSB CHI91LA249Accident · No injuriesLimited investigationFinal reportCessna 172 · Wheeling, ILInadequate compensation for wind conditions and directional control was not maintained by the pilot. Factors related to the accident were a gusty crosswind landing environment and a ditch.NTSB NYC91LA197Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Greenville, MEInadequate compensation for gusting winds by the pilot-in-command.NTSB CHI91LA233Accident · 1 fatalLimited investigationFinal reportCessna 172P · Lansing, ILThe pilot's inadvertent stall/spin during low altitude maneuvers. Related factors are ground personnel's inadequate traffic advisory, and the pilot's abrupt pull up.NTSB ATL91LA139Accident · No injuriesLimited investigationFinal reportCessna 172P · Sylva, NCThe pilot's improper in-flight planning, and his failure to maintain a proper altitude while maneuvering in the canyon. Factor(s) in this accident were: the mountainous, box canyon conditions, the high density altitude, and the downdraft conditions at the…NTSB LAX91LA323Accident · No injuriesLimited investigationFinal reportCessna C-172P · Hesperia, CAA stuck engine throttle due to improper maintenance procedures.NTSB CHI91LA222Accident · No injuriesLimited investigationFinal reportCessna 172 · West Chicago, ILDirectional control was not maintained by the cfi/pic. Factors related to the accident were a gusty cross wind and an airport facility, VASI light.NTSB FTW91LA116Accident · No injuriesLimited investigationFinal reportCessna 172P · Lakeview, AR(1) The pilot's failure to properly flare the airplane for landing and (2) his subsequent improper recovery from a bounced landing.NTSB FTW91LA115Accident · No injuriesLimited investigationFinal reportCessna 172P · El Paso, TXThe power loss due to carburetor icing and the pilot's failure to use carburetor heat. Factors were the icing conditions, lack of suitable terrain for the forced landing, and the gusty tail wind.NTSB DEN91LA094Accident · No injuriesLimited investigationFinal reportCessna 172P · Watkins, COThe pilot's failure to maintain directional control of the aircraft. A factor was the pilot misjudging his flare.NTSB CHI91DTG01Accident · 1 fatalFinal reportCessna 172P · Bismarck, NDSpatial disorientation. Factors related to the accident are failure to obtain a preflight weather brief, vrf flight into IMC conditions and lack of total experience.NTSB SEA91LA112Accident · No injuriesLimited investigationFinal reportCessna 172P · Alva, WYThe pilot's overconfidence in his personal ability, overconfidence in the aircraft's ability. Contributing to the accident was the engine failure.NTSB CHI91LA139Accident · No injuriesLimited investigationFinal reportCessna 172 · Detroit, MIThe proper touchdown point was not attained and the pilot failed to perform a go around. A factor related to the accident was the tailwind condition in which the pilot was attempting to land.NTSB DEN91LA063Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Steamboat Sprin, COThe CFI used poor judgement in giving a simulated engine failure by turning off the fuel selector valve.NTSB NYC91LA113Accident · Minor injuriesLimited investigationFinal reportGrumman American AA-5A · Pleasant Valley, NYThe failure of the pilot of N5232K to maintain visual contact and separation with N9763U.NTSB DEN91LA060Accident · No injuriesLimited investigationFinal reportCessna 172P · Lehi, ARThe pilot's failure to maintain aircraft control. Factors were: the wet runway and resultant hydroplaning.NTSB ATL91LA082Accident · No injuriesLimited investigationFinal reportCessna 172P · Hatteras, NCThe pilot's improper landing flare, subsequent inadvertent porpoise, and his failure to execute a bounced landing recovery.NTSB NYC91LA106Accident · No injuriesLimited investigationFinal reportCessna 172P · Burlington, CTThe failure of the pilot to maintain directional control during the landing. Factors related to the accident were: improper use of the flight controls by the pilot, his lack of recent experience and total time, and the crosswind.NTSB CHI91LA112Accident · No injuriesLimited investigationFinal reportCessna 172 · Wichita, KSDirectional control was not maintained by the dual student and remedial action was delayed by the CFI. Factors related to the accident were a gusty crosswind and a drainage ditch.NTSB SEA91LA065Accident · No injuriesLimited investigationFinal reportCessna 172P · Seattle, WAA hard landing due to the pilot's midjudgement of his touchdown.NTSB NYC91LA085Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Miamisburg, OHThe instructor pilot's failure to maintain control of the airplane during landing in a strong crosswind.NTSB NYC91LA081Accident · No injuriesLimited investigationFinal reportCessna 172P · Nashua, NHThe failure of the pilot to compensate for wind conditions during landing, resulting in a loss of control and collision with a tree.NTSB ANC91LA025Accident · No injuriesLimited investigationFinal reportCessna 172-P · Anchorage, AKThe pilot's failure to maintain directional control of the airplane during the takeoff roll. Contributing to the accident was the terrain (snowbank).NTSB NYC91FA069Accident · 3 fatalField investigationFinal reportCessna 172P · Augusta, METhe pilot rotated the airplane at an improper speed, then allowed the climb angle to become too steep, causing an inadvertent stall at too low an altitude to allow recovery. Contributing factors in the accident were; the pilot failed to use all of the…NTSB LAX91LA083Accident · No injuriesLimited investigationFinal reportCessna 172P · Sedona, AZThe failure of the pilot to maintain directional control of the aircraft.NTSB LAX91LA078Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Sacramento, CAThe flight's inadvertant encounter with wake turbulence.NTSB NYC91LA059Accident · No injuriesLimited investigationFinal reportCessna 172P · Charleston, WVTotal loss of engine power in cruise flight due to failure of the accessory drive gear dowel pin resulting in a forced landing over unsuitable terrain and subsequent nose over on landing roll. A factor related to the accident was the improper procedure used…NTSB CHI91FA059Accident · 1 fatalField investigationFinal reportCessna 172P · Freeport, ILThe pilot-in-command's failure to maintain airspeed. Factors contributing were the pilot-in-command's misuse of flaps and his lack of total experience in this type of operation.NTSB NYC91FA055Accident · 1 fatalField investigationFinal reportCessna 172P · Rattlesnake Isl, OHThe cfi's delayed decision to execute a go-around from a long landing and subsequent failure to obtain/maintain flying speed.NTSB CHI91LA054Accident · No injuriesLimited investigationFinal reportCessna 172P · New Holstein, WIThe pilot's decision to continue the landing approach, landing on an ice covered runway and the inadequate compensation for the croswind.