NTSB investigations: Cessna 172N, 1990
46 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
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\") = 1990
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") = 1990
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 LAX91LA063Accident · No injuriesLimited investigationFinal reportCessna 172 · Tucson, AZBoth pilots used poor visual lookout procedures.NTSB LAX91LA060Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Yucca Valley, CAThe pilot's improper use of the flaps. Contributing to this accident was the loss of control during tailwind landing, and his tailwind and the pilot's inadequate inflight planning.NTSB FTW91LA020Accident · No injuriesLimited investigationFinal reportCessna 172N · Plano, TXThe pilot's failure to follow the approved start procedures which resulted in an induction fire and the destruction of the airplane.NTSB MIA91LA038Accident · No injuriesLimited investigationFinal reportCessna 172N · Vero Beach, FLThe failure of the pilot to perfrom a proper landing flare and touchdown resulting in a hard landing.NTSB ATL91LA023Accident · No injuriesLimited investigationFinal reportCessna 172N · Chamblee, GAPilot's failure to maintain adequate wingtip clearance during taxi.NTSB CHI91LA023Accident · No injuriesLimited investigationFinal reportCessna 172 · Fort Scott, KSThe mixture control was set incorrectly resulting in fuel starvation, and the check list was not followed by the cfi/pic.NTSB BFO91LA009Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Elkton, VAThe pilot's failure to use carburetor heat which resulted in a reduction in engine power. A factor was the rough terrain.NTSB FTW91LA011Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Abilene, TXPilot's failure to compensate for gusty wind condition.NTSB CHI91LA017Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Portage, WIThe PIC became lost and disorientated and performed a premature precautionary landing.NTSB FTW91LA008Accident · No injuriesLimited investigationFinal reportCessna 172N · Grand Prairie, TXThe student pilot's improper flare technique and use of rudder.NTSB NYC91LA009Accident · No injuriesLimited investigationFinal reportCessna 172N · Dayton, OHA carburetor fire due to an engine backfire. A factor relating to the accident was improper remedial action taken by the pilot to extinguish the engine fire.NTSB ATL91LA001Accident · No injuriesLimited investigationFinal reportCessna 172N · Valdosta, GAThe student pilot's failure to maintain directional control during a takeoff attempt. Factors to the accident were the student's overall lack of flight experience, and the reported wind gust.NTSB SEA90LA199Accident · 2 fatalLimited investigationFinal reportCessna 172N · Neilton, WAThe failure of the crew to maintain adequate clearance from the terrain. Factors to the accident were mountainous and box canyon terrain.NTSB LAX90LA333Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Reno, NVThe pilot's failure to maintain sufficient airspeed resulting in an inadvertent stall. A factor in the accident was the strong crosswind conditions.NTSB LAX90LA337Accident · No injuriesLimited investigationFinal reportCessna 172 · Fresno, CAThe pilot misjudged the flare altitude and failed to properly recover from a bounced landing.NTSB CHI90FA263Accident · 2 fatalField investigationFinal reportCessna 172N · Paris, ILThe pilot's continuation of VFR flight into instrument meteorological conditions. Factors contributing to the accident were the fog and the dark night.NTSB SEA90LA191Accident · No injuriesLimited investigationFinal reportCessna 172N · Dillon, MTPilot misjudged the flare that resulted in a bounced landing.NTSB CHI90FA252Accident · 1 fatalField investigationFinal reportCessna 172N · Pine City, MNThe pilot's misjudgement of the fuel supply, and his failure to maintain adequate airspeed. A factor was the pilot's lack of experience in the make and model of aircraft.NTSB FTW90LA174Accident · Minor injuriesLimited investigationFinal reportCessna C172N · Marietta, OKFailure of the pilot to attain the proper climb rate after takeoff resulting in the aircraft colliding with trees at the departure end of the runway. Contribuing to the accident was the pilot in commands failure to account for high density altitude.NTSB DEN90LA179Accident · No injuriesLimited investigationFinal reportCessna 172N · Lakeview, ARThe pilot's failure to maintain alignment during landing.NTSB BFO90LA068Accident · No injuriesLimited investigationFinal reportCessna 172N · Tangier Island, VAThe pilot's improper recovery from a bounced landing and premature raising of the flaps.NTSB NYC90LA175Accident · No injuriesLimited investigationFinal reportCessna 172 · Edinburg, NYThe pilot did not maintain flying speed, the airplane stalled and descended into trees, at the departure end of the runway.NTSB SEA90LA134Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Yamhill, ORThe pilot's failure to retract the flaps during go-around.NTSB LAX90FA244Accident · 1 fatalField investigationFinal reportCessna 172N · Avalon, CAThe pilot's improper in-flight planning, decision, and his intentional low flying near mountainous terrain. Contributing factors related to the pilot's not maintaining/following proper VFR procedures, the related distraction of the open cabin door, and the…NTSB FTW90FA126Accident · Minor injuriesField investigationFinal reportCessna C172 · Fort Worth, TXFailure of the pilot to follow published procedures when he elected to take-off with full flaps.NTSB LAX90LA232Accident · No injuriesLimited investigationFinal reportCessna 172N · Van Nuys, CAThe pilot's failure to maintain directional control of the aircraft during the attempted go around. A factor in the accident was the failure of the pilot to follow the go around procedures specified in the aircraft flight manual.NTSB DEN90LA126Accident · No injuriesLimited investigationFinal reportCessna 172 · Boulder, COThe pilot's failure to touch down at the proper point, his misjudgment of the distance required for takeoff following the touch and go, and his delayed decision to abort the takeoff.NTSB FTW90LA115Accident · No injuriesLimited investigationFinal reportCessna 172N · Chandeleur Isld, LAMinimum airspeed required for flight (vs) was not maintained. Contributing factors were the pilot's fatigued condition, and premature lift off.NTSB CHI90LA143Accident · No injuriesLimited investigationFinal reportCessna 172N · Northwood, OHThe pilot's improper in-flight planning/decision, which resulted in an off-airport landing, when the engine lost power due to fuel exhaustion. The fact that the engine lost power over a populated area was a factor in this accident.NTSB CHI90LA134Accident · No injuriesLimited investigationFinal reportCessna 172N · Jeffersonville, INThe engine started for an undetermined reason, when the prop was moved after the pilot experienced an inoperative starter. (Most probably, there was either an isolated/intermittent problem in the ignition system or the pilot did not move the magneto switch…NTSB LAX90LA185Accident · Minor injuriesLimited investigationFinal reportCessna 172A · Novato, CAThe pilot's failure to maintain directional control.NTSB LAX90FA180Accident · 2 fatalField investigationFinal reportCessna 172N · Salinas, CAThe pilot's failure to maintain clearance with terrain while attempting visual flight in instrument meteorological conditions. Self induced pressure to adhere to the proposed flight route in instrument meteorological conditions was a factor.NTSB LAX90LA176Accident · No injuriesLimited investigationFinal reportCessna 172N · Sedona, AZThe failure of the student pilot to maintain an appropriate airspeed during the attempted go-around.NTSB CHI90FA123Accident · 3 fatalField investigationFinal reportCessna 172N · New Richmond, WIFailure of the pilot to maintain sufficient airspeed to avoid a stall/spin. A factor related related to the accident was: the pilot's lack of familiarity with the make and model of aircraft.NTSB CHI90LA120Accident · No injuriesLimited investigationFinal reportCessna 172N · Angola, INFailure of the pilot to maintain directional control of the aircraft, while landing in gusty/crosswind conditions. The adverse wind was a related factor.NTSB DEN90LA101Accident · No injuriesLimited investigationFinal reportCessna 172 · Englewood, COThe pilot landed with a tailwind, and cost control of the airplane during rollout.NTSB SEA90LA069Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Minden, NVThe pilot's poor inflight planning and decision.NTSB LAX90FA123Accident · 1 fatalField investigationFinal reportCessna 172N · Buena Park, CAThe pilot not maintaining the prescribed minimum descent altitude during an instrument approach.NTSB SEA90LA053Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Juneau, AKThe pilot did not maintain directional control of the airplane during the initial climb and did not adequately correct the situation prior to colliding with an object.NTSB BFO90FA032Accident · 2 fatalField investigationFinal reportCessna 172N · Bedford, VAThe pilot's decision to fly into known adverse weather conditions and his failure to maintain clearance above the terrain. Contributing to the accident was the pilot's self induced pressure, low ceilings, mountainous terrain and rain.NTSB ATL90FA081Accident · 2 fatalField investigationFinal reportCessna 172N · Montezuma, GAThe failure of the pilot to maintain sufficient airspeed during the takeoff.NTSB ATL90LA077Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Ocilla, GAThe aircraft's encounter with low level windshear resulting in an uncontrollable descent.NTSB FTW90LA081Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Bastrop, LAFailure of the pilot to maintain adequate airspeed for a go-around, which resulted in an inadvertent stall. Factors related to the accident were: the unfavorable wind condition and turbulence.NTSB FTW90LA080Accident · No injuriesLimited investigationFinal reportCessna 172N · Arlington, TXInstructor pilot's inadequate preflight procedures and failure to assure an adequate fuel supply for the proposed flight which led to the ensuing engine failure due to fuel exhaustion. Factors in the accident were the left fuel gauge's erroneous quantity…NTSB MIA90LA080Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Clearwater, FLThe pilot's improper flare and improper recovery from a bounced landing, which resulted in a porpoise and loss of aircraft control. Factors related to the accident were: the gusty crosswind, and failure of the pilot to maintain runway alignment.NTSB BFO90LA022Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Gaithersburg, MDInadequate supervision by the instructor pilot (CFI), which resulted in failure to maintain airspeed and a subsequent stall. Factors related to the accident were: gusty/crosswind conditions, the student pilot's inadequate compensation for wind conditions and…