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 ANC07CA023Accident · No injuriesData collectionFinal reportCessna 172 · Chugiak, AKThe instructor pilot's inadequate supervision of the student while landing, which resulted in an undershoot, and subsequent in-flight collision with snow-covered terrain.NTSB SEA07CA074Accident · Minor injuriesData collectionFinal reportCessna 172N · Phoenix, AZThe pilot's failure to maintain airspeed, which resulted in an inadvertent stall and uncontrolled descent into terrain during landing. A contributing factor was the pilot's distracted attention due to the inaccurate flap indicator.NTSB CHI07CA076Accident · No injuriesData collectionFinal reportCessna 172N · Holland, MIThe student pilot's inadequate compensation for the crosswind condition and his failure to maintain directional control during the takeoff, which caused the airplane to impact the snow bank and nose over. Contributing factors were the crosswind and the snow…NTSB CHI07CA082Accident · No injuriesData collectionFinal reportCessna 172N · Pinckneyville, ILPresence of a deer on the runway resulting in an inadvertent collision during the landing roll.NTSB DEN07CA043Accident · No injuriesData collectionFinal reportCessna 172N · Cottonwood Fall, KSthe pilot's failure to maintain clearance from the fence. Contributing to the accident was the pilot's inability to properly identify the runway environment, and the improper in-flight decision to initiate a go-around.NTSB ATL07CA022Accident · No injuriesData collectionFinal reportCessna 172N · Reidsville, NCThe pilot's failure to maintain directional control of the airplane during landing roll, which resulted in an on ground collision with trees.NTSB DFW07CA028Accident · No injuriesData collectionFinal reportCessna 172N · Spring, TXLoss of directional control for undetermined reasons.NTSB NYC07CA014Accident · No injuriesData collectionFinal reportCessna 172N · Morgantown, WVThe student pilot's failure to maintain directional control and the flight instructor's improper planning and supervision of the student's solo cross country flight. A contributing factor was the wind gusts.NTSB CHI07CA006Accident · No injuriesData collectionFinal reportCessna 172N · Grand Rapids, MNThe student pilot's misjudged landing flare and improper recovery from the bounced landing which led to the failure of the nose landing gear. The overload failure of the nose landing gear was a factor.NTSB CHI07CA004Accident · No injuriesData collectionFinal reportCessna 172N · St Charles, MOThe pilot's failure to properly judge the landing flare and his inadequate recovery from the resulting bounced landing. A contributing factor was the inadvertent pilot induced oscillation (porpoise) after initial runway contact.NTSB MIA06CA134Accident · Minor injuriesData collectionFinal reportCessna 172N · Pensacola, FLThe student pilot's failure to raise the wing flaps for a go-around resulting in the airplane not climbing and an in-flight collision with trees.NTSB NYC06CA196Accident · No injuriesData collectionFinal reportCessna 172N · Windsor, NHThe pilot's delay in aborting the takeoff, which resulted in an overrun and subsequent collision with trees. A factor in the accident was the tailwind.NTSB ANC06LA104Accident · No injuriesLimited investigationFinal reportCessna 172N · Anchorage, AKThe possible loss of engine power during takeoff/initial climb for an unknown reason, which resulted in a forced landing in rough terrain and a nose over.NTSB CHI06CA204Accident · Minor injuriesData collectionFinal reportCessna 172N · Wadsworth, OHThe pilot used an improper aborted takeoff procedure in that she failed to reduce the engine power. Factors associated with the accident were the tailwind, the wrong runway selection, the pilot's lack of experience, the guard rail, and the embankment.NTSB DFW06FA187Accident · 2 fatalField investigationFinal reportCessna 172N · Petal, MSThe pilot's improper use of flaps, which resulted in an impact with trees during takeoff-initial climb.NTSB NYC06LA179Accident · 1 fatalLimited investigationFinal reportCessna 172N · Pompton Lakes, NJImproper maintenance of the throttle shaft, which resulted in a partial loss of engine power during cruise flight, and subsequent impact with trees during a forced landing.NTSB NYC06FA154Accident · 4 fatalField investigationFinal reportCessna 172N · Newry, METhe flight instructor's failure to maintain altitude/clearance while maneuvering, which resulted in an impact with trees.NTSB CHI06CA151Accident · No injuriesData collectionFinal reportCessna 172N · Athens, OHThe student pilot's inadequate compensation for the wind conditions. Factors associated with the accident were the gusty crosswind, and the ditch.NTSB NYC06LA124Accident · Minor injuriesLimited investigationFinal reportCessna C-172N · Vineyard Haven, MAThe pilot's improper preflight planning and improper fuel consumption calculations, which resulted in fuel exhaustion and a subsequent loss of engine power.NTSB MIA06CA101Accident · No injuriesData collectionFinal reportCessna 172N · Miami, FLThe improper flare by the pilot resulting in a hard landing and substantial damage to the airplane.NTSB SEA06CA098Accident · No injuriesData collectionFinal reportCessna 172N · Billings, MTThe pilot's failure to maintain clearance from a sign while taxiing to parking.NTSB MIA06CA088Accident · No injuriesData collectionFinal reportCessna 172N · Daytona Beach, FLThe pilot's improper landing flare/touchdown, which resulted in the airplane porpoising and incurring damage.NTSB LAX06CA125Accident · Minor injuriesData collectionFinal reportCessna 172N · Compton, CAcontrol interference by the student pilot during a go-around that resulted in an in-flight collision with power lines.NTSB CHI06LA084Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Muncie, INThe loss of engine power during the final approach to land for an undetermined reason.NTSB CHI06CA083Accident · No injuriesData collectionFinal reportCessna 172N · New Hudson, MIThe solo student pilot's failure to properly compensate for the crosswind, resulting in his failure to maintain directional control during landing. Factors were the crosswind and the snow bank.NTSB LAX06LA108Accident · No injuriesLimited investigationFinal reportCessna 172N · Sacramento, CAthe failure of the pilot of the other airplane to maintain an adequate clearance from obstacles while taxiing.NTSB SEA06LA049Accident · No injuriesLimited investigationFinal reportCessna 172N · Snohomish, WACarburetor heat was not used during the initial climb in probable serious carburetor icing conditions during cruise power. Carburetor icing conditions and wet terrain were factors.NTSB LAX06LA065Accident · No injuriesLimited investigationFinal reportCessna 172N · La Verne, CAthe failure of the pilot of the other aircraft to comply with his air traffic control clearance and line up for the proper runway, and his failure to maintain an adequate visual lookout, which resulted in his in-flight collision with the Cessna airplane.NTSB DFW06CA030Accident · No injuriesData collectionFinal reportCessna 172N · Arlington, TXThe students improper recovery from a bounced landing. A contributing factor was the pilots excessive airspeed on final approach.NTSB ATL06CA118Accident · No injuriesData collectionFinal reportCessna 172N · Perry, GAThe student pilot's failure to maintain airspeed during a touch-and-go landing on initial takeoff climb, resulting in a hard landing on the departure runway.NTSB DFW06CA026Accident · No injuriesData collectionFinal reportCessna 172N · Sherman, TXThe pilot's failure to maintain directional control during takeoff.NTSB MIA06CA009Accident · No injuriesData collectionFinal reportCessna 172N · Punta Gorda, FLThe in-flight collision with a bird resulting in substantial damage to the airplane.NTSB ANC05CA132Accident · No injuriesData collectionFinal reportCessna 172 · Tyonek, AKThe pilot's inadequate compensation for wind conditions during takeoff-initial climb, which resulted in a loss of control, and subsequent in-flight collision with a creek. A factor associated with the accident is a sudden windshift.NTSB LAX05CA276Accident · No injuriesData collectionFinal reportCessna 172N · Ramona, CAthe pilot's failure to maintain directional control during landing.NTSB DEN05LA127Accident · No injuriesLimited investigationFinal reportCessna 172N · Cedar City, UTthe loss of engine power for reasons undetermined. Contributing factors include the lack of suitable terrain for a forced landing, and the soft dirt.NTSB LAX05CA240Accident · No injuriesData collectionFinal reportCessna 172N · North Las Vegas, NVthe student pilot's failure to maintain directional control.NTSB SEA05LA145Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Bonners Ferry, IDThe pilot's failure to maintain terrain clearance while maneuvering. Mountainous terrain was a factor.NTSB ATL05FA128Accident · 1 fatalField investigationFinal reportCessna 172N · Penrose, NCA loss of engine power for undetermined reasons. Contributing to the accident was the pilot's failure to use the full length of the runway for takeoff, and the inadvertent stall.NTSB ANC05CA099Accident · No injuriesData collectionFinal reportCessna 172 · Akiachak, AKThe pilot's delay in aborting the landing, which resulted in the airplane running off the end of the runway and nosing over. A factor associated with the accident was the rough/uneven terrain off the end of the runway.NTSB NYC05LA106Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Edgartown, MAThe pilot's failure to maintain airspeed during a go-around, which resulted in an inadvertent stall and subsequent impact with terrain. [This report was modified on June 10, 2008]NTSB DEN05LA093Accident · No injuriesLimited investigationFinal reportCessna 172N · Hudson, COThe flight instructor's improper use raising of the flaps. Contributing factors were the student pilot's misunderstanding of the instructor's intentions, the instructor's inadequate supervision of the student pilot, the density altitude, and the soft terrain.NTSB LAX05CA191Accident · No injuriesData collectionFinal reportCessna 172N · Stockton, CAthe pilot's improper use of the brakes, and his failure to maintain directional control during the landing rollout.NTSB LAX05CA148Accident · No injuriesData collectionFinal reportCessna 172N · Palo Alto, CAThe student's failure to maintain directional control and the CFI's failure to adequately supervise the flight.NTSB NYC05CA073Accident · No injuriesData collectionFinal reportCessna 172N · Wellington, OHThe pilot's failure to obtain the proper touchdown point, and his failure to initiate a go-around, which resulted in an overrun during landing. A factor in the accident was the tail wind.NTSB DFW05LA103Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Olney, TXThe loss of engine power due to carburetor ice. Contributing factors were the weather conditions conducive for carburetor icing and the lack of suitable terrain for a forced landing.NTSB LAX05CA128Accident · No injuriesData collectionFinal reportCessna 172N · San Jose, CAthe student pilot's misjudged landing flare, which resulted in a hard landing.NTSB DFW05CA091Accident · No injuriesData collectionFinal reportCessna 172N · Rio Grande City, TXThe pilot's failure to maintain clearance from objects, and his improper compensation for wind conditions while landing. A contributing factor was the gusty wind condition.NTSB LAX05CA111Accident · No injuriesData collectionFinal reportCessna 172A · Emigrant Gap, CAthe pilot's inadequate preflight planning and his selection of an unsuitable landing area, resulting in an encounter with a snow-covered runway.NTSB IAD05LA043Accident · No injuriesLimited investigationFinal reportCessna 172N · Frederick, MDThe inadequate visual lookout of the pilots in each airplane, which resulted in a ground collision.NTSB ANC05FA037Accident · 1 fatalField investigationFinal reportCessna 172 · Cedar Key, FLThe pilot's continued flight into instrument meteorological conditions (IMC), and his failure to maintain adequate airspeed during an abrupt maneuver to avoid a power line, which resulted in an inadvertent stall, a loss of control, and subsequent collision…
Back to Cessna 172N