NTSB investigations: Cessna 172P, 1990
28 cases on aircraft the registry lists as Cessna 172P. 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
| 1969 | 1 |
|---|---|
| 1973 | 1 |
| 1980 | 2 |
| 1981 | 9 |
| 1982 | 30 |
| 1983 | 34 |
| 1984 | 36 |
| 1985 | 32 |
| 1986 | 24 |
| 1987 | 42 |
| 1988 | 39 |
| 1989 | 27 |
| 1990 | 28 |
| 1991 | 39 |
| 1992 | 36 |
| 1993 | 26 |
| 1994 | 22 |
| 1995 | 19 |
| 1996 | 24 |
| 1997 | 25 |
| 1998 | 19 |
| 1999 | 24 |
| 2000 | 21 |
| 2001 | 16 |
| 2002 | 16 |
| 2003 | 25 |
| 2004 | 18 |
| 2005 | 17 |
| 2006 | 9 |
| 2007 | 10 |
| 2008 | 13 |
| 2009 | 9 |
| 2010 | 16 |
| 2011 | 14 |
| 2012 | 12 |
| 2013 | 6 |
| 2014 | 6 |
| 2015 | 12 |
| 2016 | 9 |
| 2017 | 7 |
| 2018 | 10 |
| 2019 | 4 |
| 2020 | 5 |
| 2021 | 7 |
| 2022 | 10 |
| 2023 | 7 |
| 2024 | 9 |
| 2025 | 7 |
| 2026 | 9 |
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\") = 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 ('2072436'))
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 ('2072436'))
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 BFO91LA016Accident · 1 fatalLimited investigationFinal reportCessna 172P · Axton, VAThe pilot's failure to maintain adequate clearance with an obstacle. Contributing was an unmarked powerline and the pilot's lack of familiarity with the geographical area.NTSB MIA91LA027Accident · 2 fatalLimited investigationFinal reportCessna 172P · Atlantic Ocean (Atlantic Ocean)Delay of the pilot to obtain assistance and, as a result, he ditched the airplane near a boat due to a low fuel supply.NTSB CHI91DEP02Accident · Serious injuriesFinal reportCessna 172P · Hayward, WIThe pilot-in-command's intentional flight into known adverse weather.NTSB CHI91FA011Accident · 3 fatalField investigationFinal reportCessna 172P · Fort Wayne, INThe failure of the pilot to maintain an airspeed above stalling speed. Factors associated with the accident are premature rotation and the pilot's lack of recent total experience.NTSB CHI91GA014Accident · 1 fatalFinal reportCessna 172P · Williamsburg, IAThe pilot-in-command's abrupt pull-up to avoid an obstacle. Contributing was the pilot-in-command's diverted attention to activities on the ground.NTSB NYC91FA001Accident · 3 fatalField investigationFinal reportCessna 172P · Gorham, NHImproper planning/decision by the pilot, and his failure to maintain proper altitude while flying over mountainous terrain. Factors related to the accident were: darkness, mountainous terrain, and pilot fatigue.NTSB BFO90LA080Accident · No injuriesLimited investigationFinal reportCessna 172 · Maryville, KYThe failure of a hydraulic brake line which resulted in a loss of fluid, and an inoperative brake system during landing roll.NTSB SEA90FA183Accident · 1 fatalField investigationFinal reportCessna 172-P · Hood River, ORThe pilot in command's encountering spatial disorientation and his failure to maintain airspeed.NTSB LAX90LA314Accident · No injuriesLimited investigationFinal reportCessna 172P · Santa Barbara, CAA disconnect of the throttle control.NTSB SEA90LA173Accident · No injuriesLimited investigationFinal reportCessna 172P · Granite Falls, WAThe pilot in command's use of excessive flaps for takeoff resulting in loss of climb performance.NTSB LAX90FA292Accident · 4 fatalField investigationFinal reportPiper PA-28RT-201 · Long Beach, CAThe inadequate visual outlook of the pilots of the Cessna 172P and their failure to see and avoid the Piper pa- 28RT-201. Contributing to the accident was the azimuth and angle of the sun which was in a position at the time of the accident to impair the scan…NTSB ATL90LA159Accident · No injuriesLimited investigationFinal reportCessna 172 · Ridge Spring, SCThe failure of the maintenance facility/owner to follow standard preventive maintenance procedures. A factor was the pilot's failure to extend the flaps during the forced landing.NTSB LAX90LA287Accident · No injuriesLimited investigationFinal reportCessna 172P · Coalinga, CAThe failure of the student pilot to accurately interpret the wind sock, and his inadvertent attempt to perform a downwind landing.NTSB LAX90LA273Accident · No injuriesLimited investigationFinal reportCessna 172P · Mammoth Lakes, CAInadvertent encounter with high velocity winds.NTSB LAX90LA216Accident · No injuriesLimited investigationFinal reportCessna 172P · Redding, CAThe failure of the pilot in command to maintain direction control. Factors in the accident were the pilot in command's premature rotation during the takeoff and the failure to take the necessary remedial action.NTSB CHI90DEV05Accident · Minor injuriesFinal reportCessna 172P · Jerseyville, ILThe pilot's failure to go around when crosswinds upset aircraft alignment with the runway in the flare. Contributing to the accident was the pilot's attempt to land in crosswinds which exceeded the maximum for which the model has been demonstrated capable.NTSB MIA90LA129Accident · No injuriesLimited investigationFinal reportCessna 172P · Plymouth, FLThe pilot's inadequate compensation for wind conditions. Factors related to the accident were: the crosswind and the pilot's lack of total flying expereince.NTSB CHI90LA122Accident · No injuriesLimited investigationFinal reportCessna 172P · Plainfield, ILThe student's improper flare, improper recovery from a bounced landing, and failure to maintain directional control. The crosswind was a related factor.NTSB CHI90LA119Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Lambertville, MIThe pilot's failure to maintain aircraft control during the aborted landing.NTSB ATL90FA095Accident · 2 fatalField investigationFinal reportEmbraer EMB-120 · Gadsden, ALInadequate visual lookout by the pilots of both aircraft, which resulted in their failure to see-and-avoid oncoming traffic. A factor related to the accident was: the sun's glare, which restricted the vision of the Cessna 172 pilot.NTSB CHI90LA109Accident · No injuriesLimited investigationFinal reportCessna 172P · Savanna, ILImproper planning/decision by the pilot. The strong/gusty crosswind was a related factor.NTSB DEN90LA090Accident · No injuriesLimited investigationFinal reportCessna 172 · Ogallala, NEThe misjudged landing flare. A factor was the pilot's lack of experience.NTSB NYC90LA080Accident · No injuriesLimited investigationFinal reportCessna CE-172P · Hollidaysburg, PAPilot factor in that he failed to ensure there was sufficient fuel on board to complete the flight. This resulted in an engine failure & subsequent forced landing.NTSB MIA90GA088Accident · Serious injuriesFinal reportCessna 172P · Tampa, FLPilots failure to maintain airspeed (vs), which resulted in an inflight loss of control (stall/spin), and in flight collision with terrain.NTSB MIA90LA069Accident · No injuriesLimited investigationFinal reportCessna 172P · Fort Lauderdale, FLThe pilot's failure to maintain control of the airplane after the right main gear contacted a tie down hole, which resulted in a collision with the hangar.NTSB NYC90LA069Accident · No injuriesLimited investigationFinal reportCessna 172P · Sunapee Lake, NHFailure of the pilot to maintain adequate altitude above the lake, which resulted in unplanned contact with its frozen surface.NTSB MKC90LA043Accident · No injuriesLimited investigationFinal reportCessna 172 · St Cloud, MNInadequate visual outlook by the pilot and his failure to maintain clearance from the light pole. The location of the pole was considered to be a related factor.NTSB CHI90LA063Accident · No injuriesLimited investigationFinal reportCessna 172 · Newark, ILImproper planning/decision by the pilot. The wet condition of the grass runway was a related factor.