NTSB investigations: Cessna 172M, 2001
30 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
| 1972 | 3 |
|---|---|
| 1973 | 24 |
| 1974 | 59 |
| 1975 | 82 |
| 1976 | 104 |
| 1977 | 99 |
| 1978 | 92 |
| 1979 | 80 |
| 1980 | 59 |
| 1981 | 50 |
| 1982 | 53 |
| 1983 | 34 |
| 1984 | 35 |
| 1985 | 34 |
| 1986 | 38 |
| 1987 | 29 |
| 1988 | 28 |
| 1989 | 38 |
| 1990 | 37 |
| 1991 | 36 |
| 1992 | 31 |
| 1993 | 37 |
| 1994 | 24 |
| 1995 | 29 |
| 1996 | 23 |
| 1997 | 35 |
| 1998 | 30 |
| 1999 | 22 |
| 2000 | 22 |
| 2001 | 30 |
| 2002 | 26 |
| 2003 | 24 |
| 2004 | 18 |
| 2005 | 16 |
| 2006 | 18 |
| 2007 | 16 |
| 2008 | 24 |
| 2009 | 14 |
| 2010 | 15 |
| 2011 | 13 |
| 2012 | 18 |
| 2013 | 20 |
| 2014 | 20 |
| 2015 | 9 |
| 2016 | 10 |
| 2017 | 19 |
| 2018 | 14 |
| 2019 | 13 |
| 2020 | 16 |
| 2021 | 8 |
| 2022 | 24 |
| 2023 | 12 |
| 2024 | 14 |
| 2025 | 12 |
| 2026 | 8 |
Where
Open the mapLatest 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\") = 2001
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 year(c."eventDate") = 2001
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 ATL02LA024Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Trenton, FLThe pilot's improper in-flight decision to make a precautionary landing after sustaining a total loss of electrical power with sufficient fuel remaining to reach his destination airport. This resulted in an off field landing to an off site location in a…NTSB MIA02LA046Accident · Serious injuriesLimited investigationFinal reportCessna 172M · New Smyrna Bch, FLthe failure of the pilot to maintain airspeed, during initial climb out, which resulted in an inadvertent stall, and subsequent impact with the terrain.NTSB FTW02LA058Accident · No injuriesLimited investigationFinal reportCessna 172 · New Braunfels, TXThe student pilot's failure to maintain directional control of the airplane during the landing roll. A contributing factor was the soft terrain.NTSB NYC02LA035Accident · No injuriesLimited investigationFinal reportCessna 172M · Ravenna, OHThe student pilot's failure to maintain directional control.NTSB MIA02LA031Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Barceloneta, PRThe pilot's failure to maintain control of the aircraft which resulted in an uncontrolled descent and an in flight collision with water. Contributing to the accident was the impairment of the pilot due to alcohol.NTSB MIA02LA024Accident · No injuriesLimited investigationFinal reportCessna 172M · Crystal River, FLthe pilot's failure to keep a proper visual lookout and ensure proper clearance during taxi operations, which resulted in a collision with vehicles.NTSB CHI02LA036Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Vandalia, MOThe student pilot's inadequate directional control on the previous landing resulting in the overload failure of the nose landing gear fork. Factors were the overload of the nose landing gear fork, and the student pilot's lack of total experience.NTSB LAX02LA026Accident · No injuriesLimited investigationFinal reportCessna 172M · Chandler, AZFailure of the student pilot to maintain directional control during landing.NTSB LAX02LA017Accident · No injuriesLimited investigationFinal reportCessna 172M · Prescott, AZThe CFI's improper remedial action and failure to maintain directional control during landing in a strong crosswind condition.NTSB ATL02LA001Accident · No injuriesLimited investigationFinal reportCessna 172 · Goldsboro, NCThe student pilot's failure to maintain directional control during a touch-and-go landing.NTSB IAD02LA003Accident · Minor injuriesLimited investigationFinal reportCessna 172M · White Stone, VAloss of engine power for undetermined reasons.NTSB SEA01LA171Accident · No injuriesLimited investigationFinal reportCessna 172M · Seattle, WAPilot's failure to maintain an adequate visual lookout during taxi. A fence was a factor.NTSB NYC01LA219Accident · No injuriesLimited investigationFinal reportCessna 172M · Danbury, CTAn inoperative airspeed indicator and the pilot's improper recovery from the bounced landing.NTSB CHI01LA265Accident · No injuriesLimited investigationFinal reportCessna 172M · Milton, WIThe unsuitable terrain for landing encountered by the pilot. Factors were the high vegetation and the loss of engine power for undetermined reasons.NTSB LAX01LA259Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Placerville, CAInadequate airspeed during climb out following an aborted landing that was precipitated by the pilot's misjudged speed/distance on final approach. Also, contributing to the accident was the pilot's inexperience in the type of operation, his failure to…NTSB LAX01LA251Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Carson City, NVThe pilot's failure to follow the approved procedures for the aircraft when he attempted to takeoff at high density altitude with the wing flaps fully extended.NTSB ATL01LA085Accident · No injuriesLimited investigationFinal reportCessna 172M · Atlantic Ocean (Atlantic Ocean)The loss of engine power for undetermined reasons.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 SEA01LA122Accident · No injuriesLimited investigationFinal reportPiper PA-38-112 · Bozeman, MTThe pilot of another aircraft failed to maintain clearance while maneuvering for a formation flight. An updraft was a factor.NTSB LAX01LA221Accident · No injuriesLimited investigationFinal reportCessna 172M · Napa, CALoss of engine power due to the restricted movement of the number 1 exhaust valve that subsequently bent the exhaust push rod and push rod housing.NTSB MIA01LA161Accident · No injuriesLimited investigationFinal reportCessna 172M · Bennettsville, SCThe pilot's improper correction for wind conditions and his failure to maintain control of the airplane resulting in the airplane sliding off an embankment during taxi from landing.NTSB CHI01LA159Accident · No injuriesLimited investigationFinal reportCessna 172M · Middleton, WIThe pilot attempted a touch and go on unsuitable terrain. A factor associated with the accident was the tall wet grass airstrip on which the touch and go was attempted.NTSB MIA01LA158Accident · No injuriesLimited investigationFinal reportCessna 172M · Miami, FLThe pilot's failure to maintain airspeed during a go-around resulting in the airplane stalling, descending uncontrolled, impacting the runway, and sliding off the runway and nosing over.NTSB FTW01LA138Accident · No injuriesLimited investigationFinal reportCessna 172M · Hot Springs, ARthe student pilot's delayed go-around, which resulted in the airplane impacting trees during the aborted landing.NTSB NYC01LA139Accident · No injuriesLimited investigationFinal reportCessna 172M · Nashua, NHThe CFI's improper decision to abort the takeoff and his improper flare, which resulted in a hard landing.NTSB SEA01LA094Accident · No injuriesLimited investigationFinal reportCessna 172 · McMinnville, ORThe student pilot's failure to adequately compensate for wind conditions while doing a touch-and-go landing.NTSB CHI01LA133Accident · No injuriesLimited investigationFinal reportCessna 172M · West Chicago, ILThe inadequate compensation for the crosswind by the student pilot. Additional factors included the student pilot's lack of total flight time, the runway sign and the crosswind.NTSB FTW01LA133Accident · No injuriesLimited investigationFinal reportCessna 172M · Patterson, LAthe pilot's failure to maintain control during the go-around. A contributing factor was the wind gust.NTSB CHI01LA127Accident · No injuriesLimited investigationFinal reportCessna 172M · Eveleth, MNThe pilot's inadequate compensation for the crosswind conditions which resulted in the loss of aircraft control. Factors associated with the accident were the gusty crosswind condition, the pilot's lack of experience, and the trees which were contacted.NTSB LAX01LA135Accident · No injuriesLimited investigationFinal reportCessna 172M · N. Las Vegas, NVThe pilot's inadequate compensation for the existing crosswind condition, and his failure to maintain runway alignment.