NTSB investigations: Cessna 172P, 1993
26 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\") = 1993
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") = 1993
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 LAX94LA061Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Panoche, CAthe pilot's improper approach speed and glide path, and his delayed initiation of a go-around. A factor in the accident was the wind shear condition created by the hills immediately off the departure end of the dirt airstrip.NTSB MIA94LA028Accident · No injuriesLimited investigationFinal reportCessna 172P · Jacksonville, FLThe improper positioning of the fuel selector by the pilot-in- command resulting in fuel starvation.NTSB LAX94LA050Accident · No injuriesLimited investigationFinal reportCessna 172RG · Santa Ana, CAwere the CFI's inadequate supervision of the flight and his delay in taking remedial action. The dual student's excessive taxi speed and the worn right brake lining were factors in this accident.NTSB LAX94LA023Accident · No injuriesLimited investigationFinal reportCessna 172 · Murrieta, CAThe unexpected windsheer that was encountered on final approach. The surrounding mountain/hilly terrain was a factor in this accident.NTSB SEA94FA014Accident · 2 fatalField investigationFinal reportCessna 172P · Kelso, WAThe pilot's failure to follow the published missed approach procedure. Factors in the accident were: the weather and mountainous terrain.NTSB BFO93LA184Accident · No injuriesLimited investigationFinal reportCessna 172 · Emporia, VAThe pilot's selection of unsuitable terrain for a takeoff. A factor related to the accident was the pilot's delay in initiating an aborted takeoff.NTSB LAX93LA368Accident · No injuriesLimited investigationFinal reportCessna 172P · Phoenix, AZThe pilot's misjudging the landing flare. A physical problem may have contributed.NTSB CHI93LA364Accident · No injuriesLimited investigationFinal reportCessna 172P · Fieldon, ILPartial failure (deterioration) of the #1 piston pin plug, which resulted in contamination of the lubricating system and failure of the #3 connecting rod.NTSB BFO93LA156Accident · 1 fatalLimited investigationFinal reportCessna 172P · Pembroke, VAThe pilot's failure to maintain proper altitude while manuevering in mountainous terrain.NTSB DEN93LA105Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Santa Fe, NMImproper planning and decision making by the pilot in command in descending into a valley at an altitude providing no escape route in mountainous terrain.NTSB NYC93FA158Accident · 1 fatalField investigationFinal reportCessna 172N · Lincoln Park, NJThe failure of both pilots to maintain adequate visual lookout while in the airport traffic pattern, which resulted in an in-flight collision.NTSB ANC93LA142Accident · No injuriesLimited investigationFinal reportCessna 172 · Black Rapids, AKThe pilot's improper in-flight planning/decision, and his delay in taking remedial action. Factor was the rough, uneven terrain.NTSB LAX93LA298Accident · No injuriesLimited investigationFinal reportCessna 172 · Vacaville, CAThe pilot's improper in-flight planning/decision by failing to allow enough time for the rotor wash to dissipate before attempting the approach. The wake turbulence (rotor wash) was a factor in this accident.NTSB FTW93LA217Accident · No injuriesLimited investigationFinal reportCessna 172P · Cookson, OKThe pilot's improper flare and his failure to maintain directional control during the aborted landing.NTSB BFO93LA127Accident · No injuriesLimited investigationFinal reportCessna 172P · Edgartown, MAThe pilot failed to maintain directional control during takeoff. Other related factors were: the tailwind, and the gross weight of the airplane being exceeded.NTSB ATL93LA129Accident · No injuriesLimited investigationFinal reportCessna 172 · Summerdale, ALThe pilot's failure to attain the proper touchdown point.NTSB FTW93LA205Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Lancaster, TXFuel exhaustion engine power loss due to the inadequate fuel supply for the flight. A factor was the lack of suitable terrain for the forced landingNTSB CHI93LA205Accident · No injuriesLimited investigationFinal reportCessna 172P · Hartford, WIThe failure of the number four cylinder and unsuitable terrain.NTSB NYC93LA101Accident · No injuriesLimited investigationFinal reportCessna 172P · Lincoln Park, NJThe pilot's inadequate compensation for wind conditions, and his failure to maintain directional control of the airplane, which resulted in a ground swerve and a collision with trees.NTSB SEA93FA125Accident · 3 fatalField investigationFinal reportCessna 172P · Enumclaw, WAInadvertent VFR flight into IMC. Factors to the accident were: fog and rain.NTSB BFO93LA079Accident · No injuriesLimited investigationFinal reportCessna 172P · Pittstown, NJThe pilot's improper recovery from a bounced landing, and his failure to maintain directional control of the airplane, which resulted in a ground swerve. The gusty wind and proximity of the parked airplane were related factors.NTSB MIA93LA118Accident · No injuriesLimited investigationFinal reportCessna 172P · Mims, FLTotal loss of engine power due to fuel exhaustion. Contributing to the accident was the failure of the pilot to lean the fuel/air mixture during cruise flight which increased the fuel consumption for the flight.NTSB MIA93LA111Accident · No injuriesLimited investigationFinal reportCessna 172P · Orlando, FLThe pilot-in-command's failure to compensate for wind drift while landing, resulting in the aircraft going off the side of the runway and colliding with a pond.NTSB LAX93FA160Accident · 4 fatalField investigationFinal reportCessna 172P · Livermore, CAThe pilot's decision to attempt VFR flight into instrument meteorological conditions. Factors that contributed to this accident were: the pilot's lack of recent instrument experience, the rain and high wind conditions in the area.NTSB NYC93LA055Accident · No injuriesLimited investigationFinal reportCessna 172P · Teterboro, NJThe failure of the pilot to maintain directional control during landing which resulted in the airplane departing the runway and nosing over. Factors related to the accident were the crosswind and the soft terrain encountered by the airplane.NTSB LAX93FA096Accident · 1 fatalField investigationFinal reportCessna 172P · Sun City, CAThe pilot's decision to initiate VFR flight into instrument meteorological conditions. Factors which contributed to the accident were: the pilot's failure to obtain a weather briefing, the adverse weather, and the mountainous terrain.