NTSB investigations: Cessna 172N, 2002
43 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\") = 2002
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") = 2002
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 LAX03LA053Accident · No injuriesLimited investigationFinal reportCessna 172N · Pacoima, CAthe student pilot's excessive use of the elevator control that resulted in an inadvertent lift-off and his failure to maintain/attain adequate airspeed, which resulted in a stall and hard landing.NTSB ATL03LA024Accident · No injuriesLimited investigationFinal reportCessna 172N · Cartersville, GAThe student pilot's failure to maintain directional control, during the landing roll resulted in the on ground collision with a ravine.NTSB CHI03LA035Accident · No injuriesLimited investigationFinal reportCessna 172N · Holland, MIThe student pilot failed to maintain directional control during landing roll. Additional factors include the student pilot's lack of total flight experience, the CFI's inadequate supervision, and the ice and snow on the runway.NTSB FTW03FA053Accident · 1 fatalField investigationFinal reportCessna 172N · Lindsay, OKThe in-flight separation of the right wing due to the missing nut that secures the right wing's strut to fuselage fitting to the fuselage.NTSB LAX03LA039Accident · No injuriesLimited investigationFinal reportCessna 172N · Hollister, CAthe pilot's failure to maintain directional control of the airplane.NTSB FTW03LA040Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Porter, TXThe loss of engine power for an undetermined reason.NTSB MIA03FA007Accident · 2 fatalField investigationFinal reportCessna 172M · Coral Springs, FLThe failure of the dual students and flight instructors on both N9840V and N6101F to see and avoid each other, which resulted in a midair collision.NTSB MIA03LA008Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Sebring, FLThe student pilot's premature rotation and failure to maintain airspeed during the takeoff, which resulted in an inadvertent stall, an uncontrolled descent, and an impact with the ground.NTSB NYC03LA014Accident · No injuriesLimited investigationFinal reportCessna 172N · Morristown, NJThe student pilot's failure to maintain directional control during takeoff.NTSB IAD03FA005Accident · 2 fatalField investigationFinal reportCessna 172N · Mount Sterling, KYThe failure of the pilot to follow the published instrument approach procedure, which resulted in an early descent into an antenna tower. A factor was the low ceiling.NTSB ATL03LA003Accident · No injuriesLimited investigationFinal reportCessna 172N · Pompano Beach, FLThe loss of engine power for undetermined reasons.NTSB IAD02LA096Accident · No injuriesLimited investigationFinal reportCessna 172N · Bumpass, VAThe pilot's failure to maintain directional control during the landing. A factor was the narrow runway width.NTSB LAX02LA269Accident · No injuriesLimited investigationFinal reportCessna 172N · Lakeside, CAThe failure of the engine to respond for undetermined reasons. Also causal was the student's decision to continue the simulated emergency maneuver to an altitude that was insufficient to allow for contingency options. The unsuitable nature of the terrain…NTSB MIA02LA158Accident · No injuriesLimited investigationFinal reportCessna 172N · Tarboro, NCThe failure of the solo student to maintain directional control of the airplane during the takeoff roll/run which resulted in the airplane veering off the runway and impacting trees, incurring substantial damage.NTSB MIA02LA157Accident · No injuriesLimited investigationFinal reportCessna 172N · Pinehurst, NCThe student pilot's improper recovery from bounced landing which resulted in substantial damage to the airplane.NTSB LAX02FA259Accident · No injuriesField investigationFinal reportCessna 172N · Mesa, AZAn electrical fire of unknown origin centered near the circuit breaker/throttle area of the instrument panel.NTSB IAD02FA088Accident · 1 fatalField investigationFinal reportCessna 172N · Stanardsville, VAThe pilot's failure to maintain sufficient altitude/clearance while descending over mountainous terrain. A factor was the night lighting conditions.NTSB CHI02FA247Accident · 1 fatalField investigationFinal reportCessna 172N · Shell Lake, WIThe pilot's failure to refuel the airplane prior to departure leading to fuel exhaustion during the flight, the inadequate preflight/inflight planning, and the unsuitable terrain encountered by the pilot during the forced landing attempt. Contributing factors…NTSB IAD02LA085Accident · No injuriesLimited investigationFinal reportCessna 172N · Williamsport, PAThe student pilot's failure to maintain adequate clearance from a building while taxiing.NTSB CHI02LA236Accident · No injuriesLimited investigationFinal reportCessna 172N · Sidney, NEThe pilot not maintaining sufficient airspeed during the takeoff, and the inadvertent stall encountered by the pilot. The low altitude was a factor.NTSB DEN02LA086Accident · No injuriesLimited investigationFinal reportCessna 172N · Fort Collins, COthe student pilot's failure to maintain aircraft control and subsequent inadvertent stall/mush into terrain during a soft field take off. Contributing factors include the pilot's lack of experience and the high density altitude conditions.NTSB ANC02LA086Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Fairbanks, AKThe failure of both pilots to maintain adequate visual outlook while taxiing.NTSB CHI02CA211Accident · No injuriesData collectionFinal reportCessna 172N · Spearfish, SDThe probable cause of this accident was the pilot's failure to maintain directional control of the airplane during the takeoff roll. Differences in control forces and aircraft handling due to initiating the takeoff without fully retracting the flaps is a…NTSB NYC02LA145Accident · No injuriesLimited investigationFinal reportCessna 172N · Middletown, RIThe pilot's improper flare. A factor was the shifting wind.NTSB NYC02LA134Accident · No injuriesLimited investigationFinal reportCessna 172 · West Milford, NJThe flight instructor's improper recovery from a bounced landing.NTSB MIA02LA132Accident · No injuriesLimited investigationFinal reportCessna 172N · Pickens, SCThe pilot's improper preflight planning/preparation that resulted in the airplane's gust lock being left installed which resulted in a loss of control during the takeoff roll and damage to the airplane when it exited the departure end of the runway and…NTSB SEA02FA125Accident · 2 fatalField investigationFinal reportCessna 172N · Otis, ORThe pilot's failure to maintain adequate clearance with power lines while conducting low altitude flight resulting in a loss of control and subsequent collision with terrain. Contributing factors were the pilot's low altitude flight and the power lines.NTSB IAD02LA067Accident · No injuriesLimited investigationFinal reportCessna 172 · Fulton, NYThe pilot's improper flare, which resulted in a misaligned, hard landing.NTSB LAX02LA205Accident · No injuriesLimited investigationFinal reportCessna 172N · North Las Vegas, NVThe pilot's decision to continue the flight after dark with an inoperative taxi/landing light deficiency, and his unfamiliarity with the taxiways.NTSB NYC02LA121Accident · No injuriesLimited investigationFinal reportCessna 172N · Lynchburg, VAThe pilot's failure to maintain control of the airplane, a factor was the tailwind.NTSB MIA02LA117Accident · No injuriesLimited investigationFinal reportCessna 172N · Marietta, GAthe pilot's failure to maintain directional control during the takeoff roll, which resulted in the airplane departing the left side of the runway, impacting with a gully and nosing over.NTSB IAD02LA061Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Rutland, VTThe pilot's failure to maintain directional control during the takeoff attempt.NTSB CHI02LA175Accident · No injuriesLimited investigationFinal reportCessna 172N · Minneapolis, MNThe pilot did not maintain clearance from the vehicle while taxiing. A factor was the fuel truck.NTSB FTW02LA159Accident · No injuriesLimited investigationFinal reportCessna 172N · Glen Rose, TXThe pilot's failure to set the ignition key to the both magnetos position, which resulted in a loss of engine power. Contributing factors were the failure of the left magneto, the lack of suitable terrain for the forced landing, and the dark night.NTSB CHI02LA103Accident · No injuriesLimited investigationFinal reportCessna 172N · Appleton, WIThe pilots failure to maintain directional control of the airplane during the takeoff roll resulting in the subsequent impact with terrain.NTSB MIA02FA066Accident · 2 fatalField investigationFinal reportCessna 172N · Bunnell, FLInadequate maintenance inspection of the airplane by comapny maintenance personnel which resulted in corrosion in an aileron control cable going undetected, failure of the aileron control cable, and impact with terrain following loss of control of the…NTSB SEA02LA047Accident · No injuriesLimited investigationFinal reportCessna 172N · Longmont, COThe student pilot's failure to maintain directional control during landing. Factors included the student pilot's lack of experience, an icy runway, and a mound of snow adjacent to the runway.NTSB LAX02LA094Accident · No injuriesLimited investigationFinal reportCessna 172N · Madera, CAThe pilot's becoming lost/disoriented.NTSB DEN02LA025Accident · No injuriesLimited investigationFinal reportCessna 172N · Durango, COthe pilot's failure to maintain directional control during the landing roll. Contributing factors were the crosswind and the pilot's fatigue from lack of sleep.NTSB LAX02LA084Accident · No injuriesLimited investigationFinal reportCessna 172S · Glendale, AZThe pilot of the landing airplane failed to maintain directional control resulting in the on-ground collission.NTSB FTW02LA079Accident · No injuriesLimited investigationFinal reportCessna 172N · Santa Fe, NMthe loss of engine power as result of the failure of the dual magneto. A contributing factor was the lack of suitable terrain for the precautionary landing.NTSB CHI02LA076Accident · No injuriesLimited investigationFinal reportCessna 172N · Ottumwa, IAthe student pilot failed to maintain directional control during takeoff. A contributing factor was the snowbank.NTSB FTW02LA063Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Durango, COthe pilot's failure to maintain clearance with the trees and mountainous terrain while maneuvering. A contributing factor was the pilot's delay in taking remedial action.