NTSB investigations: Cessna 172S

9 cases on aircraft the registry lists as Cessna 172S, where NTSB found Tailwind. 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 172S per year, 2008–2026: 9 cases
20081
20131
20171
20193
20211
20231
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 c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072439', '2072442')
      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\", '03034015')))
  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 WPR26LA222Accident · Minor injuriesClass 4 · LimitedFinal reportCessna 172S · Death Valley, CAThe pilot’s failure to maintain airspeed and encounter with a tailwind while landing on a rough runway, which resulted in a runway overrun and subsequent nose over.Jun 17, 2026 · N96FA · Substantial damageNTSB CEN23LA159Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Fredericksburg, TXThe pilot’s failure to maintain airplane control during an attempted go-around resulting in abnormal contact with the runway pavement and a runway excursion.Apr 17, 2023 · N478SP · Substantial damageNTSB ERA22LA087Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Hazleton, PAThe pilot’s failure to maintain proper airspeed on approach in tailwind conditions, which resulted in an extended touchdown, bounced landing, and runway excursion.Dec 12, 2021 · N215LP · Substantial damageNTSB GAA19CA503Accident · No injuriesData collectionFinal reportCessna 172 · Ocean City, MDThe student pilot's improper landing flare with a tailwind, which resulted in a hard, bounced landing.Aug 4, 2019 · N197ME · Substantial damageNTSB GAA19CA225Accident · No injuriesData collectionFinal reportCessna 172 · Scottsdale, AZThe pilot's improper rudder inputs and failure to maintain directional control during landing with a crosswind, which resulted in a runway excursion and impact with a runway sign.Apr 20, 2019 · N6023V · Substantial damageNTSB GAA19CA137Accident · No injuriesData collectionFinal reportCessna 172 · Sanford, FLThe student pilot's failure maintain the proper pitch attitude during landing, which resulted in the airplane porpoising.Feb 15, 2019 · N572ND · Substantial damageNTSB GAA17CA248Accident · No injuriesData collectionFinal reportCessna 172S · Jean, NVThe pilot’s runway selection, which resulted in landing with a tailwind and an unstabilized approach and subsequent runway overrun.Apr 28, 2017 · N796SP · Substantial damageNTSB CEN13CA335Accident · No injuriesData collectionFinal reportCessna 172S · Ann Arbor, MIThe pilot’s failure to make a go-around in a timely manner and his loss of control during landing.Jun 9, 2013 · N857SP · Substantial damageNTSB LAX08LA179Accident · Serious injuriesLimited investigationFinal reportCessna 172S · Beaver, UTThe pilot's failure to attain and maintain an adequate airspeed during the initial climb as a result of his inadequate preflight planning and improper use of the mixture control. Contributing to the accident were the tailwind and high density altitude.Jun 12, 2008 · N233GW · Substantial damage