NTSB investigations: Cessna 172R, 2005

13 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, 2005 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\") = 2005
    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 CHI06CA053Accident · No injuriesData collectionFinal reportCessna 172R · Morris, ILThe pilot's improper in-flight decision to land with a quartering tailwind and not maintaining directional control. Factors were the quartering tailwind and the snowdrift.Dec 23, 2005 · N723PG · Substantial damageNTSB MIA06CA021Accident · No injuriesData collectionFinal reportCessna 172R · Kissimmee, FLThe pilot's improper flare and remedial action during landing resulting in an in-flight loss of control and subsequent collision with terrain. A related factor was the crosswind.Nov 18, 2005 · N5182Z · Substantial damageNTSB LAX06LA032Accident · No injuriesLimited investigationFinal reportCessna 172R · Ramona, CAthe student pilot's failure to maintain directional control during the landing.Nov 13, 2005 · N23899 · Substantial damageNTSB DFW06CA004Accident · No injuriesData collectionFinal reportCessna 172 · Spring, TXThe pilot's failure to maintain directional control while landing.Oct 12, 2005 · N94JA · Substantial damageNTSB DFW05CA219Accident · No injuriesData collectionFinal reportCessna 172R · Springtown, TXThe pilot's improper decision to shut down the engine. Contributing factors were the failure of the oil pressure switch and the lack of a suitable landing area.Aug 21, 2005 · N93AF · Substantial damageNTSB LAX05CA207Accident · No injuriesData collectionFinal reportCessna 172R · Santa Maria, CAthe student pilot's improper flare and recovery from a bounced landing.Jun 12, 2005 · N2384L · Substantial damageNTSB MIA05CA120Accident · No injuriesData collectionFinal reportCessna 172R · Fort Myers, FLThe pilot's improper landing flare which resulted in a hard landing.May 28, 2005 · N416FR · Substantial damageNTSB ATL05CA090Accident · No injuriesData collectionFinal reportCessna 172R · Louisburg, NCThe pilot's failure to maintain adequate airspeed, which resulted in a stall and subsequent loss of control and collision with the ground.May 28, 2005 · N22055 · Substantial damageNTSB ATL05CA088Accident · No injuriesData collectionFinal reportCessna 172 · Raleigh, NCThe pilot's failure to maintain adequate obstacle clearance during initial climb, which resulted in an in-flight collision with treesMay 27, 2005 · N496AC · Substantial damageNTSB NYC05FA075Accident · 2 fatalField investigationFinal reportCessna 172R · Armonk, NYThe flight instructor's failure to maintain the proper altitude\clearance during the approach, which resulted in an in-flight collision with trees. Factors in this accident were low ceilings, fog, and gusty wind conditions.Apr 23, 2005 · N61AF · DestroyedNTSB CHI05CA090Accident · No injuriesData collectionFinal reportCessna 172R · Kalamazoo, MIThe pilot's failure to maintain directional control and the excessive taxispeed.Apr 7, 2005 · N985BT · Substantial damageNTSB IAD05LA043Accident · No injuriesLimited investigationFinal reportCessna 172N · Frederick, MDThe inadequate visual lookout of the pilots in each airplane, which resulted in a ground collision.Mar 10, 2005 · N711DA · 2 aircraft · Substantial damageNTSB MIA05CA065Accident · No injuriesData collectionFinal reportCessna 172 · Madison, MSThe pilot's improper landing flare which resulted in substantial damage during the subsequent hard landing.Mar 2, 2005 · N212CF · Substantial damage