NTSB investigations: Cessna 172P

128 cases on aircraft the registry lists as Cessna 172P, where the first occurrence was “Loss of control - on ground/water”. 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

19822026
NTSB investigations: Cessna 172P per year, 1982–2026: 128 cases
19821
19835
19847
19858
19863
19876
198810
19894
19905
19919
19924
19934
19943
19954
19962
19977
19986
19995
20008
20014
20023
20034
20046
20054
20061
20075

Latest 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072436')
      AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 260))
  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.

NTSB MIA08CA045Accident · No injuriesData collectionFinal reportCessna 172P · Northampton, MAThe student pilot's failure to maintain directional control of the airplane during the takeoff roll and inadequate supervision by the CFI.Dec 26, 2007 · N5425K · Substantial damageNTSB ATL07CA109Accident · No injuriesData collectionFinal reportCessna 172P · Newport, RIThe pilot's failure to maintain directional control during the landing roll.Jul 26, 2007 · N51250 · Substantial damageNTSB ATL07CA099Accident · No injuriesData collectionFinal reportCessna 172P · Perry, GAThe student pilot's failure to maintain directional control on landing roll out resulting in the airplane departing the runway and collision with a ditch.Jun 29, 2007 · N54730 · Substantial damageNTSB DFW07CA115Accident · No injuriesData collectionFinal reportCessna 172P · Harrah, OKThe pilot's failure to compensate for the existing wind conditons while landing. A factor was the crosswind.May 16, 2007 · N62960 · Substantial damageNTSB CHI07CA128Accident · No injuriesData collectionFinal reportCessna 172P · West Chicago, ILThe instructor's inadequate remedial action following the student pilot's loss of control during the crosswind landing and the instructor's failure to compensate for the wind conditions. Contributing factors were, the crosswind, the gusting wind conditions…May 1, 2007 · N97224 · Substantial damageNTSB NYC06CA088Accident · No injuriesData collectionFinal reportCessna 172-P · Cambridge, MDThe student pilot's improper recovery from a bounced landing.Apr 6, 2006 · N54928 · Substantial damageNTSB NYC05CA143Accident · No injuriesData collectionFinal reportCessna 172P · Caldwell, NJThe student pilot's failure to maintain directional control while landing. A factor in this accident was the crosswind condition.Sep 19, 2005 · N64763 · Substantial damageNTSB ATL05CA132Accident · No injuriesData collectionFinal reportCessna 172P · Savannah, GAThe pilot's failure to maintain directional control on landing roll out resulting in a ground loop, and on ground collision of the right wing with the ground.Jul 18, 2005 · N5299K · Substantial damageNTSB ATL05CA125Accident · No injuriesData collectionFinal reportCessna 172P · Monroeville, ALThe student pilot's failure to maintain directional control and the subsequent collision with the ground during landing.Jul 7, 2005 · N98530 · Substantial damageNTSB IAD05CA037Accident · No injuriesData collectionFinal reportCessna 172P · Cross Keys, NJThe pilots failure to maintain directional control. Factors contributing to the accident were the pilots lack of experience, and the snow bank.Feb 7, 2005 · N54812 · Substantial damageNTSB DFW05CA046Accident · No injuriesData collectionFinal reportCessna 172P · Houston, TXThe pilot's failure to maintain directional control during the landing roll. A contributing factor was the muddy condition of the terrain.Dec 29, 2004 · N118FR · Substantial damageNTSB DEN05LA031Accident · No injuriesLimited investigationFinal reportCessna 172P · Englewood, COThe student pilot's failure to maintain directional control during landing.Dec 4, 2004 · N55250 · Substantial damageNTSB DEN05LA037Accident · No injuriesLimited investigationFinal reportCessna 172P · Loveland, COthe student pilot's failure to maintain directional control during landing and the student pilot's inadequate in-flight planning and decision making. Contributing factors include the quartering tail wind, the high airspeed, and the airport sign.Nov 16, 2004 · N54165 · Substantial damageNTSB ATL04CA133Accident · No injuriesData collectionFinal reportCessna 172 · Kennesaw, GAThe student pilot's failure to maintain directional control during landing roll that resulted in the on ground collision with the ground, and the subsequent collapse of the nose gear.Jun 19, 2004 · N52846 · Substantial damageNTSB ATL04CA131Accident · No injuriesData collectionFinal reportCessna 172 · Meridianville, ALThe pilot's failure to maintain directional control during an attempted takeoff, which resulted in the on ground collision with the ground.Jun 13, 2004 · N98981 · Substantial damageNTSB CHI04CA114Accident · No injuriesData collectionFinal reportCessna 172P · Schaumburg, ILThe student pilot not maintaining directional control during the takeoff roll and his inadequate remedial action.May 5, 2004 · N65752 · Substantial damageNTSB NYC03CA167Accident · No injuriesData collectionFinal reportCessna 172P · Plainfield, CTThe pilot's failure to maintain directional control, which resulted in a collision with a ditch. A factor in this accident was the crosswind condition.Jul 25, 2003 · N62152 · Substantial damageNTSB SEA03LA103Accident · No injuriesLimited investigationFinal reportCessna 172P · Seattle, WAThe dual student's failure to maintain aircraft control and the flight instructor's delayed remedial action. Contributing factors were the crosswind condition and the flight instructor's lack of experience.Jun 15, 2003 · N9566L · Substantial damageNTSB LAX03LA117Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Van Nuys, CAthe pilot's failure to maintain directional control during an aborted landing. A contributing factor is the pilot's improper recovery from a bounced landing.Mar 23, 2003 · N63788 · Substantial damageNTSB NYC03LA065Accident · No injuriesLimited investigationFinal reportCessna 172P · Linden, NJThe pilot's inadequate compensation for the crosswind and his failure to maintain directional control during landing. Factors in the accident were the crosswind and the snowbank.Mar 10, 2003 · N30EF · Substantial damageNTSB ATL02LA073Accident · No injuriesLimited investigationFinal reportCessna 172P · Pensacola, FLThe pilot's inadequate compensation for a crosswind and his failure to maintain directional control during the landing roll. Contributing to the accident was the pilot's decision to land with a tailwind.Apr 4, 2002 · N64079 · Substantial damageNTSB IAD02LA038Accident · No injuriesLimited investigationFinal reportCessna 172P · Ocean City, NJThe pilot's inadequate compensation for wind and his failure to maintain directional control.Mar 24, 2002 · N9847L · Substantial damageNTSB CHI02LA078Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Dowagiac, MIThe pilot's inadequate compensation for the wind conditions that resulted in directional control not being maintained during the landing roll. Factors to the accident were the pilot's inadequate in-flight decision to attempt the landing with a gusting 20 knot…Feb 18, 2002 · N66986 · Substantial damageNTSB LAX01LA150Accident · No injuriesLimited investigationFinal reportCessna 172P · Torrance, CAThe failure of the pilot-in-command to execute a proper landing flare, which resulted in an improper touchdown attitude and a subsequent loss of directional control. A factor in the accident was the difference between landing characteristics of the Katana and…Apr 19, 2001 · N97984 · Substantial damageNTSB DEN01LA081Accident · No injuriesLimited investigationFinal reportCessna 172P · Rangely, COthe pilot's improper use of aileron and his failure to maintain directional control during landing. A contributing factor was the direct gusty crosswind.Mar 31, 2001 · N54663 · Substantial damageNTSB CHI01LA072Accident · No injuriesLimited investigationFinal reportCessna 172P · Prairie Du Sac, WIthe improper trim setting and the pilot failed to maintain control of the airplane. A factor was the snowbank.Jan 21, 2001 · N53118 · Substantial damageNTSB IAD01LA024Accident · No injuriesLimited investigationFinal reportCessna 172P · Concord, NHThe flight instructor's improper decision to land downwind on the snow and ice covered runway with a tailwind, and his failure to perform a go-around. Factors in the accident were the tailwind and the snow and ice on the runway.Jan 7, 2001 · N54931 · Substantial damageNTSB DEN01LA024Accident · No injuriesLimited investigationFinal reportCessna 172P · Leadville, COthe student pilot's failure to maintain directional control during landing roll. A contributing factor was the snow bank next to the runway.Dec 14, 2000 · N127FR · Substantial damageNTSB MIA01LA024Accident · No injuriesLimited investigationFinal reportCessna 172P · Inverness, FLa loss of directional control on landing due to the pilot's failure to execute a proper flare and recovery from the resultant bounced landing, causing the airplane to depart the runway, enter the uneven grass infield, and sustain a nose over.Nov 4, 2000 · N54729 · Substantial damageNTSB CHI00LA309Accident · No injuriesLimited investigationFinal reportCessna 172P · Wheeling, ILThe student pilot's inadequate compensation for the crosswind that resulted in the failure to maintain directional control of the airplane. Factors associated with the accident were the crosswind, the ditch, the student's lack of experience, and the poor…Sep 26, 2000 · N98629 · Substantial damageNTSB NYC00LA256Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Cross Keys, NJThe operator's inadequate 100-hour inspection of the airplane, and the pilot's continued operation with known deficiencies in equipment.Sep 8, 2000 · N9594L · Substantial damageNTSB FTW00LA240Accident · No injuriesLimited investigationFinal reportCessna 172P · San Antonio, TXThe pilot's failure to maintain control during landing. A factor was the reported wind gust.Aug 21, 2000 · N98873 · Substantial damageNTSB IAD00LA068Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Princeton, NJthe student pilot's failure to maintain control of the airplane during the aborted landing.Jul 29, 2000 · N65827 · Substantial damageNTSB MIA00LA223Accident · No injuriesLimited investigationFinal reportCessna 172P · Jesup, GAThe failure of the student pilot to maintain directional control during takeoff resulting in an excursion off the runway and collision with adjacent foliage. A factor in the accident was the student's decision to takeoff downwind.Jul 18, 2000 · N51996 · Substantial damageNTSB DEN00LA070Accident · No injuriesLimited investigationFinal reportCessna 172P · Fort Collins, COOn ground loss of control resulting in collision with airport markings due to inadequate compensation for wind conditions during landing roll. Factors were inaccurate in flight planning by landing with a tail wind component and lack of total pilot experience.Apr 8, 2000 · N65312 · Substantial damageNTSB NYC99LA196Accident · No injuriesLimited investigationFinal reportCessna 172P · Montgomery, NYthe failure of the student pilot to maintain directional control during the touchdown and landing roll.Aug 11, 1999 · N65742 · Substantial damageNTSB CHI99LA168Accident · No injuriesLimited investigationFinal reportCessna 172P · Wichita, KSthe student pilot's improper recovery from a bounced landing.May 18, 1999 · N172YA · Substantial damageNTSB CHI99LA104Accident · No injuriesLimited investigationFinal reportCessna 172P · Plainfield, ILthe pilot's inadequate directional control during landing roll. A factor was the snow bank.Mar 7, 1999 · N65192 · Substantial damageNTSB 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.Feb 21, 1999 · N65770 · Substantial damageNTSB 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.Jan 5, 1999 · N53637 · Substantial damageNTSB 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.Sep 26, 1998 · N54013 · Substantial damageNTSB 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.Aug 7, 1998 · N116FR · Substantial damageNTSB 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.Jul 19, 1998 · N53630 · Substantial damageNTSB 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.Jun 21, 1998 · N99548 · Substantial damageNTSB 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.May 3, 1998 · N54743 · Substantial damageNTSB NYC98LA082Accident · No injuriesLimited investigationFinal reportCessna 172P · Plainville, CTThe pilot's inadequate crosswind compensation.Mar 29, 1998 · N9821L · Substantial damageNTSB 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.Dec 24, 1997 · N9566L · Substantial damageNTSB NYC98LA040Accident · No injuriesLimited investigationFinal reportCessna 172P · Mitchellville, MDThe pilot's improper recovery from a bounced landing.Dec 8, 1997 · N99510 · Substantial damageNTSB FTW98LA041Accident · No injuriesLimited investigationFinal reportCessna 172P · Tooele, UTfailure of the pilot to maintain directional control of the airplane, while landing. Factors related to the accident were: the pilot's improper flare for landing, his delay in attempting to go around (abort the landing), and the encounter with a runway marker…Nov 1, 1997 · N96575 · Substantial damageNTSB CHI97LA303Accident · No injuriesLimited investigationFinal reportCessna 172P · Yankton, SDThe pilot's failure to maintain control of the aircraft. A factor contributing to the accident was the wind gusts.Sep 28, 1997 · N52419 · Substantial damage