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 GAA16CA188Accident · No injuriesData collectionFinal reportCessna 172 · Payson, AZThe student pilot's failure to maintain pitch control during the landing flare, resulting in the subsequent porpoise during landing and substantial damage to the firewall.NTSB GAA16CA158Accident · No injuriesData collectionFinal reportCessna 172 · Frederick, MDThe student pilot's improper pitch control during the landing flare, which resulted in a hard bounced landing.NTSB GAA16CA187Accident · No injuriesData collectionFinal reportCessna 172 · Scottsdale, AZThe failure of the student pilot to maintain pitch control while landing, which resulted in a hard landing, loss of directional control, and runway excursion.NTSB OPS16IA009IncidentClass 3 · IncidentFinal reportCessna 172S · Honolulu, HIThe air traffic controller's decision to clear an aircraft to land on a runway occupied by another aircraft that had previously been instructed to line up and wait. Contributing to the runway incursion was the failure of the air traffic controller to visually…NTSB GAA16CA134Accident · No injuriesData collectionFinal reportCessna 172 · Newport News, VAThe student pilot's failure to maintain directional control during the landing roll, resulting in a runway excursion and impact with terrain.NTSB WPR16LA063Accident · No injuriesLimited investigationFinal reportCessna 172S · San Diego, CAThe failure of the flight instructor of the other airplane to maintain awareness while parked on the ramp with the engine operating, which resulted in impact with the parked airplane.NTSB GAA16CA104Accident · No injuriesData collectionFinal reportCessna 172 · Dothan, ALThe pilot-rated student's hard landing, which resulted in fuselage damage.NTSB GAA16CA093Accident · No injuriesData collectionFinal reportCessna 172 · Newton, IAThe pilot's failure to maintain airplane control during the takeoff, resulting in a runway excursion, and airplane nose over.NTSB ANC16LA011Accident · 1 fatalLimited investigationFinal reportCessna 172 · Anchorage, AKThe pilot's intentional flight into a building.NTSB WPR16LA024Accident · Minor injuriesLimited investigationFinal reportCessna 172S · San Jose, CAThe pilot's failure to maintain directional control during the landing roll at night, which resulted in a runway excursion.NTSB GAA16CA048Accident · No injuriesData collectionFinal reportCessna 172 · Mesa, AZThe pilot's failure to maintain pitch control during landing, resulting in a porpoise, and firewall damage.NTSB GAA16CA052Accident · No injuriesData collectionFinal reportCessna 172S · Alcoa, TNThe pilot's failure to identify the taxiway, which resulted in a runway excursion and impact with terrain while turning off the runway at night.NTSB ERA16LA008Accident · 1 fatalLimited investigationFinal reportCessna 172S · Seville, FLThe airplane’s encounter with a downdraft, and the pilot's decision to maneuver the airplane at a low altitude and airspeed, which provided insufficient time and altitude to recover before impacting terrain.NTSB ERA15LA366Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Bally, PAThe pilot's failure to maintain altitude during low-level aerobatic maneuvers. Contributing to the accident were the pilot's improper decision to attempt the low-level aerobatic maneuvers and his impairment due to psychiatric conditions and the medications he…NTSB GAA15CA237Accident · No injuriesData collectionFinal reportCessna 172 · Springfield, OHThe pilot's improper pitch control during landing, which resulted in a hard landing.NTSB ERA15LA274Accident · No injuriesLimited investigationFinal reportCessna 172S · Linden, NJThe pilot’s delayed decision to reject the takeoff, which resulted in a runway overrun. Contributing to the accident was the pilot’s failure to properly configure the flaps for maximum takeoff performance with the airplane near its maximum gross weight.NTSB GAA15CA140Accident · No injuriesData collectionFinal reportCessna 172 - S · Traverse City, MIThe student pilot's failure to maintain pitch control during the landing, resulting in a hard landing.NTSB GAA15CA241Accident · No injuriesData collectionFinal reportCessna 172 · Upperville, VAAn inflight bird strike, which resulted in wing spar damage.NTSB GAA15CA161Accident · No injuriesData collectionFinal reportCessna 172S · Galesburg, ILFirewall damage reported by maintenance personnel that occurred during an unknown phase of flight, because the accident flight and pilot could not be determined.NTSB WPR15FAMS1Accident · 1 fatalMissing aircraftFinal reportCessna 172S · Davenport, CAUndetermined because the airplane was not located.NTSB GAA15CA064Accident · No injuriesData collectionFinal reportCessna 172S · Daytona Beach, FLThe landing airplane pilot's failure to maintain directional control during landing, which resulted in a runway excursion and ground collision with a taxiing airplane.NTSB GAA15CA046Accident · No injuriesData collectionFinal reportCessna 172S · Naples, FLThe pilot's failure to maintain airplane control, resulting in a hard landing.NTSB GAA15CA026Accident · No injuriesData collectionFinal reportCessna 172S · Vernal, UTThe student pilot's failure to maintain attitude control during landing flare.NTSB GAA15CA018Accident · No injuriesData collectionFinal reportCessna 172S · Camarillo, CAThe pilot involved and the phase of flight when the damage occurred were not determined.NTSB ERA15CA150Accident · No injuriesData collectionFinal reportCessna 172S · Richmond, VAThe student pilot's inadequate landing flare which resulted in a hard landing and substantial damage to the airplane.NTSB ERA15LA094Accident · No injuriesLimited investigationFinal reportCessna 172 · Norfolk, VAThe engine’s failure to regain full power after a simulated engine failure for reasons that could not be determined during postaccident examinations and testing.NTSB ERA15CA056Accident · No injuriesData collectionFinal reportCessna 172S · Sarasota, FLThe student pilot's failure to maintain airplane control during the initial climb, resulting in a runway excursion and substantial damage to the engine firewall. The student pilot's lack of overall flying experience was a factor.NTSB ERA15FA046Accident · 1 fatalField investigationFinal reportCessna 172 · Hinton, VAThe flight instructor’s decision to conduct a night training flight in mountainous terrain without conducting or allowing the student to conduct appropriate preflight planning and his lack of situational awareness of the surrounding terrain altitude, which…NTSB WPR15LA025Accident · No injuriesLimited investigationFinal reportCessna 172S · Santa Monica, CAThe separation of a section of a propeller blade due to fatigue cracking. Contributing to the accident was the operator’s failure to comply with the manufacturer’s maintenance and inspection instructions.NTSB WPR15CA028Accident · No injuriesData collectionFinal reportCessna 172 - S · Hawthorne, CAThe pilot's improper flare which resulted in a loss of aircraft control and subsequent hard landing.NTSB WPR15LA014Accident · Serious injuriesLimited investigationFinal reportCessna 172S · Big Bear, CAA partial loss of engine power for reasons that could not be determined because postaccident examination of the airframe and engine did not reveal any anomalies that would have precluded normal operation.NTSB WPR15CA004Accident · Minor injuriesData collectionFinal reportCessna 172S · Sedona, AZThe pilot's failure to maintain airplane control during the landing roll out.NTSB ERA14CA452Accident · No injuriesData collectionFinal reportCessna 172S · Naples, FLThe student pilot's improper landing flare, which resulted in a hard landing. Contributing to the accident was the pilot's self-induced pressure to land due to the deteriorating weather conditions.NTSB WPR14CA351Accident · No injuriesData collectionFinal reportCessna 172S · Santa Ynez, CAThe student pilot's inadequate flare and loss of aircraft control during landing, which resulted in multiple bounces.NTSB ERA14CA317Accident · Minor injuriesData collectionFinal reportCessna 172S · Orlando, FLThe flight instructor's failure to maintain control while taxiing in a strong gusty wind.NTSB CEN14CA322Accident · No injuriesData collectionFinal reportCessna 172S · Knox, INThe student pilot's use of excessive back pressure on the flight controls during an attempted go around that induced a stall and loss of control.NTSB ERA14FA283Accident · 2 fatalField investigationFinal reportCessna 172S · Daytona Beach, FLA partial loss of engine power during the initial climb after takeoff for reasons that could not be determined due to the postaccident condition of the wreckage. Contributing to the accident was the pilots' decision to turn back to the airport, which led to…NTSB ERA14CA273Accident · No injuriesData collectionFinal reportCessna 172S · Harrisburg, PAThe pilot's failure to compensate for wind conditions during landing, which resulted in a hard landing.NTSB WPR14CA163Accident · No injuriesData collectionFinal reportCessna 172S · Everett, WAThe pilot's failure to maintain directional control during a takeoff, which resulted in the airplane veering off the runway surface and colliding with a sign.NTSB CEN14CA191Accident · No injuriesData collectionFinal reportCessna 172S · Albuquerque, NMThe student pilot's improper flare that resulted in a bounced landing.NTSB CEN14CA187Accident · No injuriesData collectionFinal reportCessna 172 · Larimore, NDFailure of the pilot to attain and maintain sufficient control inputs to compensate for the crosswind. Contributing to the accident was the flight instructor's failure to adequately monitor the pilot and the flight.NTSB ERA14CA127Accident · Minor injuriesData collectionFinal reportCessna 172S · Caldwell, NJThe pilot's failure to maintain directional control while landing.NTSB ERA14CA124Accident · No injuriesData collectionFinal reportCessna 172S · Mansfield, MAThe student pilot's failure to maintain an adequate approach glide path, which resulted in a collision with a snow bank.NTSB ERA14CA109Accident · No injuriesData collectionFinal reportCessna 172S · Immokalee, FLThe student pilot's improper landing flare, which resulted in a hard landing.NTSB ERA14CA078Accident · No injuriesData collectionFinal reportCessna 172S · Miami, FLThe pilot's improper flare during a gusty, crosswind landing.NTSB CEN14CA070Accident · No injuriesData collectionFinal reportCessna 172 · New Orleans, LAThe pilot's failure to maintain aircraft control after starting the engine, which resulted in a collision with a building.NTSB ERA14CA106Accident · No injuriesData collectionFinal reportCessna 172S · St. Augustine, FLThe student pilot’s failure to maintain directional control during the landing roll with a crosswind.NTSB WPR14LA025Accident · No injuriesLimited investigationFinal reportCessna 172 - S · Livermore, CAFailure of the pilots of the Pitts airplane to maneuver the airplane as necessary to observe the taxi route and avoid the Cessna airplane ahead. Contributing to the accident was the local controller's failure to provide the required warning of traffic ahead…NTSB WPR13CA397Accident · No injuriesData collectionFinal reportCessna 172S · Deer Valley, AZThe student pilot's inadequate flare and the flight instructor's delayed remedial action and failure to maintain control of the airplane during a go-around. Contributing to the accident was the flight instructor's improper go-around procedures.NTSB ERA13CA395Accident · No injuriesData collectionFinal reportCessna 172S · Fort Lauderdale, FLThe student pilot’s failure to apply power to go-around following a bounced landing resulting in abnormal runway contact and collapse of the nose landing gear.
Back to Cessna 172S