NTSB investigations: Cessna 172M, 1992
31 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\") = 1992
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") = 1992
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 LAX93FA068Accident · 3 fatalField investigationFinal reportCessna 172M · Laie, HIThe pilot's inadvertent flight into a mountainous area where he lost visual reference to illuminated ground features which resulted in his becoming disoriented. Factors which contributed to the accident were: 1) the dark sky and low cloud conditions; 2) the…NTSB FTW93FA039Accident · 1 fatalField investigationFinal reportCessna 172M · Snook, TXThe pilot's intentional flight into instrument meteorological conditions as a result of his alcoholic and drug impairment of efficiency and judgement. Factors contributing to the accident were: the pilot's failure to obtain weather information, the dark night…NTSB SEA93LA024Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Vancouver, WAThe pilot's inability to see birds due to darkness.NTSB SEA93LA021Accident · No injuriesLimited investigationFinal reportCessna 172M · Olympia, WAThe pilot's poor inflight decision, and excessive airspeed on final. Factors include a wet turf runway, and trees adjacent to the runway.NTSB NYC93LA035Accident · No injuriesLimited investigationFinal reportCessna 172M · Mallory, WVThe pilot failed to maintain control of the airplane, which resulted in the airplane departing the runway and striking a tree.NTSB MIA93WA008Accident · No injuriesForeign investigationCessna 172M · Mayaguana Isl, BahamasNTSB DEN93LA019Accident · No injuriesLimited investigationFinal reportCessna 172 · Colorado Spring, COProper descent rate was not maintained by the pilot in command which resulted in a hard landing.NTSB LAX93FA007Accident · 1 fatalField investigationFinal reportCessna 172M · Fairfield, CAThe pilot's delay in initiating a go-around during a night landing. Factors related to the accident were: the pilot misjudging distance and speed resulting a overshooting the touchdown, the night light condition, his lack of night flying experience in a…NTSB DEN93LA004Accident · No injuriesLimited investigationFinal reportCessna 172N · Addison, TXThe attempt by both pilots to pass each other without adequate clearance between their airplanes.NTSB MIA92LA185Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Picayune, MSThe pilot in command's failure to maintain airspeed (vso) while conducting slow flight at a low altitude. This resulted in an in flight loss of control (stall) and subsequent in flight collision with trees.NTSB DEN92FA093Accident · 1 fatalField investigationFinal reportCessna 172M · Evanston, WYLoss of control for undetermined reasons.NTSB ATL92LA178Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Boone, NCThe pilot's failure to abort the take off, and his abrupt pull up with insufficient airspeed to continue flight. Factors were the inadequate airspeed and the inadvertent stall.NTSB MIA92LA171Accident · No injuriesLimited investigationFinal reportCessna 172M · Hernando, MSThe failure of the pilot in command to compensate for the crosswind condition, resulting in a ground loop. Contributing to the accident was the pilot's lack of experience in the type of aircraft.NTSB BFO92LA120Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Mount Vernon, OHThe pilot's failure to maintain airspeed which resulted in a stall.NTSB BFO92LA111Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Charleston, WVThe pilot's failure to attain adequate airspeed to outclimb obstacles.NTSB ANC92LA110Accident · No injuriesLimited investigationFinal reportCessna 172 · Twin Hills, AKThe pilot in command not following the procedures outlined in the pilot's operating handbook.NTSB BFO92LA097Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Bedford, PAThe pilot failed to maintain adequate airspeed which resulted in a stall.NTSB CHI92FA201Accident · 4 fatalField investigationFinal reportCessna 172N · St Paul, MNInadequate visual lookout by the pilots of both airplanes, which resulted in their failure to see-and-avoid conflicting traffic, and failure of the relieving controllers to use the radar display to identify and sequence an airplane entering the pattern.…NTSB CHI92LA168Accident · No injuriesLimited investigationFinal reportCessna 172M · Hastings, MIThe pilot-in-command's misjudgement of the touchdown point which resulted in an undershoot and damage to the elevator. In addition, the pilot-in-command failed to properly inspect the airplane for damage prior to further flight.NTSB ANC92LA089Accident · No injuriesLimited investigationFinal reportCessna 172 · Anchorage, AKInadequate visual look out by the pilot of both aircraft. Contributing to the accident were the pilot's diverted attention, the other moving aircraft/object (c 172), and the excessive taxi speed of the c 172.NTSB NYC92LA105Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Buffalo, NYThe pilot's failure to maintain airspeed during a go around, which resulted in an inadvertent stall and in flight collision with terrain. Contributing to the accident was the pilot delayed the go around and lack of recent flight expereince.NTSB NYC92LA104Accident · No injuriesLimited investigationFinal reportCessna 172N · Dexter, MEA failure of the top torque link bolt on the nose landing gear which resulted in a landing with a flat strut and misaligned wheel.NTSB CHI92LA151Accident · No injuriesLimited investigationFinal reportCessna 172M · Climax Springs, MODelay in aborting the landing by the pilot in command.NTSB FTW92LA124Accident · No injuriesLimited investigationFinal reportCessna 172M · Canton, TXThe pilot's failure to maintain adequate airspeed and directional control during the attempted go around following an encounter with adverse wind conditions on approach.NTSB BFO92LA053Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Amelia, VAThe pilot's misjudgement of distance and altitude that resulted in an landing overrun and collision with an embankment. Contributing was failure to initiate a go around and inadequate supervision.NTSB SEA92FA083Accident · 1 fatalField investigationFinal reportCessna 172M · Shaw Island, WAA delayed go-around, and procedures not being followed. Factors include a lack of total experience in this type of operation, trees near the runway, and an uphill runway slope.NTSB FTW92LA114Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Stuttgart, ARThe pilot's failure to compensate for wind conditions. Factors were the crosswind and the downdraft.NTSB CHI92LA121Accident · No injuriesLimited investigationFinal reportCessna 172M · Osage Beach, MOThe pilot-in-command's failure to use all th eavailable runway and his misjudgment of the proper touchdown point during landing.NTSB 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 CHI92LA099Accident · No injuriesLimited investigationFinal reportCessna 172 · Manhattan, KSThe pilot's failure to refuel the airplane. A factor related to the accident was the rough terrain on which the landing was made.NTSB NYC92LA069Accident · No injuriesLimited investigationFinal reportCessna 150 · Sanford, METhe failure of the pilot of N64147 to maintain adequate spacing and visual lookout from N6544G while taxiing, resulting in a ground collision.