NTSB investigations: Cessna 172N, 1995
48 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\") = 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 ('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") = 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 ('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 LAX96LA092Accident · No injuriesLimited investigationFinal reportClassic Waco YMF · Kailua Kona, HIThe failure of the Waco pilot to see and avoid the opposite direction Cessna 172 while both aircraft were taxiing in a non-movement area of the airport. Factors in the accident were: the congested nature of the taxi lane, which limited the Waco pilot's…NTSB SEA96LA035Accident · No injuriesLimited investigationFinal reportCessna 172N · Pacific City, ORThe pilot's delay in aborting the landing, which resulted in his failure to clear the perimeter fence. Factors relating to the accident were: the tailwind, and the pilot's failure to land at the proper touchdown point.NTSB MIA96LA044Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Bryceville, FLThe pilot's improper planning/decision. Factors relating to the accident were: the pilot's inaccurate evaluation of the weather conditions, the pilot becoming lost/disoriented, and the lack of braking action on wet grass during the precautionary landing.NTSB NYC96LA039Accident · No injuriesLimited investigationFinal reportCessna 172N · Sanford, MEthe pilot's failure to adequately compensate for a crosswind during the landing roll, which resulted in a collision with a snowbank. Factors relating to the accident were: ice on the runway and the gusty crosswind condition.NTSB LAX96LA062Accident · No injuriesLimited investigationFinal reportCessna 172N · Winslow, AZthe student pilot's use of an excessive airspeed during the landing approach, which resulted in a hard landing, a porpoise, and a collapse of the nose landing gear.NTSB CHI96LA039Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Stevens Point, WIflying into known icing conditions and descending below the minimum descent altitude.NTSB CHI96LA030Accident · No injuriesLimited investigationFinal reportCessna 172N · Niles, MIfuel exhaustion as a result of the pilot's improper fuel consumption calculations. Factors related to the accident were: the pilot's lack of familiarity with the aircraft and operating with a known malfunctioning fuel gauge.NTSB LAX96LA025Accident · No injuriesLimited investigationFinal reportCessna 172 · Livermore, CAthe pilot's failure to maintain directional control during the landing roll. A contributing factor was the rough/uneven terrain.NTSB SEA96LA009Accident · No injuriesLimited investigationFinal reportCessna 172N · Laurel, MTthe student pilot's improper planning/decision, which resulted in inadequate altitude/clearance from hangar buildings and a subsequent emergency landing, while attempting to evade a flock of geese. The flock of geese was a related factor.NTSB LAX96LA006Accident · No injuriesLimited investigationFinal reportCessna 172N · Tucson, AZthe pilot's inadequate compensation for the existing tailwind conditions, improper flare, and failure to maintain directional control.NTSB FTW96LA010Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Crockett, TXfailure of both magnetos to operate properly due to inadequate maintenance by other maintenance personnel. A factor was the lack of suitable terrain available for the forced landing.NTSB NYC96FA002Accident · 2 fatalField investigationFinal reportCessna 172N · Caton, NYThe pilot's improper IFR procedure by failing to maintain proper altitude, while on the initial approach for an ILS. A factor relating to the accident was: failure of the tower controller to issue a safety advisory.NTSB FTW95LA386Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Kerrville, TXthe pilot's inadequate preflight preparation and his failure to use all the available runway. A factor was the dark night.NTSB ANC95LA160Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Glennallen, AKImproper planning/decision by the pilot, which resulted in fuel exhaustion, due to an inadequate supply of fuel. A factor relating to the accident was: the lack of suitable terrain for an emergency landing.NTSB FTW95LA375Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Bonham, TXThe partial loss of engine power for undetermined reasons. Factors were the high density altitude and lack of suitable terrain for the forced landing.NTSB FTW95LA374Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Colorado Spgs, COBlockage of the carburetor by a piece of foreign material, which resulted in a loss of engine power, and failure of the pilot to maintain airspeed, which resulted in an inadvertent stall. The high density altitude and the pilot's failure to properly lean the…NTSB CHI95LA297Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Clarkston, MIthe pilot's failure to refuel.NTSB NYC95LA193Accident · No injuriesLimited investigationFinal reportCessna 172 · Fulton, NYthe pilot misjudged the flare, resulting in a hard landing and subsequent collapse of the nose gear.NTSB LAX95LA266Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Carlsbad, CAThe pilot's poorly planned approach, misjudged distance/altitude, and failure to make a go-around. The pilot inadvertently becoming lost and disoriented was a factor in this accident.NTSB LAX95LA256Accident · No injuriesLimited investigationFinal reportCessna 172N · Napa, CAthe pilot's failure to maintain directional control of the aircraft after one foot slipped off the rudder pedals, and his inadvertent application of asymmetrical brake forces.NTSB NYC95LA150Accident · No injuriesLimited investigationFinal reportCessna 172N · Stormville, NYThe reported pothole in the runway.NTSB ANC95LA085Accident · No injuriesLimited investigationFinal reportCessna 172 · Delta Junction, AKThe pilot's improper compensation for the wind conditions which resulted in dragging the right wing and shearing off the nose gear.NTSB CHI95LA195Accident · No injuriesLimited investigationFinal reportCessna 172 · St Cloud, MNThe pilot's improper inflight planning/decision, which resulted in continued flight into adverse weather. Factors relating to the accident were: the thunderstorm outflow, and inadequate weather evaluation by the pilot.NTSB BFO95LA069Accident · No injuriesLimited investigationFinal reportCessna 172N · Factoryville, PAthe loss of engine power for undetermined reasons, and the subsequent hard landing by the student pilot.NTSB LAX95FA217Accident · 1 fatalField investigationFinal reportCessna 172N · Vidal Junction, CAThe pilot's failure to maintain an altitude adequate to avoid the mountainous/hilly terrain. Contributing to the accident was the glare from the setting sun.NTSB FTW95LA250Accident · No injuriesLimited investigationFinal reportCessna 172N · Houston, TXThe pilot's failure to attain runway alignment. Factors were the pilot's failure to perform a go-around and his lack of total experience in the make and model of airplane.NTSB LAX95LA208Accident · No injuriesLimited investigationFinal reportCessna 172N · North Las Vegas, NVThe pilot's improper recovery from a bounced landing. His misjudgment of the height above the runway during flare was a factor.NTSB LAX95LA323Accident · No injuriesLimited investigationFinal reportCessna 172N · Big Bear, CAthe pilot's failure to maintain directional control during an aborted takeoff attempt, which was necessitated by his failure to properly lean the fuel mixture. The pilot's limited experience in small piston engine airplanes was a factor in the accident.NTSB ATL95LA114Accident · No injuriesLimited investigationFinal reportCessna 172 · Peachtree City, GAThe pilot's failure to maintain an adequate lookout while maneuvering on the ramp which resulted in his misjudging the clearance between his airplane and parked aircraft.NTSB BFO95LA054Accident · No injuriesLimited investigationFinal reportCessna 172N · Head Waters, VAthe pilot's poor planning/decision making in the attempted departure. Contributing factors are the wet, recently mowed grass airstrip, and the embankment/downhill grade encountered during the aborted takeoff.NTSB MIA95LA244Accident · No injuriesLimited investigationFinal reportCessna 172N · Madison, MSThe pilot's improper flare and/or improper recovery from a bounced landing.NTSB LAX95FA198Accident · 4 fatalField investigationFinal reportCessna 172N · Lovelock, NVthe pilot's intentional flight at low altitude and subsequent collision with transmission wires during dusk light conditions.NTSB NYC95LA122Accident · 2 fatalLimited investigationFinal reportCessna 172N · Weston, WVthe pilot's failure to maintain airspeed which resulted in an inadvertent stall, and a subsequent uncontrolled descent and collision with the ground.NTSB LAX95LA182Accident · No injuriesLimited investigationFinal reportCessna 172N · Stockton, CAthe failure of the pilot to properly judge the landing flare, and his improper bounced landing recovery technique, which resulted in a landing gear collapse during a hard landing.NTSB ATL95FA088Accident · 1 fatalField investigationFinal reportCessna 172N · Atlanta, GAThe pilot's impairment of judgment and performance due to a drug, VFR flight into instrument meteorological conditions, and failure to remain clear of the obstacle (towering smoke stack). Factors relating to the accident were: the adverse weather conditions.NTSB CHI95LA132Accident · No injuriesLimited investigationFinal reportCessna 172N · Detroit, MIthe student pilot's failure to maintain directional control during the takeoff ground run. A factor associated with the accident was the soft terrain.NTSB LAX95LA155Accident · No injuriesLimited investigationFinal reportCessna 172N · Phoenix, AZThe use of excessive break-away thrust by the Boeing 737 crew. A factor related to the accident was: improper planning/decision by the Cessna 172 pilot by accepting a clearance to taxi behind the Boeing 737 without assurance that the Boeing 737 crew would not…NTSB ATL95LA072Accident · No injuriesLimited investigationFinal reportCessna 172N · Paris, TNThe failure of the pilots of both aircraft to maintain proper visual lookout during landing at the uncontrolled airport.NTSB MIA95FA094Accident · 2 fatalField investigationFinal reportCessna 172N · Venice, FLIntentional VFR flight into IMC by the pilot-in-command, failure of the pilot to maintain aircraft control, spatial disorientation, and altitude inadequate for recovery following the in flight loss of control.NTSB ANC95LA042Accident · No injuriesLimited investigationFinal reportCessna 172N · Anchorage, AKThe pilot's failure to correct for torque/p factor. The presence of snowberms that narrowed the width of the runway and the pilot's lack of total experience were factors in the accident.NTSB LAX95LA124Accident · No injuriesLimited investigationFinal reportCessna 172 · Prescott, AZfailure of the pilot to maintain directional control.NTSB FTW95LA121Accident · No injuriesLimited investigationFinal reportCessna 172N · Santa Fe, NMThe pilot's delayed landing flare and the improper bounced landing recovery.NTSB CHI95LA110Accident · No injuriesLimited investigationFinal reportCessna 172 · Nevis, MNthe loss of engine power due to a blockage caused by ice. A factor in the accident was the snow.NTSB MIA95FA070Accident · 2 fatalField investigationFinal reportCessna 172N · Mintonville, KYThe flightcrew's intentional VFR flight into known instrument meteorological conditions. A factor was the inadequate altitude to prevent an inadvertent collision with an obstruction.NTSB MIA95WA059Accident · No injuriesForeign investigationCessna 172N · Nevis Island, WNNTSB ATL95LA041Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Meridianville, ALThe failure of the student pilot to maintain directional control of the aircraft.NTSB CHI95LA067Accident · No injuriesLimited investigationFinal reportCessna 172N · Kansas City, MOAn improper recovery from a bounced landing. Factors associated with the accident were an improper airspeed and not attaining a proper descent rate by the pilot.NTSB SEA95FA037Accident · 3 fatalField investigationFinal reportCessna 172N · Blyn, WAThe pilot's VFR flight into instrument meteorological conditions. Factors in the accident were the weather conditions and the dark night.