NTSB investigations: Cessna 172S, MD

7 cases on aircraft the registry lists as Cessna 172S, where the sequence of events included 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

20102026
NTSB investigations: Cessna 172S, MD per year, 2010–2026: 7 cases
20102
20111
20161
20181
20191
20251

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.\"eventStateOrRegion\" = 'MD' AND c.\"eventCountry\" = 'USA'
    AND 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_events.parquet' s WHERE s.case_mkey = x.case_mkey AND s.aircrafts_position = x.position AND s.\"tier2Number\" = '090' AND s.case_mkey IN (SELECT case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' WHERE \"isDefiningEvent\")))
  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 ERA25LA306Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Baltimore, MDThe pilot’s inadequate landing flare at night, which resulted in a hard landing.Aug 17, 2025 · N6208C · 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 GAA18CA505Accident · No injuriesData collectionFinal reportCessna 172 · Churchville, MDThe pilot's failure to maintain directional control after landing left of the runway centerline, which resulted in a runway excursion and impact with a power box.Aug 23, 2018 · N419SP · Substantial damageNTSB GAA16CA158Accident · No injuriesData collectionFinal reportCessna 172 · Frederick, MDThe student pilot's improper pitch control during the landing flare, which resulted in a hard bounced landing.Mar 23, 2016 · N65329 · Substantial damageNTSB ERA11CA408Accident · No injuriesData collectionFinal reportCessna 172S · Cambridge, MDThe student pilot's improper recovery from a bounced landing.Jul 1, 2011 · N789EP · Substantial damageNTSB ERA10CA350Accident · No injuriesData collectionFinal reportCessna 172S · Salisbury, MDThe student pilot's improper recovery from a bounced landing.Jun 25, 2010 · N2373K · Substantial damageNTSB ERA10CA305Accident · No injuriesData collectionFinal reportCessna 172S · Baltimore, MDThe pilot’s improper flare, which resulted in a hard landing. Contributing to the accident was the pilot’s improper decision to land during a thunderstorm.Jun 4, 2010 · N789EP · Substantial damage