NTSB investigations: Cessna 172P, 2003
25 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\") = 2003
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") = 2003
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 LAX04LA053Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Fountain Hills, AZThe flight instructor's delayed remedial action and inadequate altitude during a go-around following a simulated forced landing, which resulted in an in-flight collision with terrain.NTSB ATL04LA013Accident · No injuriesLimited investigationFinal reportCessna 172P · Pell City, ALThe pilot's inadequate compensation for wind and his failure to maintain directional control during landing. A factor was the crosswind.NTSB MIA03TA175Accident · Serious injuriesFinal reportCessna 172P · Jay, FL**This case was modified on 2/18/2016. Refer to the public docket for this accident to view the changes.** Loss of engine power for undetermined reasons.NTSB CHI03LA280Accident · No injuriesLimited investigationFinal reportCessna 172P · Wichita, KSFailure of the maintenance crew to provide adequate clearance to an active taxiway during the engine run-up. Contributing factors were the failure of the control tower to provide a wake turbulence advisory to the accident aircraft when assigning a taxi route…NTSB NYC03CA167Accident · No injuriesData collectionFinal reportCessna 172P · Plainfield, CTThe pilot's failure to maintain directional control, which resulted in a collision with a ditch. A factor in this accident was the crosswind condition.NTSB CHI03LA229Accident · No injuriesLimited investigationFinal reportCessna 172P · Huntingburg, INThe pilot's inadequate flare and the failure to perform a go-around during landing. The planned approach with a quartering tailwind were contributing factors.NTSB MIA03LA143Accident · No injuriesLimited investigationFinal reportCessna 172P · Plymouth, FLThe pilot's continue operation with known deficiencies (engine vibration) resulting in a partial loss of engine power during climb after takeoff and overrun of the runway during the aborted takeoff.NTSB DEN03LA132Accident · No injuriesLimited investigationFinal reportCessna 172P · Watkins, COthe right seat shifting aft during the take off roll, rendering aircraft control not possible by the flight instructor. Contributing factors include the inboard seat pin which did not engage fully, the outboard seat pin which was installed incorrectly, the…NTSB CHI03LA212Accident · No injuriesLimited investigationFinal reportCessna 172P · Pinckneyville, ILThe planned approach not maintained by the pilot and the delayed remedial action by the certified flight instructor. A contributing factor to the accident was the approach light.NTSB ANC03LA069Accident · No injuriesLimited investigationFinal reportCessna 172 · Seldovia, AKThe failure of company maintenance personnel to properly maintain the airplane's brake system, which resulted in a loss of the right brake during landing roll due to a chafed brake line.NTSB SEA03LA103Accident · No injuriesLimited investigationFinal reportCessna 172P · Seattle, WAThe dual student's failure to maintain aircraft control and the flight instructor's delayed remedial action. Contributing factors were the crosswind condition and the flight instructor's lack of experience.NTSB CHI03FA151Accident · 2 fatalField investigationFinal reportCessna 172P · Sheboygan, WIThe pilot failed to maintain control of the airplane after encountering instrument meteorological conditions during takeoff. Factors associated with the accident were the low ceiling, fog and lack of instrument rating.NTSB FTW03LA165Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Gainesville, TXThe pilot's failure to maintain directional control while landing. Contributing factors were the prevailing crosswind and the pilot's failure to abort landing.NTSB ATL03LA097Accident · No injuriesLimited investigationFinal reportCessna 172P · Newnan, GAThe pilot's failure to maintain directional control during the landing roll that resulted in the collapse of the right main landing gear.NTSB MIA03LA100Accident · No injuriesLimited investigationFinal reportCessna 172P · Lantana, FLthe pilot's use of excessive airspeed and the improper touchdown point during the landing roll, which resulted in the airplane departing the runway, and impacting with trees.NTSB DEN03LA072Accident · No injuriesLimited investigationFinal reportCessna 172P · Colo. Springs, COthe student pilot's failure to obtain and maintain adequate altitude during the go-around. Factors contributing to the accident were the encountered windshear, the student pilot's premature raising of the flaps, the instructor pilot's inadequate supervision,…NTSB LAX03FA124Accident · 2 fatalField investigationFinal reportCessna 172P · North Las Vegas, NVthe applicant pilot's failure to maintain an adequate airspeed while maneuvering, which resulted in an inadvertent stall/spin.NTSB LAX03LA117Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Van Nuys, CAthe pilot's failure to maintain directional control during an aborted landing. A contributing factor is the pilot's improper recovery from a bounced landing.NTSB MIA03LA078Accident · No injuriesLimited investigationFinal reportCessna 172P · Potts Camp, MSThe pilot's inadequate planning which resulted in fuel exhaustion, a forced landing to a field, and damage to the airplane during the landing rollout.NTSB NYC03LA065Accident · No injuriesLimited investigationFinal reportCessna 172P · Linden, NJThe pilot's inadequate compensation for the crosswind and his failure to maintain directional control during landing. Factors in the accident were the crosswind and the snowbank.NTSB ATL03LA060Accident · No injuriesLimited investigationFinal reportCessna 172P · Concord, NCThe pilot's improper flare during touchdown and failure to properly recover from a bounced landing, which resulted in a loss of control and inflight collision with the runway. A factor was the pilot did not understand the porpoise condition during landing.NTSB MIA03FA066Accident · 1 fatalField investigationFinal reportCessna 172P · Osteen, FLThe intentional suicidal act by the pilot-in-command resulting in the in-flight collision with trees then the ground.NTSB LAX03FA090Accident · Serious injuriesField investigationFinal reportCessna 172P · Santa Susana, CAThe flight instructor's inadequate in-flight decision to cross mountainous terrain at a inadequate altitude to guarantee terrain clearance.NTSB DEN03MA035Accident · 5 fatalMajor investigationFinal reportPiper PA-31T · Denver, COBoth pilots' inadequate visual lookout. A contributing factor was the Cheyenne pilot operating the airplane with a known transponder deficiency.NTSB MIA03FA043Accident · 4 fatalField investigationFinal reportCessna 172P · Edgewater, FLThe pilot's inflight loss of control and the pilot's failure to recover from the resultant dive for unknown reasons which resulted in flight beyond the design stress limits of the airplane and subsequent in flight airframe breakup.