NTSB investigations: Cessna 172S, 2015

18 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, 2015 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\") = 2015
    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 ANC16LA011Accident · 1 fatalLimited investigationFinal reportCessna 172 · Anchorage, AKThe pilot's intentional flight into a building.Dec 29, 2015 · N914CP · DestroyedNTSB WPR16LA024Accident · Minor injuriesLimited investigationFinal reportCessna 172S · San Jose, CAThe pilot's failure to maintain directional control during the landing roll at night, which resulted in a runway excursion.Nov 8, 2015 · N21679 · Substantial damageNTSB GAA16CA048Accident · No injuriesData collectionFinal reportCessna 172 · Mesa, AZThe pilot's failure to maintain pitch control during landing, resulting in a porpoise, and firewall damage.Nov 7, 2015 · N1107G · Substantial damageNTSB GAA16CA052Accident · No injuriesData collectionFinal reportCessna 172S · Alcoa, TNThe pilot's failure to identify the taxiway, which resulted in a runway excursion and impact with terrain while turning off the runway at night.Nov 5, 2015 · N905CP · Substantial damageNTSB ERA16LA008Accident · 1 fatalLimited investigationFinal reportCessna 172S · Seville, FLThe airplane’s encounter with a downdraft, and the pilot's decision to maneuver the airplane at a low altitude and airspeed, which provided insufficient time and altitude to recover before impacting terrain.Oct 10, 2015 · N5295Y · Substantial damageNTSB ERA15LA366Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Bally, PAThe pilot's failure to maintain altitude during low-level aerobatic maneuvers. Contributing to the accident were the pilot's improper decision to attempt the low-level aerobatic maneuvers and his impairment due to psychiatric conditions and the medications he…Sep 21, 2015 · N347SP · Substantial damageNTSB GAA15CA237Accident · No injuriesData collectionFinal reportCessna 172 · Springfield, OHThe pilot's improper pitch control during landing, which resulted in a hard landing.Aug 23, 2015 · N691SP · Substantial damageNTSB ERA15LA274Accident · No injuriesLimited investigationFinal reportCessna 172S · Linden, NJThe pilot’s delayed decision to reject the takeoff, which resulted in a runway overrun. Contributing to the accident was the pilot’s failure to properly configure the flaps for maximum takeoff performance with the airplane near its maximum gross weight.Jul 19, 2015 · N962SP · Substantial damageNTSB GAA15CA140Accident · No injuriesData collectionFinal reportCessna 172 - S · Traverse City, MIThe student pilot's failure to maintain pitch control during the landing, resulting in a hard landing.Jun 25, 2015 · N195NW · Substantial damageNTSB GAA15CA241Accident · No injuriesData collectionFinal reportCessna 172 · Upperville, VAAn inflight bird strike, which resulted in wing spar damage.Jun 22, 2015 · N5210A · Substantial damageNTSB GAA15CA161Accident · No injuriesData collectionFinal reportCessna 172S · Galesburg, ILFirewall damage reported by maintenance personnel that occurred during an unknown phase of flight, because the accident flight and pilot could not be determined.Jun 10, 2015 · N740SP · Substantial damageNTSB WPR15FAMS1Accident · 1 fatalMissing aircraftFinal reportCessna 172S · Davenport, CAUndetermined because the airplane was not located.May 8, 2015 · N191TGNTSB GAA15CA064Accident · No injuriesData collectionFinal reportCessna 172S · Daytona Beach, FLThe landing airplane pilot's failure to maintain directional control during landing, which resulted in a runway excursion and ground collision with a taxiing airplane.May 7, 2015 · N5144H · 2 aircraft · Substantial damageNTSB GAA15CA046Accident · No injuriesData collectionFinal reportCessna 172S · Naples, FLThe pilot's failure to maintain airplane control, resulting in a hard landing.Apr 19, 2015 · N100PM · Substantial damageNTSB GAA15CA026Accident · No injuriesData collectionFinal reportCessna 172S · Vernal, UTThe student pilot's failure to maintain attitude control during landing flare.Mar 28, 2015 · N2168D · Substantial damageNTSB GAA15CA018Accident · No injuriesData collectionFinal reportCessna 172S · Camarillo, CAThe pilot involved and the phase of flight when the damage occurred were not determined.Mar 23, 2015 · N2104H · Substantial damageNTSB ERA15CA150Accident · No injuriesData collectionFinal reportCessna 172S · Richmond, VAThe student pilot's inadequate landing flare which resulted in a hard landing and substantial damage to the airplane.Mar 7, 2015 · N144ME · Substantial damageNTSB ERA15LA094Accident · No injuriesLimited investigationFinal reportCessna 172 · Norfolk, VAThe engine’s failure to regain full power after a simulated engine failure for reasons that could not be determined during postaccident examinations and testing.Jan 6, 2015 · N2102P · Substantial damage