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 LAX94LA350Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Rescue, CAThe pilot's delayed go-around. His inadequate compensation for the wind was a factor.NTSB LAX94LA349Accident · 1 fatalLimited investigationFinal reportCessna 172M · Jackpot, NVthe pilot's failure to maintain aircraft control due to spatial disorientation during a moonless night departure over an area without ground reference lights. A factor in the accident was the pilot's lack of instrument training and experience.NTSB BFO94LA143Accident · No injuriesLimited investigationFinal reportCessna 172M · Vestal, NYLoss of engine power during an aborted landing due to the throttle cable separating from the carburetor.NTSB LAX94LA310Accident · No injuriesLimited investigationFinal reportCessna 172M · Carson City, NVthe pilot's decision to attempt a landing in crosswind conditions which exceeded the capability of the aircraft.NTSB SEA94LA189Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Seattle, WAThe proper touchdown point was misjudged by the pilot. During the go-around attempt, he failed to maintain clearance from obstacles.NTSB LAX94FA289Accident · 4 fatalField investigationFinal reportCessna 172M · Sacramento, CAthe failure of the pilot to maintain adequate airspeed while maneuvering after takeoff and his failure to retract the flaps prior to departure. A factor in this accident was the pilot's lack of recent experience.NTSB LAX94FA282Accident · 1 fatalField investigationFinal reportCessna 172M · Running Springs, CAthe flying pilot's operation of the aircraft at an altitude that did not provide sufficient terrain clearance necessary to recover from an inadvertent, pilot-induced stall.NTSB LAX94LA277Accident · No injuriesLimited investigationFinal reportCessna 172 · Hanford, CAThe failure of the pilot to stop the aircraft in a timely manner after landing back on the runway following a loss of engine power for undetermined reasons.NTSB SEA94LA133Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Lookout Pass, IDPoor in-flight planning. Factors include cloudy weather.NTSB NYC94LA093Accident · No injuriesLimited investigationFinal reportCessna 172M · Groton, CTthe pilot's inadequate visual lookout during taxi, which resulted in the airplane's wing tip striking ground support equipment.NTSB ATL94LA091Accident · No injuriesLimited investigationFinal reportCessna 172M · Barnwell, SCThe pilot's failure to flare properly which resulted in a hard landing.NTSB LAX94LA173Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Santa Maria, CAAn engine failure due to the improper installation and service of an incorrect model magneto by maintenance personnel, and the failure of the pilot-in-command to follow published airplane emergency procedures.NTSB FTW94LA111Accident · No injuriesLimited investigationFinal reportCessna 172M · Flippin, ARThe student pilot's premature flare and the resultant inadvertent stall.NTSB SEA94LA068Accident · No injuriesLimited investigationFinal reportCessna 172 · Gillette, WYWas the pilot's inadequate remedial action. Factors include an inadvertent porpoise, and a lack of total experience.NTSB BFO94LA047Accident · No injuriesLimited investigationFinal reportCessna 172M · Slatington, PAThe pilot's inadequate compensation for wind conditions and failure to maintain alignment with the runway. The crosswind was a factor.NTSB BFO94LA042Accident · No injuriesLimited investigationFinal reportCessna 172M · Ravenna, OHFailure of the pilot to maintain directional control during takeoff leading to a collision with a snow bank which resulted in the airplane nosing over.NTSB FTW94FA050Accident · 1 fatalField investigationFinal reportCessna 172M · Lancaster, TXwas THE FAILURE OF THE PILOT TO MAINTAIN AIRCRAFT CONTROL DUE TO PHYSICAL IMPAIRMENT (ALCOHOL).NTSB LAX94FA056Accident · 2 fatalField investigationFinal reportCessna 172M · Julian, CAThe pilot's failure to maintain aircraft control. Factors in this accident were: 1) the dark night and lack of ambient light which resulted in the pilot inadvertently flying from visual meteorological conditions into instrument meteorological conditions; 2)…NTSB MIA94LA023Accident · No injuriesLimited investigationFinal reportCessna 172M · Orlando, FLThe failure of the pilot-in-command of the other aircraft to maintain a visual lookout and clearance between aircraft.NTSB SEA94LA023Accident · Minor injuriesLimited investigationFinal reportCessna 172H · Mckenzie Bridge, ORA partial loss of engine power for undetermined reasons.NTSB ATL94LA004Accident · No injuriesLimited investigationFinal reportCessna 172 · Blountville, TNImproper planning/decision by the pilot, which resulted in inadequate fuel and fuel exhaustion.NTSB SEA94LA011Accident · No injuriesLimited investigationFinal reportCessna 172M · Longbranch, WAThe instructor pilot's failure to follow procedures. Factors include carburetor icing conditions and soft terrain in the landing area.NTSB NYC94LA001Accident · No injuriesLimited investigationFinal reportCessna 172M · Wellsville, NYThe pilot's failure to maintain adequate airspeed which resulted in an inadvertent stall and inflight collision with the terrain.NTSB MIA93LA202Accident · No injuriesLimited investigationFinal reportCessna 172M · Hollywood, FLInadvertent exceeding of vfe with the flaps extended by the student pilot while practicing maneuvers.NTSB BFO93LA179Accident · No injuriesLimited investigationFinal reportCessna 172 · North Kingstown, RIThe pilot inadvertently allowed the airplane to stall as he was maneuvering to avoid birds on final approach.NTSB ANC93LA145Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Atigan Pass, AKThe pilot's improper inflight planning/decision and delay in taking remedial action.NTSB CHI93LA336Accident · No injuriesLimited investigationFinal reportCessna 172M · Adrian, MIan excessive taxi speed used by the pilot-in-command. A factor related to the accident was loose gravel on the ramp and inadequate airport maintenance by the airport personnel.NTSB CHI93LA332Accident · No injuriesLimited investigationFinal reportCessna 172M · Lincoln, NEthe pilot's failure to attain the proper touchdown point.NTSB DEN93FA097Accident · 1 fatalField investigationFinal reportCessna 172M · Clines Corners, NMThe pilot's failure to maintain a safe and proper altitude. Factors were the pilot's failure to obtain a preflight weather briefing, dark night condition, and weather conditions that included obscuration, fog, and drizzle.NTSB ATL93LA140Accident · No injuriesLimited investigationFinal reportCessna 172M · Manteo, NCInadequate compensation for wind conditions by the pilot. Factors related to the accident were: the adverse wind and the pilot's failure to obtain a weather briefing (inadequate weather evaluation).NTSB SEA93LA170Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Yellow Pine, IDThe pilot's improperly planned approach and delayed remedial action. A factor related to the accident was: the proximity of mountainous terrain.NTSB ATL93FA136Accident · Serious injuriesField investigationFinal reportCessna 172M · Harvest, ALThe pilot's poorly planned approach and the failure of the pilot to execute a go-around.NTSB FTW93LA210Accident · No injuriesLimited investigationFinal reportCessna 172M · Lamesa, TXThe pilot's improper flare, improper recovery from a bounced landing and the inadvertent stall. A factor was the gusty wind.NTSB ATL93LA100Accident · No injuriesLimited investigationFinal reportCessna 172 · Tuskegee, ALThe pilot's failure to establish a final approach course to the runway surface during a night landing. A factor was the inoperative aircraft landing light.NTSB LAX93LA230Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Turlock, CAThe pilot's poorly planned approach and his failure to maintain airspeed.NTSB ATL93LA095Accident · No injuriesLimited investigationFinal reportCessna 172 · Athens, TNFailure of the aircraft engine to produce power for unknown reasons.NTSB MIA93LA119Accident · No injuriesLimited investigationFinal reportCessna 172M · Ochopee, FLThe pilot's poor judgement in attempting the takeoff from the parking ramp when a 12,000-FT runway was available.NTSB SEA93LA103Accident · No injuriesLimited investigationFinal reportCessna 172M · Kapowsin, WAAn undetermined loss of engine power.NTSB DEN93LA046Accident · No injuriesLimited investigationFinal reportCessna 172M · Meeker, COThe pilot's improper compensation for wind conditions. A factor was: gusty crosswinds.NTSB ATL93LA073Accident · No injuriesLimited investigationFinal reportCessna 172 · Greenville, TNThe pilot's improper procedures in that he landed with excessive flap extension, and his inadequate compensation for the gusting crosswind.NTSB FTW93FA128Accident · 2 fatalField investigationFinal reportCessna 172M · Hobart, OKInadvertent stall. Factors were the instructor pilot's spatial disorientation, his lack of total instrument time, the weather, and the dark night conditions.NTSB ANC93LA052Accident · No injuriesLimited investigationFinal reportCessna 172M · Kasigluk, AKThe pilot's improper planning/decision and delay in aborting the takeoff. Factors related to the accident were: loose gravel on the surface of the runway and the snowbank (berm) on the overrun (stopway).NTSB BFO93LA059Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Lewisburg, OHThe pilot experienced spatial disorientation. Contributing to the accident was the dark night and inadvertent flight into instrument meteorological conditions.NTSB LAX93FA154Accident · 2 fatalField investigationFinal reportCessna 172M · White Water, CAThe pilot's failure to see and avoid the tower due to drug impairment. Factors which contributed to the accident were: the low altitude and the dawn light condition.NTSB FTW93LA104Accident · No injuriesLimited investigationFinal reportCessna 172M · Overbrook, OKThe pilot's failure to assure that the elevator trim was properly set for takeoff and his delay in aborting the takeoffNTSB SEA93LA075Accident · No injuriesLimited investigationFinal reportCessna 172M · Logan-Cache, UTThe pilot's failure to maintain directional control, and insufficient remedial action. Factors include a snow bank near the edge of the runway.NTSB CHI93LA105Accident · No injuriesLimited investigationFinal reportCessna 172M · Romeo, MIThe pilot's failure to maintain directional control.NTSB SEA93LA070Accident · No injuriesLimited investigationFinal reportCessna 172M · Salem, ORThe failure of the engine oil pump impeller.NTSB CHI93LA098Accident · No injuriesLimited investigationFinal reportCessna 172M · Grain Valley, MOThe student pilot's improper recovery from a bounced landing and failure to maintain directional control.NTSB NYC93LA063Accident · No injuriesLimited investigationFinal reportCessna 172M · Valley Point, WVThe failure of the pilot to make a rejected landing when the airplane failed to decelerate properly. A factor related to the accident was the failure of the pilot to close the throttle upon touchdown.
Back to Cessna 172M