NTSB investigations: Cessna 172M, 1995
29 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\") = 1995
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") = 1995
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 CHI96LA062Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Excelsior Sprg, MOthe pilot's selection of the wrong runway for landing and the delayed aborted landing. Factors associated with the accident were the tailwind condition and the pilot's inadequate level-off.NTSB LAX96LA077Accident · No injuriesLimited investigationFinal reportCessna 172 · Bakersfield, CAthe pilot's improper aborted landing procedure which resulted in the aircraft stalling and impacting terrain.NTSB LAX96LA071Accident · No injuriesLimited investigationFinal reportCessna 172M · Palm Springs, CAthe pilot's inadequate bounced landing recovery technique, which resulted in porpoising during a downwind emergency landing. The loss of engine power for undetermined reasons was a factor.NTSB LAX96LA073Accident · No injuriesLimited investigationFinal reportCessna 172 · Mohave Valley, AZthe failure of the pilot to assure that clearance was maintained while taxiing in proximity of buildings at an excessive taxi speed.NTSB MIA96LA034Accident · No injuriesLimited investigationFinal reportCessna 172M · Madison, MSThe pilot's premature raising of flaps during a go-around.NTSB BFO96FA007Accident · 2 fatalField investigationFinal reportCessna 172M · Norwich, VTloss of engine power for undetermined reason(s), during a low altitude operation. A factor relating to the accident was: the lack of suitable terrain for a forced landing.NTSB FTW96LA014Accident · No injuriesLimited investigationFinal reportCessna 172M · Sugar Land, TXthe student pilot's diverted attention and failure to maintain directional control.NTSB ATL96LA001Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Savannah, GAThe pilot's selection of unsuitable terrain for a precautionary landing, and his failure to maintain clearance from an obstacle (road sign) during the landing.NTSB FTW95FA393Accident · 3 fatalField investigationFinal reportCessna 172M · Witter, ARfailure of the pilot to maintain sufficient altitude/clearance from high/wooded terrain. Factors relating to the accident were: darkness, high terrain, and foggy weather conditions. Also, the pilot's use of Methamphetamine (not approved by the FAA) was a…NTSB CHI95FA307Accident · 1 fatalField investigationFinal reportCessna 172M · Orr, MNthe pilot misjudged the landing flare. Factors associated with the accident were the visual illusion caused by the glassy smooth water condition and the forward center of gravity.NTSB NYC95FA210Accident · 3 fatalField investigationFinal reportCessna 172M · Portland, MEan engine malfunction for an undetermined reason, and the pilot's failure to maintain airspeed during a forced landing which resulted in an accelerated stall. A factor was the pilot's lack of recent experience.NTSB NYC95LA207Accident · 1 fatalLimited investigationFinal reportCessna 172M · Kingswood Twsp, NJFailure of the pilot to maintain control of the airplane, which resulted in an in-flight collision with trees.NTSB NYC95LA205Accident · No injuriesLimited investigationFinal reportCessna 172M · Williamson, NYthe loss of engine power and the eruption of a fire for undetermined reasons.NTSB CHI95LA298Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Independence, MOthe pilot's failure to perform the pre-takeoff checklist and set the elevator trim tab to the takeoff position.NTSB NYC95LA200Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Hopedale, MAthe student pilot's improper flare and improper recovery from a bounced landing, which resulted in a loss of control and collision with a fence and a building.NTSB SEA95FA171Accident · 2 fatalField investigationFinal reportCessna 172M · Quilcene, WAThe pilot's continued VFR flight into instrument meteorological conditions, and his failure to maintain clearance from the mountains. Factors in the accident were the clouds and mountainous terrain.NTSB ATL95LA133Accident · No injuriesLimited investigationFinal reportCessna 172 · Bayboro, NCThe pilot's inadequate procedure in that he elected to land the aircraft on unsuitable terrain with no mechanical malfunctions.NTSB ANC95LA116Accident · No injuriesLimited investigationFinal reportCessna 172 · Kotzebue, AKFuel exhaustion due to the pilot's improper planning/decision. The unfavorable (stronger than forecast) headwind was a related factor.NTSB LAX95LA236Accident · No injuriesLimited investigationFinal reportCessna 172M · New Cuyama, CAthe pilot's failure to attain and maintain an adequate airspeed, his premature rotation, and his failure to maintain directional control when the aircraft settled back onto the runway. The pilot's selection of a closed airport for the takeoff attempt was a…NTSB NYC95LA135Accident · No injuriesLimited investigationFinal reportCessna 172M · Bridgewater, CTthe loss of engine power for undetermined reasons resulting in a forced landing, and a subsequent collision with trees.NTSB ANC95LA072Accident · No injuriesLimited investigationFinal reportCessna 172 · Skwentna, AKThe pilot's failure to maintain directional control. Factors associated with the accident are the wet and uneven airstrip surface.NTSB CHI95LA147Accident · No injuriesLimited investigationFinal reportCessna 172M · Brooklyn, MIFatigue failure of the left main landing gear. Factors relating to the accident were: the pilot's improper flare for landing, and soft terrain.NTSB NYC95WA097Accident · 1 fatalForeign investigationCessna 172M · St. Johns, CanadaNTSB LAX95LA163Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Yolo, CAthe pilot's improper preflight preparation which led to fuel exhaustion.NTSB MIA95LA108Accident · No injuriesLimited investigationFinal reportCessna 172M · Panacea, FLThe pilot's failure to attain the proper touchdown point during a forced landing to a runway. This resulted in the airplane rolling off the departure end of the runway, and subsequent on ground collision with a fence and a telephone booth. Contributing to the…NTSB BFO95FA045Accident · 3 fatalField investigationFinal reportCessna 172M · Eldersburg, MDThe pilot's failure to maintain proper airspeed. Factors in the accident were the pilot's failure to remove carburetor heat during the go-around and the presence of a tailwind.NTSB NYC95LA061Accident · No injuriesLimited investigationFinal reportCessna 172M · West Seneca, NYThe pilot's improper planning/decision to attempt a takeoff on a narrow icy runway with crosswind conditions, which resulted in the loss of control of the airplane, impact with a snow bank, and a nose over.NTSB LAX95LA110Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Corona, CAthe pilot's failure to maintain runway alignment after aborting a takeoff and improper use of the brakes during the abort.NTSB FTW95LA110Accident · No injuriesLimited investigationFinal reportCessna 172M · Boulder, COThe pilot's premature rotation.