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 WPR09FA248Accident · 3 fatalField investigationFinal reportCessna 172N · Long Beach, CAThe failure of both pilots to see and avoid each other's aircraft.NTSB WPR09LA245Accident · No injuriesLimited investigationFinal reportCessna 172N · Desert Center, CAA partial loss of engine power due to low compression from an obstructed intake valve. Contributing to the accident was the pilot’s decision to shut down the engine while in flight.NTSB CEN09CA292Accident · No injuriesData collectionFinal reportCessna 172N · Springdale, ARThe student pilot's failure to maintain control of the airplane during the landing roll and subsequent go-around.NTSB CEN09CA253Accident · No injuriesData collectionFinal reportCessna 172N · Roanoke, TXThe partial loss of engine power due to a failure of the throttle control rod-end to carburetor arm hardware. A contributing factor was the pilot's decision to fly the airplane without a current annual inspection.NTSB WPR09CA182Accident · No injuriesData collectionFinal reportCessna 172S · Snohomish, WAAn in-flight collision with a crow.NTSB WPR09LA149Accident · 1 fatalLimited investigationFinal reportCessna 172N · Oceanside, CAA loss of aircraft control for undetermined reasons.NTSB CEN09CA187Accident · No injuriesData collectionFinal reportCessna 172N · Carlisle, ARThe student pilot's improper recovery from a bounced landing.NTSB CEN09CA181Accident · No injuriesData collectionFinal reportCessna 172N · Broomfield, COThe pilot and airplane's inability to compensate for the unforecasted gusting wind conditions.NTSB CEN09LA182Accident · No injuriesLimited investigationFinal reportCessna 172N · Johnson County Exec Airport, KSFailure of the pilot of the Cessna 172S to ensure the taxiway was clear prior to initiating the turn. Contributing to the accident was the failure of the pilot of the Cessna 172N to obtain taxi clearance prior to entering the movement area.NTSB CEN09CA229Accident · No injuriesData collectionFinal reportCessna 172 · Manhattan, KSThe pilot's improper recovery from a bounced landing.NTSB WPR09LA122Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Big Bear Lake, CAThe pilot's failure to maintain clearance from terrain while maneuvering in a ravine. Contributing to the accident was the pilot's decision to continue flight in an area that exceeded the climb rate capabilities of the airplane.NTSB ANC09LA018Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Atmautluak, AKThe pilot's failure to maintain adequate airspeed while landing in gusty winds, which resulted in an aerodynamic stall; his improper aircraft weight calculations; and his operation of the airplane over the allowable gross weight limit.NTSB ERA09CA103Accident · No injuriesData collectionFinal reportCessna 172 · Corning, NYThe student pilot's failure to maintain directional control during landing. Contributing to the accident were the gusty wind conditions and the flight instructor's delayed remedial action.NTSB ERA09CA058Accident · No injuriesData collectionFinal reportCessna 172 · Gulf Shores, ALThe pilot's improper flare during landing.NTSB ERA09LA015Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Kissimmee, FLThe pilot's inadequate preflight inspection, which resulted in a total loss of engine power during initial climb due to fuel contamination. Contributing to the accident was a fuel tank cap that did not seal properly.NTSB CHI08CA291Accident · No injuriesData collectionFinal reportCessna 172 · Wadsworth, OHThe pilot's excessive airspeed during the approach and landing and failure to perform a go-around. Contributing to the accident were the barricade and the down-sloping terrain at the end of the runway.NTSB SEA08LA191Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Burbank, CAThe pilot's improper preflight and in-flight planning, which resulted in fuel exhaustion. Contributing to the accident were the pilot's loss of situational awareness while conducting the normal and emergency checklists during his turn from base to final…NTSB CHI08CA256Accident · Minor injuriesData collectionFinal reportCessna 172N · Huntington, INThe pilot's failure to maintain directional control during the takeoff roll. Contributing to the accident was the pilot's inadvertent use of the toe brake.NTSB LAX08FA246Accident · 3 fatalField investigationFinal reportCessna 172N · McMurray, WAThe pilot's improper decision to continue VFR flight into instrument meteorological weather conditions. Contributing to the accident were low ceilings, reduced visibility, and mountainous terrain.NTSB NYC08CA250Accident · No injuriesData collectionFinal reportCessna 172 N · Williamstown, NJThe student pilot's inability to maintain directional control during the attempted aborted landing. Contributing to the severity of the accident were the trees.NTSB NYC08CA248Accident · No injuriesData collectionFinal reportCessna 172N · Edgewater, MDThe pilot's misjudged distance/speed during landing.NTSB LAX08LA206Accident · No injuriesLimited investigationFinal reportCessna 172N · El Cajon, CAThe loss of engine power due to carburetor ice resulting from the flight instructor's failure to use the carburetor heat when simulating an engine failure. Contributing to the accident were the carburetor icing weather condition and the lack of suitable…NTSB CHI08CA161Accident · No injuriesData collectionFinal reportCessna 172 · Cincinnati, OHThe pilot's failure to maintain clearance from a building during taxi. A factor was the building.NTSB LAX08CA155Accident · No injuriesData collectionFinal reportCessna 172N · Sells, AZThe pilot's inadequate recovery from a bounced landing and failure to maintain proper runway alignment.NTSB CHI08CA139Accident · No injuriesData collectionFinal reportCessna 172N · Blue Ash, OHThe separation of the throttle cable from the linkage during the approach to land and the altitude/clearance not being available to the pilot during the forced landing. Contributing to the accident was the electrical wires the airplane impacted.NTSB LAX08CA149Accident · No injuriesData collectionFinal reportCessna 172N · Palo Alto, CAThe pilot's inadequate recovery from a bounced landing.NTSB SEA08FA116Accident · 3 fatalField investigationFinal reportCessna 172N · McCall, IDThe failure of the pilot to maintain adequate visual lookout and clearance from another airplane while attempting to land on the same runway. Contributing to the accident was the non-standard pattern entry of the pilot.NTSB NYC08CA127Accident · No injuriesData collectionFinal reportCessna 172N · Charlottesville, VAThe pilot's improper engine starting procedures.NTSB MIA08CA057Accident · No injuriesData collectionFinal reportCessna 172N · Centre, ALThe pilot's improper landing flare, resulting in a hard landing.NTSB NYC08CA110Accident · No injuriesData collectionFinal reportCessna 172N · Perry, GAThe student pilot's inadequate compensation for wind conditions during landing. Contributing to the accident were the gusting winds.NTSB LAX08CA053Accident · Minor injuriesData collectionFinal reportCessna 172N · Beaver Marsh, ORThe pilot's inadequate in-flight planning/decision to land on a snow covered runway without first determining the depth of the snow.NTSB CHI08CA069Accident · No injuriesData collectionFinal reportCessna 172N · South St. Paul, MNThe student pilot's failure to maintain directional control of the airplane during the landing roll. Contributing to the accident were the snow-covered runway and the gusty wind conditions.NTSB LAX08FA049Accident · 5 fatalField investigationFinal reportCessna 172N · Corona, CAThe failure of both pilots to see and avoid the other airplane.NTSB NYC08LA049Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Gaithersburg, MDThe student pilot's failure to maintain aircraft control during an attempted touch-and-go. Contributing to the accident was the instructor's delay in taking remedial action, and the presence of trees in proximity to the side of the runway.NTSB DFW08FA040Accident · 2 fatalField investigationFinal reportCessna 172N · Marlow, OKThe pilot's failure to maintain airspeed while maneuvering, which resulted in an inadvertent stall/spin and impact with terrain. Contributing to the accident were the low altitude for recovery and the gusty tailwind.NTSB NYC08CA042Accident · No injuriesData collectionFinal reportCessna 172N · Hamilton, NJThe pilot's inadequate fuel consumption calculations which resulted in fuel exhaustion.NTSB SEA08CA030Accident · Minor injuriesData collectionFinal reportCessna 172N · Atwater, CAThe failure of the student pilot to maintain directional control during the landing roll. Factors contributing to the accident included the sign and the ditch.NTSB NYC08CA037Accident · No injuriesData collectionFinal reportCessna 172N · Statesboro, GAThe student pilot's failure to maintain a proper flare at touchdown.NTSB DEN08CA020Accident · No injuriesData collectionFinal reportCessna 172N · Grand Junction, COthe pilot's improper flare resulting in a hard landing.NTSB LAX08CA015Accident · No injuriesData collectionFinal reportCessna 172N · Daggett, CAThe flight's encounter with a strong gusty wind condition.NTSB DFW08CA003Accident · Minor injuriesData collectionFinal reportCessna 172N · Oxford, MSThe pilots inadvertent stall during takeoff. A contributing factor was his failure to calculate the aircraft gross weight prior to the flight.NTSB DEN08CA002Accident · Minor injuriesData collectionFinal reportCessna 172N · Calhan, COThe student pilot's failure to maintain directional control during the takeoff roll.NTSB MIA07CA143Accident · Minor injuriesData collectionFinal reportCessna 172N · Carrabelle, FLThe improper flare by the pilot-in-command resulting in a hard landing.NTSB ATL07CA132Accident · No injuriesData collectionFinal reportCessna C172N · Manassas, VAThe student pilot's failure to correct for a pilot-induced oscillation/porpoise, during flare/touchdown, which resulted in a hard landing.NTSB NYC07FA193Accident · 2 fatalField investigationFinal reportCessna 172N · Rochester, NYThe pilot's failuire to maitain adequate airspeed during a turning maneuver which resulted in an inadvertent stall.NTSB CHI07CA245Accident · No injuriesData collectionFinal reportCessna 172N · New Hudson, MIThe student pilot's improper flare, which resulted in a hard landing. An additional cause was the pilot's inadequate recovery from a bounced landing. Factors in the accident include the pilot's failure to maintain directional control during the landing roll…NTSB CHI07CA202Accident · No injuriesData collectionFinal reportCessna 172N · Yorkville, ILThe inadequate fuel consumption calculations by the pilot, the fuel exhaustion during cruise flight, and the unsuitable landing area encountered by the pilot. Contributing factors were the night light conditions and trees.NTSB SEA07CA183Accident · No injuriesData collectionFinal reportCessna 172N · Greenwater, WAThe in-flight encounter with a sudden windshift during the takeoff initial climb, to which the certified flight instructor responded by aborting the takeoff and landing off the end of the runway. The ditch was a contributing factor.NTSB CHI07FA140Accident · 3 fatalField investigationFinal reportCessna 172N · Sharonville, OHThe inadequate visual lookout of the pilots in both airplanes and their not maintaining clearance from each others airplane during climb.NTSB LAX07FA123Accident · 2 fatalField investigationFinal reportCessna 172N · Page, AZThe pilot's failure to maintain an adequate terrain clearance altitude, and, his failure to maintain an adequate airspeed while maneuvering to reverse course in a box canyon. Contributing to the accident were the rising terrain and the box canyon.
Back to Cessna 172N