Cessna 172M
NTSB investigations · 1,699
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 ('2072418')
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 ('2072418')
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 ATL02LA039Accident · No injuriesLimited investigationFinal reportCessna 172M · Sanford, NCThe pilots failure to maintain directional control during landing roll that resulted in a collision with an airport sign. Factors were wet runway surface and wind gust.NTSB ATL02LA024Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Trenton, FLThe pilot's improper in-flight decision to make a precautionary landing after sustaining a total loss of electrical power with sufficient fuel remaining to reach his destination airport. This resulted in an off field landing to an off site location in a…NTSB MIA02LA046Accident · Serious injuriesLimited investigationFinal reportCessna 172M · New Smyrna Bch, FLthe failure of the pilot to maintain airspeed, during initial climb out, which resulted in an inadvertent stall, and subsequent impact with the terrain.NTSB FTW02LA058Accident · No injuriesLimited investigationFinal reportCessna 172 · New Braunfels, TXThe student pilot's failure to maintain directional control of the airplane during the landing roll. A contributing factor was the soft terrain.NTSB NYC02LA035Accident · No injuriesLimited investigationFinal reportCessna 172M · Ravenna, OHThe student pilot's failure to maintain directional control.NTSB MIA02LA031Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Barceloneta, PRThe pilot's failure to maintain control of the aircraft which resulted in an uncontrolled descent and an in flight collision with water. Contributing to the accident was the impairment of the pilot due to alcohol.NTSB MIA02LA024Accident · No injuriesLimited investigationFinal reportCessna 172M · Crystal River, FLthe pilot's failure to keep a proper visual lookout and ensure proper clearance during taxi operations, which resulted in a collision with vehicles.NTSB CHI02LA036Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Vandalia, MOThe student pilot's inadequate directional control on the previous landing resulting in the overload failure of the nose landing gear fork. Factors were the overload of the nose landing gear fork, and the student pilot's lack of total experience.NTSB LAX02LA026Accident · No injuriesLimited investigationFinal reportCessna 172M · Chandler, AZFailure of the student pilot to maintain directional control during landing.NTSB LAX02LA017Accident · No injuriesLimited investigationFinal reportCessna 172M · Prescott, AZThe CFI's improper remedial action and failure to maintain directional control during landing in a strong crosswind condition.NTSB ATL02LA001Accident · No injuriesLimited investigationFinal reportCessna 172 · Goldsboro, NCThe student pilot's failure to maintain directional control during a touch-and-go landing.NTSB IAD02LA003Accident · Minor injuriesLimited investigationFinal reportCessna 172M · White Stone, VAloss of engine power for undetermined reasons.NTSB SEA01LA171Accident · No injuriesLimited investigationFinal reportCessna 172M · Seattle, WAPilot's failure to maintain an adequate visual lookout during taxi. A fence was a factor.NTSB NYC01LA219Accident · No injuriesLimited investigationFinal reportCessna 172M · Danbury, CTAn inoperative airspeed indicator and the pilot's improper recovery from the bounced landing.NTSB CHI01LA265Accident · No injuriesLimited investigationFinal reportCessna 172M · Milton, WIThe unsuitable terrain for landing encountered by the pilot. Factors were the high vegetation and the loss of engine power for undetermined reasons.NTSB LAX01LA259Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Placerville, CAInadequate airspeed during climb out following an aborted landing that was precipitated by the pilot's misjudged speed/distance on final approach. Also, contributing to the accident was the pilot's inexperience in the type of operation, his failure to…NTSB LAX01LA251Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Carson City, NVThe pilot's failure to follow the approved procedures for the aircraft when he attempted to takeoff at high density altitude with the wing flaps fully extended.NTSB ATL01LA085Accident · No injuriesLimited investigationFinal reportCessna 172M · Atlantic Ocean (Atlantic Ocean)The loss of engine power for undetermined reasons.NTSB FTW01LA161Accident · No injuriesLimited investigationFinal reportCessna 172 · Kingston, OKthe pilot's failure to maintain directional control during the takeoff roll, which required his evasive maneuver and resulted in a stall.NTSB SEA01LA122Accident · No injuriesLimited investigationFinal reportCessna 172M · Bozeman, MTThe pilot of another aircraft failed to maintain clearance while maneuvering for a formation flight. An updraft was a factor.NTSB LAX01LA221Accident · No injuriesLimited investigationFinal reportCessna 172M · Napa, CALoss of engine power due to the restricted movement of the number 1 exhaust valve that subsequently bent the exhaust push rod and push rod housing.NTSB MIA01LA161Accident · No injuriesLimited investigationFinal reportCessna 172M · Bennettsville, SCThe pilot's improper correction for wind conditions and his failure to maintain control of the airplane resulting in the airplane sliding off an embankment during taxi from landing.NTSB CHI01LA159Accident · No injuriesLimited investigationFinal reportCessna 172M · Middleton, WIThe pilot attempted a touch and go on unsuitable terrain. A factor associated with the accident was the tall wet grass airstrip on which the touch and go was attempted.NTSB MIA01LA158Accident · No injuriesLimited investigationFinal reportCessna 172M · Miami, FLThe pilot's failure to maintain airspeed during a go-around resulting in the airplane stalling, descending uncontrolled, impacting the runway, and sliding off the runway and nosing over.NTSB FTW01LA138Accident · No injuriesLimited investigationFinal reportCessna 172M · Hot Springs, ARthe student pilot's delayed go-around, which resulted in the airplane impacting trees during the aborted landing.NTSB NYC01LA139Accident · No injuriesLimited investigationFinal reportCessna 172M · Nashua, NHThe CFI's improper decision to abort the takeoff and his improper flare, which resulted in a hard landing.NTSB SEA01LA094Accident · No injuriesLimited investigationFinal reportCessna 172 · McMinnville, ORThe student pilot's failure to adequately compensate for wind conditions while doing a touch-and-go landing.NTSB CHI01LA133Accident · No injuriesLimited investigationFinal reportCessna 172M · West Chicago, ILThe inadequate compensation for the crosswind by the student pilot. Additional factors included the student pilot's lack of total flight time, the runway sign and the crosswind.NTSB FTW01LA133Accident · No injuriesLimited investigationFinal reportCessna 172M · Patterson, LAthe pilot's failure to maintain control during the go-around. A contributing factor was the wind gust.NTSB CHI01LA127Accident · No injuriesLimited investigationFinal reportCessna 172M · Eveleth, MNThe pilot's inadequate compensation for the crosswind conditions which resulted in the loss of aircraft control. Factors associated with the accident were the gusty crosswind condition, the pilot's lack of experience, and the trees which were contacted.NTSB LAX01LA135Accident · No injuriesLimited investigationFinal reportCessna 172M · N. Las Vegas, NVThe pilot's inadequate compensation for the existing crosswind condition, and his failure to maintain runway alignment.NTSB NYC01LA063Accident · No injuriesLimited investigationFinal reportCessna 172M · Farmville, VAthe failure of the pilot to maintain directional control.NTSB IAD01LA020Accident · No injuriesLimited investigationFinal reportCessna 172M · Medford, NJThe pilot's failure to attain the proper touchdown point. Factors included the loss of electrical power, the dark night, and the pilot's lack of night experience.NTSB CHI01LA051Accident · No injuriesLimited investigationFinal reportCessna 172M · Sturgis, SDThe pilot failed to maintain control of the airplane during takeoff and he discontinued an aborted takeoff once initiated. Factors associated with the accident were the inaccurate elevator trim indicator, the pilot's failure to verify the trim setting,…NTSB NYC01LA055Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Mount Sterling, KYThe student pilot's inadequate recovery from a bounced landing.NTSB NYC01LA025Accident · No injuriesLimited investigationFinal reportCessna 172M · Camp Springs, MDThe pilot's improper in-flight decision to operate close behind a large airplane at the same altitude, which resulted in a wake turbulence encounter.NTSB CHI01LA004Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Sparta, WIthe pilot's inaccurate fuel consumption calculations, improper fuel management, inadequate in-flight planning/decision, flight to destination alternate not performed, and the discontinued planned approach to the initially selected runway. Contributing factors…NTSB ANC00LA111Accident · No injuriesLimited investigationFinal reportCessna 172 · Alexander Creek, AKThe pilot's inadequate compensation for wind conditions. Factors associated with the accident were gusty winds, and a downdraft.NTSB CHI00LA259Accident · No injuriesLimited investigationFinal reportCessna 172M · Harbor Springs, MIthe pilot's long touchdown, and inadequate braking to stop on the runway. Factors relating to this accident were the pilot's improper in-flight planning and decision resulting in the long touchdown, and the fence.NTSB ATL00LA076Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Manteo, NCThe pilot's failure of preflight planning preparation, which resulted in the fuel exhaustion, and the subsequent loss of engine power.NTSB LAX00LA299Accident · No injuriesLimited investigationFinal reportCessna 172M · Oakland, CAThe pilot's improper landing flare.NTSB NYC00LA203Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Columbus, OHa partial power loss for undetermined reason(s).NTSB LAX00LA256Accident · No injuriesLimited investigationFinal reportCessna 172 · Chandler, AZfailure of the pilot-in-command to adequately compensate for a crosswind condition and maintain directional control during the landing roll, resulting in the airplane departing the runway and colliding with a sign.NTSB SEA00LA113Accident · No injuriesLimited investigationFinal reportCessna 172M · Wallace, IDThe pilot's failure to maintain airspeed and his failure to maintain clearance from the trees. Related factors were trees and mountainous terrain.NTSB CHI00LA168Accident · No injuriesLimited investigationFinal reportCessna 172M · Decatur, ILthe pilot's failure to maintain clearance with the T-hangar while taxiing. A Factor associated with the accident was the pilot's attention was diverted to an other airplane which was taxiing on the same taxi line in the opposite direction.NTSB MIA00LA187Accident · No injuriesLimited investigationFinal reportCessna 172M · Davis, NCThe pilot's inadequate compensation for wind. The crosswind was a contributing factor.NTSB CHI00FA129Accident · 3 fatalField investigationFinal reportCessna 172M · Cornell, WIthe pilot not maintaining aircraft control and the stall/spin he encountered. A factor was the extended flaps.NTSB ATL00LA052Accident · No injuriesLimited investigationFinal reportCessna 172M · Clinton, TNThe pilot's inadequate in-flight planning necessitating an intentional ground loop maneuver on landing. Contributing factors were the pilot's misjudgment of distance/airspeed, the high terrain surrounding the runway, and the tailwind condition.NTSB LAX00LA133Accident · No injuriesLimited investigationFinal reportCessna 172M · Sacramento, CAThe failure of the pilot to maintain directional control of the aircraft during the takeoff roll. A rough, uneven runway surface was a factor in the accident.NTSB FTW00LA090Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Manilla, ARThe pilot's performance of low altitude flight and his failure to maintain clearance with the power lines.
Back to Cessna 172M