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 CHI95LA290Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Port Washington, WIthe failure of the #2 cylinder due to fatigue cracking. A factor was the soft terrain.NTSB LAX95LA296Accident · No injuriesLimited investigationFinal reportCessna 172P · Hesperia, CAThe failure of the connecting rod due to the rod bolt backing off, and the pilot's misjudging the distance and altitude.NTSB NYC95LA172Accident · No injuriesLimited investigationFinal reportCessna 172P · Teterboro, NJthe student pilot's improper flare which resulted in the airplane porpoising and the subsequent buckling of the firewall.NTSB LAX95LA267Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Reno, NVthe pilot's loss of directional control during a crosswind landing using full flaps and the lack of familiarity with the crosswind landing component chart for the aircraft.NTSB CHI95LA235Accident · No injuriesLimited investigationFinal reportCessna 172 · Springfield, MOimproper in-flight planning/decision by the pilot, and his continued flight into adverse weather conditions, which resulted in an uncontrolled altitude deviation and collision with terrain. Factors relating to the accident were: the adverse weather conditions.NTSB CHI95LA233Accident · No injuriesLimited investigationFinal reportCessna 172 · Motley, MNthe pilot's failure to maintain control of the airplane during a soft field takeoff.NTSB SEA95LA155Accident · No injuriesLimited investigationFinal reportCessna 172P · Vashon, WAThe loss of engine power due to connecting rod bolt overload failure. The rough, uneven terrain in the emergency landing area was a factor.NTSB MIA95LA165Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Lake Placid, FLTotal failure of the fuel vent system resulting in the total loss of engine power during cruise flight. Contributing to the accident was the inadequate inspection of the airplane during the last annual inspection for failure of the mechanic to identify that…NTSB ATL95LA113Accident · No injuriesLimited investigationFinal reportCessna 172 · Brownsville, TNThe pilot's improper in-flight decision to land on the wet, sod runway, and his failure to use all of the available runway for landing.NTSB MIA95LA122Accident · No injuriesLimited investigationFinal reportCessna 172P · Clearwater, FLThe pilot-in-command's improper remedial action after the aircraft porpoised during the landing flare and touchdown.NTSB FTW95LA166Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Mountain Home, ARThe pilot's failure to compensate for the gusty crosswind. A factor was gusting crosswinds.NTSB NYC95FA080Accident · 1 fatalField investigationFinal reportCessna 172P · Naples, NYThe pilot's continued VFR flight into instrument meteorological conditions. Factors contributing to the accident were: the night conditions, fog, low ceiling, and hilly terrain.NTSB NYC95LA081Accident · No injuriesLimited investigationFinal reportCessna 172 · Mitchellville, MDThe pilot's failure to maintain directional control and the instructor's inadequate supervision. Related factors: high winds, and a crosswind.NTSB CHI95LA108Accident · No injuriesLimited investigationFinal reportCessna 172 · Alma, MIthe flight instructor's inadequate remedial action during the approach to landing/landing roll. Related factors are the flight instructor's inadequate supervision, the dual student's wrong runway selection, the tailwind, and the dual student's failure to…NTSB LAX95LA133Accident · No injuriesLimited investigationFinal reportCessna 172P · Redlands, CAthe pilot's use of an excessive approach speed and glidepath angle and his improper bounced landing recovery technique.NTSB FTW95LA052Accident · No injuriesLimited investigationFinal reportCessna 172P · Blanco, TXThe pilot's use of unsuitable terrain for takeoff. Factors were the uphill terrain, the long vegetation, and short takeoff area available.NTSB FTW95FA050Accident · 2 fatalField investigationFinal reportCessna 172P · Deming, NMThe pilot's failure to maintain sufficient altitude and clearance in moutainous terrain. Factors were rising terrain and gusty, high wind conditions.NTSB FTW95LA036Accident · No injuriesLimited investigationFinal reportCessna 172P · Colorado Spgs, COThe pilot's improper landing flare, the resultant porpoise and an inadequate recovery from the bounced landing.NTSB CHI94LA324Accident · No injuriesLimited investigationFinal reportCessna 172 · Warrenton, MOthe pilot's failure to use the proper procedure for an aborted takeoff. Factors associated with the accident were the trees, the pilot's poor preflight/preparation, and the pilot's selection of unsuitable terrain for landing.NTSB CHI94LA289Accident · No injuriesLimited investigationFinal reportCessna 172 · Plato Center, ILThe pilot's attempt to take off on a short runway with a gross weight which exceeded the maximum allowable weight and an improper flap setting. A factor was the location of obstructions (trees) at the departure end of the runway.NTSB LAX94LA321Accident · No injuriesLimited investigationFinal reportCessna 172P · Scottsdale, AZthe pilot's misjudging the flare altitude and failing to maintain adequate airspeed resulting in an inadvertent stall and hard landing. The pilot's lack of total time in the airplane is a factor in this accident.NTSB NYC94LA159Accident · No injuriesLimited investigationFinal reportCessna 172P · Pottsville, PAThe pilot's failure to attain adequate airpseed, which resulted in a stall/mush and collision with a tree.NTSB SEA94LA178Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Easton, WAImproper planning/decision by the pilot-in-command, and inadequate supervision by the check pilot, which resulted in their failure to remain clear of trees during takeoff. Factors related to the accident were: a downdraft and the proximity of trees to the…NTSB NYC94LA115Accident · No injuriesLimited investigationFinal reportCessna 172P · Leesburg, VAThe student pilot's failure to attain adequate airpseed during an aborted landing which resulted in an inadvertent stall and collision with the ground. A factor is the the student pilot's inexperience.NTSB NYC94LA107Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Newport News, VAThe pilot's (1) improper recovery from a bounced landing and (2) failure to maintain aircraft control.NTSB NYC94LA104Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Greenville, METhe premature retraction of the wing flaps by the pilot after takeoff, resulting in a loss of lift and collision with trees.NTSB BFO94LA116Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Massena, NYThe pilot's improper compensation for wind conditions.NTSB ATL94LA125Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Kitty Hawk, NCThe pilot's improper compensation for the wind conditions, his improper recovery from a bounced landing, and the inadvertent stall. Factors were the wind conditions and the trees that bounded the runway.NTSB SEA94LA130Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Jackson Hole, WYThe failure of the pilot of the christen eagle ii, N246RL, to see and avoid the Cessna 172, N62463, and the pilot of the christen eagle ii diverting his attention from operation of his airplane.NTSB MIA94LA139Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Fernandina, FLThe pilot in command's improper use of flight controls and his failure to maintain airspeed resulting in an inadvertent stall and uncontrolled descent to ground impact.NTSB FTW94FA155Accident · 2 fatalField investigationFinal reportCessna 172P · Arlington, TXThe pilot's loss of aircraft control for an undetermined reason, while maneuvering in the vicinity of the airport.NTSB SEA94LA115Accident · No injuriesLimited investigationFinal reportCessna 172P · Hillsboro, ORPoor in-flight planning. Factors to the accident were: inadequate remedial action and uncontrolled porpoise.NTSB FTW94LA129Accident · No injuriesLimited investigationFinal reportCessna 172P · Tulsa, OKThe pilot's failure to compensate for wind conditions. A factor was the gusting cross wind.NTSB LAX94LA186Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Elko, NVthe student pilot's improper use of the throttle and flap controls during a bounced landing recovery, and, his failure to maintain an adequate airspeed, which led to an inadvertent stall/spin.NTSB CHI94LA122Accident · No injuriesLimited investigationFinal reportCessna 172P · Wheeling, ILthe pilot's inadequate compensation for wind conditions. A factor associated with the accident was the crosswind.NTSB SEA94LA083Accident · No injuriesLimited investigationFinal reportCessna 172 · Seattle, WAThe student's improper flare for landing and the instructor's delayed remedial action.NTSB MIA94LA068Accident · No injuriesLimited investigationFinal reportCessna 172P · Orlando, FLThe failure of the student pilot to follow instuctions given by ground control and the failure of both pilots to maintain proper obstruction clearance between aircraft.NTSB LAX94LA061Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Panoche, CAthe pilot's improper approach speed and glide path, and his delayed initiation of a go-around. A factor in the accident was the wind shear condition created by the hills immediately off the departure end of the dirt airstrip.NTSB MIA94LA028Accident · No injuriesLimited investigationFinal reportCessna 172P · Jacksonville, FLThe improper positioning of the fuel selector by the pilot-in- command resulting in fuel starvation.NTSB LAX94LA050Accident · No injuriesLimited investigationFinal reportCessna 172P · Santa Ana, CAwere the CFI's inadequate supervision of the flight and his delay in taking remedial action. The dual student's excessive taxi speed and the worn right brake lining were factors in this accident.NTSB LAX94LA023Accident · No injuriesLimited investigationFinal reportCessna 172 · Murrieta, CAThe unexpected windsheer that was encountered on final approach. The surrounding mountain/hilly terrain was a factor in this accident.NTSB SEA94FA014Accident · 2 fatalField investigationFinal reportCessna 172P · Kelso, WAThe pilot's failure to follow the published missed approach procedure. Factors in the accident were: the weather and mountainous terrain.NTSB BFO93LA184Accident · No injuriesLimited investigationFinal reportCessna 172 · Emporia, VAThe pilot's selection of unsuitable terrain for a takeoff. A factor related to the accident was the pilot's delay in initiating an aborted takeoff.NTSB LAX93LA368Accident · No injuriesLimited investigationFinal reportCessna 172P · Phoenix, AZThe pilot's misjudging the landing flare. A physical problem may have contributed.NTSB CHI93LA364Accident · No injuriesLimited investigationFinal reportCessna 172P · Fieldon, ILPartial failure (deterioration) of the #1 piston pin plug, which resulted in contamination of the lubricating system and failure of the #3 connecting rod.NTSB BFO93LA156Accident · 1 fatalLimited investigationFinal reportCessna 172P · Pembroke, VAThe pilot's failure to maintain proper altitude while manuevering in mountainous terrain.NTSB DEN93LA105Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Santa Fe, NMImproper planning and decision making by the pilot in command in descending into a valley at an altitude providing no escape route in mountainous terrain.NTSB NYC93FA158Accident · 1 fatalField investigationFinal reportCessna 172P · Lincoln Park, NJThe failure of both pilots to maintain adequate visual lookout while in the airport traffic pattern, which resulted in an in-flight collision.NTSB ANC93LA142Accident · No injuriesLimited investigationFinal reportCessna 172 · Black Rapids, AKThe pilot's improper in-flight planning/decision, and his delay in taking remedial action. Factor was the rough, uneven terrain.NTSB LAX93LA298Accident · No injuriesLimited investigationFinal reportCessna 172 · Vacaville, CAThe pilot's improper in-flight planning/decision by failing to allow enough time for the rotor wash to dissipate before attempting the approach. The wake turbulence (rotor wash) was a factor in this accident.
Back to Cessna 172P