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 LAX02LA133Accident · No injuriesLimited investigationFinal reportCessna 172S · Phoenix, AZthe pilot flaring the airplane too high above the runway causing a stall and resulting in the hard landing. Factors relating to the accident were the light conditions (dusk) and the pilot's lack of total experience in the type of airplane.NTSB LAX02LA130Accident · No injuriesLimited investigationFinal reportCessna 172S · Palm Springs, CAThe pilot lost directional control and collided with a runway edge light and taxiway sign.NTSB LAX02LA092Accident · Minor injuriesLimited investigationFinal reportCessna 172S · Santa Paula, CAThe pilot's selection of the wrong landing runway due to his failure to correctly interpret wind indicators, which resulted in his landing with a tailwind.NTSB LAX02LA084Accident · No injuriesLimited investigationFinal reportCessna 172S · Glendale, AZThe pilot of the landing airplane failed to maintain directional control resulting in the on-ground collission.NTSB FTW02LA068Accident · No injuriesLimited investigationFinal reportCessna 172S · Sugar Land, TXthe student pilot's failure to maintain directional control during landing.NTSB IAD02LA013Accident · Serious injuriesLimited investigationFinal reportCessna 172S · Leesburg, VAThe pilot's improper stowage of hazardous material.NTSB ATL02LA013Accident · No injuriesLimited investigationFinal reportCessna 172S · Sarasota, FLThe operators failure to ensure adequate training had been provided to the student pilot in autopilot operations, and the student pilot's failure to comply/ follow written instructions (Federal Regulations/172 Skyhawk Information Manual) pertaining to the…NTSB NYC01FA217Accident · 2 fatalField investigationFinal reportCessna 172SP · Matawan, NJThe pilot's failure to maintain runway alignment during the initial climb. Factors were the pilot's failure to perform a go-around, the pilot's lack of flight experience in nighttime conditions, the nighttime conditions, and a tailwind.NTSB MIA01LA227Accident · No injuriesLimited investigationFinal reportCessna 172S · Gadsden, ALthe pilot misjudged the flare, resulting in a hard landing, and impact with the runway.NTSB ANC01FA100Accident · Serious injuriesField investigationFinal reportCessna 172S · Cooper Landing, AKThe pilot's inadequate remedial action to disconnect the autopilot during an uncommanded altitude deviation while in cruise flight. Factors in the accident were activation of the autopilot; the pilot's lack of familiarity with the airplane's autopilot system;…NTSB LAX01LA267Accident · No injuriesLimited investigationFinal reportCessna 172S · Scottsdale, AZThe pilot's misjudged landing flare, which lead to a hard landing, inadvertent porpoise, and his improper recovery from a bounced landing.NTSB CHI01LA205Accident · No injuriesLimited investigationFinal reportCessna 172S · Lake in the Hil, ILThe student pilot misjudging the flare during that landing. Factors were the wrong runway selected by the student pilot, the tailwinds encountered during that landing and the flight instructor's inadequate supervision during that landing.NTSB CHI01LA173Accident · No injuriesLimited investigationFinal reportCessna 172S · Cambridge, NEthe pilot's high airspeed and improper emergency procedures during the emergency landing. Factors relating to this accident were the fractured engine exhaust valve push rod, the bent intake valve push rod, and oil exhaustion during cruise flight, the…NTSB FTW01LA145Accident · No injuriesLimited investigationFinal reportCessna 172S · Baton Rouge, LAthe student pilot's improper recovery from a bounced landing.NTSB SEA01IA113Incident · No injuriesIncident investigationFinal reportCessna 172S · Monroe, ORA degradation of aircraft control for undetermined reasons.NTSB LAX01LA191Accident · Serious injuriesLimited investigationFinal reportCessna 172S · Cottonwood, AZthe student's inadequate compensation for the gusty crosswind conditions and the subsequent loss of aircraft control during landing roll. The flight instructor’s inadequate supervision and his inadequate remedial action is also causal. Contributing factors…NTSB CHI01FA136Accident · No injuriesField investigationFinal reportCessna 172S · Springfield, MOthe excessive touchdown airspeed by the pilot.NTSB NYC01LA113Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Hodgenville, KYThe pilot's failure to maintain runway alignment during landing. A factor in the accident was the pilot's lack of experience in conducting soft field landings.NTSB SEA01LA077Accident · No injuriesLimited investigationFinal reportCessna 172S · Renton, WAA Canadian goose which crossed the aircraft's flight path and impacted the left wing during the aircraft's final approach.NTSB LAX01LA137Accident · No injuriesLimited investigationFinal reportCessna 172S · Long Beach, CAThe student pilot's inadequate compensation for the exisiting crosswind and his improper landing flare that resulted in a hard landing, and loss of directional control during the landing roll.NTSB NYC01LA083Accident · No injuriesLimited investigationFinal reportCessna 172S · Keene, NHThe pilot's failure to maintain directional control during the landing roll. A factor included the patchy snow on the runway.NTSB FTW01IA062Incident · No injuriesIncident investigationFinal reportCessna 172S · Ruston, LAthe loss of engine power while manuevering as a result of an incorrect mixture control adjustment. A contributing factor was the lack of suitable terrain for the ensuing forced landing.NTSB ATL01LA023Accident · Serious injuriesLimited investigationFinal reportCessna 172SP · Austell, GAThe pilots failure to follow instrument flight procedures and descended below the published the minimum descent altitude and subsequently collided with trees short of the runway.NTSB IAD01LA023Accident · No injuriesLimited investigationFinal reportCessna 172S · Lincoln Park, NJthe pilot's failure to maintain proper runway alignment during landing. Factors in the accident were the night lighting and the snow bank.NTSB CHI01LA060Accident · No injuriesLimited investigationFinal reportCessna 172S · Sioux Falls, SDAircraft directional control not being maintained by the student pilot during the takeoff roll. Factors to the accident were the snow bank and the student pilot's lack of total experience.NTSB CHI01IA047Incident · No injuriesIncident investigationFinal reportCessna 172S · St. Cloud, MNthe fatigue failure of the propeller blade during the initial takeoff climb. The failure was a result of a material defect, which occurred during the manufacturing process and the manufacturers failure to detect the defect.NTSB NYC00LA243Accident · No injuriesLimited investigationFinal reportCessna 172 · Dunkirk, NYThe pilot's improper recovery from a bounced landing.NTSB ANC00FA082Accident · 1 fatalField investigationFinal reportCessna 172S · Whittier, AKSuicide.NTSB CHI00LA113Accident · Minor injuriesLimited investigationFinal reportCessna 172S · Near Muskegon, MIthe pilot failed to maintain altitude after inadvertently flying to instrument meteorological conditions. Factors associated with the accident were the low ceilings and visibility, the pilot became disoriented after inadvertently flying into IMC, and the…NTSB FTW00LA050Accident · No injuriesLimited investigationFinal reportCessna 172S · Sugar Land, TXThe student pilot's failure to maintain control of the airplane during the landing roll.NTSB CHI99LA092Accident · No injuriesLimited investigationFinal reportCessna 172RG · Lawrenceville, ILthe fatigue fracture of the landing gear actuator.NTSB NYC87FA120Accident · 4 fatalField investigationFinal reportCessna 172P · Berwick, METhe acft was observed doing stalls. A witness said that prior to the crash he saw the nose lower and the right wing drop. The aircraft then entered into a spiral. It was observed descending into trees in a spiral. The plt was found in the right front seat.…NTSB MIA80DLD11Accident · Minor injuriesClosedCessna 182 · Ocala, FLNTSB CHI79FEI22Accident · No injuriesClosedN American SNJ-4 · Painesville, OHNTSB NYC79DFJ10Accident · No injuriesClosedCessna 182 · Buffalo, NYNTSB MIA72DLD35Accident · No injuriesClosedCessna 150 · Maitland, FLNTSB CHI70DDM01Accident · No injuriesClosedCessna 180 · Grantsburg, WINTSB SEA67D0314Accident · No injuriesClosedCessna 150 · Sultan, WANTSB MKC67F0456Accident · No injuriesClosedCessna 310 · Bridgeton, MO
Back to Cessna 172S