NTSB investigations: Cessna 172M, OK

23 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, OK per year, 1974–2026: 23 cases
19742
19761
19791
19802
19821
19831
19841
19871
19881
19901
19921
19932
19961
19981
20011
20021
20032
20102

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\" = 'OK' 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 CEN11LA082Accident · 1 fatalLimited investigationFinal reportCessna 172M · Velma, OKThe pilot’s failure to maintain control of the airplane while maneuvering, which resulted in an inadvertent stall and subsequent impact with terrain. Contributing to the accident was the pilot's relative inexperience in pipeline patrols.Nov 24, 2010 · N4428Q · DestroyedNTSB CEN10CA199Accident · Serious injuriesData collectionFinal reportCessna 172 · Lawton, OKThe private pilot's failure to maintain adequate airspeed, which resulted in a stall, and the failure of both pilots to initiate a go-around. Contributing to the severity of both pilots' injuries was the lack of available shoulder harnesses.Apr 9, 2010 · N12614 · Substantial damageNTSB FTW03LA220Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Ardmore, OKThe failure of the pilot to adequately compensate for existing wind conditions. A contributing factor was the gusty crosswind conditions from the east.Sep 11, 2003 · N9651Q · Substantial damageNTSB FTW03LA177Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Bristow, OKThe pilot's premature retracting of the flaps, and his failure to maintain airspeed which resulted in an inadvertent stall.Jun 25, 2003 · N20679 · Substantial damageNTSB FTW03LA056Accident · No injuriesLimited investigationFinal reportCessna 172M · Vici, OKThe pilot's departure and continued flight into adverse weather conditions. Contributing factors were the icing conditions, and the lack of suitable terrain for the precautionary landing.Dec 3, 2002 · N4470R · Substantial damageNTSB FTW01LA161Accident · No injuriesLimited investigationFinal reportCessna 172 · Kingston, OKthe pilot's failure to maintain directional control during the takeoff roll, which required his evasive maneuver and resulted in a stall.Jul 10, 2001 · N1581V · Substantial damageNTSB FTW99FA006Accident · 1 fatalField investigationFinal reportCessna 172M · Oklahoma City, OKSuicide.Oct 11, 1998 · N172JF · DestroyedNTSB FTW97LA008Accident · No injuriesLimited investigationFinal reportCessna 172M · Tuttle, OKfailure of the pilot to maintain directional control during takeoff roll, which resulted in a ground swerve. Factors relating to the accident were: tall grass along the edges of the runway, and the proximity of the fence, fence posts, and trees.Oct 5, 1996 · N172JF · Substantial damageNTSB FTW93FA128Accident · 2 fatalField investigationFinal reportCessna 172M · Hobart, OKInadvertent stall. Factors were the instructor pilot's spatial disorientation, his lack of total instrument time, the weather, and the dark night conditions.Apr 13, 1993 · N61529 · DestroyedNTSB FTW93LA104Accident · No injuriesLimited investigationFinal reportCessna 172M · Overbrook, OKThe pilot's failure to assure that the elevator trim was properly set for takeoff and his delay in aborting the takeoffMar 15, 1993 · N9689H · Substantial damageNTSB FTW92FA098Accident · 1 fatalField investigationFinal reportCessna 172M · Oklahoma City, OKInadvertent stall during aborted landing. Factors were the tailwind, the pilot's selection of the wrong runway for existing wind conditions and his long landing.Mar 26, 1992 · N20059 · DestroyedNTSB FTW90LA158Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Broken Arrow, OKThe pilot in command's failure to maintain directional control during the takeoff.Aug 20, 1990 · N73571 · Substantial damageNTSB FTW88DPJ03Accident · Serious injuriesFinal reportCessna 172M · Norman, OKPilot retracted flaps during go around and aircraft settled into trees and was destroyed. Front seat occupants were not wearing the available shoulder harnesses. The acft was landing with a quartering tailwind. Due to serious head injuries the plt never…Feb 24, 1988 · N20129 · DestroyedNTSB FTW87LA145Accident · No injuriesLimited investigationFinal reportCessna 172 · Yukon, OKOn touchdown the aircraft started to drift to the left. The pilot applied right rudder and lost directional control of the aircraft. The aircraft's right wing contacted the runway and the aircraft nosed over.Jun 14, 1987 · N13618 · Substantial damageNTSB FTW84LA373Accident · No injuriesLimited investigationFinal reportCessna 172M · Bethany, OKAccording to the plt of N9646H, while he was taxiing under the direction of ground control the acft was struck from behind by N1PN. The plt of N1PN stated that he was cleared to taxi and did not see any other acft as he entered the taxiway. Seated in the rear…Aug 30, 1984 · N9646H · 2 aircraft · Substantial damageNTSB FTW84LA067Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Okmulgee, OKAccording to the plt, the eng was not producing sufficient power to maintain alt in normal cruise. Also, he reported that 'extra power' was required on final apch for landing at the destination arpt. He further stated that he was unable 'to cut power to idle'…Nov 21, 1983 · N80110 · DestroyedNTSB FTW82FPJ19Accident · Serious injuriesFinal reportCessna 172M · Overbrook, OKThe pilot stated that he began his takeoff from the very beginning of the runway, and that on rotation, the engine seemed to lose power. He stated that he observed the tachometer and saw that the engine was dropping below 1500 RPM. Subsequently, the aircraft…Aug 8, 1982 · N46172 · DestroyedNTSB FTW80FA105Accident · 2 fatalClosedCessna 172M · Caddo, OKAug 16, 1980 · N12906 · DestroyedNTSB FTW80DPJ29Accident · No injuriesClosedCessna 172M · Hobart, OKJul 18, 1980 · N80117 · Substantial damageNTSB FTW79FPJ08Accident · No injuriesClosedCessna 172 · Bethany, OKMar 15, 1979 · N61624 · DestroyedNTSB FTW76AF103Accident · 3 fatalClosedCessna 172M · Sperry, OKJun 18, 1976 · N13132 · 2 aircraft · DestroyedNTSB FTW74FPM24Accident · Serious injuriesClosedCessna 172M · Bunch, OKMay 1, 1974 · N12093 · Substantial damageNTSB FTW74AF051Accident · 3 fatalClosedCessna 172M · Ada, OKJan 5, 1974 · N19959 · Destroyed