NTSB investigations: Cessna 172N, 1989
45 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\") = 1989
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") = 1989
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 MIA90FA046Accident · 1 fatalField investigationFinal reportCessna 172N · Meridian, MSIn flight loss of control by the pilot while flying in instrument meteorological conditions. Contributing factor(s) was: the pilot's apprehension toward instrument flying and the adverse weather conditions that existed at the time.NTSB DEN90LA036Accident · No injuriesLimited investigationFinal reportCessna 172N · Broomfield, COFailure of the pilot to maintain directional control, which resulted in an inadvertent ground swerve. The snowbank was a related factor.NTSB NYC90FA041Accident · 3 fatalField investigationFinal reportCessna 172N · Washington Twp, NJThe failure of the pilot to properly pre-flight plan and execute the VFR flight. Factor's related to the accident were: the pilot's inexperience; no visual cues (lights) due to dark night conditions; the pilot's disregard of the weather briefing.NTSB SEA90FA027Accident · 2 fatalField investigationFinal reportCessna 172N · Nordland, WAUndetermined.NTSB LAX90LA051Accident · No injuriesLimited investigationFinal reportCessna 172 · Monterey, CAPilot misjudged clearance between the aircraft's wing tip & the fuel truck. A factor related to the accident was: the proximity of the vehicle (fuel truck).NTSB CHI90LA041Accident · No injuriesLimited investigationFinal reportCessna 172N II · Middleton, WIThe pilot's improper use of flaps to provide lift on short final approach instead of applying power and the failure to maintain aircraft control.NTSB NYC90LA017Accident · Minor injuriesLimited investigationFinal reportCessna T172N · Townsend, MAThe pilot's failure to use carburetor heat during weather conditions favorable to carburetor icing. A contributing factor was the lack of suitable terrain.NTSB ATL90LA012Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Knightdale, NCThe pilot's failure to maintain the proper glide path to the runway resulting in the airplane colliding with trees while making an approach to landing with no electrical power.NTSB ATL90LA020Accident · No injuriesLimited investigationFinal reportCessna 172N · Valdosta, GAInadequate visual lookout by the pilot (failure to see & avoid the obstruction). Contributing factors were the transmission (power) line and lack of visual cues (pilot's visual perception).NTSB ATL90FA008Accident · 2 fatalField investigationFinal reportCessna 172N · Eddyville, KYThe pilot continuing VFR flight into adverse weather conditions. Contributing factor(s) was: low ceiling and rain.NTSB ATL90LA006Accident · No injuriesLimited investigationFinal reportCessna 172 · Ridgeland, SCThe pilot misjudged the airspeed and failed to attain the proper touchdown point.NTSB MIA89FA253Accident · 2 fatalField investigationFinal reportCessna 172N · Ochopee, FLThe failure of the pilots of both airplanes to see and avoid each other while maneuvering.NTSB LAX89LA325Accident · No injuriesLimited investigationFinal reportCessna 172 · Phoenix, AZThe pilot misjudged clearance between the wingtip and the blast deflector shield. The proximity of the shield was a related factor.NTSB MKC89FA197Accident · Serious injuriesField investigationFinal reportCessna 172N · Hyannis, NEFailure of the pilot to maintain sufficient altitude. Darkness and adverse weather conditions were related factors.NTSB LAX89FA318Accident · No injuriesField investigationFinal reportCessna 152 · Chandler, AZThe failure of the pilot's of both aircraft to maintain adequate visual outlook for other aircraft.NTSB DEN89FA222Accident · 2 fatalField investigationFinal reportCessna 172N · Afton, WYThe non-instrument rated pilot's continued flight into instrument meteorological conditions (IMC) and his failure to maintain sufficient altitude to clear the terrain. Factors related to the accident were: darkness, adverse weather conditions, and…NTSB FTW89LA165Accident · No injuriesLimited investigationFinal reportCessna 172N · Waxahachie, TXFailure of the #3 exhaust valve due to exposure to overtemperature operating conditions.NTSB MIA89LA245Accident · No injuriesLimited investigationFinal reportWaco UPF-7 · Key West, FLInadequate visual lookout by the Waco pilot, which resulted in his misjudgement of clearance between his aircraft and the Cessna 172 and a subsequent collision.NTSB NYC89LA214Accident · No injuriesLimited investigationFinal reportCessna 172N · Bayport, NYThe pilot's misjudging speed and distance resulting in his overshooting the landing and running off the end of the runway.NTSB DEN89LA212Accident · No injuriesLimited investigationFinal reportCessna 172N · Burlington, COImproper use of the rudder by the pilot, which resulted in a loss of directional control. The soft terrain was a related factor.NTSB MIA89LA235Accident · No injuriesLimited investigationFinal reportCessna 172N · Madison, MSThe pilot's improper flare and improper recovery from a bounced landing, which resulted in porpoising of the aircraft and an uncontrolled ground swerve.NTSB MIA89LA234Accident · No injuriesLimited investigationFinal reportCessna 172N · Jacksonville, FLInadequate visual lookout by the pilot. Factors related to the accident were: dark night, light pole with an inoperative light, and the lack of visual perception concerning the pilot's ability to see the pole at night.NTSB CHI89LA166Accident · No injuriesLimited investigationFinal reportCessna 172P · Ravenna, OHFailure of pilot in command to maintain directional control of the airplane while executing a touch-and-go.NTSB LAX89LA273Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Seligman, AZA loss of engine power due to a failure of the number 3 cylinder exhaust valve rocker arm pivot stud, which was in turn caused by a stuck exhaust valve.NTSB MIA89LA207Accident · No injuriesLimited investigationFinal reportCessna 172N · Gainesville, FLThe student's improper flare for landing. The crosswind (quartering headwind) and the student's lack of experience in this aircraft were considered to be contributing factors.NTSB MIA89LA201Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Leesburg, FLFailure of the pilot to maintain adequate airspeed, which resulted in an inadvertent stall as he initiated a go-around.NTSB DEN89LA166Accident · No injuriesLimited investigationFinal reportCessna 172 · Glenwood Spgs, COInadequate compensation for wind conditions by the dual student, resulting in a loss of control and a forced landing. The pilot-in-command, CFI, failed to adequately supervise the operation.NTSB NYC89LA150Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Niagara Falls, NYEngine failure due to oil starvation and collision with terrain during the forced landing. The oil starvation was caused by the oil leaking out of the drain because maintenance personnel failed to install the drain plug.NTSB SEA89LA110Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Chemult, ORImproper inflight planning/decision by the pilot, which resulted in a sudden altitude deviation, and his delay in initiating remedial action to maintain clearance from the trees. Contributing factors were the downdrafts, high density altitude, the pilot…NTSB MIA89LA170Accident · No injuriesLimited investigationFinal reportCessna 172 · Cedar Key, FLThe pilot's failure to maintain directional control during landing.NTSB LAX89LA208Accident · No injuriesLimited investigationFinal reportCessna 172N · Sacramento, CAThe pilot of the other aircraft displayed poor judgement when he elected to continue taxiing in the runup area when visual lookout could not be maintained.NTSB FTW89LA105Accident · No injuriesLimited investigationFinal reportCessna 172 · Addison, TXFailure of the pilot to maintain clearance from the telephone pole. Factors related to the accident were: darkness, the pilot's disorientation, lack of visual perception at night, the telephone (utility) pole, and the ditch.NTSB ATL89LA147Accident · No injuriesLimited investigationFinal reportCessna 172N · Fuquay, NCFailure of the student pilot to maintain directional control of the aircraft during the landing, which resulted in an inadvertent ground swerve. Contributing factors were: improper flare by the student during the landing, which resulted in a hard landing, and…NTSB MKC89LA100Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Wentzville, MOThe pilot's delay in aborting the landing, and his failure to maintain clearance from the power lines. Factors related to the accident were: the pilot's selection of the wrong runway, the adverse weather conditions, the pilot's failure to attain the proper…NTSB LAX89LA158Accident · No injuriesLimited investigationFinal reportCessna 172N · Eureka, CAThe improper in-flight planning by the instructor pilot when he allowed the private pilot student to land long. Additionally, the instructor delayed remedial action until the runway overrun was inevitable.NTSB ATL89LA127Accident · No injuriesLimited investigationFinal reportCessna 172 · Xenia, OHThe pilot's improper in-flight planning/decision and improper use of the flaps. Contributing was the downdraft.NTSB LAX89LA150Accident · No injuriesLimited investigationFinal reportCessna 172N · Prescott, AZImproper use of the elevator flight control by the pilot and his failure to maintain a proper rate of climb after lift-off. Contributing factors were: improper use of elevator trim by the pilot, his lack of total experience, and an inadvertent porpoise.NTSB MKC89LA074Accident · No injuriesLimited investigationFinal reportCessna 172 · Cresco, IAFailure of the pilot to maintain control of the airplane during the landing on a closed runway.NTSB CHI89LA055Accident · No injuriesLimited investigationFinal reportCessna 172N · Superior, WIFailure of the pilot to maintain directional control during the landing, which resulted in an inadvertent ground swerve. Factors related to the accident were the icy and snow covered runway conditions and the snowbank.NTSB MKC89LA067Accident · No injuriesLimited investigationFinal reportCessna 172 · Grand Rapids, MNThe pilot's failure to adequately compensate for the crosswind conditions. Contributing to the accident were the gusty crosswind conditions.NTSB FTW89LA058Accident · No injuriesLimited investigationFinal reportCessna 172 · Marietta, OKFailure of the pilot to select the proper runway, which resulted in a downwind landing and an overrun of the runway. The gusty tailwind, ditch, and railing (fence) were factors.NTSB MIA89IA095Incident · No injuriesIncident investigationFinal reportCessna 172N · Homestead, FLFuel starvation caused by a sticking needle valve which was softened by contact with automotive fuel previously used to operate the engine.NTSB LAX89LA107Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Deer Valley, AZThe pilot's failure to raise the wing flaps during the aborted landing, and his failure to maintain airspeed during the climbing right turn.NTSB MKC89LA056Accident · No injuriesLimited investigationFinal reportCessna 172 · Ainsworth, NEThe loss of power from undetermined reasons during an attempted go-around. Contributing to the accident was the pilot's failure to maintain directional control of the airplane and the crosswind conditions.NTSB BFO89LA014Accident · No injuriesLimited investigationFinal reportCessna 172N · Ashland, VAThe pilot's failure to maintain directional control of the airplane during landing and the failure to achieve sufficient airspeed during the go-around to initiate a climb.