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 NYC00FA106Accident · 2 fatalField investigationFinal reportCessna 172P · Ballston Spa, NYa loss of control for undetermined reason(s).NTSB MIA00LA124Accident · No injuriesLimited investigationFinal reportCessna 172P · St. Petersburg, FLThe failure of the pilot to maintain clearance between the left wingtip and a hangar door resulting in the on-ground collision.NTSB CHI00MA066Accident · 3 fatalMajor investigationFinal reportCessna 172P · 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 DEN00LA041Accident · No injuriesLimited investigationFinal reportCessna 172P · Huntsville, UTThe snow shower, and the lack of suitable terrain for the precautionary landing.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 CHI00LA032Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Greenfield, INThe student pilot not maintaining aircraft control. A contributing factor was the student's aural perception.NTSB LAX00LA031Accident · No injuriesLimited investigationFinal reportCessna 172N · Chandler, AZThe pilot's misjudged landing flare and failure to maintain an adequate airspeed margin, which resulted in a stall/mush and hard landing.NTSB CHI00LA017Accident · No injuriesLimited investigationFinal reportCessna 172 · Waukon, IAthe pilot failed to maintain directional control of the airplane during the aborted landing. Factors relating to the accident included the crosswinds, the fence, and the trees.NTSB SEA00IA007Incident · No injuriesIncident investigationFinal reportCessna 172P · Wenatchee, WAThe failure of the pilots in both aircraft to maintain an adequate visual lookout. Haze was a factor.NTSB IAD99LA068Accident · No injuriesLimited investigationFinal reportCessna 172P · Friendly, MDThe pilot's misjudgment of speed during the landing approach. The inoperative airspeed indicator was a contributing factor.NTSB DEN99LA159Accident · No injuriesLimited investigationFinal reportCessna 172P · Englewood, COThe pilot's failure to maintain adequate airspeed during the flare for landing/touchdown phase of flight. A factor was a ditch off the side of the runway.NTSB NYC99LA196Accident · No injuriesLimited investigationFinal reportCessna 172P · Montgomery, NYthe failure of the student pilot to maintain directional control during the touchdown and landing roll.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 SEA99LA101Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Auburn, WATotal mechanical failure of the hydraulic tappet. A factor was an overdue major overhaul per manufacturer's recommendations.NTSB IAD99FA051Accident · No injuriesField investigationFinal reportCessna 172P · Gaithersburg, MDwas the pilot's failure to obtain the proper rotation speed and his subsequent loss of directional control. A factor in the accident was the improper setting of the elevator trim.NTSB SEA99LA084Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Easton, WAThe flight instructor's delayed remedial action. Factors include the student allowing the aircraft to climb too steeply at too low an airspeed, and the soft/rough terrain on which the aborted takeoff took place.NTSB MIA99LA182Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Seymour, TNThe failure of the pilot to perform a go-around earlier resulting in a long landing, insufficient runway remaining to stop, and subsequent in flight collision with a marked power line during an aborted landing.NTSB NYC99LA137Accident · No injuriesLimited investigationFinal reportCessna 172 · Ravenna, OHThe pilot-in-command's failure to maintain aircraft control during landing.NTSB LAX99LA204Accident · No injuriesLimited investigationFinal reportCessna 172P · Mesa, AZThe failure of the tower (local) air traffic controller to issue a landing sequence to the climbing, high wing Cessna 172 aircraft, and, the controller's failure to maintain visual separation between the two aircraft on downwind leg.NTSB FTW99FA153Accident · 2 fatalField investigationFinal reportCessna 172P · 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 CHI99LA168Accident · No injuriesLimited investigationFinal reportCessna 172P · Wichita, KSthe student pilot's improper recovery from a bounced landing.NTSB DEN99LA063Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Dulce, NMThe pilot-in-command becoming disoriented during cruise flight, and his intentional flight into instrument meteorological conditions without proper certification. Factors were the existing weather conditions that included snow, fog, obscuration and icing, the…NTSB NYC99LA086Accident · No injuriesLimited investigationFinal reportCessna 172P · Lawrence, MAThe student pilot's improper flare, and his improper recover from a bounced landing.NTSB CHI99LA104Accident · No injuriesLimited investigationFinal reportCessna 172P · Plainfield, ILthe pilot's inadequate directional control during landing roll. A factor was the snow bank.NTSB LAX99LA109Accident · No injuriesLimited investigationFinal reportCessna 172P · Death Valley, CAThe pilot's use of an excessive approach reference speed and his misjudged distance/speed relationship to the runway, which resulted in a landing overrun. The pilot's failure to execute a timely go-around was also causal.NTSB MIA99LA090Accident · No injuriesLimited investigationFinal reportCessna 172P · Pelion, SCThe pilot's loss of directional control during landing roll as a result of improper recovery from a bounced landing and the subsequent excursion from the runway, collision with the adjacent terrain, and collapse of the nose landing gear.NTSB MIA99LA080Accident · No injuriesLimited investigationFinal reportCessna 172P · Cleveland, MSThe pilot's improper recovery from a bounced landing, resulting in a blown nose tire, loss of directional control, and subsequent collision with terrain.NTSB CHI99LA058Accident · No injuriesLimited investigationFinal reportCessna 172P · Lambertville, MIthe pilot-in-command's loss of directional control during landing roll. Factors to the accident were the icy terrain condition, crosswind, and the snow bank.NTSB CHI99LA040Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Brainerd, MNThe visual lookout not obtained/maintained by the pilot of the other aircraft. Contributing factors were the unicom frequency not selected and the traffic advisory not issued by the pilot of the other aircraft. An additional factor was the aircraft moving on…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 ATL98LA132Accident · No injuriesLimited investigationFinal reportCessna 172P · Farmville, NCThe pilot's failure to maintain directional control of the aircraft and his improper use of the brakes, which led to the aircraft departing the left side of the runway. Contributing factors were the wet runway and the vehicle.NTSB NYC98LA163Accident · Minor injuriesLimited investigationFinal reportCessna 172P · West Milford, NJThe student pilot's improper recovery from a bounced landing and the instructor's inadequate supervision of the flight.NTSB SEA98LA144Accident · No injuriesLimited investigationFinal reportCessna 172P · Seattle, WAThe student pilot's failure to maintain directional control of the aircraft. Related factors were the student pilot's lack of total experience, and airport signs in the accident area.NTSB CHI98LA215Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Grays Lake, ILthe pilot's not performing a recovery from a bounced landing and his not maintaining directional control. A factor was soft terrain.NTSB CHI98LA254Accident · No injuriesLimited investigationFinal reportCessna 172P · Abilene, KSThe student pilot's failure to plan his approach so as to be able to stop the airplane on the runway, and the instructor pilot's delay in taking control of the airplane, so as to correct the student's mistake. A factor contributing to this accident was the…NTSB FTW98LA220Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Monument Valley, UTThe pilot's failure to maintain directional control of the aircraft during landing. Factors were gusty, crosswind conditions, the pilot's lack of experience in type of operation and geographic area, mountainous terrain, and high density altitude.NTSB MIA98LA164Accident · No injuriesLimited investigationFinal reportCessna 172P · Fort Myers, FLThe pilot's inadequate inflight decision and her selection of unsuitable terrain to conduct a precautionary landing.NTSB FTW98LA212Accident · No injuriesLimited investigationFinal reportCessna 172P · Georgetown, TXinadequate supervision by the flight instructor (CFI), by failing to ensure that the student obtained and/or maintained sufficient airspeed, which led to an inadvertent stall and collision with the terrain.NTSB ATL98LA072Accident · No injuriesLimited investigationFinal reportCessna 172P · Key West, FLfailure of the student pilot to maintain directional control of the airplane during the landing roll. The student pilot's lack of experience in the make and model of airplane was a related factor.NTSB FTW98LA240Accident · No injuriesLimited investigationFinal reportCessna 172P · La Porte, TXThe pilot's premature landing flare and improper recovery procedures from a bounced landing. A factor was the gusty winds.NTSB FTW98LA188Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Longmont, COThe pilot inadvertently stalling the aircraft during the landing touchdown. Factors were a crosswind and the pilot's lack of total flight experience.NTSB NYC98LA082Accident · No injuriesLimited investigationFinal reportCessna 172P · Plainville, CTThe pilot's inadequate crosswind compensation.NTSB ATL98TA054Accident · No injuriesFinal reportCessna 172 · Arcadia, FLThe pilot's inadequate pre-flight and in-flight planning, which resulted in fuel exhaustion and the loss of power. Trees and rough/uneven terrain are contributing factors.NTSB MIA98LA095Accident · No injuriesLimited investigationFinal reportCessna 172P · Destin, FLthe pilot's improper flare and improper recovery from a bounced landing, which resulted in a hard landing.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 IAD98LA019Accident · No injuriesLimited investigationFinal reportCessna 172P · Augusta, METhe inadequate lookout of the pilot in command.NTSB SEA98LA026Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Kenmore, WAthe pilot's inadequately planned approach and failure to maintain directional control. The pilot's lack of total experience in kind of aircraft and haze were factors.NTSB NYC98LA040Accident · No injuriesLimited investigationFinal reportCessna 172P · Mitchellville, MDThe pilot's improper recovery from a bounced landing.NTSB LAX98LA030Accident · No injuriesLimited investigationFinal reportCessna 172P · San Diego, CAThe student pilot's failure to maintain adequate clearance from a hangar while taxiing.
Back to Cessna 172P