NTSB investigations: Cessna 172P

11 cases on aircraft the registry lists as Cessna 172P, where the defining event was Abnormal runway contact. 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 172P per year, 2008–2026: 11 cases
20081
20103
20112
20141
20151
20161
20171
20181

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 ('2072436')
      AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' e WHERE e.case_mkey = x.case_mkey AND e.aircrafts_position = x.position AND e.\"isDefiningEvent\" AND e.\"tier2Number\" = '090'))
  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 GAA19CA087Accident · No injuriesData collectionFinal reportCessna 172 · Monroe, NCThe student pilot's improper landing flare, which resulted in a hard, bounced landing and nose landing gear collapse.Dec 3, 2018 · N65773 · Substantial damageNTSB GAA17CA268Accident · No injuriesData collectionFinal reportCessna 172 · Kaunakakai, HIThe student pilot’s incorrect flap configuration during the go-around, which resulted in a hard, forced landing.May 3, 2017 · N173LL · Substantial damageNTSB GAA17CA067Accident · No injuriesData collectionFinal reportCessna 172 · Concord, NHThe pilot's improper landing flare, which resulted in a hard landing.Nov 10, 2016 · N53402 · Substantial damageNTSB ERA15CA222Accident · No injuriesData collectionFinal reportCessna 172P · Mitchellville, MDThe pilot’s improper landing flare, which resulted in a bounced landing and damage to the airplane.May 25, 2015 · N6155K · Substantial damageNTSB ERA14CA354Accident · No injuriesData collectionFinal reportCessna 172P · Hagerstown, MDThe student pilot's improper landing flare.Jul 17, 2014 · N97528 · Substantial damageNTSB ERA12CA098Accident · No injuriesData collectionFinal reportCessna 172P · Schenectady, NYThe pilot’s inadequate recovery from a bounced landing, which resulted in a loss of control.Dec 1, 2011 · N83PD · Substantial damageNTSB WPR12CA008Accident · No injuriesData collectionFinal reportCessna 172P · Cornelius, ORThe airplane’s encounter with an unseen hole or obstacle on the grass runway.Oct 12, 2011 · N52013 · Substantial damageNTSB WPR10CA392Accident · No injuriesData collectionFinal reportCessna 172P · San Jose, CAThe pilot’s improper flare and inadequate recovery from a bounced landing.Aug 8, 2010 · N64204 · Substantial damageNTSB ERA10CA406Accident · Minor injuriesData collectionFinal reportCessna 172 · Chattanooga, TNThe student pilot's improper execution of the go-around procedure.Aug 8, 2010 · N51745 · Substantial damageNTSB ERA10CA241Accident · No injuriesData collectionFinal reportCessna 172P · Wurtsboro, NYThe student pilot's improper flare and recovery from a bounced landing.Apr 24, 2010 · N51231 · Substantial damageNTSB DFW08CA148Accident · No injuriesData collectionFinal reportCessna 172P · Rose Bud, ARThe pilot landed long and collided with a fence.May 17, 2008 · N5350K · Substantial damage