NTSB investigations: Cessna 172P, 2000
21 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\") = 2000
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") = 2000
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 DEN01LA024Accident · No injuriesLimited investigationFinal reportCessna 172P · Leadville, COthe student pilot's failure to maintain directional control during landing roll. A contributing factor was the snow bank next to the runway.NTSB MIA01WA033Accident · Serious injuriesForeign investigationCessna 172P · Port Au Prince, HaitiNTSB MIA01LA024Accident · No injuriesLimited investigationFinal reportCessna 172P · Inverness, FLa loss of directional control on landing due to the pilot's failure to execute a proper flare and recovery from the resultant bounced landing, causing the airplane to depart the runway, enter the uneven grass infield, and sustain a nose over.NTSB SEA01LA012Accident · No injuriesLimited investigationFinal reportCessna 172P · Waldron Island, WAThe pilot's improper distance/speed during the approach, which lead to an overrun during the landing roll and subsequent collision with trees. A factor was the trees beyond the upwind end of the runway.NTSB MIA01LA013Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Knoxville, TNThe pilot's failure to maintain Vs during takeoff/initial climb, which resulted in an inadvertent stall/mush, an uncontrolled descent, and an impact with the ground. Factors in the accident were the pilot's improper preflightplanning/preparation and failure…NTSB LAX01LA021Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Half Moon Bay, CAA local windshear condition that exceeded the airplane's climb performance capability during landing approach and resulted in the runway overrun during an attempted go-around.NTSB CHI00LA309Accident · No injuriesLimited investigationFinal reportCessna 172P · Wheeling, ILThe student pilot's inadequate compensation for the crosswind that resulted in the failure to maintain directional control of the airplane. Factors associated with the accident were the crosswind, the ditch, the student's lack of experience, and the poor…NTSB SEA00LA179Accident · No injuriesLimited investigationFinal reportCessna 172P · Friday Harbor, WAThe Cessna 172 pilot's failure to maintain clearance with the Cessna 182. Factors included aircraft parked/standing on the taxiway and the refueling area, and a congested/confined taxiway.NTSB NYC00LA256Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Cross Keys, NJThe operator's inadequate 100-hour inspection of the airplane, and the pilot's continued operation with known deficiencies in equipment.NTSB SEA00LA177Accident · No injuriesLimited investigationFinal reportCessna 172P · Auburn, WADamage to aircraft under unknown circumstances.NTSB FTW00LA240Accident · No injuriesLimited investigationFinal reportCessna 172P · San Antonio, TXThe pilot's failure to maintain control during landing. A factor was the reported wind gust.NTSB IAD00LA068Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Princeton, NJthe student pilot's failure to maintain control of the airplane during the aborted landing.NTSB MIA00LA223Accident · No injuriesLimited investigationFinal reportCessna 172P · Jesup, GAThe failure of the student pilot to maintain directional control during takeoff resulting in an excursion off the runway and collision with adjacent foliage. A factor in the accident was the student's decision to takeoff downwind.NTSB DEN00LA121Accident · No injuriesLimited investigationFinal reportCessna 172P · Price, UTThe pilot's failure to maintain directional control of the aircraft during landing roll. Factors were strong and gusty winds.NTSB LAX00FA178Accident · 4 fatalField investigationFinal reportCessna 172P · Chester, CAThe pilot's encounter with a wind shear at low altitude, which resulted in a loss of control and a stall/spin. Factors in the accident were the high density altitude and the pilot's lack of experience and training in high density altitude operations. The…NTSB SEA00LA067Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Seattle, WAThe pilot's failure to attain proper alignment with the landing runway, and her failure to maintain proper glide path for the landing runway, resulting in an encounter with vortex turbulence from a preceding heavy aircraft landing on a parallel runway and…NTSB DEN00LA070Accident · No injuriesLimited investigationFinal reportCessna 172P · Fort Collins, COOn ground loss of control resulting in collision with airport markings due to inadequate compensation for wind conditions during landing roll. Factors were inaccurate in flight planning by landing with a tail wind component and lack of total pilot experience.NTSB NYC00FA106Accident · 2 fatalField investigationFinal reportCessna 172P · Ballston Spa, NYa loss of control for undetermined reason(s).NTSB MIA00LA124Accident · No injuriesLimited investigationFinal reportCessna 172P · St. Petersburg, FLThe failure of the pilot to maintain clearance between the left wingtip and a hangar door resulting in the on-ground collision.NTSB CHI00MA066Accident · 3 fatalMajor investigationFinal reportMoravan Z242L · Zion, ILClearance not maintained by the pilot of the other airplane. A factor relating to the accident was the airport control tower's local controller's failure to provide effective sequencing.NTSB DEN00LA041Accident · No injuriesLimited investigationFinal reportCessna 172P · Huntsville, UTThe snow shower, and the lack of suitable terrain for the precautionary landing.