NTSB investigations: Cessna 172F

7 cases on aircraft the registry lists as Cessna 172F, where the first occurrence was “Hard landing”. 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

19822026
NTSB investigations: Cessna 172F per year, 1982–2026: 7 cases
19822
19941
19971
19982
19991

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 ('2072414')
      AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 200))
  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 FTW00LA049Accident · No injuriesLimited investigationFinal reportCessna 172 · Fort Worth, TXThe student pilot's improper flare and improper recovery from a bounced landing, which resulted in a porpoise.Dec 18, 1999 · N8250U · Substantial damageNTSB LAX98LA301Accident · No injuriesLimited investigationFinal reportCessna 172F · Long Beach, CAThe pilot's misjudging the flare point and failure to maintain an adequate airspeed margin, which resulted in a stall/mush and hard landing. A contributing factor was the dark night conditions.Sep 21, 1998 · N8761U · Substantial damageNTSB FTW98LA166Accident · No injuriesLimited investigationFinal reportCessna 172F · Fort Collins, COthe pilot's improper in flight planning/decision in electing to land with a known 30 knot tailwind. Factors were high winds and a tailwind.Mar 31, 1998 · N7894U · Substantial damageNTSB FTW98LA070Accident · Serious injuriesLimited investigationFinal reportCessna 172F · Gonzales, LAThe inadvertent stall resulting from the flight instructor's failure to maintain airspeed during his delayed recovery from the bounced landing. Factors were the student's failure to maintain the proper airspeed and the instructor's inadequate supervision…Dec 18, 1997 · N8426U · Substantial damageNTSB MIA95LA005Accident · Minor injuriesLimited investigationFinal reportCessna 172F · Indiantown, FLThe improper landing flare by the pilot resulting in the hard landing.Oct 11, 1994 · N5415R · Substantial damageNTSB FTW82DA333Accident · No injuriesFinal reportCessna 172F · Springlake, TXThe student pilot reported that during a landing, he flared too high. The aircraft then stalled onto the runway and was substantially damaged. Reportedly, he had a 3 kt tail wind and the density altitude was about 6000 ft.Aug 13, 1982 · N8239U · Substantial damageNTSB ATL82IA076Incident · No injuriesIncident investigationFinal reportCessna 172F · Mobile, ALUpon arrival at the aircraft, the pilot noted that the nose gear strut was under inflated. The pilot, who is training to be an A&P mechanic, diagnosed the problem as an oil leak. However, to avoid aborting the flight, he inflated the strut with air only and…Mar 20, 1982 · N8423U · Minor damage