NTSB investigations: Cessna 172S, 2026

14 cases on aircraft the registry lists as Cessna 172S. 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

19672026
NTSB investigations: Cessna 172S, 2026 per year, 1967–2026: 586 cases
19672
19701
19721
19793
19871
19992
20004
200120
200222
200329
200427
200528
200625
200726
200831
200922
201027
201120
201229
201324
201418
201518
201629
201724
201822
201923
202018
202122
20229
202313
202414
202518
202614

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 year(c.\"eventDate\") = 2026
    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'))
  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 WPR26FA232Accident · 1 fatalClass 3 · FieldPreliminary reportCessna 172 · Willard, UTOn June 23, 2026, at about 2247 mountain daylight time, a Cessna 172S, N387AF, was destroyed when it was involved in an accident near Willard, Utah. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91…Jun 24, 2026 · N387AF · DestroyedNTSB ERA26LA248Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Brooksville, FLThe student pilot’s failure to ensure clearance while taxiing, which resulted in contact with another airplane that was performing an engine run-up.Jun 23, 2026 · N413AA · 2 aircraft · Substantial damageNTSB 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 WPR26LA220Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Morgan Hill, CAAn in-flight collision with a bird.Jun 11, 2026 · N55231 · Substantial damageNTSB CEN26LA210Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Colorado Springs, COThe student pilot’s failure to maintain directional control of the airplane during the takeoff, which resulted in a runway excursion and collision with runway signs.May 29, 2026 · N386SP · Substantial damageNTSB CEN26LA212Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Georgetown, TXThe pilot’s improper landing flare, which resulted in a hard, bounced landing.May 24, 2026 · N964SP · Substantial damageNTSB ERA26LA209Accident · Minor injuriesClass 4 · LimitedFinal reportCessna 172S · Harrison, NYThe student pilot’s excessive pitch up attitude during takeoff, which resulted in an aerodynamic stall and loss of control.May 18, 2026 · N5114Z · Substantial damageNTSB CEN26LA187Accident · No injuriesClass 3 · LimitedPreliminary reportCessna 172S · Denton, TXOn May 13, 2026, about 1815 central daylight time, a Cessna 172S, N2134M, sustained substantial damage when it was involved in an accident near Denton, Texas. The pilot was not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part…May 13, 2026 · N2134M · Substantial damageNTSB WPR26LA164Accident · Serious injuriesClass 3 · LimitedPreliminary reportCessna 172S · Pacoima, CAOn April 20, 2026, about 1107 Pacific daylight time, a Cessna 172S airplane, N2126F, sustained substantial damage when it was involved in an accident near Whiteman Airport (WHP), Pacoima, California. The pilot was seriously injured. The airplane was operated…Apr 20, 2026 · N2126F · Substantial damageNTSB ERA26LA174Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · The Rock, GAThe pilot’s improper landing flare, which resulted in a hard, porpoised landing.Apr 13, 2026 · N63405 · Substantial damageNTSB ERA26LA167Accident · No injuriesClass 3 · LimitedPreliminary reportCessna 172S · Marathon, FLOn April 11, 2026, about 1330 eastern daylight time, a Cessna 172S airplane, N529ND sustained substantial damage and a Raytheon Aircraft Company B200 (King Air) airplane, N699BW sustained minor damage when they collided in flight near Marathon, Florida. The 2…Apr 11, 2026 · N529ND · 2 aircraft · Substantial damageNTSB ERA26LA143Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Carthage, NCThe pilot’s failure to maintain clearance from trees while on final approach for landing. Contributing to the accident were the flight instructor’s inadequate remedial actions.Mar 1, 2026 · N972WW · Substantial damageNTSB CEN26LA133Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Denver, COThe solo student pilot's improper landing flare and subsequent improper recovery from a bounced landing which resulted in substantial damage to the airplane.Feb 28, 2026 · N1071Z · Substantial damageNTSB ERA26LA102Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · New Castle, DEThe pilots’ failure to properly identify the assigned runway during the landing approach, which resulted in the airplane landing on a closed, snow-covered runway. Contributing was the illumination of the closed runway’s edge lighting.Jan 29, 2026 · N969FG · Substantial damage