Cessna 172P
NTSB investigations · 844
Matched to the registry by N-number and event date, newest first.
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_aircrafts.parquet' a JOIN 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c ON c.\"mKey\" = a.case_mkey
WHERE a.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_aircrafts.parquet' a JOIN 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c ON c."mKey" = a.case_mkey
WHERE a.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 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 reportCessna 172P · 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.NTSB BFO91LA016Accident · 1 fatalLimited investigationFinal reportCessna 172P · Axton, VAThe pilot's failure to maintain adequate clearance with an obstacle. Contributing was an unmarked powerline and the pilot's lack of familiarity with the geographical area.NTSB MIA91LA027Accident · 2 fatalLimited investigationFinal reportCessna 172P · Atlantic Ocean (Atlantic Ocean)Delay of the pilot to obtain assistance and, as a result, he ditched the airplane near a boat due to a low fuel supply.NTSB CHI91DEP02Accident · Serious injuriesFinal reportCessna 172P · Hayward, WIThe pilot-in-command's intentional flight into known adverse weather.NTSB CHI91FA011Accident · 3 fatalField investigationFinal reportCessna 172P · Fort Wayne, INThe failure of the pilot to maintain an airspeed above stalling speed. Factors associated with the accident are premature rotation and the pilot's lack of recent total experience.NTSB CHI91GA014Accident · 1 fatalFinal reportCessna 172P · Williamsburg, IAThe pilot-in-command's abrupt pull-up to avoid an obstacle. Contributing was the pilot-in-command's diverted attention to activities on the ground.NTSB NYC91FA001Accident · 3 fatalField investigationFinal reportCessna 172P · Gorham, NHImproper planning/decision by the pilot, and his failure to maintain proper altitude while flying over mountainous terrain. Factors related to the accident were: darkness, mountainous terrain, and pilot fatigue.NTSB BFO90LA080Accident · No injuriesLimited investigationFinal reportCessna 172 · Maryville, KYThe failure of a hydraulic brake line which resulted in a loss of fluid, and an inoperative brake system during landing roll.NTSB SEA90FA183Accident · 1 fatalField investigationFinal reportCessna 172-P · Hood River, ORThe pilot in command's encountering spatial disorientation and his failure to maintain airspeed.NTSB LAX90LA314Accident · No injuriesLimited investigationFinal reportCessna 172P · Santa Barbara, CAA disconnect of the throttle control.NTSB SEA90LA173Accident · No injuriesLimited investigationFinal reportCessna 172P · Granite Falls, WAThe pilot in command's use of excessive flaps for takeoff resulting in loss of climb performance.NTSB LAX90FA292Accident · 4 fatalField investigationFinal reportCessna 172P · Long Beach, CAThe inadequate visual outlook of the pilots of the Cessna 172P and their failure to see and avoid the Piper pa- 28RT-201. Contributing to the accident was the azimuth and angle of the sun which was in a position at the time of the accident to impair the scan…NTSB ATL90LA159Accident · No injuriesLimited investigationFinal reportCessna 172 · Ridge Spring, SCThe failure of the maintenance facility/owner to follow standard preventive maintenance procedures. A factor was the pilot's failure to extend the flaps during the forced landing.
Back to Cessna 172P