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 OPS12IA041Incident · No injuriesIncident investigationFinal reportCessna 172S · Daytona Beach, FLThe departing pilot's incorrect runway selection and non-compliance with an air traffic control clearance. Contributing to the incident was the air traffic controller's inadequate monitoring of the departing aircraft to ensure that the pilot complied with the…NTSB ERA11CA516Accident · No injuriesData collectionFinal reportCessna 172S · Westminster, MDThe pilot's inadequate recovery from a bounced landing, which resulted in a loss of airplane control. Contributing to the accident was the pilot's improper approach airspeed for a short-field landing.NTSB WPR11CA466Accident · Minor injuriesData collectionFinal reportCessna 172S · Phoenix, AZThe pilot’s failure to maintain directional control during the landing rollout.NTSB WPR11CA440Accident · No injuriesData collectionFinal reportCessna 172 · Phoenix, AZThe pilot's failure to maintain directional control during the landing roll.NTSB CEN11CA624Accident · No injuriesData collectionFinal reportCessna 172S · Bemidji, MNThe student pilot's improper flare, which resulted in a hard landing.NTSB WPR11LA362Accident · Minor injuriesLimited investigationFinal reportCessna 172S · Syracuse, UTThe failure of the maintenance technicians who installed the engine to properly tighten the fuel injection servo to a spider supply line, which caused a loss of engine power due to fuel starvation.NTSB ERA11CA408Accident · No injuriesData collectionFinal reportCessna 172S · Cambridge, MDThe student pilot's improper recovery from a bounced landing.NTSB WPR11LA284Accident · No injuriesLimited investigationFinal reportCessna 172S · Palo Alto, CAA total loss of engine power for undetermined reasons during the landing approach over unsuitable terrain.NTSB ERA11CA343Accident · No injuriesData collectionFinal reportCessna 172S · Covington, GAThe pilot's failure to maintain directional control during takeoff.NTSB CEN11CA392Accident · No injuriesData collectionFinal reportCessna 172S · Cortez, COThe pilot's failure to maintain aircraft control while landing in gusty crosswind conditions.NTSB CEN11LA386Accident · No injuriesLimited investigationFinal reportCessna 172S · Grand Forks, NDThe flight instructor’s delayed remedial action to the student pilot’s bounced landing and subsequent loss of aircraft control.NTSB WPR11LA201Accident · No injuriesLimited investigationFinal reportCessna 172S · Payson, AZThe pilot's decision to conduct a touch-and-go arrival during his first flight to a high elevation airport, which resulted in an improper mixture adjustment and a partial loss of engine power for the takeoff and attempted climbout.NTSB ERA11CA244Accident · No injuriesData collectionFinal reportCessna 172S · Saint Petersburg, FLThe failure of the student pilot to maintain directional control during a touch-and-go landing.NTSB ERA11FA146Accident · 2 fatalField investigationFinal reportCessna 172S · New Smyrna Beach, FLThe flight instructor's failure to recognize or implement adequate remedial action to counter the effects of spatial disorientation. Contributing to the accident was the spatial disorientation experienced by one or both pilots.NTSB ERA11CA147Accident · No injuriesData collectionFinal reportCessna 172S · Daytona Beach, FLThe pilot's inadequate flare that resulted in a hard landing.NTSB ERA11CA132Accident · No injuriesData collectionFinal reportCessna 172S · St. Petersburg, FLThe student pilot's failure to maintain directional control while attempting to turn the airplane onto a taxiway after landing.NTSB CEN11CA158Accident · No injuriesData collectionFinal reportCessna 172S · McKinney, TXThe student pilot's loss of directional control during takeoff, which resulted in a runway excursion and impact with terrain.NTSB ERA11FA118Accident · 2 fatalField investigationFinal reportCessna 172S · North Myrtle Beach, SCThe pilot's loss of airplane control during a missed approach due to spatial disorientation.NTSB ERA11CA096Accident · No injuriesData collectionFinal reportCessna 172S · Fort Myers, FLThe pilot's failure to maintain directional control during the takeoff roll. Contributing to the accident was the pilot’s attempt to take off with full flaps.NTSB ERA11LA100Accident · No injuriesLimited investigationFinal reportCessna 172 · St. ThomasThe pilot's failure to maintain an adequate visual lookout while taxiing.NTSB CEN11CA100Accident · No injuriesData collectionFinal reportCessna 172S · Lawrence, KSThe student pilot’s non-stabilized approach and improper landing flare, which resulted in a hard landing.NTSB WPR11CA037Accident · No injuriesData collectionFinal reportCessna 172S · Port Townsend, WAThe pilot's improper flare/touchdown while landing, resulting in a loss of directional control and a runway excursion.NTSB WPR11CA035Accident · No injuriesData collectionFinal reportCessna 172S · Branscomb, CAThe pilot's failure to maintain clearance from trees during the landing roll on an unimproved airstrip.NTSB ERA11LA015Accident · No injuriesLimited investigationFinal reportCessna 172SP · Boynton Beach, FLThe loss of engine power for undetermined reasons.NTSB ERA10CA505Accident · No injuriesData collectionFinal reportCessna 172S · Franconia, NHThe pilot’s delay in initiating a go-around, which resulted in an in-flight collision with a fence.NTSB CEN10LA563Accident · No injuriesLimited investigationFinal reportCessna 172S · Longmont, COThe pilot's inadequate landing flare and improper recovery from a bounced landing.NTSB ERA10CA468Accident · No injuriesData collectionFinal reportCessna 172S · Frederick, MDUndetermined.NTSB WPR10CA475Accident · No injuriesData collectionFinal reportCessna 172S · Santa Maria, CAThe pilot's inadequate flare which resulted in a bounce and hard landing.NTSB ERA10CA398Accident · No injuriesData collectionFinal reportCessna 172 · White Plains, NYThe student pilot's improper landing flare and the flight instructor's delayed remedial action resulting in a bounced landing.NTSB ERA10CA358Accident · No injuriesData collectionFinal reportCessna 172 · Fairhope, ALThe student pilot's failure to maintain directional control during a crosswind takeoff.NTSB CEN10LA381Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Goddard, KSThe pilot did not maintain airspeed during takeoff, which resulted in an aerodynamic stall. Contributing to the accident was the pilot’s poor preflight planning.NTSB ERA10CA363Accident · No injuriesData collectionFinal reportCessna 172S · Chesapeake, VAA hard landing by person(s)unknown.NTSB ERA10CA350Accident · No injuriesData collectionFinal reportCessna 172S · Salisbury, MDThe student pilot's improper recovery from a bounced landing.NTSB CEN10CA325Accident · No injuriesData collectionFinal reportCessna 172 · Traverse City, MIDamage to the firewall for undetermined reasons.NTSB ERA10CA326Accident · No injuriesData collectionFinal reportCessna 172 · New Smyrna Beach, FLThe student pilot’s improper landing flare, and the flight instructor's delayed remedial action.NTSB ERA10CA305Accident · No injuriesData collectionFinal reportCessna 172S · Baltimore, MDThe pilot’s improper flare, which resulted in a hard landing. Contributing to the accident was the pilot’s improper decision to land during a thunderstorm.NTSB CEN10CA289Accident · No injuriesData collectionFinal reportCessna 172S · Greenfield, INThe pilot's improper landing flare and recovery from a bounced landing.NTSB ERA10CA278Accident · No injuriesData collectionFinal reportCessna 172S · East Haddam, CTThe pilot's delayed decision to attempt a go-around, and his subsequent failure to maintain directional control while landing.NTSB ERA10CA282Accident · No injuriesData collectionFinal reportCessna 172S · Jekyll Island, GAThe pilot's loss of airplane control while landing with a crosswind.NTSB WPR10CA238Accident · No injuriesData collectionFinal reportCessna 172S · Corvallis, ORThe pilot's improper use of the flight and engine controls, resulting in a bounced landing.NTSB WPR10CA230Accident · No injuriesData collectionFinal reportCessna 172S · Palo Alto, CAThe student pilot's failure to maintain directional control and the certified flight instructor’s delayed response to the student pilot's loss of control during the takeoff roll.NTSB ERA10CA200Accident · No injuriesData collectionFinal reportCessna 172 · Sarasota, FLThe student pilot's inadequate recovery from a bounced landing.NTSB CEN10CA176Accident · No injuriesData collectionFinal reportCessna 172S · Mckinney, TXThe student pilot's loss of directional control while landing with a crosswind.NTSB CEN10CA163Accident · No injuriesData collectionFinal reportCessna 172S · Lawrence, KSThe student pilot's failure to maintain an appropriate glide path during approach. Contributing to the accident was the student pilot's decision to continue the approach instead of going around.NTSB ERA10LA105Accident · 1 fatalLimited investigationFinal reportCessna 172S · Greenbush, METhe pilot's improper decision to attempt a transoceanic flight in turbulent, icing conditions, with an overweight airplane that was not approved for moderate turbulence and not equipped with deicing systems. Contributing to the accident was the pilot's…NTSB ERA10FA091Accident · 4 fatalField investigationFinal reportCessna 172S · Kissimmee, FLThe pilot's decision to depart under special VFR flight at night when instrument meteorological conditions prevailed at the departure airport and along the route of flight and his continued VFR flight into instrument meteorological conditions, which resulted…NTSB CEN10CA062Accident · No injuriesData collectionFinal reportCessna 172S · Mt. Comfort, INThe pilot's failure to maintain directional control of the airplane while touching down during the landing.NTSB ERA10CA057Accident · No injuriesData collectionFinal reportCessna 172S · Summit, DEThe student pilot’s failure to maintain directional control during takeoff.NTSB ERA10FA048Accident · 2 fatalField investigationFinal reportCessna 172S · Tallahassee, FLThe pilots' spatial disorientation during flight in dark conditions, which resulted in an uncontrolled descent into terrain.NTSB CEN10CA025Accident · No injuriesData collectionFinal reportCessna 172S · Grand Forks, NDThe student pilot's improper landing flare and recovery from a bounced landing.
Back to Cessna 172S