NTSB investigations: Cessna 172RG

8 cases on aircraft the registry lists as Cessna 172RG, where the first occurrence was “Loss of engine power”. 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

19872026
NTSB investigations: Cessna 172RG per year, 1987–2026: 8 cases
19871
19901
19911
19921
19951
19961
20021
20041

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\" = 350))
  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 SEA04LA033Accident · No injuriesLimited investigationFinal reportCessna 172RG · Enumclaw, WAA loss of engine power while maneuvering due to the failure of the heads of six of the eight cam followers. Factors include the pilot's decision to keep the gear retracted during the forced landing, and the rough/uneven terrain.Jan 13, 2004 · N64ML · Substantial damageNTSB FTW02LA128Accident · No injuriesLimited investigationFinal reportCessna 172RG · Alamogordo, NMthe loss of engine power for an undetermined reason, which resulted in a forced landing after takeoff.Apr 24, 2002 · N6288R · Substantial damageNTSB IAD96LA123Accident · No injuriesLimited investigationFinal reportCessna 172 RG · Union Bridge, MDloss of engine power for undetermined reason(s).Jul 25, 1996 · N6169R · Substantial damageNTSB MIA95FA174Accident · 2 fatalField investigationFinal reportCessna 172RG · Ft. Lauderdale, FLThe failure of the pilot to maintain airspeed after a momentary loss of engine power during takeoff, resulting in an inadvertent stall/spin. The reason for power loss could not be determined.Jul 7, 1995 · N9324B · DestroyedNTSB LAX92LA387Accident · No injuriesLimited investigationFinal reportCessna 172RG · Casa Grande, AZThe loss of engine power for undetermined reasons.Sep 16, 1992 · N519PU · Substantial damageNTSB CHI91LA196Accident · No injuriesLimited investigationFinal reportCessna 172RG · Hawley, MNInattentiveness of both the flight instructor and the student pilot, and failure to use carburetor heat. A factor related to the accident is the unsuitable terrain encountered during the forced landing.Jun 19, 1991 · N9431D · Substantial damageNTSB MIA90LA048Accident · No injuriesLimited investigationFinal reportCessna 172RG · Astatula, FLLoss of engine power for an undetermined reason during a simulated forced landing.Jan 5, 1990 · N6290R · Substantial damageNTSB LAX87LA118Accident · Serious injuriesLimited investigationFinal reportCessna 172RG · San Diego, CADuring a local pleasure flight, the pilot returned to the airport to practice touch-and-go landings. On take-off, ascending through 200 feet, the engine began to surge then quit. The pilot made a forced landing on an occupied road where the aircraft collided…Feb 19, 1987 · N4590V · Substantial damage