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 LAX90LA287Accident · No injuriesLimited investigationFinal reportCessna 172P · Coalinga, CAThe failure of the student pilot to accurately interpret the wind sock, and his inadvertent attempt to perform a downwind landing.NTSB LAX90LA273Accident · No injuriesLimited investigationFinal reportCessna 172P · Mammoth Lakes, CAInadvertent encounter with high velocity winds.NTSB LAX90LA216Accident · No injuriesLimited investigationFinal reportCessna 172P · Redding, CAThe failure of the pilot in command to maintain direction control. Factors in the accident were the pilot in command's premature rotation during the takeoff and the failure to take the necessary remedial action.NTSB CHI90DEV05Accident · Minor injuriesFinal reportCessna 172P · Jerseyville, ILThe pilot's failure to go around when crosswinds upset aircraft alignment with the runway in the flare. Contributing to the accident was the pilot's attempt to land in crosswinds which exceeded the maximum for which the model has been demonstrated capable.NTSB MIA90LA129Accident · No injuriesLimited investigationFinal reportCessna 172P · Plymouth, FLThe pilot's inadequate compensation for wind conditions. Factors related to the accident were: the crosswind and the pilot's lack of total flying expereince.NTSB CHI90LA122Accident · No injuriesLimited investigationFinal reportCessna 172P · Plainfield, ILThe student's improper flare, improper recovery from a bounced landing, and failure to maintain directional control. The crosswind was a related factor.NTSB CHI90LA119Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Lambertville, MIThe pilot's failure to maintain aircraft control during the aborted landing.NTSB ATL90FA095Accident · 2 fatalField investigationFinal reportCessna 172 · Gadsden, ALInadequate visual lookout by the pilots of both aircraft, which resulted in their failure to see-and-avoid oncoming traffic. A factor related to the accident was: the sun's glare, which restricted the vision of the Cessna 172 pilot.NTSB CHI90LA109Accident · No injuriesLimited investigationFinal reportCessna 172P · Savanna, ILImproper planning/decision by the pilot. The strong/gusty crosswind was a related factor.NTSB DEN90LA090Accident · No injuriesLimited investigationFinal reportCessna 172 · Ogallala, NEThe misjudged landing flare. A factor was the pilot's lack of experience.NTSB NYC90LA080Accident · No injuriesLimited investigationFinal reportCessna CE-172P · Hollidaysburg, PAPilot factor in that he failed to ensure there was sufficient fuel on board to complete the flight. This resulted in an engine failure & subsequent forced landing.NTSB MIA90GA088Accident · Serious injuriesFinal reportCessna 172P · Tampa, FLPilots failure to maintain airspeed (vs), which resulted in an inflight loss of control (stall/spin), and in flight collision with terrain.NTSB MIA90LA069Accident · No injuriesLimited investigationFinal reportCessna 172P · Fort Lauderdale, FLThe pilot's failure to maintain control of the airplane after the right main gear contacted a tie down hole, which resulted in a collision with the hangar.NTSB NYC90LA069Accident · No injuriesLimited investigationFinal reportCessna 172P · Sunapee Lake, NHFailure of the pilot to maintain adequate altitude above the lake, which resulted in unplanned contact with its frozen surface.NTSB MKC90LA043Accident · No injuriesLimited investigationFinal reportCessna 172 · St Cloud, MNInadequate visual outlook by the pilot and his failure to maintain clearance from the light pole. The location of the pole was considered to be a related factor.NTSB CHI90LA063Accident · No injuriesLimited investigationFinal reportCessna 172 · Newark, ILImproper planning/decision by the pilot. The wet condition of the grass runway was a related factor.NTSB DEN90LA035Accident · No injuriesLimited investigationFinal reportCessna 172P · Billings, MTThe failure of the pilot to maintain directional control during adverse wind conditions.NTSB CHI90LA052Accident · No injuriesLimited investigationFinal reportCessna 172P · Middletown, OHThe inability to establish a sufficient climb after takeoff. Contributing to the accident was the pilot's lack of total experinece in this type of aircraft.NTSB LAX90LA045Accident · No injuriesLimited investigationFinal reportCessna 172 · Van Nuys, CAThe P-51 pilot's failure to see and avoid the standing C-172.NTSB SEA90LA020Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Bremerton, WAFuel exhaustion and inadequate preflight planning.NTSB BFO90LA013Accident · No injuriesLimited investigationFinal reportCessna 172 · Mitchellville, MDThe pilot allowed the aircraft to enter an inadvertent porpoise during an aborted takeoff.NTSB ATL90FA024Accident · 4 fatalField investigationFinal reportCessna 172P · Gadsden, ALFailure of the pilots of both aircraft to maintain adequate visual lookout to see-and-avoid the other aircraft.NTSB NYC90LA001Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Bingham, METhe pilot's inadequate preflight planning to assure that the airplane was capable of outclimbing the surrounding terrain under the existing wind and airplane weight conditions, resulting in an intentional stall into the terrain. Contributing factor(s) was:…NTSB SEA89LA161Accident · No injuriesLimited investigationFinal reportCessna 172P · Alderwood Manor, WAImproper planning/decision by the pilot. The tailwind and high obstructions were related factors.NTSB NYC89FA206Accident · 4 fatalField investigationFinal reportCessna 172P · Northfield, NHThe pilot initiated flight into known adverse weather which resulted in a loss of control. Contributing factor(s) was: the pilot's overconfidence and the existing weather conditions.NTSB NYC89LA198Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Gardner, MAThe worn throttle arm.NTSB CHI89FA174Accident · Serious injuriesField investigationFinal reportCessna 172P · Superior, WIThe failure of the pilot to maintain directional control.NTSB MIA89FA220Accident · 4 fatalField investigationFinal reportCessna 172P · Pass-A-Grille, FLFailure of the pilot to recover from a stall/spin. Excessive gross weight of the aircraft and lack of available altitude for spin recovery were probable contributing factors.NTSB LAX89LA272Accident · No injuriesLimited investigationFinal reportCessna 172P · Redlands, CAThe pilot's improper level-off, recovery from bounced landing, and failure to maintain directional control during the landing. The pilot's limited recent experience was a contributing factor.NTSB NYC89LA203Accident · No injuriesLimited investigationFinal reportCessna 172P · Newburgh, NYThe dual student's misjudgement of the airplane's altitude and speed during the flare for landing, and the improper use of power during the flare. In addition, the CFI failed to adequately supervise the dual student's action.NTSB MKC89LA164Accident · No injuriesLimited investigationFinal reportCessna 172 · Duluth, MNAircraft control was not maintained by the pilot in command due to improper use of the aircraft flight controls.NTSB ATL89LA183Accident · No injuriesLimited investigationFinal reportCessna 172P · Cincinnati, OHThe pilot's improper go-around procedure of fully retracting the flaps which resulted in the airplane mushing into trees. Contributing factor(s) was: a misjudgement of flare height above the runway and failure to remove the carburetor heat which may have…NTSB CHI89LA131Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Logansport, INPoor judgement of the pilot due to physical impairment from consumption of alcohol, his inadvertent flight into known adverse weather, and his inadequate control of the aircraft during a precautionary landing. Contributing factors were: the weather conditions…NTSB BFO89FA048Accident · 4 fatalField investigationFinal reportCessna 172P · Caesars Head, SCFailure of the pilot to maintain sufficient airspeed while flying over rising terrain, which resulted in an inadvertent stall and collision with wooded terrain. Factors related to the accident were: the terrain conditions and failure of the pilot to maintain…NTSB MKC89LA127Accident · No injuriesLimited investigationFinal reportCessna 172 · Pine Bluff, ARImproper in-flight planning/decision by the pilot by continuing the approach when the runway lights did not activate. Contributing factors were: dark night and soft terrain.NTSB MIA89GA155Accident · 2 fatalFinal reportCessna 172P · Davie, FLFailure of the pilot in command to maintain adequate airplane control while entering an area of turbulence caused by wild fires on the ground beneath his flight path.NTSB FTW89FA090Accident · 2 fatalField investigationFinal reportCessna 172P · Burnet, TXContinued VFR flight by the pilot into instrument meteorological conditions (IMC), and his failure to maintain control of the aircraft, due to spatial disorientation. Factors related to the accident were: the adverse weather conditions and the pilot's lack of…NTSB CHI89LA081Accident · No injuriesLimited investigationFinal reportCessna 172D · Ottawa, ILStudent pilot's continuing an approach to landing beyond the point where she could bring the aircraft to a controlled stop on the remaining runway surface.NTSB SEA89GA064Accident · Minor injuriesFinal reportCessna 172P · Hawthorne, NVThe failure of the pilot to maintain flying speed and proper flying attitude resulting in a stall mush. Contributing to the accident were the density altitude and the variable winds.NTSB LAX89LA132Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Oceanside, CAThe failure of the student pilot to compensate adequately for wind conditions and to relinquish the flight controls to the instructor. Contributing to the accident was inadequate supervision by the instructor.NTSB LAX89LA126Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Rio Vista, CAThe improper planning and execution of an emergency (simulated) maneuver by the pilot.NTSB LAX89LA102Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Santa Ynez, CAThe failure of the pilot to obtain an adequate preflight weather briefing or to obtain inflight weather advisory information, and the failure of the pilot to maintain flying speed while descending in a downdraft.NTSB ATL89DMG02Accident · Minor injuriesFinal reportCessna 172P · Mooresville, NCFailure of the pilot to maintain airspeed on final approach to land, which resulted in an inadvertent stall. Factors related to the accident were: carburetor icing conditions, night conditions, and the pilot's decision to land at an unlighted runway.NTSB MKC89LA032Accident · No injuriesLimited investigationFinal reportCessna 172 · Little Falls, MNWhile attempting a touch and go ldg during a student solo cross country flt, directional control was lost during the takeoff phase on the snow packed runway. The student pilot said he had never landed and taken off under those runway conditions. The acft…NTSB CHI89LA025Accident · No injuriesLimited investigationFinal reportCessna 172P · Samaria, MINTSB BFO89LA006Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Cambridge, MDThe stu plt did three takeoffs & lndgs with the instr aboard and then three more during solo flight. On his fourth takeoff try he used aileron and rudder to maintain directional control on the rwy. There was an 8 to 10 kt crosswind. The stu said when the acft…NTSB MKC89LA015Accident · No injuriesLimited investigationFinal reportCessna 172 · Blue Springs, MOThe plt said, while cruising over a water reservoir at about 500 feet AGL, he collided with two waterfowl, believed to be geese. One struck the wing tip, the other near the wing root. Acft control remained constant with no control problems encountered, and…NTSB LAX89FA018Accident · 2 fatalField investigationFinal reportCessna 172P · Union City, CALoss of control of the aircraft by the pilot when he inadvertently entered instrument meteorological conditions. Factors contributing to the accident were, dark night light conditions and foggy weather conditions, inadvertent flight into IMC under visual…NTSB DEN89LA016Accident · No injuriesLimited investigationFinal reportCessna 172P · Englewood, COThe pilot was practicing touch-and-go landings in a 15 kt crosswind condition in an acft in which he had 8 hrs experience. During takeoff roll after the sixth landing the plt lost control and the acft departed the side of the rnwy.NTSB CHI89LA007Accident · No injuriesLimited investigationFinal reportCessna 172 · Carbondale, ILThe student pilot, while on the takeoff roll on his first solo flight, experienced a loss of directional control which he failed to correct. The aircraft swerved to the left and departed the runway, striking a VASI installation before coming to a stop. The…
Back to Cessna 172P