Cessna 172S
NTSB investigations · 589
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 ('2072439', '2072442')
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 ('2072439', '2072442')
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 CEN23LA354Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Clewiston, FLThe student pilot’s improper landing flare, which resulted in a hard landing on the nose landing gear. Contributing to the accident was the flight instructor’s inadequate supervision of the student pilot.NTSB WPR23LA298Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Long Beach, CAThe flight instructor’s inattention during ground operations, which resulted in unintentional movement of the airplane and ground collision with another airplane.NTSB WPR23LA253Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Novato, CAThe pilot's failure to maintain directional control of the airplane during the landing roll for a touch and go, which resulted in a collision with terrain.NTSB WPR23LA199Accident · No injuriesClass 3 · LimitedFinal reportCessna 172S · Casa Grande, AZAn in-flight separation of the throttle linkage, which resulted in a loss of throttle control. Contributing to the accident was maintenance personnel’s failure to follow the maintenance manual inspection procedure for the throttle cable assembly.NTSB CEN23LA175Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Brookings, SDThe student pilot’s failure to maintain pitch and directional control during the takeoff roll. Contributing to the accident, was the student pilot’s delay in relinquishing control of the airplane and the instructor's delayed reaction before the loss of…NTSB WPR23FA172Accident · 1 fatalClass 3 · FieldFinal reportCessna 172S · Los Angeles, CAThe pilot’s failure to maintain clearance with the hilly terrain resulting from his loss of situational awareness due to the deteriorating weather conditions as he descended to approach his destination airport.NTSB CEN23LA159Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Fredericksburg, TXThe pilot’s failure to maintain airplane control during an attempted go-around resulting in abnormal contact with the runway pavement and a runway excursion.NTSB CEN23LA122Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Princeton, MNThe pilot’s failure to maintain directional control during the takeoff roll. Contributing to the accident, was the runway condition combined with a right crosswind.NTSB CEN23LA102Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Limon, COThe pilot’s failure to maintain directional control during the takeoff roll.NTSB ERA23LA085Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Knoxville, TNThe pilot’s loss of directional control during engine start.NTSB CEN23LA035Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Olathe, KSThe inflight collision with multiple geese during initial climb.NTSB ERA23LA022Accident · 1 fatalClass 3 · LimitedFinal reportCessna 172S · Statesboro, GAThe pilot’s failure to include deplaning procedures as part of a passenger safety briefing and failure to have the passengers remain onboard until the engine was shut down, which resulted in a passenger subsequently being struck by the rotating propeller.NTSB ERA23LA017Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Sanford, FLThe pilot's unstable approach, which resulted in a hard landing and impact with a runway threshold light. Also causal was the flight instructor’s failure to take remedial action to prevent the hard landing.NTSB ERA23FA001Accident · 3 fatalClass 3 · FieldFinal reportCessna 172S · Hermantown, MNThe pilot’s loss of airplane control due to spatial disorientation during initial climb in dark night and low instrument meteorological conditions, which resulted in a descent into terrain. Contributing to the accident was the pilot’s fatigue due to a long…NTSB CEN22FA424Accident · 3 fatalClass 3 · FieldFinal reportCessna 172S · Longmont, COThe pilots’ inability to see and avoid each other, resulting in a midair collision.NTSB CEN22LA281Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Fargo, NDThe flight instructor’s failure to adequately monitor the pilot flying, which resulted in a nose-wheel first hard landing.NTSB CEN22LA194Accident · No injuriesClass 3 · LimitedFinal reportCessna 172S · Traverse City, MIThe failure of maintenance personnel to properly torque a fuel line “B” nut, which resulted in a total loss of engine power.NTSB WPR22LA123Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · San Carlos, CAThe pilot’s improper landing flare which resulted in a bounced landing.NTSB ERA22LA087Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Hazleton, PAThe pilot’s failure to maintain proper airspeed on approach in tailwind conditions, which resulted in an extended touchdown, bounced landing, and runway excursion.NTSB ERA22LA084Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Midland, VACollision with a bird in flight, which resulted in damage to the right-wing leading-edge spar.NTSB ERA22LA065Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Palm Coast, FLThe student pilot’s improper landing flare and subsequent improper recovery from a bounced landing, resulting in a hard landing and substantial damage to the lower fuselage and firewall.NTSB ERA22FA058Accident · 2 fatalClass 3 · FieldFinal reportCessna 172 · Branchville, NJThe flight instructor’s failure to recover from a steep spiral turn during an instructional flight.NTSB CEN22LA056Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Madison, MSThe student pilot’s failure to maintain aircraft control following a bounced landing.NTSB ERA22LA029Accident · No injuriesClass 3 · LimitedFinal reportCessna 172 · Westhampton Beach, NYA total loss of engine power during cruise flight for reasons that could not be determined based on the available evidence.NTSB ERA21LA388Accident · No injuriesClass 3 · LimitedFinal reportCessna 172 · Port Orange, FLThe separation of the nut from the stud and the fracture of the bolt that secured the crankshaft idler gear to the engine crankcase, which resulted in a total loss of engine power due to the inability of the left crankshaft idler gear assembly to drive of the…NTSB CEN21LA414Accident · Minor injuriesClass 3 · LimitedFinal reportCessna 172S · LaSalle, COA loss of engine power for undetermined reasons.NTSB ERA21LA359Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Venice, FLMaintenance personnel’s failure to use the correct throttle linkage hardware when reinstalling the engine, resulting in a disconnection of the throttle during flight.NTSB ERA21LA302Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Brooksville, FLThe pilot's failure to maintain an appropriate distance between the airplane and hangar, which resulted in substantial damage to the right wing.NTSB ERA21LA282Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Mount Pocono, PAThe pilot’s loss of aircraft control following a bounced landing.NTSB ERA21LA314Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Clarksville, TNThe flight instructor’s inadequate remedial action during takeoff, which resulted in a runway excursion.NTSB WPR21LA303Accident · No injuriesClass 3 · LimitedFinal reportCessna 172S · Yelm, WAA total loss of engine power for reasons that could not be determined based on the available evidence.NTSB CEN21LA268Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Saint James, LAThe in-flight fatigue failure of an air-conditioning system hose which resulted in a precautionary landing and impact with a road sign.NTSB CEN21LA235Accident · Minor injuriesClass 4 · LimitedFinal reportCessna 172 · McAllen, TXThe student pilot’s failure to maintain directional control during landing, which resulted in a runway excursion and collision with a runway sign.NTSB ERA21LA215Accident · Minor injuriesClass 4 · LimitedFinal reportCessna 172 · Daytona Beach, FLBoth pilots’ failure to maintain control during the landing flare and the flight instructor’s failure to maintain control during an attempted go-around, in gusting quartering headwind conditions, which resulted in the exceedance of the airplane’s critical…NTSB ERA21LA202Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Martinsville, VAThe pilot’s improper pitch control during a go-around in gusting crosswind conditions, which resulted in a tail strike and a runway excursion.NTSB ERA21LA187Accident · No injuriesClass 3 · LimitedFinal reportCessna 172S · Venice, FLA total loss of engine power for reasons that could not be determined based on the available information.NTSB ERA21LA180Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Orangeburg, SCThe student pilot’s improper recovery from a bounced landing, which resulted in a hard landing.NTSB WPR21LA140Accident · Minor injuriesClass 3 · LimitedFinal reportCessna 172S · Everett, WAA total loss of engine power during climb, for reasons that could not be determined based on available evidence.NTSB CEN21LA160Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Watkins, COThe pilot’s failure to maintain directional control during takeoff and the instructor pilot’s inadequate supervision of the pilot’s takeoff.NTSB ERA21LA128Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Orange, VAThe student pilot’s improper recovery from a bounced landing.NTSB ERA21LA092Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Culpeper, VAThe pilot’s decision to land the airplane in crosswind conditions that exceeded the airplane’s maximum demonstrated crosswind velocity.NTSB CEN21LA083Accident · Serious injuriesClass 4 · LimitedFinal reportCessna 172 · Glencoe, MNA bystander’s inadvertent contact with the propeller while the engine was running.NTSB ERA21LA057Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Sanford, NCThe pilot's loss of directional control during takeoff in crosswind conditions, which resulted in a runway excursion and impact with terrain.NTSB CEN21LA066Accident · No injuriesClass 3 · LimitedFinal reportCessna 172 · Lawrence, KSThe student pilot’s improper landing flare/touchdown which resulted in a hard landing.NTSB CEN20LA419Accident · Serious injuriesClass 3 · LimitedFinal reportCessna 172S · San Marcos, TXThe F1 pilot’s failure to see and avoid the lower altitude Cessna while on final approach for landing. Contributing to the accident were the restrictions to pilot visibility inherent to low- and high-wing airplanes, and both pilots’ failure to recognize the…NTSB WPR20CA293Accident · No injuriesClass 4 · Data collectionFinal reportCessna 172 · Phoenix, AZThe pilot's improper pitch attitude and landing flare, which resulted in a hard landing. Contributing to the accident was the flight instructors delayed remedial action.NTSB WPR20LA256Accident · No injuriesClass 3 · LimitedFinal reportCessna 172 · San Jose, CAThe airplane’s collision with a bird while maneuvering in the airport traffic pattern.NTSB ERA20LA247Accident · No injuriesClass 3 · LimitedFinal reportCessna 172 · Fort Lauderdale, FLThe failure of both pilots to see and avoid each other while taxiing, which resulted in a ground collision. Contributing to the accident was the tower controller’s failure to provide information to each pilot regarding the position and intention of the other…NTSB ERA20CA263Accident · No injuriesClass 4 · Data collectionFinal reportCessna 172 · Prattville, ALThe student pilot's failure improper landing flare, which resulted in a hard landing.NTSB CEN20CA205Accident · No injuriesClass 4 · Data collectionFinal reportCessna 172 · Lakeview, ARThe pilot’s failure to maintain control of the airplane during the takeoff.
Back to Cessna 172S