Cessna 172P
NTSB investigations · 844
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 ('2072436')
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 ('2072436')
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 FTW93LA217Accident · No injuriesLimited investigationFinal reportCessna 172P · Cookson, OKThe pilot's improper flare and his failure to maintain directional control during the aborted landing.NTSB BFO93LA127Accident · No injuriesLimited investigationFinal reportCessna 172P · Edgartown, MAThe pilot failed to maintain directional control during takeoff. Other related factors were: the tailwind, and the gross weight of the airplane being exceeded.NTSB ATL93LA129Accident · No injuriesLimited investigationFinal reportCessna 172 · Summerdale, ALThe pilot's failure to attain the proper touchdown point.NTSB FTW93LA205Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Lancaster, TXFuel exhaustion engine power loss due to the inadequate fuel supply for the flight. A factor was the lack of suitable terrain for the forced landingNTSB CHI93LA205Accident · No injuriesLimited investigationFinal reportCessna 172P · Hartford, WIThe failure of the number four cylinder and unsuitable terrain.NTSB NYC93LA101Accident · No injuriesLimited investigationFinal reportCessna 172P · Lincoln Park, NJThe pilot's inadequate compensation for wind conditions, and his failure to maintain directional control of the airplane, which resulted in a ground swerve and a collision with trees.NTSB SEA93FA125Accident · 3 fatalField investigationFinal reportCessna 172P · Enumclaw, WAInadvertent VFR flight into IMC. Factors to the accident were: fog and rain.NTSB BFO93LA079Accident · No injuriesLimited investigationFinal reportCessna 172P · Pittstown, NJThe pilot's improper recovery from a bounced landing, and his failure to maintain directional control of the airplane, which resulted in a ground swerve. The gusty wind and proximity of the parked airplane were related factors.NTSB MIA93LA118Accident · No injuriesLimited investigationFinal reportCessna 172P · Mims, FLTotal loss of engine power due to fuel exhaustion. Contributing to the accident was the failure of the pilot to lean the fuel/air mixture during cruise flight which increased the fuel consumption for the flight.NTSB MIA93LA111Accident · No injuriesLimited investigationFinal reportCessna 172P · Orlando, FLThe pilot-in-command's failure to compensate for wind drift while landing, resulting in the aircraft going off the side of the runway and colliding with a pond.NTSB LAX93FA160Accident · 4 fatalField investigationFinal reportCessna 172P · Livermore, CAThe pilot's decision to attempt VFR flight into instrument meteorological conditions. Factors that contributed to this accident were: the pilot's lack of recent instrument experience, the rain and high wind conditions in the area.NTSB NYC93LA055Accident · No injuriesLimited investigationFinal reportCessna 172P · Teterboro, NJThe failure of the pilot to maintain directional control during landing which resulted in the airplane departing the runway and nosing over. Factors related to the accident were the crosswind and the soft terrain encountered by the airplane.NTSB LAX93FA096Accident · 1 fatalField investigationFinal reportCessna 172P · Sun City, CAThe pilot's decision to initiate VFR flight into instrument meteorological conditions. Factors which contributed to the accident were: the pilot's failure to obtain a weather briefing, the adverse weather, and the mountainous terrain.NTSB FTW93LA060Accident · No injuriesLimited investigationFinal reportCessna 172P · Little Rock, ARThe certified flight instructor's failure to attain the proper touchdown point.NTSB NYC93LA051Accident · No injuriesLimited investigationFinal reportCessna 172 · Andover, NJThe pilot's failure to abort the landing which resulted in a overrun of the runway. Contributing was the pilot's misjudgement of distance and an improper touchdown point.NTSB SEA93LA012Accident · No injuriesLimited investigationFinal reportCessna 172P · Lind, WAThe aircraft encountered rough terrain during the landing roll after the pilot elected to perform a precautionary landing in an open field, due to deteriorating weather.NTSB DEN93FA008Accident · 1 fatalField investigationFinal reportCessna 172P · Woody Creek, COAircraft climb performance exceeded. Factors were: the pilot's lack of experience in mountain flying, and the high density altitude conditions.NTSB ATL93LA010Accident · No injuriesLimited investigationFinal reportCessna 172P · Buford, GAFuel exhaustion due to the pilot's inadequate inflight planning.NTSB CHI93LA003Accident · No injuriesLimited investigationFinal reportCessna 172P · Kokomo, INThe pilot's delayed remedial action.NTSB FTW92LA230Accident · No injuriesLimited investigationFinal reportCessna 172P · Fulshear, TXThe pilot's failure to attain the proper point of touchdown. Factors were the popped circuit breaker, the inoperative alternator, and the darkness of the night.NTSB SEA92LA206Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Leavenworth, WAThe premature lift off by the pilot. Factors relating to the accident were the soft, rough turf airstrip and the high obstructions at the end of the runway.NTSB CHI92LA278Accident · No injuriesLimited investigationFinal reportCessna 172P · Yipslanti, MIThe pilot's premature flare during landing and not performing a recovery from a bounced landing.NTSB CHI92LA274Accident · No injuriesLimited investigationFinal reportCessna 172P · St. Charles, MIThe jamming of the oil pressure pump caused by the failure of the oil pressure pump driven impeller. The lack of a suitable landing area was a factor.NTSB FTW92FA201Accident · 1 fatalField investigationFinal reportCessna 172P · Breckenridge, TXAn inadvertent stall.NTSB LAX92LA328Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Burbank, CAThe binding and over temperature of an exhaust valve due to the lack of compliance with factory service instructions and bulletins regarding valve sticking by other maintenance personnel.NTSB MIA92LA157Accident · No injuriesLimited investigationFinal reportCessna 172P · Valkaria, FLExcessive airspeed on final approach by the pilot in command resulting in failure to attain the proper touchdown point and running off the runway colliding with a tree.NTSB LAX92LA306Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Kernville, CAThe pilot's selection of the wrong runway; poorly planned approach; failure to attain the proper touch down point; and delay in executing the go-around. Contributing to this accident was the existing tailwind and crosswind.NTSB CHI92LA202Accident · No injuriesLimited investigationFinal reportCessna 172P · Waukegan, ILThe student pilot's failure to maintain airplane directional control. Related factors are the student's lack of total flight experience, and improper aircraft control.NTSB DEN92LA068Accident · No injuriesLimited investigationFinal reportCessna 172P · Broomfield, COFailure by the pilot to maintain directional control.NTSB CHI92LA172Accident · No injuriesLimited investigationFinal reportCessna 172 · Wheeling, ILThe pilot's improper approach to landing. Related factors are the thunderstorm and the excessive airspeed.NTSB ATL92LA125Accident · No injuriesLimited investigationFinal reportCessna 172 · Auburn, ALThe pilot's improper landing flare, and his improper recovery from a bounced landing.NTSB CHI92LA173Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Ladysmith, WIFailure of the pilot to attain a proper touchdown point and the attempted abort of the precautionary landing attempt.NTSB DEN92LA057Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Englewood, COAirplane climb capability exceeded and an inadvertent pilot induced stall. Factors were: weight and balance exceeded, high density altitude, and improper use of the mixture control.NTSB LAX92FA241Accident · 3 fatalField investigationFinal reportCessna 172P · Big Sur, CAPilot incapacition.NTSB BFO92LA073Accident · No injuriesLimited investigationFinal reportCessna 172P · Poughkeepsie, NYThe pilot failed to maintain directional control.NTSB BFO92FA069Accident · 2 fatalField investigationFinal reportCessna 172P · Princeton, NJThe pilot's failure to maintain clearance over an obstacle. Contributing factors were a tailwind, dark night, and premature raising of the flaps.NTSB MIA92LA124Accident · No injuriesLimited investigationFinal reportCessna 172-P · Daytona Beach, FLThe delayed remedial action by the pilot-in-command (CFI) to the student's pushing the control yoke forward on short final approach.NTSB BFO92LA066Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Caldwell, NJThe pilot's improper IFR operation. Contributing was the pilot's lack of recent instrument flight time.NTSB CHI92FA127Accident · 1 fatalField investigationFinal reportCessna 172P · Kellyville, OKAn inadvertent stall and misjudgement of an emergency procedure by the pilot in trying to stretch the forced landing approach to make it to the airstrip.NTSB SEA92FA075Accident · 5 fatalField investigationFinal reportCessna 172P · Englewood, COA loss of airplane control initiated by inadvertent control interference by the passenger pilot while apparently attempting to quell a disturbance of an unknown nature. As a result, the pilot did not, or was unable to, maintain sufficient control of the…NTSB BFO92FA044Accident · 2 fatalField investigationFinal reportCessna 172P · Accokeek, MDThe pilot experienced spatial disorientation which resulted in loss of control of the airplane.NTSB FTW92LA091Accident · No injuriesLimited investigationFinal reportCessna 172P · West Helena, ARPilot's improper flarea ND improper recovery from a bounced landing.NTSB LAX92LA140Accident · No injuriesLimited investigationFinal reportCessna 172P · Santa Monica, CAThe pilot's misjudged landing flare and her improper bounced landing recovery technique. Contributing factors were the airplane's excessive approach airspeed and the student's lack of experience.NTSB FTW92LA086Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Harrison, ARThe pilot's failure to attain the proper touchdown point, and his failure to maintain the proper descent rate.NTSB ATL92FA053Accident · 2 fatalField investigationFinal reportCessna 172P · N Topsail Beach, NCThe failure of the pilot to obtain and/or maintain adequate airspeed during takeoff, which resulted in an inadvertent stall and collision with the ground. Factors were: the failure of the pilot to follow procedures/directives, his operation of the aircraft…NTSB SEA92LA048Accident · No injuriesLimited investigationFinal reportCessna 172P · Nordman, IDThe pilot selected unsuitable terrain. Factors contributing to the accident were: the snow covered runway, and the pilot in command's inadequate preflight planning.NTSB ATL92LA046Accident · No injuriesLimited investigationFinal reportCessna 172 · Leesburg, FLThe unfavorable wind conditions encountered by the flight during taxi.NTSB DEN92LA027Accident · No injuriesLimited investigationFinal reportCessna 172P · Englewood, COA loss of control due to the pilot's failure to follow proper soft field takeoff procedures by flying out of ground effect at an inadequate airspeed. A factor was the pilot's improper use of flaps.NTSB DEN92LA026Accident · No injuriesLimited investigationFinal reportCessna 172P · Englewood, COLoss of directional control when the student pilot inadvertently activated the brakes during takeoff roll. Inadequate supervision by the certified flight instructor was a factor.NTSB SEA92FA026Accident · 7 fatalField investigationFinal reportCessna 172P · Snohomish, WAA visual lookout was not maintained.
Back to Cessna 172P