NTSB investigations: Cessna 172M, 1991
36 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 | 9 |
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\") = 1991
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") = 1991
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 CHI92FA062Accident · 2 fatalField investigationFinal reportCessna 172M · Sanford, MIThe pilot-in-command's failure to maintain a visual lookout to avoid a wire strike. Factors were the pilot-in-command's intentional low level flight, his failure to maintain proper altitude, and the transmission wires.NTSB NYC92LA046Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Lockport, NYAn inadvertent stall during an attempted go-around by the second pilot. Factors related to the accident were improper use of the flight controls by both pilots and the second pilot's attempted control of the airplane.NTSB SEA92FA022Accident · Serious injuriesField investigationFinal reportCessna 150E · Vancouver, WAInadequate visual lookout on the part of the pilot as well as both the flight instructor and student of the other aircraft. A factor contributing to the accident was the other pilot's lack of landing light usage.NTSB DEN92LA009Accident · No injuriesLimited investigationFinal reportCessna 172N · Boulder, COFailure of the pilot to maintain clearance from the sign.NTSB CHI92LA029Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Howell, MIProper glidepath was not maintained resulting in an undershoot. A factor related to the accident was dark night flying conditions.NTSB LAX92FA043Accident · 3 fatalField investigationFinal reportCessna 172M · Carmel Valley, CAThe pilot's failure to maintain a safe altitude above the ground during an intentional low altitude flight in mountainous terrain. Contributing factors related to the pilot becoming distracted while flying over the ground and to his failure to initiate a…NTSB FTW92LA017Accident · No injuriesLimited investigationFinal reportCessna 172M · Springer, NMThe pilot's poor judgement in attempting flight into forcasted adverse weather, his disregard for the hazardous weather advisory received which resulted in partial loss of engine power as a result of a blocked induction system due to ice and snow, and the…NTSB SEA92LA010Accident · No injuriesLimited investigationFinal reportCessna 172C · Colville, WAThe pilot's delayed go-around. Factors contributing to the accident was the pilot's misjudgement of distance and speed during the approach.NTSB DEN92LA002Accident · No injuriesLimited investigationFinal reportCessna 172M · Erie, COThe pilot's failure to maintain directional control land his inadequate compensation for wind conditions. Factors were: crosswind conditions and the pilot's total lack of experience.NTSB ANC92FA002Accident · No injuriesField investigationFinal reportCessna 172M · Bethel, AKA power loss over unsuitable terrain which resulted in a nose over.NTSB BFO91LA086Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Grayson, KYThe pilot's failure to maintain control of the aircraft during the attempted go-around.NTSB NYC91LA236Accident · No injuriesLimited investigationFinal reportCessna 172M · Norwood, MAPremature retraction of the wing flaps during a go-around which resulted in an inadvertent stall with insufficient altitude for recovery. Factors related to the accident were: the pilot's lack of total experience in make and model, and lack of recent…NTSB CHI91FA254Accident · 2 fatalField investigationFinal reportCessna 172M · Ottumwa, IAImproper IFR procedure by the pilot by not maintaining the proper minimum descent altitude (mda) until established on the ILS localizer and glidepath.NTSB ATL91LA146Accident · No injuriesLimited investigationFinal reportCessna C172M · Mc Minnville, TNThe failure of the pilot to maintain cleearance from obstacles during the final approach to landing.NTSB NYC91FA188Accident · Serious injuriesField investigationFinal reportCessna 172M · Phillips, MEAn inadvertent stall and loss of control due to the pilot's improper use of the wing flaps for takeoff. Factors related to the accident were: the pilot's misunderstanding of airplane performance, and the pilot's decision to takeoff uphill.NTSB SEA91LA192Accident · No injuriesLimited investigationFinal reportCessna 172M · Little Rock, WAA delayed go-around, and airspeed not being maintained. Factors include the pilot's overconfidence in the aircraft's ability, the pilot's lack of total experience in this type of operation, misjudged clearance, and the use of improper procedure.NTSB LAX91LA296Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Minden, NVThe flight instructor's inadequate supervision of the student pilot during a simulated emergency.NTSB NYC91LA169Accident · No injuriesLimited investigationFinal reportCessna 172 · Millville, OHThe pilot's improper in-flight planning/decision after becoming lost, resulting in engine fuel exhaustion. Factors related to the accident were: the pilot's lack of familiarity with the geographic area, and his lack of experience in this type of operation.NTSB BFO91LA058Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Beckley, WVThe pilot's failure to attain adequate flying speed.NTSB DEN91LA087Accident · No injuriesLimited investigationFinal reportCessna 172M · Keenesburg, COThe pilot's misjudging the approach, and disregard of wind conditions. Factors were: a tailwind condition and the pilot's anxiety.NTSB SEA91LA141Accident · No injuriesLimited investigationFinal reportCessna 172-M · Salem, ORThe pilot's poor in-flight decision and his failure to select a proper touchdown point. Factors include a wet runway, soft terrain and high vegetation.NTSB SEA91LA171Accident · No injuriesLimited investigationFinal reportCessna 172N · Vancouver, WAA hard landing by the pilot due to improper bounced landing recovery.NTSB ATL91LA109Accident · No injuriesLimited investigationFinal reportCessna 172M · Knighdale, NCFailure of the pilot to attain the proper touch down point on the runway and/or perform a go-around.NTSB LAX91LA241Accident · No injuriesLimited investigationFinal reportCessna 172M · Crescent City, CAThe failure of the pilot to employ proper flight control positioning to maintain control of the airplane during taxi.NTSB LAX91LA244Accident · No injuriesLimited investigationFinal reportCessna 172M · Willits, CAThat the pilot misjudged the flare and failed to properly recover from a bounced landing. Contributing to this accident was entering into an inadvertent porpoise.NTSB CHI91LA169Accident · No injuriesLimited investigationFinal reportCessna 172M · Cadillac, MIThe pilot-in-command's maintaining excessive airspeed through the landing touchdown which resulted in overrunning the runway.NTSB MIA91LA149Accident · 1 fatalLimited investigationFinal reportCessna 172M · Missing (Atlantic Ocean)The lose of engine power for undetermined reasons which resulted in a forced landing and ditching in the atlantic ocean.NTSB DEN91FA071Accident · 1 fatalField investigationFinal reportCessna 172M · Wray, COThe pilot intentionally buzzing and failure to maintain proper altitude.NTSB LAX91LA208Accident · No injuriesLimited investigationFinal reportCessna C172M · Coalinga, CAThe pilot's encounter with a dust devil which resulted in his loss of control during landing rollout.NTSB NYC91LA119Accident · No injuriesLimited investigationFinal reportCessna 172M · Bloomvale, NYThe pilot's delay in aborting the takeoff.NTSB FTW91FA060Accident · 2 fatalField investigationFinal reportCessna 172M · Flippin, ARThe pilot's attempted VFR flight in instrument meteorological conditions and his failure to maintain altitude.NTSB SEA91LA082Accident · No injuriesLimited investigationFinal reportCessna 172M · Ogden, UTThe pilot's poorly planned approached for landing. Factors to the accident were: an excessive airspeed, and the inadequacy of the pilot's recovery from a bounced landing.NTSB CHI91LA117Accident · No injuriesLimited investigationFinal reportCessna 172 · Yankton, SDFailure of the pilot to maintain directional control of the aircraft during landing. The adverse wind condition and the pilot's lack of total experience were related factors.NTSB NYC91LA091Accident · No injuriesLimited investigationFinal reportCessna 172M · Leroy, NYThe hard landing made by the pilot. Factors relating to the accident were the decision of the pilot to land on the runway despite the runway lighting system being partially inoperative, and the lack of experience of the pilot at night.NTSB NYC91LA074Accident · No injuriesLimited investigationFinal reportCessna 172M · Easton, PAThe pilot's improperly executed approach, resulting in a landing with excessive airspeed.NTSB NYC91LA070Accident · No injuriesLimited investigationFinal reportCessna 172M · Nashua, NHFuel system contamination by other personnel which resulted in an inflight engine failure and a subsequent forced landing in unsuitable terrain.