NTSB investigations: Cessna 172R, 2004

9 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, 2004 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\") = 2004
    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 NYC05LA034Accident · Minor injuriesLimited investigationFinal reportCessna 172R · Smoketown, PAThe pilot's failure to maintain directional control during takeoff, which resulted in a collision with a parked airplane.Dec 30, 2004 · N9962F · Substantial damageNTSB NYC05LA024Accident · No injuriesLimited investigationFinal reportCessna 172R · Martinsburg, WVA loss of engine power for undetermined reasons.Nov 21, 2004 · N5294W · Substantial damageNTSB ATL04CA170Accident · Minor injuriesData collectionFinal reportCessna 172R · Atlanta, GAThe intentional interuption of the flight controls in flight that resulted in a uncontrolled descent and collision with a fence.Aug 28, 2004 · N26486 · Substantial damageNTSB CHI04CA241Accident · No injuriesData collectionFinal reportCessna 172R · Olathe, KSThe student pilot flared too high and failed to recover from a bounced landing.Aug 5, 2004 · N458CM · Substantial damageNTSB NYC04CA145Accident · No injuriesData collectionFinal reportCessna 172R · Hartford, CTThe student pilot's improper flare and inadequate compensation for wind conditions. A factor was the gusty winds.Jun 21, 2004 · N356ES · Substantial damageNTSB CHI04LA097Accident · No injuriesLimited investigationFinal reportCessna 172R · Kalamazoo, MIThe air traffic control procedures/directives not followed by tower air traffic controller, the inadequate compensation for wind conditions by the student pilot during landing, the lack of total experience by the student pilot, and the recommended crosswind…Apr 2, 2004 · N986AV · Substantial damageNTSB CHI04LA085Accident · Minor injuriesLimited investigationFinal reportCessna 172R · Dubuque, IAThe flight instructor's inadequate in-flight planning/decision which resulted in ice accretion on the airframe, and his failure to maintain adequate airspeed resulting in a stall. Contributing factors were the ice contamination, the aircraft's low altitude…Mar 9, 2004 · N105FS · Substantial damageNTSB NYC04CA070Accident · No injuriesData collectionFinal reportCessna 172R · Batavia, OHThe student pilot's improper flare and improper recover from a bounced landing, which resulted in a hard landing.Feb 16, 2004 · N121UC · Substantial damageNTSB IAD04CA009Accident · No injuriesData collectionFinal reportCessna 172R · Fredrick, MDThe student pilot's failure to maintain directional control during the landing. A factor was the snow bank.Feb 5, 2004 · N5165M · Substantial damage