NTSB investigations: Cessna 172E, NC

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

19722026
NTSB investigations: Cessna 172E, NC per year, 1972–2026: 10 cases
19721
19731
19771
19801
19831
19921
20071
20121
20131
20211

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\" = 'NC' 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 ('2072412'))
  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 ERA21LA313Accident · Minor injuriesClass 3 · LimitedFinal reportCessna 172 · Waxhaw, NCThe pilot’s failure to abort the takeoff in sufficient time to stop the airplane on the runway remaining. Contributing to the accident was the lack of airplane takeoff performance due to the pilot’s failure to assure that the carburetor heat control was in…Aug 2, 2021 · N3090U · Substantial damageNTSB ERA13CA393Accident · No injuriesData collectionFinal reportCessna 172E · Apex, NCThe pilot's failure to attain the proper touchdown point on the runway, which resulted in a runway overrun and subsequent aircraft noseover.Aug 30, 2013 · N3513S · Substantial damageNTSB ERA12LA545Accident · Minor injuriesLimited investigationFinal reportCessna 172E · East Bend, NCA total loss of engine power during the initial climb after takeoff for reasons that could not be determined because examination of the engine did not reveal any anomalies that would have precluded normal operation.Sep 1, 2012 · N377SP · Substantial damageNTSB MIA08CA028Accident · No injuriesData collectionFinal reportCessna 172E · Fair Bluff, NCThe pilot's inadequate preflight inspection which failed to detect contaminated fuel, and subsequent loss of engine power.Dec 9, 2007 · N3699S · DestroyedNTSB ATL92LA092Accident · No injuriesLimited investigationFinal reportCessna 172E · Concord, NCThe loss of engine power because of the formation of carburetor ice.May 1, 1992 · N5529T · Substantial damageNTSB ATL83FA224Accident · Serious injuriesField investigationFinal reportCessna 172 · Mocksville, NCN5722T, a Cessna 172, and N3452J, a Cessna 150, collided over the approach end of runway 09 while both acft were on short final approach. Both acft impacted the runway and came to rest about 280 ft east of runway 09 threshold.Jun 8, 1983 · N5722T · 2 aircraft · Substantial damageNTSB ATL80DLJ25Accident · Minor injuriesClosedCessna 172 · Zebulon, NCOct 4, 1980 · N5389T · Substantial damageNTSB IAD77DKM18Accident · No injuriesClosedCessna 172 · Archdale, NCApr 10, 1977 · N5600T · DestroyedNTSB IAD74AI002Accident · 3 fatalClosedCessna 172E · Southern Pines, NCJul 4, 1973 · N3886S · DestroyedNTSB NYC72FLJ32Accident · No injuriesClosedCessna 172 · Roper, NCApr 15, 1972 · N5799T · Substantial damage