NTSB investigations: Cessna 172RG, 1997

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

19652026
NTSB investigations: Cessna 172RG, 1997 per year, 1965–2026: 256 cases
19651
19661
19701
19721
19792
19803
198111
19827
198310
198411
198513
19863
198710
19885
19898
19909
19918
19928
19936
199412
19958
19968
19978
19985
19997
20002
200111
20026
20035
20046
20055
20064
20073
200810
20095
20102
20113
20122
20134
20142
20151
20163
20174
20181
20192
20201
20211
20224
20241
20251
20261

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\") = 1997
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072438'))
  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 LAX98LA036Accident · No injuriesLimited investigationFinal reportCessna 172RG · San Diego, CAOverload of the main gear actuator piston and the subsequent collapse of the landing gear.Nov 12, 1997 · N9451D · Substantial damageNTSB SEA97LA214Accident · No injuriesLimited investigationFinal reportCessna 172RG · Monroe, WAThe failure of the flight instructor to adequately perform remedial action, and her failure to abort the takeoff. Factors contributing to the accident include the premature rotation of the airplane by the dual student, the failure of the dual student to…Sep 23, 1997 · N64ML · Substantial damageNTSB LAX97LA297Accident · No injuriesLimited investigationFinal reportCessna 172RG · Lancaster, CAImproper flare.Aug 21, 1997 · N9710B · Substantial damageNTSB NYC97LA158Accident · No injuriesLimited investigationFinal reportCessna 172 RG · Quinton, VAThe pilot's failure to identify an unsafe landing gear condition. A factor in the accident was the loss of electrical power.Aug 3, 1997 · N9647B · Substantial damageNTSB CHI97LA180Accident · No injuriesLimited investigationFinal reportCessna 172RG · Chicago, ILthe pilot inadvertently executed a wheels up landing.Jun 22, 1997 · N6280R · Substantial damageNTSB FTW97LA197Accident · Minor injuriesLimited investigationFinal reportCessna 172RG · Rio Hondo, TXfailure of the pilot to use all of the available runway during landing, and his resultant failure to attain a proper touchdown point for a safe rollout. Factors relating to the accident were: the wet runway with hydroplaning conditions, the uneven terrain…May 22, 1997 · N9492D · DestroyedNTSB FTW97FA181Accident · 1 fatalField investigationFinal reportCessna 172RG · Intracoastal, LAthe pilot's decision to fly, when he was not in good physical condition; and his subsequent loss of aircraft control due to incapacitation. A related factor was: the pilot's perception of an urgency (pressure) to fly, induced by conditions/events.May 8, 1997 · N6505V · DestroyedNTSB LAX97LA095Accident · No injuriesLimited investigationFinal reportCessna 172RG · Corona, CAFailure of the pilot in command to follow the airplane's before landing checklist and verify the landing gear was fully extended before landing. Factors in the accident were anxiety and diversion of the pilot's attention due to fuel gauge readings.Jan 28, 1997 · N80138 · Substantial damage