NTSB investigations: Cessna 172R

7 cases on aircraft the registry lists as Cessna 172R, where NTSB found Sign/marker. 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

20082026
NTSB investigations: Cessna 172R per year, 2008–2026: 7 cases
20082
20121
20171
20192
20201

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 ('2072401')
      AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_findings.parquet' f WHERE f.case_mkey = x.case_mkey AND f.aircrafts_position = x.position AND starts_with(f.\"findingCode\", '03022015')))
  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 WPR20CA219Accident · No injuriesClass 4 · Data collectionFinal reportCessna 172 · Concord, CAThe student pilot's failure to maintain airplane control when the airplane drifted off of runway centerline and subsequently collided with a taxiway sign during a go-around.Jul 12, 2020 · N9559D · Substantial damageNTSB GAA19CA472Accident · No injuriesData collectionFinal reportCessna 172 · Mt. Sterling, KYThe pilot's loss of directional control during the takeoff roll due to distraction by the passenger window being unsecured, which resulted in a runway excursion and impact with a runway distance marker. Contributing to the accident was pilot’s failure to…Jul 28, 2019 · N9548W · Substantial damageNTSB GAA19CA368Accident · No injuriesData collectionFinal reportCessna 172 · Tulsa, OKThe pilot's failure to maintain directional control while landing in gusting crosswind conditions, which resulted in a runway excursion and impact with a taxiway sign.Jun 22, 2019 · N9200B · Substantial damageNTSB GAA17CA482Accident · No injuriesData collectionFinal reportCessna 172 · Kearney, NEThe pilot’s failure to maintain directional control of the airplane during the landing roll, which resulted in a runway excursion.Aug 2, 2017 · N91966 · Substantial damageNTSB WPR12CA357Accident · No injuriesData collectionFinal reportCessna 172R · Everett, WAThe pilot’s failure to maintain directional control during takeoff.Aug 14, 2012 · N863CP · Substantial damageNTSB CEN09CA002Accident · No injuriesData collectionFinal reportCessna 172 · Alton, ILThe student pilot's failure to maintain directional control during landing. A contributing factor was the presence of the sign struck during the runway excursion.Oct 3, 2008 · N5172J · Substantial damageNTSB LAX08CA222Accident · No injuriesData collectionFinal reportCessna 172R · Byron, CAThe pilot's failure to maintain directional control during the landing rollout.Jul 9, 2008 · N354ES · Substantial damage