NTSB investigations: Cessna 172RG

8 cases on aircraft the registry lists as Cessna 172RG, where the first occurrence was “In flight collision with object”. 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 172RG per year, 1982–2026: 8 cases
19821
19901
19921
19931
19952
19961
19991

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 ('2072438')
      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\" = 220))
  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 FTW99LA216Accident · No injuriesLimited investigationFinal reportCessna 172RG · Celina, TXThe failure of the pilot in command to use all of the available runway for takeoff.Aug 7, 1999 · N9620B · Substantial damageNTSB FTW96LA238Accident · Serious injuriesLimited investigationFinal reportCessna 172RG · Leadville, COInadequate preflight planning and preparation and failure to follow aircraft operating procedures and directives. Factors were high density altitude, inadequate training of the flight instructor and insufficient standards and requirements for flight…Jun 6, 1996 · N9431D · Substantial damageNTSB FTW96FA012Accident · 3 fatalField investigationFinal reportCessna 172RG · Bayfield, COThe pilot's failure to maintain adequate terrain clearance. A factor was the pilot diverting attention while looking for game.Oct 10, 1995 · N4834V · DestroyedNTSB FTW95LA281Accident · No injuriesLimited investigationFinal reportCessna 172RG · Weston, TXThe pilot receiving instruction's failure to maintain clearance with power lines while maneuvering at low altitude and the flight instructor's inadequate supervision. A factor was the instructor's decision to allow the simulation to continue to such a low…Jun 29, 1995 · N9502D · Substantial damageNTSB FTW93LA231Accident · Serious injuriesLimited investigationFinal reportCessna 172RG · Salida, COThe climb capability of the airplane being exceeded and the pilot's decision to turn into the rising terrain. A factor was the high density altitude.Aug 6, 1993 · N9633B · DestroyedNTSB DEN92FA077Accident · 1 fatalField investigationFinal reportCessna 172RG · Fairplay, COThe flight instructor's operation at an altitude insufficient to clear obstacles in rising mountainous terrain. Factors were: high density altitude, diversion of the instructor's attention, and the rising terrain.Jul 24, 1992 · N4963R · DestroyedNTSB LAX90LA236Accident · No injuriesLimited investigationFinal reportCessna 172RG · Concord, CAThe student pilot's initiating an excessive descent and the cfi's inadequate remedial action.Jul 6, 1990 · N5388R · Substantial damageNTSB SEA82DA033Accident · No injuriesFinal reportCessna 172RG · Plush, ORThe pilot departed lakeview, Oregon on a local flight with two passengers on board. After a stopover at a private airstrip, he began a short field takeoff from a grass/gravel/dirt runway that was 2500 ft in length. The density altitude was approximately 4600…Mar 7, 1982 · N6247R · Substantial damage