NTSB investigations: Cessna 172M, 1998
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
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 year(c.\"eventDate\") = 1998
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") = 1998
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 MIA99LA051Accident · No injuriesLimited investigationFinal reportCessna 172M · Okeechobee, FLThe inadequate visual lookout of the pilot of the Cessna airplane and of the pilot of the glider resulting in the midair collision.NTSB CHI99LA040Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Brainerd, MNThe visual lookout not obtained/maintained by the pilot of the other aircraft. Contributing factors were the unicom frequency not selected and the traffic advisory not issued by the pilot of the other aircraft. An additional factor was the aircraft moving on…NTSB DEN99LA019Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Belen, NMThe pilot's inadequate preflight planning, resulting in fuel supply exhaustion.NTSB NYC99LA021Accident · No injuriesLimited investigationFinal reportCessna 172M · Cumberland, MDThe pilot's decision to land, instead of performing a go-around.NTSB FTW99FA006Accident · 1 fatalField investigationFinal reportCessna 172M · Oklahoma City, OKSuicide.NTSB ATL99WA010Accident · 4 fatalForeign investigationCessna 172M · Freeport, BahamasNTSB NYC98LA189Accident · No injuriesLimited investigationFinal reportCessna 172M · Teterboro, NJThe pilot's failure to maintain control of the airplane. Factors in this accident were the night light conditions, and pilot's lack of recent night flight experience.NTSB FTW98LA387Accident · No injuriesLimited investigationFinal reportCessna 172M · Englewood, COThe pilot's failure to maintain directional control during landing. Factors were the runway light and the terrain conditions.NTSB LAX98LA253Accident · No injuriesLimited investigationFinal reportYakovlev YAK-55M · Lincoln, CAThe pilot of the other aircraft's inadequate visual lookoutNTSB FTW98LA335Accident · No injuriesLimited investigationFinal reportCessna 172M · Franktown, COFlight at an altitude insufficient to clear terrain. Factors were the pilot's failure to reset or correct a precessing directional gyro, his becoming lost/disoriented, and dark night light conditions.NTSB CHI98FA274Accident · 1 fatalField investigationFinal reportCessna 172M · Brooklyn, MIThe proper touchdown point was not attained and the visual lookout not being maintained by the pilot-in-command. Contributing factors to the accident were the unmarked static and transmission wires.NTSB IAD98LA076Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Somerset, KYthe pilot's failure to follow procedures to hand-prop the airplane.NTSB CHI98LA237Accident · No injuriesLimited investigationFinal reportCessna 172M · Chesterfield, MOthe pilot's not obtaining and maintaining directional control. A factor was wet terrain (grass).NTSB CHI98LA225Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Flushing, MIwas a delayed go-around maneuver by the pilot. Factors associated with this accident were the pilot misjudging his final approach altitude and glide path, having inadequate altitude to clear the trees at the end of the runway, and inadequate training on how…NTSB NYC98LA134Accident · No injuriesLimited investigationFinal reportCessna 172 · Westminster, MDthe pilot's misjudgment of distance and speed during the approach/landing, and his delay in initiating a go-around. The quartering tailwind was a related factor.NTSB IAD98FA072Accident · 1 fatalField investigationFinal reportCessna 172M · Hebron, CTThe pilot's failure to obtain a weather briefing which resulted in inadvertent flight into instrument meteorological conditions, and his failure to maintain control of the airplane due to spatial disorientation. Factors in this accident were low ceilings and…NTSB FTW98LA219Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Albuquerque, NMThe flight instructor's failure to maintain directional control of the aircraft. Factors were crosswind, high wind conditions, insufficient demonstrated crosswind component information provided by the manufacturer, and insufficient aircraft…NTSB ANC98FA048Accident · 2 fatalField investigationFinal reportCessna 172M · Palmer, AKThe pilot's intentional flight into known adverse weather conditions. Contributing factors were the terrain induced turbulence, clouds, the pilot's overconfidence in his abilities, and mountainous terrain conditions.NTSB CHI98LA149Accident · No injuriesLimited investigationFinal reportCessna 172M · Elkhart, INthe pilot's disorientation that led him to believe he was on the active runway. A factor was the pilot's inattentiveness.NTSB SEA98LA071Accident · No injuriesLimited investigationFinal reportCessna 172M · Ocean Shores, WAThe pilot's failure to maintain clearance from a light standard (utility pole) just off the edge of the parking ramp. Factors include a light standard placed near the edge of the parking ramp.NTSB LAX98LA143Accident · No injuriesLimited investigationFinal reportCessna 172M · Henderson, NVThe pilot's decision to attempt a landing in crosswind conditions at or above the demonstrated capability of the aircraft, and his subsequent failure to maintain proper runway alignment.NTSB ANC98LA042Accident · No injuriesLimited investigationFinal reportCessna 172M · Anchor Point, AKThe pilot's failure to compensate for a crosswind. A related factor was the crosswind.NTSB CHI98LA141Accident · No injuriesLimited investigationFinal reportCessna 172M · Superior, NEthe pilot's failure to maintain clearance with the sign. Factors associated with the accident were the sign which the airplane contacted and inadequate preflight planning/preparation.NTSB LAX98LA135Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Scottsdale, AZThe pilot's failure to maintain directional control and his inadequate compensation for the wind condition. A contributing factor was the crosswind.NTSB MIA98LA113Accident · No injuriesLimited investigationFinal reportCessna 172M · Kingsport, TNThe dual student's failure to maintain adequate airspeed which resulted in a stall mush. Contributing to the accident were the flight instructor's inadequate supervision and the night conditions.NTSB NYC98LA081Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Weyers Cave, VAthe pilot's inadequate compensation for crosswind conditions and failure to maintain directional control of the airplane during the landing roll, which resulted in an encounter with a fence on uneven terrain and a nose over.NTSB FTW98LA122Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Port Lavaca, TXThe pilot's failure to maintain clearance from the power line. Factors were the gusty winds, the pilots lack of experience in the type of operation, inadequate training and insufficient standards/requirements by the company/operator management, and the power…NTSB FTW98LA118Accident · No injuriesLimited investigationFinal reportCessna 172M · Bulverde, TXThe pilot's failure to maintain the proper glidepath following a total electrical failure resulting from an inoperative voltage regulator. Factors were the dark night conditions, the pilot's lack of experience in night flying, and the trees.NTSB IAD98LA020Accident · No injuriesLimited investigationFinal reportCessna 172M · Blue Bell, PAThe pilot's failure to attain the proper touchdown point, and his failure to make a go-around, while there was sufficient runway remaining.NTSB LAX98FA066Accident · 2 fatalField investigationFinal reportCessna 172M · Chandler, AZThe pilot's intentional flying at a low altitude and failure to see and avoid the power lines during dusk conditions.