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 ERA13CA371Accident · No injuriesData collectionFinal reportCessna 172S · Manassas, VAThe student pilot’s improper recovery from a bounced landing.NTSB CEN13CA498Accident · No injuriesData collectionFinal reportCessna 172S · Indianapolis, INThe pilot's inadequate monitoring on the airplane's airspeed during the go-around, resulting in a stall.NTSB ERA13CA384Accident · No injuriesData collectionFinal reportCessna 172S · Middletown, DEThe student pilot’s improper recovery from a bounced landing.NTSB ERA13CA350Accident · No injuriesData collectionFinal reportCessna 172S · Portsmouth, NHThe pilot’s inadequate preflight inspection resulting in his failure to remove the pin he used to lock the flight controls in place of the approved control lock.NTSB WPR13CA348Accident · No injuriesData collectionFinal reportCessna 172S · Phoenix, AZA substantially damaged firewall that occurred during an unknown phase of flight for reasons that could not be determined.NTSB ERA13CA335Accident · No injuriesData collectionFinal reportCessna 172S · New Smyrna Beach, FLThe student pilot's improper landing flare and subsequent inadequate recovery from a bounced landing.NTSB WPR13CA332Accident · No injuriesData collectionFinal reportCessna 172S · Santa Barbra, CAThe pilot's inadequate landing flare, which resulted in a hard landing.NTSB WPR13CA328Accident · No injuriesData collectionFinal reportCessna 172S · Redlands, CAThe student pilot's improper flare and unsuccessful attempt to correct a bounced landing, which resulted in the overrun landing.NTSB WPR13CA309Accident · Minor injuriesData collectionFinal reportCessna 172S · Monroe, WAThe student pilot's failure to maintain directional control during the landing roll, and the flight instructor's delayed remedial action that resulted in a runway excursion.NTSB WPR13LA286Accident · No injuriesLimited investigationFinal reportCessna 172S · San Diego, CABoth pilots’ failure to maintain a proper visual lookout while taxiing during nighttime conditions, which resulted in an on-ground collision.NTSB ERA13LA291Accident · No injuriesLimited investigationFinal reportCessna 172S · Clearwater, FLA total loss of engine power for reasons that could not be determined because neither postaccident visual examinations nor test runs of the engine revealed any anomalies that would have precluded normal operation.NTSB CEN13LA348Accident · Serious injuriesLimited investigationFinal reportCessna 172S · Grand Forks, NDThe student pilot’s inadequate recovery from a bounced landing, which resulted in an aerodynamic stall during the go-around.NTSB CEN13CA335Accident · No injuriesData collectionFinal reportCessna 172S · Ann Arbor, MIThe pilot’s failure to make a go-around in a timely manner and his loss of control during landing.NTSB WPR13FA254Accident · 4 fatalField investigationFinal reportCessna 172S · Anthem, AZThe failure of the pilots in both aircraft to maintain adequate visual lookout in a known training area where multiple aircraft frequently operated, which resulted in a midair collision.NTSB CEN13CA289Accident · No injuriesData collectionFinal reportCessna 172S · Ankeny, IAThe student pilot's improper flare which resulted in a hard landing.NTSB WPR13LA180Accident · No injuriesLimited investigationFinal reportCessna 172 · Phoenix, AZThe student pilot's excessive directional control inputs during the takeoff roll and the flight instructor's delayed and ineffective corrective actions, which resulted in the loss of airplane control.NTSB WPR13CA158Accident · No injuriesData collectionFinal reportCessna 172 · Gila Bend, AZThe student pilot’s failure to maintain clearance from an above-ground fuel tank while taxiing.NTSB WPR13FA116Accident · 1 fatalField investigationFinal reportCessna 172S · Minden, NVThe pilot’s failure to maintain airplane control while maneuvering over mountainous terrain.NTSB WPR13LA062Accident · 1 fatalLimited investigationFinal reportCessna 172S · Kahului, HIThe noninstrument-rated pilot’s spatial disorientation and subsequent failure to maintain airplane control while operating over water in dark night conditions with reduced visibility due to rain in the area.NTSB ERA12FA572Accident · 1 fatalField investigationFinal reportCessna 172S · Land O'Lakes, FLThe pilot’s decision to continue the cross-country flight while fatigued, which resulted in him falling asleep during the initial descent for landing.NTSB ERA12CA560Accident · No injuriesData collectionFinal reportCessna 172S · Sebring, FLThe student pilot's improper flare, which resulted in a hard landing.NTSB ERA12CA569Accident · No injuriesData collectionFinal reportCessna 172S · Farmingdale, NYThe student pilot's improper landing flare, which resulted in a hard landing.NTSB ERA12CA496Accident · Minor injuriesData collectionFinal reportCessna 172S · Culpeper, VAThe pilot’s failure to maintain directional control during an attempted takeoff.NTSB CEN12CA510Accident · No injuriesData collectionFinal reportCessna 172S · Oshkosh, WIThe flight instructor’s loss of directional control during landing, which resulted in a collision with a runway light.NTSB CEN12CA426Accident · No injuriesData collectionFinal reportCessna 172S · Grand Forks, NDThe student pilot’s inadequate landing flare, which resulted in a hard landing.NTSB ERA12LA445Accident · No injuriesLimited investigationFinal reportCessna 172S · Allentown, PAThe student pilot's failure to maintain directional control during a touch-and-go takeoff, which resulted in a runway excursion and a subsequent impact with a gopher hole, and the flight instructor's inadequate supervision of the student pilot and his delayed…NTSB CEN12LA414Accident · Minor injuriesLimited investigationFinal reportCessna 172S · Glenwood Springs, COThe pilot's decision to fly into a mountainous area where conditions were such that the airplane was unable to climb above rising terrain. Contributing to the accident was the pilot's insufficient pilot-in-command experience and inadequate training in…NTSB ERA12CA419Accident · No injuriesData collectionFinal reportCessna 172S · West Palm Beach, FLThe flight instructor’s failure to maintain airplane control during the takeoff in gusting crosswind conditions. Contributing to the accident was the flight instructor’s decision to conduct takeoffs and landings in conditions exceeding the airplane’s maximum…NTSB ERA12CA439Accident · No injuriesData collectionFinal reportCessna 172S · Frederick, MDThe pilot's inadequate landing flare, which resulted in a hard landing.NTSB WPR12CA251Accident · No injuriesData collectionFinal reportCessna 172S · Bend, ORThe pilot’s inadequate crosswind correction, which resulted in a loss of airplane control and runway excursion into a berm.NTSB WPR12CA232Accident · No injuriesData collectionFinal reportCessna 172S · Page, AZThe pilot's failure to maintain directional control during the landing flare.NTSB ERA12CA369Accident · No injuriesData collectionFinal reportCessna 172 · Gainesville, GAThe student pilot's improper use of the flight controls during the takeoff and the flight instructor's delayed remedial action. Contributing to the accident was the student pilot’s interference with the flight instructor’s attempted remedial actions.NTSB WPR12FA230Accident · 4 fatalField investigationFinal reportCessna 172S · St. George, UTThe pilot's failure to maintain adequate airspeed during an aggressive pitch-up maneuver, which resulted in a low-altitude aerodynamic stall shortly after takeoff. Contributing to the accident was the pilot's impairment from alcohol consumption and an…NTSB CEN12CA342Accident · No injuriesData collectionFinal reportCessna 172S · Fort Scott, KSThe student pilot’s loss of directional control during the landing roll. Contributing to the accident was the student pilot’s diverted attention to retract the flaps.NTSB WPR12LA444Accident · No injuriesLimited investigationFinal reportCessna 172S · Glendale, AZThe pilot's inadequate flare and compensation for gusting wind conditions, which resulted in a bounced landing.NTSB WPR12CA171Accident · No injuriesData collectionFinal reportCessna 172S · Prescott, AZThe pilot's inadequate compensation for a crosswind during takeoff, which resulted in a loss of directional control.NTSB CEN12CA240Accident · No injuriesData collectionFinal reportCessna 172S · Monroe, LAThe student pilot's improper landing flare, which resulted in a bounced landing and loss of directional control.NTSB ERA12LA274Accident · No injuriesLimited investigationFinal reportCessna 172S · Daytona Beach, FLA total loss of engine power due to a catastrophic engine failure, the origin of which could not be determined during postaccident examination.NTSB CEN12LA214Accident · No injuriesLimited investigationFinal reportCessna 172S · Midlothian, TXThe pilot's failure to maintain directional control during the landing roll.NTSB CEN12FA199Accident · 2 fatalField investigationFinal reportCessna 172S · Longmont, COThe inadequate visual lookout by the pilots of both airplanes, which resulted in a mid-air collision.NTSB ERA12CA209Accident · No injuriesData collectionFinal reportCessna 172S · Lafayette, TNThe pilot’s inadequate compensation for gusting crosswind conditions during landing, which resulted in a hard landing.NTSB ERA12FA193Accident · 2 fatalField investigationFinal reportCessna 172S · Key West, FLThe non-night-qualified pilot's improper decision to depart in dark night visual meteorological conditions, which resulted in his subsequent spatial disorientation, loss of control, and impact with water.NTSB ERA12CA189Accident · No injuriesData collectionFinal reportCessna 172S · Caldwell, NJThe student pilot’s loss of directional control during a crosswind landing.NTSB WPR12FA105Accident · 3 fatalField investigationFinal reportCessna 172S · North Bend, WAThe pilot's physical impairment due to alcohol, which adversely affected his ability to operate the airplane and to maintain clearance from mountainous terrain while operating in dark night conditions.NTSB ERA12CA185Accident · No injuriesData collectionFinal reportCessna 172S · Eufaula, ALAn inadvertent collision with a deer during a night landing.NTSB WPR12CA088Accident · No injuriesData collectionFinal reportCessna 172S · Mokuleia, HIThe pilot's improper landing flare and inadequate recovery from a bounced landing.NTSB ERA12IA169Incident · No injuriesIncident investigationFinal reportCessna 172S · Jackson, MSThe separation of the propeller blade tip due to fatigue cracking that initiated at the blade’s leading edge.NTSB WPR12CA038Accident · No injuriesData collectionFinal reportCessna 172S · Phoenix, AZThe student pilot's inadequate directional control during takeoff.NTSB ERA12LA066Accident · No injuriesLimited investigationFinal reportCessna 172S · Fort Lauderdale, FLThe Cessna 172 flight instructor and student pilot's inadequate visual lookout and failure to maintain clearance from the stationary Cessna 182.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…
Back to Cessna 172S