Cessna 172N
NTSB investigations · 1,815
Matched to the registry by N-number and event date, newest first.
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_aircrafts.parquet' a JOIN 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c ON c.\"mKey\" = a.case_mkey
WHERE a.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_aircrafts.parquet' a JOIN 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c ON c."mKey" = a.case_mkey
WHERE a.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 MIA04CA009Accident · No injuriesData collectionFinal reportCessna 172N · Melbourne, FLInadvertent full retraction of the flaps, while recovering from a bounced landing, resulting in an inadvertent stall, uncontrolled descent, and subsequent impact with terrain.NTSB MIA04CA005Accident · Minor injuriesData collectionFinal reportCessna 172N · Everglades City, FLThe pilot's improper preflight planning/preparation which resulted in the airplane's gust lock being left installed, which resulted in the airplane not being able lift off during the takeoff roll, and damage to the airplane when it overran the runway and…NTSB LAX03LA294Accident · No injuriesLimited investigationFinal reportCessna 172N · Pahrump, NVthe pilot's failure to maintain altitude/clearance from the mountainous terrain while maneuvering, which resulted in an in-flight collision with terrain.NTSB CHI03LA250Accident · No injuriesLimited investigationFinal reportCessna 172M · La Monte, MOThe pilot's misjudgment of speed and distance resulting in an overrun of the runway.NTSB LAX03CA247Accident · No injuriesData collectionFinal reportCessna 172N · Livermore, CAThe pilot's misjudged landing flare, which resulted in a porpoise pilot induced oscillation and hard landing.NTSB NYC03LA146Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Linden, NJThe mechanic's improper installation of the carburetor, and his failure to secure the mixture control wire to the mixture control arm pivot bolt.NTSB CHI03LA290Accident · No injuriesLimited investigationFinal reportCessna 172N · Romeo, MIThe pilot not maintaining directional control during landing. A factor to the accident was the parked airplane.NTSB MIA03FA124Accident · 5 fatalField investigationFinal reportCessna 172N · Deerfield Beach, FL**This case was revised 6/10/2005 and 2/24/2016. Refer to the public docket for this accident for details.** The failure of the pilot of N4903F, the Cessna 172, and the pilot of N759XA, the Cessna 182, to see and avoid each other while operating in Class E…NTSB CHI03LA163Accident · No injuriesLimited investigationFinal reportCessna 172N · Anoka, MNThe pilot's failure to attain the proper touchdown point, and his failure to maintain directional control. Contributing factors were the pilot's lack of experience, and the runway sign.NTSB MIA03LA116Accident · No injuriesLimited investigationFinal reportCessna 172N · Clearwater, FLthe pilot's failure to maintain directional control during the takeoff roll, which resulted in the airplane departing the runway, and impacting with trees.NTSB ATL03LA100Accident · No injuriesLimited investigationFinal reportCessna 172N · Orangeburg, SCThe pilot's continued operation of the airplane with known deficiencies in the equipment. Also causal was the other maintenance personnel's improper installation of the mixture control linkage bolt that resulted in binding of the mixture control linkage and…NTSB ATL03LA098Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Hampton, GAThe certified flight instructor's failure to maintain clearance from the runway during a low pass. A factor was gusty wind conditions.NTSB SEA03LA084Accident · No injuriesLimited investigationFinal reportCessna 172 N · Center Island, WAThe pilot did not attain the proper touchdown point during landing. The pilot's diverted attention, deer near the runway, and trees were factors.NTSB LAX03LA152Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Payson, AZthe pilot's inadequate recovery from a bounced landing, failure to retract the flaps during an aborted landing attempt, failure to maintain an adequate airspeed, and failure to maintain directional control. A factor in the accident was the high density…NTSB CHI03LA103Accident · No injuriesLimited investigationFinal reportCessna 172N · Carbondale, ILThe pilot failed to properly recover from a bounced landing which resulted in the airplane porpoising.NTSB MIA03LA098Accident · No injuriesLimited investigationFinal reportCessna 172N · Foxworth, MSThe failure of the pilot to perform a go-around, his failure to attain the proper touchdown point, and his delay in applying the normal brakes resulting in his inability to stop the airplane and subsequent on-ground collision with a fence.NTSB LAX03LA128Accident · No injuriesLimited investigationFinal reportCessna 172N · Anaheim, CAFailure of company maintenance personnel to correctly install and safety wire the oil drain plug, which led to a loss of engine oil and a catastrophic internal failure of the engine.NTSB CHI03FA086Accident · 3 fatalField investigationFinal reportCessna 172N · Foley, MNThe pilot's continued visual flight into instrument meteorological conditions which led to spatial disorientation and subsequent impact with the ground. Contributing factors was the pilot's lack of instrument rating, the pilot's disregard of the preflight…NTSB NYC03LA062Accident · No injuriesLimited investigationFinal reportCessna 172N · Cincinnati, OHThe student pilot's failure to maintain directional control.NTSB LAX03FA100Accident · 2 fatalField investigationFinal reportCessna 172N · Ely, NVthe pilot's failure to maintain adequate terrain clearance while flying in a box canyon.NTSB CHI03FA071Accident · 1 fatalField investigationFinal reportCessna 172N · Wellington, KSSpatial disorientation experienced by the pilot and his subsequent failure to maintain control of the aircraft. Contributing factors were the pilot's failure to obtain an updated preflight weather briefing prior to the return flight, his attempted flight into…NTSB SEA03LA036Accident · No injuriesLimited investigationFinal reportCessna 172N · McMinnville, ORThe pilot's inadequate compensation for wind conditions and his failure to maintain directional control during the landing roll. Factors include gusty crosswinds and soft terrain in the area where the aircraft departed the side of the runway.NTSB LAX03FA077Accident · 1 fatalField investigationFinal reportCessna 172N · Kalaupapa, HIthe student pilot's inadvertent VFR flight into IMC, which resulted in his in-flight collision with mountainous terrain while maneuvering. A contributing factor was the low ceiling weather condition.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 172N · 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 reportCessna 172 · 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.
Back to Cessna 172N