NTSB investigations: Cessna 172N, 2000
35 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\") = 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 ('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") = 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 ('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 CHI01LA058Accident · No injuriesLimited investigationFinal reportCessna 172N · Elkhart, INThe loss of directional control by the student pilot and the inadequate remedial action and inadequate supervision by the certified flight instructor. Factors were the snow and ice covered runway and the snowbank.NTSB LAX01LA048Accident · No injuriesLimited investigationFinal reportCessna 172N · Marana, AZThe student pilot's improper flare and improper recovery from a bounced landing. A factor in the accident was the morning sun, which momentarily restricted the pilot's vision.NTSB FTW01FA025Accident · 1 fatalField investigationFinal reportCessna 172N · Katy, TXthe failure of both pilot's to maintain visual lookout during cruise flight. A contributory factor was the sun glare, which obscured the Cessna 150 pilot's visual lookout.NTSB MIA01FA028Accident · 1 fatalField investigationFinal reportLockheed-Martin F-16CG · Bradenton, FLthe failure of the F-16 flight lead pilot and F-16 accident pilot to maintain an adequate visual lookout while maneuvering. Factors contributing to the accident were: the F-16 flight lead pilot’s decision to discontinue radar traffic advisory service, the…NTSB SEA01LA013Accident · No injuriesLimited investigationFinal reportCessna 172N · Spangle, WAThe pilot's inadequately executed remedial action and his failure to ensure that the aircraft touched down at the proper location. Factors include a dark night, an unlighted runway, and trees off the approach end of the runway.NTSB NYC01LA030Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Ridgefield, CTThe pilot's failure to verify the airplane's fuel tank selector position, which resulted in a loss of engine power.NTSB DEN01LA004Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Jensen, UTan undershoot due to misjudging distance/altitude during an emergency landing. Factors were: inadequate preflight, failure to refuel, fuel exhaustion, operating with an inoperative fuel gauge, and failure to attain a proper glide path during approach.NTSB NYC01LA017Accident · No injuriesLimited investigationFinal reportCessna 172 · Poughkeepsie, NYThe student pilot's improper recovery from a bounced landing.NTSB LAX00LA323Accident · No injuriesLimited investigationFinal reportCessna 172N · North Las Vegas, NVThe failure of the pilot-in-command to maintain proper airspeed during the aborted landing go-around which resulted in a stall/mush and impact with terrain.NTSB LAX00LA305Accident · No injuriesLimited investigationFinal reportCessna 172 · Flagstaff, AZThe pilot's improper go-around procedure and his failure to maintain directional control on landing.NTSB DEN00FA149Accident · 1 fatalField investigationFinal reportCessna 172N · Kamas, UTThe pilot's improper inflight decision to enter a valley at low altitude and attempt a climb towards rising terrain. A factor was exceeding the airplane's climb performance.NTSB CHI00LA254Accident · No injuriesLimited investigationFinal reportCessna 208B · North Platte, NEthe pilot of the other airplane not maintaining clearance while taxiing. A factor was the dark night.NTSB SEA00LA155Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Gleneden Beach, ORThe pilot's failure to remove the control lock during his preflight inspection. Factors contributing to the accident were the pilot's failure to follow the BEFORE TAKEOFF checklist, trees beyond the upwind end of the runway, and the pilot's self-induced…NTSB FTW00LA207Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Columbus, TXthe failure of both magnetos of the dual-magneto single-drive unit. A factor contributing to the accident was the lack of suitable terrain for the forced landing.NTSB DEN00LA129Accident · No injuriesLimited investigationFinal reportCessna 172N · Durango, COThe pilot prematurely flaring the airplane for landing, resulting in a hard landing, followed by an inadvertent pilot-induced porpoise and loss of directional control. A factor was the fence.NTSB FTW00LA188Accident · No injuriesLimited investigationFinal reportCessna 172N · San Antonio, TXThe flight instructor's failure to refuel the airplane, which resulted in fuel exhaustion. Contributing factors were the flight instructor's fatigued condition and diverted attention.NTSB CHI00LA172Accident · No injuriesLimited investigationFinal reportCessna 172N · Canton, MIthe CFI delayed initiating a go-around during the landing. Factors associated with the accident were the student pilot's inadequate handling of the airplane, the crosswind condition, and the soft terrain on which the airplane touched down.NTSB ATL00LA066Accident · No injuriesLimited investigationFinal reportCessna 172N · Atlantic Ocean (Atlantic Ocean)Loss of engine power for undetermined reasons. A factor was the pilot failed to use carburetor heat during the descent.NTSB CHI00LA169Accident · No injuriesLimited investigationFinal reportCessna 172N · Greenville, ILthe student pilot failed to properly flare the airplane while landing. A factor associated with the accident was the student pilot's lack of total experience.NTSB ANC00FA076Accident · 1 fatalField investigationFinal reportCessna 172N · Tuntutuliak, AKThe pilot's disregard of the existing wind conditions, and an inadvertent stall. Factors associated with the accident are a tailwind, and wind gusts.NTSB LAX00LA260Accident · No injuriesLimited investigationFinal reportCessna 172N · Santa Ana, CAThe loss of engine power during the initial takeoff climb, at too low an altitude to afford remedial action, because of an ingested valve, and the airplane's subsequent collision with the ground adjacent to the runway.NTSB DEN00LA114Accident · No injuriesLimited investigationFinal reportCessna 172 · Abuquerque, NMThe pilot's improper flare and his inadequate recovery from a bounced landing.NTSB CHI00LA146Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Plainwell, MIthe pilot exceeded the proper touchdown point during the landing. Factors associated with the accident were the fence and the ditch which the airplane contacted.NTSB MIA00LA175Accident · No injuriesLimited investigationFinal reportCessna 172N · Lincolnton, NCThe inadequate supervision of the student pilot by the CFI for his failure to note that the student was performing a go-around from a low pass with 30-degree of flaps extended instead of the POH recommended 20-degrees. A factor in the accident was the failure…NTSB SEA00LA100Accident · No injuriesLimited investigationFinal reportCessna 172N · Atlantic Ocean (Atlantic Ocean)A loss of engine power for undetermined reasons.NTSB IAD00LA043Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Tappahannock, VAthe pilots's inability to maintain aircraft control after a loss of consciosness.NTSB CHI00LA117Accident · No injuriesLimited investigationFinal reportCessna 172N · Chesterfield, MOthe pilot misjudged the landing flare which resulted in the airplane porpoising on the runway during the landing.NTSB LAX00LA152Accident · No injuriesLimited investigationFinal reportCessna 172N · Lakeport, CAThe pilot's decision to continue with a high, steep, and fast approach, which resulted in a touchdown beyond the halfway point of the runway and the inability to stop on the remaining pavement, and, his delayed decision to initiate a landing abort. Also…NTSB NYC00LA109Accident · No injuriesLimited investigationFinal reportCessna 172 · North Adams, MAThe pilot's failure to obtain the proper touchdown point. A factor was a tailwind.NTSB FTW00LA107Accident · No injuriesLimited investigationFinal reportCessna 172N · Maud, OKthe loss of engine power while maneuvering as a result of the separation of the exhaust rocker arm retaining stud due to fatigue, which resulted in a precautionary landing.NTSB SEA00LA054Accident · No injuriesLimited investigationFinal reportCessna 172N · Quincy, WAFailure to maintain terrain clearance. Factors include mountainous/hilly terrain.NTSB LAX00FA101Accident · Minor injuriesField investigationFinal reportCessna 172N · Palm Springs, CAthe failure of both flight crews to see and avoid the other airplane while operating in the traffic pattern, which resulted in a mid-air collision. A contributing factor was the failure of the arriving aircraft to comply with air traffic control requests by…NTSB LAX00LA096Accident · No injuriesLimited investigationFinal reportCessna 172N · Bermuda Dunes, CAFailure of the student pilot to maintain directional control of the airplane during takeoff.NTSB CHI00LA065Accident · No injuriesLimited investigationFinal reportCessna 172 · Chesterfield, MOThe pilot failed to maintain directional control during the takeoff portion of a touch and go landing.NTSB MIA00LA074Accident · No injuriesLimited investigationFinal reportCessna 172N · Lincolnton, GAThe pilot's failure to remove ice from the wings prior to takeoff resulting in the aircraft not climbing after takeoff and colliding with a tree.