NTSB investigations: Cessna 172N

10 cases on aircraft the registry lists as Cessna 172N, where the sequence of events included Landing gear collapse. 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

20092026
NTSB investigations: Cessna 172N per year, 2009–2026: 10 cases
20092
20101
20131
20151
20162
20171
20181
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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072434')
      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\" = '094' 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 ERA25LA101Accident · No injuriesClass 4 · LimitedFinal reportCessna 172N · Mayfield, KYThe student pilot’s improper landing flare, which resulted in a hard landing and nose landing gear collapse.Jan 9, 2025 · N4942G · Substantial damageNTSB GAA19CA081Accident · No injuriesData collectionFinal reportCessna 172 · Inverness, FLThe pilot receiving instruction's failure to maintain directional control during landing.Nov 12, 2018 · N4642J · Substantial damageNTSB GAA17CA111Accident · No injuriesData collectionFinal reportCessna 172 · Hollywood, FLThe student pilot’s improper landing flare in gusting crosswind conditions, which resulted in a hard landing.Jan 7, 2017 · N907WA · Substantial damageNTSB GAA16CA511Accident · No injuriesData collectionFinal reportCessna 172 · Auburn, CAThe pilot's improper landing flare, which resulted in a hard, bounced landing.Sep 18, 2016 · N7560D · Substantial damageNTSB GAA16CA202Accident · No injuriesData collectionFinal reportCessna 172 · Camarillo, CAThe student pilot's incorrect pitch control input, resulting in a porpoise during landing and substantial damage to the airplane's firewall.Apr 20, 2016 · N6616D · Substantial damageNTSB GAA15CA235Accident · No injuriesData collectionFinal reportCessna 172N · Kalispell, MTThe pilot's loss of directional control, which resulted in a runway excursion, and collision with runway and taxiway lights and terrain.Aug 19, 2015 · N733NH · Substantial damageNTSB ERA13CA404Accident · No injuriesData collectionFinal reportCessna 172N · Knoxville, TNThe student pilot's improper flare and improper recovery from a bounced landing.Aug 3, 2013 · N737PD · Substantial damageNTSB ERA11CA061Accident · No injuriesData collectionFinal reportCessna 172N · Gaithersburg, MDThe student pilot's inadequate use of the rudder, and subsequent loss of directional control.Nov 14, 2010 · N249ER · Substantial damageNTSB CEN09CA373Accident · Serious injuriesData collectionFinal reportCessna 172N · Marysville, OHThe pilot's inability to maintain directional control of the airplane during the landing roll for undetermined reasons.Jun 22, 2009 · N734EN · Substantial damageNTSB CEN09CA253Accident · No injuriesData collectionFinal reportCessna 172N · Roanoke, TXThe partial loss of engine power due to a failure of the throttle control rod-end to carburetor arm hardware. A contributing factor was the pilot's decision to fly the airplane without a current annual inspection.May 8, 2009 · N172SV · Substantial damage