Cessna R172K
NTSB investigations · 207
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 ('2072431')
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 ('2072431')
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 SEA03FA026Accident · No injuriesField investigationFinal reportCessna 172K · Gig Harbor, WAThe loss of engine power in the climb due to the fracture of the number seven engine crankshaft cheek due to the propagation of a fatigue crack initiation point. Factors include a vehicle pulling onto the road that the pilot selected for his forced emergency…NTSB SEA02LA181Accident · Minor injuriesLimited investigationFinal reportCessna R172K · Shaw Island, WAThe pilot's failure to adequately compensate for ambient wind conditions. Factors include the pilot's misjudgment of distance/altitude, gusting crosswinds, and trees growing near the edge of the airstrip.NTSB SEA02LA179Accident · No injuriesLimited investigationFinal reportCessna R172K · Salmon, IDFailure to maintain airspeed while on approach which resulted in an aerodynamic stall and hard landing.NTSB DEN02LA087Accident · No injuriesLimited investigationFinal reportCessna R172K · Monticello, UTthe student pilot's failure to maintain aircraft control during landing flare, which resulted in a hard landing. Contributing factors include the porpoise and subsequent bounced landing and the student pilot's lack of total experience.NTSB CHI02LA220Accident · No injuriesLimited investigationFinal reportCessna R172K · Flushing, MIA loss of engine power for undetermined reasons. Contributing to the accident was the wet runway.NTSB FTW02LA182Accident · No injuriesLimited investigationFinal reportCessna R172K · Llano, TXthe pilot's failure to refuel the airplane, which resulted in fuel exhaustion and a forced landing.NTSB ATL01LA096Accident · No injuriesLimited investigationFinal reportCessna R172K · Valdosta, GAThe flight instructor's improper flare of the airplane, which resulted in a hard landing. Factors were the dual student's failure to relinquish control of the airplane and the dual student's interference on the flight controls.NTSB LAX01LA256Accident · Serious injuriesLimited investigationFinal reportCessna R172K · Mammoth Lakes, CAThe pilot's inadequate in-flight planning and his failure to maintain sufficient altitude above the terrain. Factors were the high terrain and the blind canyon.NTSB ATL01LA086Accident · No injuriesLimited investigationFinal reportCessna R172-K · Culebras Island, PRPilots improper flare which resulted in a hard landing.NTSB DEN00LA167Accident · Minor injuriesLimited investigationFinal reportCessna R172K · Aurora, COThe unsuitable terrain for a forced landing. Contributing factors were the total loss of engine power due to the failure of the engine oil pump and the dark night light conditions.NTSB DEN00LA091Accident · No injuriesLimited investigationFinal reportCessna 172XP · Larkspur, COA forced landing on soft unsuitable terrain. Factors were improper wiring of the electric fuel boost pump, which produce high pressure when either on position was selected causing the engine to flood during the practice engine out approach.NTSB IAD00LA007Accident · No injuriesLimited investigationFinal reportCessna 172XP · Phillipi, WVThe pilot's improper flare that resulted in a hard landing.NTSB MIA99LA205Accident · No injuriesLimited investigationFinal reportCessna R172K · Pontotoc, MSa complete loss of engine power due to the failure of the oil pressure pump, resulting in oil starvation, a forced landing and subsequent nose over.NTSB SEA99LA072Accident · No injuriesLimited investigationFinal reportCessna R172K · Aurora, ORAircraft control was not maintained. The pilot's misjudged flare and inadequate remedial action, along with the flight instructors delayed remedial action were factors.NTSB MIA99FA126Accident · Minor injuriesField investigationFinal reportCessna 172K · Lakeland, FLFailure of the pilot of the other aircraft to maintain a visual lookout and visual separation while on approach for landing. This resulted in a midair collision with another airplane and subsequent in-flight collision with the runway.NTSB NYC99LA088Accident · Minor injuriesLimited investigationFinal reportCessna 172XP · Ramapo, NYFuel exhaustion due to the pilot's inaccurate fuel consumption calculations. A factor in the accident was the flight instructor's inadequate supervision of the solo cross-country flight.NTSB SEA99LA008Accident · No injuriesLimited investigationFinal reportCessna 172K · Dillon, MTThe student pilot-in-command's failure to maintain directional control. Contributing factors were rough terrain and crosswind conditions.NTSB IAD99FA005Accident · 1 fatalField investigationFinal reportCessna R172K · Bowie, MDThe pilot's failure to maintain adequate airspeed which resulted in an inadvertent stall. Also causal was the pilot's poor in-flight planning/decision, and his continued VFR flight into instrument meteorological conditions. A related factor was the fog.NTSB CHI98LA196Accident · No injuriesLimited investigationFinal reportCessna 172K · Omaha, NEThe aircraft modification not being in compliance with the Supplemental Type Certificate. A factor to the accident was the fracture of the landing gear axle during landing.NTSB FTW98LA083Accident · Serious injuriesLimited investigationFinal reportCessna R172K · Lakeview, ARthe pilot's failure to maintain runway alignment during the approach, and his delayed decision to execute a go-around. A related factor was the sunglare interfering with the pilot's view.NTSB LAX97FA225Accident · 2 fatalField investigationFinal reportCessna R172K · Moreno Valley, CAThe pilot's continued VFR flight into instrument meteorological conditions, and his attempt to climb through a low stratus cloud layer while in mountainous/hilly terrain. The pilot's failure to obtain a weather briefing, the weather, and the terrain were…NTSB FTW97LA108Accident · No injuriesLimited investigationFinal reportCessna R172K · Brownsville, TXthe pilot's failure to refuel the airplane which resulted in a loss of engine power due to fuel exhaustion.NTSB LAX97FA093Accident · 1 fatalField investigationFinal reportCessna R172K · Bagdad, AZcontinued flight by the pilot into adverse weather conditions, and his failure to maintain sufficient altitude or clearance from terrain. Factors relating to the accident were: the high/mountainous terrain and adverse weather conditions.NTSB LAX96LA247Accident · Serious injuriesLimited investigationFinal reportCessna R172K · Oroville, CAundetermined.NTSB FTW96LA256Accident · No injuriesLimited investigationFinal reportCessna R172K · Watkins, COan improper flare by the pilot, which resulted in a hard landing.NTSB SEA96LA053Accident · No injuriesLimited investigationFinal reportCessna R172K · Garden Valley, IDThe pilot's selection of an unsuitable landing area. The snow covered runway was a related factor.NTSB CHI96LA093Accident · No injuriesLimited investigationFinal reportCessna 172 · Worthington, MNProgressive failure of the engine, beginning with failure of the left magneto, which resulted in preignition or detonation, a burned hole in the #3 piston, subsequent oil exhaustion, and failure of the #1 and #2 connecting rods.NTSB BFO96FA039Accident · 2 fatalField investigationFinal reportCessna R172K · Highland Hills, OHthe pilot's continued VFR flight into instrument meteorological conditions at a low altitude with known obstacles in the area.NTSB BFO95LA089Accident · No injuriesLimited investigationFinal reportCessna R172K · Lisbon, OHLoss of oil, where an oil filter adapter had separated from the crankcase cover, due to stripped threads that were caused or allowed by inadequate maintenance or inspection, which resulted in oil exhaustion and subsequent loss of engine power. A factor…NTSB ANC95LA135Accident · No injuriesLimited investigationFinal reportCessna 172 · Cordova, AKThe pilot's improper planning/decision and delayed decision to abort the takeoff.NTSB SEA95LA008Accident · Minor injuriesLimited investigationFinal reportCessna R172K · St. George, UTInadequate fuel consumption calculations. Factors to the accident were: fuel exhaustion and a parked aircraft in the landing path.NTSB ATL94LA158Accident · No injuriesLimited investigationFinal reportCessna 172XP · Clarksburg, TNThe failure of the alternator drive coupling, and debris from the failed coupling that lodged in the engine oil pump, resulting in a sheared oil pump drive shaft. The engine subsequently failed because of oil starvation.NTSB NYC94FA128Accident · 4 fatalField investigationFinal reportCessna K172R · Tremont City, OHFailure of the pilot to maintain control of the airplane. A factor related to the accident was: the pilot's lack of experience in the type of operation.NTSB MIA94FA179Accident · 1 fatalField investigationFinal reportCessna 172XP · Indian Shores, FLA bird collision, which resulted in pilot incapacitation.NTSB FTW94LA039Accident · Minor injuriesLimited investigationFinal reportCessna R172K · Mancos, COFuel exhaustion induced power loss and the pilot's inadequate preflight inspection, during which he failed to insure that the airplane had been refueled to capacity. A factor was the lack of suitable terrain for a forced landing.NTSB NYC94LA003Accident · No injuriesLimited investigationFinal reportCessna 172 · Mt. Gilead, OHthe pilot's improper inflight decision to conduct a night landing at an airport without runway lights, and the subsequent misalignment with the runway and collision with an object.NTSB DEN93LA078Accident · No injuriesLimited investigationFinal reportCessna 172XP · Allen, TXFuel exhaustion induced power loss. A factor was the lack of suitable terrain for the forced landing.NTSB ANC93LA065Accident · No injuriesLimited investigationFinal reportCessna 172K · Rohn Roadhouse, AKThe pilot in command's inadequate compensation for the wind conditions and allowing the airspeed to go below stalling speed in the landing configuration.NTSB LAX93LA159Accident · Minor injuriesLimited investigationFinal reportCessna 172K · Fresno, CAthe improper installation of an electrical wire bundle, and, the chaffing and subsequent arcing of the wires against a fuel line which resulted in a fire.NTSB LAX93LA008Accident · No injuriesLimited investigationFinal reportCessna R172K · Picacho, AZThe pilot's encounter with the unforecasted cyclonic wind.NTSB SEA92LA180Accident · Minor injuriesLimited investigationFinal reportCessna R172K · Pocatello, IDAn undetermined loss of engine power. A factor to the accident was: an in flight planning/decision delay.NTSB BFO92LA060Accident · Minor injuriesLimited investigationFinal reportCessna 172XP · Milton, DEThe pilot's failure to attain adequate airspeed for climb.NTSB MIA92GA002Accident · 2 fatalFinal reportCessna 172K · Everglades City, FLThe pilot-in-command's improper management of fuel. This resulted in the airplane experiencing fuel exhaustion, forced landing, and in flight collision with terrain.NTSB LAX91LA227Accident · No injuriesLimited investigationFinal reportCessna R172K · Santa Clarita, CAFuel exhaustion due to the failure of the pilot to properly perform preflight planning and to ensure that an adequate fuel supply existed for the flight.NTSB CHI91LA094Accident · No injuriesLimited investigationFinal reportCessna R172K · Herington, KSLoss of engine power due to failure of a connecting rod bolt. A factor related to the accident was: the soft, unsuitable terrain.NTSB DEN90LA151Accident · No injuriesLimited investigationFinal reportCessna 172XP · Tooele, UTThe flights encounter with turblence on final which resulted in a loss of control and a subsequent collision with the ground.NTSB FTW90LA109Accident · No injuriesLimited investigationFinal reportCessna 172XP · Leona, TXEngine power loss due to a totally obstructed air intake manifold. Contributing to the accident was the unsuitable terrain in which the forced landing had to be performed.NTSB DEN90LA091Accident · No injuriesLimited investigationFinal reportCessna 172XP · Hurricane, UTThe engine oil leak induced connecting rod failure and subsequent total power loss.NTSB LAX90LA271Accident · 1 fatalLimited investigationFinal reportCessna R172K · Lone Pine, CAThe pilot's decision to continue VFR flight into instrument meteorological conditions. Factors to the accident were the adverse weather conditions, mountainous terrain, and the likely effect of hypoxia on the pilot.NTSB CHI89LA186Accident · No injuriesLimited investigationFinal reportCessna 172 · Ypsilanti, MIThe failure of the plt to maintain directional control during the takeoff ground roll. Rain softened terrain adjacent to the runway surface is a contributing factor to the accident.
Back to Cessna R172K