NTSB investigations: Cessna 172M, WV

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

19742026
NTSB investigations: Cessna 172M, WV per year, 1974–2026: 11 cases
19741
19791
19821
19881
19911
19922
19931
19971
19991
20111

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\" = 'WV' 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 ('2072418'))
  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 ERA11CA450Accident · No injuriesData collectionFinal reportCessna 172M · Elkins, WVThe flight instructor's unfamiliarity with the geographic area, resulting in controlled flight into terrain.Aug 13, 2011 · N5399Q · Substantial damageNTSB NYC99LA152Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Fayetteville, WVThe pilot's failure to maintain directional control during the aborted landing. A factor in this accident was the crosswind condition.Jun 20, 1999 · N20952 · Substantial damageNTSB NYC97LA156Accident · No injuriesLimited investigationFinal reportCessna 172M · Milton, WVThe student pilot's improper recovery from a bounced landing.Aug 1, 1997 · N80987 · Substantial damageNTSB NYC93LA063Accident · No injuriesLimited investigationFinal reportCessna 172M · Valley Point, WVThe failure of the pilot to make a rejected landing when the airplane failed to decelerate properly. A factor related to the accident was the failure of the pilot to close the throttle upon touchdown.Feb 4, 1993 · N9839V · Substantial damageNTSB NYC93LA035Accident · No injuriesLimited investigationFinal reportCessna 172M · Mallory, WVThe pilot failed to maintain control of the airplane, which resulted in the airplane departing the runway and striking a tree.Oct 29, 1992 · N20493 · Substantial damageNTSB BFO92LA111Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Charleston, WVThe pilot's failure to attain adequate airspeed to outclimb obstacles.Jul 23, 1992 · N12921 · DestroyedNTSB BFO91LA058Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Beckley, WVThe pilot's failure to attain adequate flying speed.Jun 25, 1991 · N20430 · DestroyedNTSB BFO88LA038Accident · No injuriesLimited investigationFinal reportCessna 172M · Fayetteville, WVThe pilot landed long and with excessive airspeed, which resulted in an overrun of the runway. Inadequate inflight planning is a contributing factor.Apr 29, 1988 · N13261 · Substantial damageNTSB ATL82DA181Accident · No injuriesFinal reportCessna 172 · Martinsburg, WVShortly after level-off to cruise, the engine began to lose power. The pilot attempted to restore the power, but the engine RPM continued to decrease. A turn was made back toward the airport. While scanning the instruments, zero oil pressure and a high oil…Jun 30, 1982 · N61791 · Substantial damageNTSB IAD79FA081Accident · 1 fatalClosedCessna 172 · Elkins, WVSep 10, 1979 · N80979 · DestroyedNTSB IAD75FGM08Accident · No injuriesClosedCessna 172 · N Cumberland, WVAug 26, 1974 · N174KA · Substantial damage