NTSB investigations: Cessna 172N, 1996
37 cases on aircraft the registry lists as Cessna 172N. 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
| 1965 | 1 |
|---|---|
| 1966 | 2 |
| 1967 | 2 |
| 1975 | 1 |
| 1976 | 2 |
| 1977 | 26 |
| 1978 | 62 |
| 1979 | 81 |
| 1980 | 107 |
| 1981 | 86 |
| 1982 | 91 |
| 1983 | 53 |
| 1984 | 55 |
| 1985 | 40 |
| 1986 | 44 |
| 1987 | 42 |
| 1988 | 47 |
| 1989 | 45 |
| 1990 | 46 |
| 1991 | 57 |
| 1992 | 40 |
| 1993 | 51 |
| 1994 | 43 |
| 1995 | 48 |
| 1996 | 37 |
| 1997 | 40 |
| 1998 | 37 |
| 1999 | 46 |
| 2000 | 35 |
| 2001 | 32 |
| 2002 | 43 |
| 2003 | 32 |
| 2004 | 38 |
| 2005 | 26 |
| 2006 | 23 |
| 2007 | 21 |
| 2008 | 21 |
| 2009 | 20 |
| 2010 | 23 |
| 2011 | 22 |
| 2012 | 14 |
| 2013 | 20 |
| 2014 | 15 |
| 2015 | 10 |
| 2016 | 24 |
| 2017 | 19 |
| 2018 | 14 |
| 2019 | 16 |
| 2020 | 25 |
| 2021 | 15 |
| 2022 | 16 |
| 2023 | 20 |
| 2024 | 13 |
| 2025 | 15 |
| 2026 | 11 |
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\") = 1996
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072434'))
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") = 1996
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072434'))
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 IAD97LA036Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Manville, NJThe pilot's failure to perform a go-around, and his failure to retract the flaps in increments.NTSB MIA97LA030Accident · No injuriesLimited investigationFinal reportCessna 172N · Olive Branch, MSthe pilot's improper flare and improper recovery from a ballooned/bounced landing. The gusty wind was a related factor.NTSB MIA97LA007Accident · No injuriesLimited investigationFinal reportCessna 172N · Fruitland Park, FLThe pilot's inadequate compensation for wind conditions and failure to maintain proper runway alignment during takeoff. The unfavorable wind condition was a related factor.NTSB NYC97LA001Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Coudersport, PAthe pilot's improper in-flight planning/decision, and his failure to ensure that adequate airspeed would be maintained, while maneuvering at low altitude to photograph a residence. The rising terrain and lack of altitude were related factors.NTSB NYC96LA184Accident · No injuriesLimited investigationFinal reportCessna 172N · Shirley, NYthe pilot's prematurely retraction of flaps during the go-around, which resulted in settling (mushing) of the airplane and a collision with the ground.NTSB LAX96LA324Accident · No injuriesLimited investigationFinal reportCessna 172N · Auburn, CAthe pilot's misjudged landing flare and improper bounced landing recovery. A contributing factor was his lack of recent flying experience.NTSB CHI96LA302Accident · No injuriesLimited investigationFinal reportCessna 172 · Greenwood, ILthe pilot's failure to obtain a proper touchdown point.NTSB LAX96LA304Accident · No injuriesLimited investigationFinal reportCessna 172N · Fullerton, CAthe pilot's misjudged glide path and delayed remedial action by not promptly initiating a go-around. A contributing factor was the pilot's lack of experience flying the airplane.NTSB SEA96LA183Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Enumclaw, WAfailure of the engine magneto drive, which resulted in a loss of engine power. The lack of suitable terrain for a forced landing was a related factor.NTSB ATL96LA118Accident · No injuriesLimited investigationFinal reportCessna 172N · Nashville, TNinadequate annual inspection by other maintenance personnel and inadequate pre-flight inspection by the pilot.NTSB MIA96LA199Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Victoria, MSThe pilot's improper fuel management resulting in a total loss of engine power due to fuel exhaustion.NTSB LAX96LA283Accident · No injuriesLimited investigationFinal reportCessna 172 · Boulder City, NVa loss of directional control due to the student pilot's inadequate compensation for wind conditions and improper remedial action. Factors in the accident were crosswinds, inadvertent brake application, and failure to use the ailerons.NTSB IAD96LA120Accident · No injuriesLimited investigationFinal reportCessna 172 · Stowe, VTfailure of the pilot to follow proper IFR procedures and to maintain proper terrain clearance (altitude) during an NDB approach. Factors related to the accident were: the pilot's lack of instrument experience, low ceiling, and mountainous terrain.NTSB LAX96LA274Accident · No injuriesLimited investigationFinal reportCessna 172N · Daggett, CAThe fracture and separation of an exhaust valve head for undetermined reasons.NTSB ATL96LA100Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Hillsborough, NCThe failure of the magneto impulse coupling spring. A factor was the power line at the approach end of the forced landing site.NTSB NYC96LA136Accident · No injuriesLimited investigationFinal reportCessna 172N · Newry, PAfailure of the pilot to identify the inoperative airspeed indication and abort the takeoff, while there was sufficient runway remaining; excessive speed during the approach/landing; and the pilot's failure to perform a go-around after not attaining a proper…NTSB CHI96LA227Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Cottage Grove, WIthe pilot's failure to maintain directional control of the airplane during landing. A factor was the delayed go-around.NTSB LAX96LA235Accident · No injuriesLimited investigationFinal reportCessna 172N · Avalon, CAthe pilot's failure to initiate a landing flare, which resulted in a bounced landing and porpoise, and his loss of directional control during an attempt to initiate a go-around with insufficient airspeed, which resulted in an inadvertent stall/mush and…NTSB ATL96FA094Accident · 1 fatalField investigationFinal reportCessna 172N · Arlington, TNThe pilot's failure to maintain clearance above the trees. A factor was the dark night.NTSB FTW96LA246Accident · No injuriesLimited investigationFinal reportCessna 172N · Farmington, NMfailure of the pilot to maintain directional control during a touch-and-go landing, which resulted in a ground swerve and subsequent collision with a parked airplane.NTSB LAX96LA227Accident · No injuriesLimited investigationFinal reportCessna 172N · Prescott, AZThe failure of the pilot to adequately compensate for gusty crosswind conditions, which resulted in loss of aircraft control.NTSB LAX96FA223Accident · 3 fatalField investigationFinal reportCessna 172N · Bermuda Dunes, CAthe pilot's impairment of judgment and performance due to alcohol and drugs (methamphetamine, amphetamine, & marijuana), his excessive maneuvering (pull-up) after making a touch-and-go landing, and his failure to maintain sufficient airspeed, which resulted…NTSB LAX96LA237Accident · No injuriesLimited investigationFinal reportCessna 172N · Ramona, CAthe pilot's misjudged and delayed landing flare, and inadequate recovery technique from a bounced landing (porpoise). Sun glare was a factor in the accident.NTSB IAD96LA084Accident · No injuriesLimited investigationFinal reportCessna 172M · Findlay, OHthe student pilot's misjudged flare during landing.NTSB CHI96LA156Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Crystal Lake, ILthe pilot not flying a proper glidepath for the displaced runway threshold.NTSB FTW96LA182Accident · No injuriesLimited investigationFinal reportCessna 172N · Broomfield, COthe student pilot's inadequate compensation for wind conditions, and his failure to obtain/maintain directional control. A factor was the cross wind.NTSB CHI96LA140Accident · No injuriesLimited investigationFinal reportCessna 172 · Dekalb, ILThe flight instructor's inadequate supervision, and his delay in taking remedial action to regain directional control of the airplane. Factors relating to the accident were: the student's improper flare for landing, improper recovery from a bounced landing,…NTSB CHI96LA136Accident · No injuriesLimited investigationFinal reportCessna 172N · Middleton, WIfailure of the pilot to maintain directional control of the airplane during the landing, which resulted in an inadvertent ground swerve. Factors relating to the accident were: the gusty crosswind condition, the pilot's excessive lowering of flaps, and the…NTSB SEA96LA083Accident · No injuriesLimited investigationFinal reportCessna 172 · Cheyenne, WYthe pilot's improper flare during the landing and improper recovery from the subsequent bounced landing. A factor relating to the accident was: the pilot's failure to maintain the proper approach path during the approach for landing.NTSB MIA96LA105Accident · No injuriesLimited investigationFinal reportCessna 172N · New Smyrna Bch, FLThe student pilot's improper flare and improper recovery from a bounced landing, which resulted in an inadvertent porpoise, and subsequent overload failure of the nose gear.NTSB ANC96LA029Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Ketchikan, AKloss of engine power for undetermined reason(s). A factor relating to the accident was: the lack of a suitable area for an emergency landing.NTSB SEA96LA063Accident · Minor injuriesLimited investigationFinal reportCessna 172 · West Jordan, UTimproper installation of the airplane's carburetor fuel lines by maintenance personnel.NTSB FTW96LA134Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Austin, TXthe partial loss of engine power due to the failure of the #3 connecting rod. A factor was the lack of suitable terrain for the forced landing.NTSB LAX96FA115Accident · 3 fatalField investigationFinal reportCessna 172N · Julian, CAthe pilot's delay in requesting assistance to avoid high terrain. Factors were: the downdrafts, mountainous terrain, and the pilot's improper in-flight planning.NTSB FTW96LA104Accident · No injuriesLimited investigationFinal reportCessna 172N · Norman, OKthe student pilot's improper level-off during landing.NTSB CHI96LA075Accident · No injuriesLimited investigationFinal reportCessna 172N · Grand Forks, NDthe pilot's failure to maintain control of the airplane while taxiing. Factors in the accident were the icy condition of the taxiway and the high gusting wind.NTSB MIA96LA060Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Lantana, FLLoss of engine power for an undetermined reason, while over water, which resulted in a forced landing/ditching at sea.