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
| 1974 | 2 |
|---|---|
| 1976 | 1 |
| 1979 | 1 |
| 1980 | 2 |
| 1982 | 1 |
| 1983 | 1 |
| 1984 | 1 |
| 1987 | 1 |
| 1988 | 1 |
| 1990 | 1 |
| 1992 | 1 |
| 1993 | 2 |
| 1996 | 1 |
| 1998 | 1 |
| 2001 | 1 |
| 2002 | 1 |
| 2003 | 2 |
| 2010 | 2 |
Where
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.
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" DESCRun it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
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.NTSB 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.NTSB 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.NTSB 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.NTSB 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.NTSB 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.NTSB FTW99FA006Accident · 1 fatalField investigationFinal reportCessna 172M · Oklahoma City, OKSuicide.NTSB 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.NTSB 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.NTSB 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 takeoffNTSB 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.NTSB FTW90LA158Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Broken Arrow, OKThe pilot in command's failure to maintain directional control during the takeoff.NTSB 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…NTSB 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.NTSB 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…NTSB 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'…NTSB 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…NTSB FTW80FA105Accident · 2 fatalClosedCessna 172M · Caddo, OKNTSB FTW80DPJ29Accident · No injuriesClosedCessna 172M · Hobart, OKNTSB FTW79FPJ08Accident · No injuriesClosedCessna 172 · Bethany, OKNTSB FTW76AF103Accident · 3 fatalClosedCessna 172M · Sperry, OKNTSB FTW74FPM24Accident · Serious injuriesClosedCessna 172M · Bunch, OKNTSB FTW74AF051Accident · 3 fatalClosedCessna 172M · Ada, OK