NTSB investigations: Cessna 172N

192 cases on aircraft the registry lists as Cessna 172N, 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 172N per year, 1982–2026: 192 cases
198221
198310
198416
19854
19866
19878
19888
19897
19906
19916
19926
19937
19947
19957
19968
19979
19983
19997
20004
20015
200213
20036
20044
20057
20064
20073

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 ('2072434')
      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 SEA08CA030Accident · Minor injuriesData collectionFinal reportCessna 172N · Atwater, CAThe failure of the student pilot to maintain directional control during the landing roll. Factors contributing to the accident included the sign and the ditch.Nov 17, 2007 · N3318E · Substantial damageNTSB DEN08CA002Accident · Minor injuriesData collectionFinal reportCessna 172N · Calhan, COThe student pilot's failure to maintain directional control during the takeoff roll.Oct 4, 2007 · N2263E · Substantial damageNTSB CHI07CA076Accident · No injuriesData collectionFinal reportCessna 172N · Holland, MIThe student pilot's inadequate compensation for the crosswind condition and his failure to maintain directional control during the takeoff, which caused the airplane to impact the snow bank and nose over. Contributing factors were the crosswind and the snow…Feb 23, 2007 · N5321D · Substantial damageNTSB ATL07CA022Accident · No injuriesData collectionFinal reportCessna 172N · Reidsville, NCThe pilot's failure to maintain directional control of the airplane during landing roll, which resulted in an on ground collision with trees.Nov 25, 2006 · N172LF · Substantial damageNTSB DFW07CA028Accident · No injuriesData collectionFinal reportCessna 172N · Spring, TXLoss of directional control for undetermined reasons.Nov 22, 2006 · N81HT · Substantial damageNTSB CHI06CA151Accident · No injuriesData collectionFinal reportCessna 172N · Athens, OHThe student pilot's inadequate compensation for the wind conditions. Factors associated with the accident were the gusty crosswind, and the ditch.Jun 9, 2006 · N240U · Substantial damageNTSB CHI06CA083Accident · No injuriesData collectionFinal reportCessna 172N · New Hudson, MIThe solo student pilot's failure to properly compensate for the crosswind, resulting in his failure to maintain directional control during landing. Factors were the crosswind and the snow bank.Feb 12, 2006 · N222UN · Substantial damageNTSB DFW06CA026Accident · No injuriesData collectionFinal reportCessna 172N · Sherman, TXThe pilot's failure to maintain directional control during takeoff.Nov 6, 2005 · N2884E · Substantial damageNTSB LAX05CA276Accident · No injuriesData collectionFinal reportCessna 172N · Ramona, CAthe pilot's failure to maintain directional control during landing.Aug 22, 2005 · N734MY · Substantial damageNTSB LAX05CA240Accident · No injuriesData collectionFinal reportCessna 172N · North Las Vegas, NVthe student pilot's failure to maintain directional control.Jul 20, 2005 · N4961D · Substantial damageNTSB LAX05CA191Accident · No injuriesData collectionFinal reportCessna 172N · Stockton, CAthe pilot's improper use of the brakes, and his failure to maintain directional control during the landing rollout.May 30, 2005 · N172MR · Substantial damageNTSB LAX05CA148Accident · No injuriesData collectionFinal reportCessna 172N · Palo Alto, CAThe student's failure to maintain directional control and the CFI's failure to adequately supervise the flight.Apr 27, 2005 · N737WF · Substantial damageNTSB CHI05LA070Accident · No injuriesLimited investigationFinal reportCessna 172N · Grafton, NDThe pilot's inadequate compensation for the wind conditions which resulted in a loss of directional control during the landing. Factors associated with the accident were the crosswind condition and the snow bank.Feb 10, 2005 · N2291E · Substantial damageNTSB SEA05CA043Accident · No injuriesData collectionFinal reportCessna 172N · Idaho Falls, IDThe student pilot's failure to maintain directional control and the instructor's inadequate supervision of the flight. A contributing factor was the deep snow beside the runway.Feb 3, 2005 · N5204K · Substantial damageNTSB FTW04LA215Accident · No injuriesLimited investigationFinal reportCessna 172N · New Braunfels, TXThe student pilot's failure to maintain directional control of the airplane. A contributing factor was the high wind condition.Aug 18, 2004 · N739AM · Substantial damageNTSB DEN04LA114Accident · No injuriesLimited investigationFinal reportCessna 172N · Hurricane, UTthe student pilot's failure to maintain aircraft control during the landing. Contributing factors include the crosswind, the wind gusts, and the exceeded maximum demonstrated crosswind component.Jul 31, 2004 · N5426J · Substantial damageNTSB IAD04LA034Accident · No injuriesLimited investigationFinal reportCessna 172N · Wellsboro, PAThe pilot's inadequate compensation for wind conditions and his failure to maintain directional control. A factor was the crosswind.Jul 4, 2004 · N10DJ · Substantial damageNTSB MIA04CA085Accident · No injuriesData collectionFinal reportCessna 172N · Pembroke Pines, FLThe pilot's failure to establish a climb and his failure to maintain directional control of the airplane during an aborted landing leading to the airplane departing the runway and incurring substantial damage.May 17, 2004 · N737FE · Substantial damageNTSB LAX04CA082Accident · No injuriesData collectionFinal reportCessna 172N · Angels Camp, CAthe CFI's inadequate compensation for a crosswind condition, which resulted in the loss of directional control. The crosswind and wind gusts were factors.Dec 29, 2003 · N461BD · Substantial damageNTSB LAX04LA056Accident · No injuriesLimited investigationFinal reportCessna 172N · Nogales, AZThe student pilot's improper recovery from a bounced landing and his failure to maintain directional control.Dec 4, 2003 · N5216J · Substantial damageNTSB CHI03LA290Accident · No injuriesLimited investigationFinal reportCessna 172N · Romeo, MIThe pilot not maintaining directional control during landing. A factor to the accident was the parked airplane.Jun 27, 2003 · N739NW · Substantial damageNTSB CHI03LA163Accident · No injuriesLimited investigationFinal reportCessna 172N · Anoka, MNThe pilot's failure to attain the proper touchdown point, and his failure to maintain directional control. Contributing factors were the pilot's lack of experience, and the runway sign.Jun 14, 2003 · N2238E · Substantial damageNTSB NYC03LA062Accident · No injuriesLimited investigationFinal reportCessna 172N · Cincinnati, OHThe student pilot's failure to maintain directional control.Feb 26, 2003 · N733XP · Substantial damageNTSB SEA03LA036Accident · No injuriesLimited investigationFinal reportCessna 172N · McMinnville, ORThe pilot's inadequate compensation for wind conditions and his failure to maintain directional control during the landing roll. Factors include gusty crosswinds and soft terrain in the area where the aircraft departed the side of the runway.Feb 8, 2003 · N734KU · Substantial damageNTSB ATL03LA024Accident · No injuriesLimited investigationFinal reportCessna 172N · Cartersville, GAThe student pilot's failure to maintain directional control, during the landing roll resulted in the on ground collision with a ravine.Dec 6, 2002 · N5891E · Substantial damageNTSB LAX03LA039Accident · No injuriesLimited investigationFinal reportCessna 172N · Hollister, CAthe pilot's failure to maintain directional control of the airplane.Nov 28, 2002 · N2423E · Substantial damageNTSB NYC03LA014Accident · No injuriesLimited investigationFinal reportCessna 172N · Morristown, NJThe student pilot's failure to maintain directional control during takeoff.Oct 24, 2002 · N4599D · Substantial damageNTSB IAD02LA096Accident · No injuriesLimited investigationFinal reportCessna 172N · Bumpass, VAThe pilot's failure to maintain directional control during the landing. A factor was the narrow runway width.Sep 21, 2002 · N737TG · Substantial damageNTSB MIA02LA158Accident · No injuriesLimited investigationFinal reportCessna 172N · Tarboro, NCThe failure of the solo student to maintain directional control of the airplane during the takeoff roll/run which resulted in the airplane veering off the runway and impacting trees, incurring substantial damage.Aug 25, 2002 · N2291E · Substantial damageNTSB CHI02CA211Accident · No injuriesData collectionFinal reportCessna 172N · Spearfish, SDThe probable cause of this accident was the pilot's failure to maintain directional control of the airplane during the takeoff roll. Differences in control forces and aircraft handling due to initiating the takeoff without fully retracting the flaps is a…Jul 18, 2002 · N1373E · Substantial damageNTSB NYC02LA121Accident · No injuriesLimited investigationFinal reportCessna 172N · Lynchburg, VAThe pilot's failure to maintain control of the airplane, a factor was the tailwind.Jun 22, 2002 · N5408E · Substantial damageNTSB MIA02LA117Accident · No injuriesLimited investigationFinal reportCessna 172N · Marietta, GAthe pilot's failure to maintain directional control during the takeoff roll, which resulted in the airplane departing the left side of the runway, impacting with a gully and nosing over.Jun 22, 2002 · N739PF · Substantial damageNTSB IAD02LA061Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Rutland, VTThe pilot's failure to maintain directional control during the takeoff attempt.Jun 21, 2002 · N739RS · Substantial damageNTSB CHI02LA103Accident · No injuriesLimited investigationFinal reportCessna 172N · Appleton, WIThe pilots failure to maintain directional control of the airplane during the takeoff roll resulting in the subsequent impact with terrain.Apr 10, 2002 · N733PX · Substantial damageNTSB SEA02LA047Accident · No injuriesLimited investigationFinal reportCessna 172N · Longmont, COThe student pilot's failure to maintain directional control during landing. Factors included the student pilot's lack of experience, an icy runway, and a mound of snow adjacent to the runway.Mar 3, 2002 · N5413J · Substantial damageNTSB DEN02LA025Accident · No injuriesLimited investigationFinal reportCessna 172N · Durango, COthe pilot's failure to maintain directional control during the landing roll. Contributing factors were the crosswind and the pilot's fatigue from lack of sleep.Feb 17, 2002 · N4642J · Substantial damageNTSB CHI02LA076Accident · No injuriesLimited investigationFinal reportCessna 172N · Ottumwa, IAthe student pilot failed to maintain directional control during takeoff. A contributing factor was the snowbank.Feb 5, 2002 · N733FT · Substantial damageNTSB DEN02LA014Accident · No injuriesLimited investigationFinal reportCessna 172N · Broomfield, COthe pilot's failure to maintain directional control of the airplane while landing. A contributing factor was the crosswind.Dec 13, 2001 · N73892 · Substantial damageNTSB CHI02LA004Accident · No injuriesLimited investigationFinal reportCessna 172N · Beaver Island, MIThe pilot not maintaining directional control of the airplane during landing. The gusty crosswind and the berm were factors.Oct 6, 2001 · N73630 · Substantial damageNTSB LAX01LA115Accident · No injuriesLimited investigationFinal reportCessna 172N · Show Low, AZThe pilot's failure to maintain directional control resulting in an encounter with terrain and a nose over.Mar 14, 2001 · N738PP · Substantial damageNTSB LAX01LA102Accident · No injuriesLimited investigationFinal reportCessna 172N · San Diego, CAThe pilot's failure to maintain directional control of the airplane during landing rollout.Feb 15, 2001 · N4922D · Substantial damageNTSB CHI01LA057Accident · No injuriesLimited investigationFinal reportCessna 172N · Lincoln, ILThe pilot's failure to maintain directional control on the runway. Factors relating to this accident were the aborted takeoff attempt, the pilot's improper in-flight planning/decision, and the snowbank.Jan 1, 2001 · N737WQ · Substantial damageNTSB CHI01LA058Accident · No injuriesLimited investigationFinal reportCessna 172N · Elkhart, INThe loss of directional control by the student pilot and the inadequate remedial action and inadequate supervision by the certified flight instructor. Factors were the snow and ice covered runway and the snowbank.Dec 30, 2000 · N6326F · Substantial damageNTSB CHI00LA117Accident · No injuriesLimited investigationFinal reportCessna 172N · Chesterfield, MOthe pilot misjudged the landing flare which resulted in the airplane porpoising on the runway during the landing.Apr 13, 2000 · N5909E · Substantial damageNTSB LAX00LA096Accident · No injuriesLimited investigationFinal reportCessna 172N · Bermuda Dunes, CAFailure of the student pilot to maintain directional control of the airplane during takeoff.Feb 7, 2000 · N739GQ · Substantial damageNTSB CHI00LA065Accident · No injuriesLimited investigationFinal reportCessna 172 · Chesterfield, MOThe pilot failed to maintain directional control during the takeoff portion of a touch and go landing.Feb 5, 2000 · N738EJ · Substantial damageNTSB IAD00LA006Accident · No injuriesLimited investigationFinal reportCessna 172N · Hopedale, MAwas the student pilot's improper flare that resulted in a bounced landing and the flight instructor's delay in taking remedial action.Nov 15, 1999 · N738NL · Substantial damageNTSB MIA99LA247Accident · No injuriesLimited investigationFinal reportCessna 172N · Lakeland, FLThe student pilots improper use of brakes on landing rollout resulting in a loss of directional control and subsequent collision with a ditch. Contributing to the accident was the certified flight instructors improper supervision of the student pilot.Sep 4, 1999 · N172AN · Substantial damageNTSB CHI99LA245Accident · No injuriesLimited investigationFinal reportCessna 172N · Greenville, MIthe student pilot's inadequate use of the rudder which resulted in a loss of directional control during an aborted landing. A factor associated with the accident was the student's lack of total experience and the segmented circle which the airplane contacted.Jul 20, 1999 · N3558E · Substantial damageNTSB CHI99LA224Accident · No injuriesLimited investigationFinal reportCessna 172N · Faribault, MNthe pilot's failure to maintain directional control of the airplane during the takeoff ground run.Jul 11, 1999 · N4886G · Substantial damage