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 FTW98LA041Accident · No injuriesLimited investigationFinal reportCessna 172P · Tooele, UTfailure of the pilot to maintain directional control of the airplane, while landing. Factors related to the accident were: the pilot's improper flare for landing, his delay in attempting to go around (abort the landing), and the encounter with a runway marker…NTSB NYC98LA012Accident · No injuriesLimited investigationFinal reportCessna 172P · Pittsfield, MAThe pilot's poor in-flight decision to continue VFR flight in IFR conditions. Factor's in this accident were the pilot's inadequate pre-flight planning, and fog.NTSB MIA98TA011Accident · Minor injuriesFinal reportCessna 172P · Wiggins, MSLoss of engine power for undetermined reasons resulting in a forced landing on unsuitable terrain and the aircraft nosing over during landing roll.NTSB CHI97LA303Accident · No injuriesLimited investigationFinal reportCessna 172P · Yankton, SDThe pilot's failure to maintain control of the aircraft. A factor contributing to the accident was the wind gusts.NTSB IAD97FA122Accident · 1 fatalField investigationFinal reportCessna 172P · Airville, PAThe student pilot's failure to maintain adequate airspeed which resulted in a stall/mush and subsequent collision with terrain.NTSB ATL97LA117Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Rockhill, SCThe pilot's failure to plan and have adequate fuel for the flight.NTSB FTW97LA289Accident · No injuriesLimited investigationFinal reportCessna 172P · La Porte, TXfailure of the pilot to maintain directional control of the airplane during the takeoff roll, as he attempted to close and lock the left cabin window. Factors relating to the accident were: the pilot's failure to follow the before takeoff checklist (secure…NTSB CHI97FA218Accident · 7 fatalField investigationFinal reportCessna 172P · Chicago, ILthe pilots not maintaining visual separation between their airplanes. A factor in this accident was the pilot of the southbound airplane not reporting her position abeam the airport as directed by the ATC controller.NTSB NYC97LA136Accident · No injuriesLimited investigationFinal reportCessna 172P · Wildwood, NJThe pilot's inadequate use of carburetor heat, which resulted in carburetor icing.NTSB NYC97LA131Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Tioga, PAThe pilot's improper inflight decision to land downwind with an inoperative airspeed indicator, and his improper landing flare.NTSB FTW97LA247Accident · No injuriesLimited investigationFinal reportCessna 172P · Fort Worth, TXimproper planning/decision by the flight instructor (CFI), which resulted in his inadvertent encounter with jet blast from a twin jet transport airplane.NTSB CHI97LA189Accident · No injuriesLimited investigationFinal reportCessna 172P · Fowlerville, MIfailure of the pilot to either attain proper touchdown point for landing or go around while he had sufficient airspeed and runway remaining.NTSB NYC97LA090Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Morristown, NJThe flight instructor's inadequate supervision which allowed the student to solo at night with less than one hour of night instruction with a known inoperative landing and taxi light. A Factor was the student pilot's spatial disorientation which resulted in…NTSB FTW97LA175Accident · No injuriesLimited investigationFinal reportCessna 172P · Austin, TXThe pilot's failure to maintain aircraft control. A factor was the pilot's inadequate compensation for the wind conditions.NTSB LAX97LA167Accident · Serious injuriesLimited investigationFinal reportCessna 172P · San Jose, CAThe student pilot's failure to maintain adequate airspeed to preclude stalling following an improper recovery from a bounced landing. Contributing factors were the pilot's premature and excessive flap retraction and misjudged landing flare.NTSB FTW97LA163Accident · No injuriesLimited investigationFinal reportCessna 172P · Mckinney, TXthe student pilot's failure to maintain directional control on the ground after recovery from a bounced landing.NTSB SEA97FA076Accident · 1 fatalField investigationFinal reportCessna 172P · Burlington, WYloss of engine power for undetermined reason(s). The lack of suitable terrain for a forced landing was a related factor.NTSB FTW97LA116Accident · No injuriesLimited investigationFinal reportCessna 172P · Cleveland, OKThe pilot/mechanic's improper installation of the spark plug, resulting in its separation from the engine. A factor was the unsuitable terrain available in the runway's overrun area.NTSB MIA97LA090Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Jackson, TNThe pilot's failure to maintain an adequate visual lookout while taxing. The reduced visibility was a factor.NTSB IAD97LA046Accident · No injuriesLimited investigationFinal reportCessna 172P · Chesapeake, OHthe pilot's failure to maintain proper altitude during the approach at night. Related factors were: darkness, and the pilot's lack of night flying experience.NTSB MIA97LA066Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Fort Lauderdale, FLFailure of other maintenance personnel to properly torque a connecting rod bolt and nut for the No. 3 cylinder during engine overhaul.NTSB CHI97LA054Accident · No injuriesLimited investigationFinal reportCessna 172P · Bloomington, INthe pilot failed to maintain control of the aircraft. Factors included the icy runway and the crosswind.NTSB MIA97LA051Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Atlanta, GAfailure of the pilot to initiate an immediate climb (go-around or missed approach) after encountering fog, while on final approach to land. Darkness and fog at the end of the runway were related factors.NTSB LAX97LA053Accident · No injuriesLimited investigationFinal reportCessna 172P · Van Nuys, CAimproper flare by the pilot during the landing, and his improper recovery from a bounced landing, which resulted in a hard landing, dragged wing tip, and a collapsed main gear.NTSB CHI97LA026Accident · No injuriesLimited investigationFinal reportCessna 172P · Waukegan, ILthe pilot's improper recovery from a bounced landing. A factor was the pilot's misjudging the flare.NTSB MIA97FA013Accident · 3 fatalField investigationFinal reportCessna 172P · St. Croixthe pilot's failure to maintain airspeed.NTSB LAX97LA018Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Kingsburg, CAthe student pilot's use of an excessively lean mixture, which led to engine overheating, detonation, subsequent failure of the number 2 piston, and a forced landing.NTSB CHI96LA326Accident · No injuriesLimited investigationFinal reportCessna 172 · Chicago, ILthe pilot's improper flare and improper recovery from a bounced landing. A factor relating to the accident was: the pilot's lack of experience (or lack of training) in recovery from bounced landings.NTSB IAD96FA132Accident · 3 fatalField investigationFinal reportCessna 172P · Summersville, WVThe pilot's improper flare, his delay in aborting a landing, and his failure to maintain adequate airspeed, which resulted in a bounced landing and a stall during climb out in an attempt to avoid collision with trees.NTSB NYC96LA149Accident · No injuriesLimited investigationFinal reportCessna 172P · Fairfield, NJthe pilot's improper aborted takeoff by extending full flaps which resulted in a porpoise. Subsequently, the airplane veered off the runway and the nose gear collapsed.NTSB FTW96LA300Accident · No injuriesLimited investigationFinal reportCessna 172P · Owasso, OKInadequate maintenance by maintenance personnel resulting in inoperative brake system during an aborted takeoff. A factor was the downhill runway condition.NTSB LAX96LA250Accident · No injuriesLimited investigationFinal reportCessna 172 · Camarillo, CAthe student pilot misjudged the landing flare resulting in a hard landing. A factor in the accident was high airspeed.NTSB ATL96LA086Accident · No injuriesLimited investigationFinal reportCessna 172 · Winston-Salem, NCThe pilot's improper use of the elevator in response to a bounced landing.NTSB NYC96LA093Accident · No injuriesLimited investigationFinal reportCessna 172P · Rutland, VTthe pilot's improper flare and recovery from a bounced landing. A contributing factor was his lack of recent flight experience.NTSB FTW96LA191Accident · No injuriesLimited investigationFinal reportCessna 172P · Denton, TXthe student pilot's delayed landing flare and his improper bounced landing recovery technique.NTSB FTW96LA179Accident · No injuriesLimited investigationFinal reportCessna 172P · Colorado Spgs, COthe student pilot'S failure to maintain control of the aircraft during a go-around.NTSB LAX96LA157Accident · No injuriesLimited investigationFinal reportCessna 172 · Sedona, AZthe pilot misjudged the flare.NTSB SEA96LA077Accident · No injuriesLimited investigationFinal reportCessna 172P · Friday Harbor, WAthe pilot's misjudgment of the aircraft's altitude above the runway and failure to flare for landing. Darkness (bright night) was a related factor.NTSB LAX96LA148Accident · No injuriesLimited investigationFinal reportCessna 172P · Fullerton, CAthe student pilot's inadequate compensation for the encounter with wake turbulence from a preceding small aircraft, and his improper bounced landing recovery technique.NTSB CHI96LA097Accident · No injuriesLimited investigationFinal reportCessna 172P · West Chicago, ILthe student pilot's misjudging the flare. A factor was the gusts.NTSB FTW96LA128Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Iowa, LAthe pilot's selection of the wrong runway for landing, his delay in initiating a go-around (aborted landing), and his failure to maintain clearance from the transmission lines. Factors relating to the accident were: the pilot's improper weather evaluation,…NTSB LAX96LA117Accident · No injuriesLimited investigationFinal reportCessna 172P · Raymond, CAThe pilot's failure to verify the quantity of fuel onboard the aircraft prior to departure, which resulted in fuel exhaustion.NTSB SEA96LA056Accident · No injuriesLimited investigationFinal reportCessna 172P · Cashmere, WAthe pilot's selection of the wrong runway for landing, by not observing a procedure to land uphill during calm wind conditions, and his subsequent failure to retract the flaps during landing roll, as recommended by the airplane's short-field landing…NTSB SEA96LA055Accident · No injuriesLimited investigationFinal reportCessna 172P · Salmon, IDfailure of the pilot to maintain directional control during the landing, which resulted in a ground swerve. A factor relating to the accident was: the rock pile to the left of the runway.NTSB ATL96LA038Accident · No injuriesLimited investigationFinal reportCessna 172 · Sanford, FLthe pilot-in-command's excessive taxi speed and his failure to maintain adequate clearance from obstacles.NTSB MIA96WA058Accident · 5 fatalForeign investigationCessna 172 · Nassau, BahamasNTSB FTW96FA058Accident · 3 fatalField investigationFinal reportCessna 172P · Hallett, OKThe flight instructor's intentional low altitude flight maneuver. Factors were the static wire and the bright night condition.NTSB LAX96LA043Accident · No injuriesLimited investigationFinal reportCessna 172 · Santa Ana, CAThe pilot's failure to maintain directional control which resulted in an inadvertent ground loop. The pilot's diverted attention while raising the flaps and pushing in the carburetor heat control was a factor in this accident.NTSB MIA95LA216Accident · No injuriesLimited investigationFinal reportCessna 172 · Atlantic Ocean (Atlantic Ocean)The failure of the oil lubrication system for undetermined reasons. Contributing to the accident was the lack of suitable terrain for a forced landing.NTSB ANC95LA149Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Soldotna, AKThe pilot's improper in-flight planning/decision, and his failure to maintain sufficient altitude to assure clearance from obstructions. The downdraft was a related factor.
Back to Cessna 172P