NTSB investigations: Cessna 172M, 2000

22 cases on aircraft the registry lists as Cessna 172M. 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

19722026
NTSB investigations: Cessna 172M, 2000 per year, 1972–2026: 1,698 cases
19723
197324
197459
197582
1976104
197799
197892
197980
198059
198150
198253
198334
198435
198534
198638
198729
198828
198938
199037
199136
199231
199337
199424
199529
199623
199735
199830
199922
200022
200130
200226
200324
200418
200516
200618
200716
200824
200914
201015
201113
201218
201320
201420
20159
201610
201719
201814
201913
202016
20218
202224
202312
202414
202512
20268

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 year(c.\"eventDate\") = 2000
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072418'))
  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 NYC01LA063Accident · No injuriesLimited investigationFinal reportCessna 172M · Farmville, VAthe failure of the pilot to maintain directional control.Dec 29, 2000 · N73404 · Substantial damageNTSB IAD01LA020Accident · No injuriesLimited investigationFinal reportCessna 172M · Medford, NJThe pilot's failure to attain the proper touchdown point. Factors included the loss of electrical power, the dark night, and the pilot's lack of night experience.Dec 19, 2000 · N789FW · Substantial damageNTSB CHI01LA051Accident · No injuriesLimited investigationFinal reportCessna 172M · Sturgis, SDThe pilot failed to maintain control of the airplane during takeoff and he discontinued an aborted takeoff once initiated. Factors associated with the accident were the inaccurate elevator trim indicator, the pilot's failure to verify the trim setting,…Dec 19, 2000 · N13584 · Substantial damageNTSB NYC01LA055Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Mount Sterling, KYThe student pilot's inadequate recovery from a bounced landing.Dec 9, 2000 · N80854 · Substantial damageNTSB NYC01LA025Accident · No injuriesLimited investigationFinal reportCessna 172M · Camp Springs, MDThe pilot's improper in-flight decision to operate close behind a large airplane at the same altitude, which resulted in a wake turbulence encounter.Oct 19, 2000 · N950ME · Substantial damageNTSB CHI01LA004Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Sparta, WIthe pilot's inaccurate fuel consumption calculations, improper fuel management, inadequate in-flight planning/decision, flight to destination alternate not performed, and the discontinued planned approach to the initially selected runway. Contributing factors…Oct 7, 2000 · N13214 · DestroyedNTSB ANC00LA111Accident · No injuriesLimited investigationFinal reportCessna 172 · Alexander Creek, AKThe pilot's inadequate compensation for wind conditions. Factors associated with the accident were gusty winds, and a downdraft.Aug 22, 2000 · N12188 · Substantial damageNTSB CHI00LA259Accident · No injuriesLimited investigationFinal reportCessna 172M · Harbor Springs, MIthe pilot's long touchdown, and inadequate braking to stop on the runway. Factors relating to this accident were the pilot's improper in-flight planning and decision resulting in the long touchdown, and the fence.Aug 17, 2000 · N80310 · Substantial damageNTSB ATL00LA076Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Manteo, NCThe pilot's failure of preflight planning preparation, which resulted in the fuel exhaustion, and the subsequent loss of engine power.Aug 8, 2000 · N3529Q · Substantial damageNTSB LAX00LA299Accident · No injuriesLimited investigationFinal reportCessna 172M · Oakland, CAThe pilot's improper landing flare.Jul 27, 2000 · N4312R · Substantial damageNTSB NYC00LA203Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Columbus, OHa partial power loss for undetermined reason(s).Jul 19, 2000 · N80624 · Substantial damageNTSB LAX00LA256Accident · No injuriesLimited investigationFinal reportCessna 172 · Chandler, AZfailure of the pilot-in-command to adequately compensate for a crosswind condition and maintain directional control during the landing roll, resulting in the airplane departing the runway and colliding with a sign.Jul 8, 2000 · N1897V · Substantial damageNTSB SEA00LA113Accident · No injuriesLimited investigationFinal reportCessna 172M · Wallace, IDThe pilot's failure to maintain airspeed and his failure to maintain clearance from the trees. Related factors were trees and mountainous terrain.Jun 22, 2000 · N9895V · Substantial damageNTSB CHI00LA168Accident · No injuriesLimited investigationFinal reportCessna 172M · Decatur, ILthe pilot's failure to maintain clearance with the T-hangar while taxiing. A Factor associated with the accident was the pilot's attention was diverted to an other airplane which was taxiing on the same taxi line in the opposite direction.Jun 18, 2000 · N6557H · Substantial damageNTSB MIA00LA187Accident · No injuriesLimited investigationFinal reportCessna 172M · Davis, NCThe pilot's inadequate compensation for wind. The crosswind was a contributing factor.Jun 8, 2000 · N4422Q · Substantial damageNTSB CHI00FA129Accident · 3 fatalField investigationFinal reportCessna 172M · Cornell, WIthe pilot not maintaining aircraft control and the stall/spin he encountered. A factor was the extended flaps.May 2, 2000 · N13145 · DestroyedNTSB ATL00LA052Accident · No injuriesLimited investigationFinal reportCessna 172M · Clinton, TNThe pilot's inadequate in-flight planning necessitating an intentional ground loop maneuver on landing. Contributing factors were the pilot's misjudgment of distance/airspeed, the high terrain surrounding the runway, and the tailwind condition.Apr 30, 2000 · N13330 · Substantial damageNTSB LAX00LA133Accident · No injuriesLimited investigationFinal reportCessna 172M · Sacramento, CAThe failure of the pilot to maintain directional control of the aircraft during the takeoff roll. A rough, uneven runway surface was a factor in the accident.Mar 18, 2000 · N80205 · Substantial damageNTSB FTW00LA090Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Manilla, ARThe pilot's performance of low altitude flight and his failure to maintain clearance with the power lines.Mar 7, 2000 · N20179 · Substantial damageNTSB NYC00LA081Accident · No injuriesLimited investigationFinal reportPiper PA-28-236 · Parkertown, OHThe inadequate visual lookout by the pilots of both airplanes.Feb 15, 2000 · N8264G · 2 aircraft · Substantial damageNTSB SEA00WA042Accident · No injuriesForeign investigationCessna 172M · Squamish, CanadaJan 23, 2000 · N1673V · Substantial damageNTSB CHI00LA058Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Liberal, KSthe pilot not maintaining proper glidepath on the ILS approach, the pilot's improper decision to continue the approach below the glidepath, and the pilot's failure to perform a missed approach. Factors relating to the accident were the low ceiling and…Jan 17, 2000 · N12654 · Substantial damage