NTSB investigations: Cessna 172R, 2000

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

19982026
NTSB investigations: Cessna 172R, 2000 per year, 1998–2026: 228 cases
19982
199912
20008
20018
20026
20038
20049
200513
20067
200718
200812
20094
20106
201112
201210
20135
201410
20155
20169
20178
201810
20198
20206
20218
20224
20237
20246
20254
20263

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 ('2072401'))
  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 CHI00LA287Accident · No injuriesLimited investigationFinal reportCessna 172R · New Lenox, ILThe pilot's failure to maintain directional control during landing. Factors to the accident were the pipe that was struck, the crosswind, and the pilot's runway selection.Aug 29, 2000 · N364SA · Substantial damageNTSB CHI00LA182Accident · No injuriesLimited investigationFinal reportCessna 172R · Athens, MIthe failure of the student pilot to maintain control of the aircraft, the inadequate supervision by the flight instructor, and the delayed remedial action performed by the flight instructor. A factor to the accident was the runway edge light that was struck…Jul 5, 2000 · N996WW · Substantial damageNTSB NYC00LA155Accident · Minor injuriesLimited investigationFinal reportCessna 172R · West Milford, NJA loss of engine power for undetermined reasons.Jun 9, 2000 · N7274D · Substantial damageNTSB CHI00LA115Accident · No injuriesLimited investigationFinal reportCessna 172R · Battle Creek, MIthe student pilot's failure to maintain directional control of the airplane during the landing. Factors associated with the accident were the misjudged landing flare, the student's lack of total experience, the runway lights, and the runway signs.Apr 18, 2000 · N975BC · Substantial damageNTSB CHI00LA081Accident · No injuriesLimited investigationFinal reportCessna 172R · Waterford, MIthe directional control not obtained/maintained by the dual student and the remedial action not performed by the certified flight instructor. Contributing factors were the crosswind and the snow bank.Feb 21, 2000 · N922TA · Substantial damageNTSB MIA00LA086Accident · No injuriesLimited investigationFinal reportCessna 172R · Olive Branch, MSThe student pilot's failure to maintain directional control during landing and the subsequent collision with a taxiway sign and collapsed right main landing gear.Feb 7, 2000 · N2630B · Substantial damageNTSB FTW00LA060Accident · No injuriesLimited investigationFinal reportCessna 172R · Angleton, TXThe pilot's failure to maintain control of the airplane during landing. A factor was the gust of wind.Jan 10, 2000 · N8292 · Substantial damageNTSB MIA00FA064Accident · 1 fatalField investigationFinal reportCessna 172R · Atlantic Ocean (Atlantic Ocean)The pilot's lack of total experience in instrument flight, simulated instrument flight, and night flight resulting in the pilot becoming spatially disoriented, and subsequent in-flight collision with water. Contributing to the accident was the dark night with…Jan 6, 2000 · N156RA · Destroyed