Cessna 172F
NTSB investigations · 563
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 ('2072414')
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 ('2072414')
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 CHI08CA058Accident · No injuriesData collectionFinal reportCessna 172F · Crystal Falls, MIThe rough, unsuitable terrain encountered during the landing which resulted in the total failure of the nose landing gear.NTSB ANC08CA017Accident · No injuriesData collectionFinal reportCessna 172 · Nashville, TNA propwash encounter during taxi from a four-engine airplane that overturned the pilot's single-engine airplane when he elected to taxi across the larger airplane's propwash.NTSB SEA06CA148Accident · No injuriesData collectionFinal reportCessna 172F · American Falls, IDThe pilot's failure to maintain an airspeed above stall speed. Factors include his improper decision to takeoff with a tailwind, and the effects of the tailwind upon the aircraft's takeoff performance.NTSB CHI06FA184Accident · 1 fatalField investigationFinal reportCessna 172F · Brookville, INThe in-flight loss of engine power during cruise flight due to restricted fuel flow and the inadequate preflight the pilot performed. An additional cause was the trees.NTSB ATL06CA106Accident · Serious injuriesData collectionFinal reportCessna 172F · Rome, GAThe pilot's failure to maintain airspeed, which resulted in an inadvertent stall, and subsequent impact with the ground.NTSB DFW06CA164Accident · Serious injuriesData collectionFinal reportCessna 172F · Marietta, OKThe pilot's improper weather evaluation. Contributing factors were the strong tailwind and the high density altitude.NTSB ATL05CA165Accident · No injuriesData collectionFinal reportCessna C172F · Sparta, TNThe pilot's delay in applying carburetor heat that resulted in the loss of engine power due to carburetor ice.NTSB ATL05CA157Accident · Minor injuriesData collectionFinal reportCessna 172F · Haleyville, ALThe pilots inadequate preflight of the fuel tank resulting in a total loss of engine power in cruise flight due to fuel exhaustion, resulting in a forced landing, and nose over on landing roll out.NTSB DFW05FA082Accident · 1 fatalField investigationFinal reportCessna 172F · Hot Springs, ARA loss of engine power due to the pilot's failure to refuel resulting in fuel starvation. Contributing factors were the lack of suitable terrain for the forced landing, and a shoulder harness restraint system was not installed.NTSB CHI05CA058Accident · No injuriesData collectionFinal reportCessna 172F · Willmar, MNThe student pilot's failure to properly compensate for the crosswind conditions and his failure to maintain directional control during the landing rollout. Contributing factors were the crosswind and the snow bank.NTSB DFW05LA067Accident · No injuriesLimited investigationFinal reportCessna 172F · Sallisaw, OKA loss of engine power for undetermined reasons. A contributing factor was the lack of suitable terrain for the forced landing.NTSB NYC04LA183Accident · Serious injuriesLimited investigationFinal reportCessna 172F · Cooperstown, NYThe pilot's failure to maintain adequate airspeed and her premature rotation which resulted in an inadvertent stall/mush and subsequent impact with the ground.NTSB ATL04FA130Accident · 2 fatalField investigationFinal reportCessna 172F · Madisonville, TNThe pilot's failure to maintain airspeed while maneuvering on a touch and go landing resulting in a stall and collision with the ground.NTSB LAX04CA086Accident · No injuriesData collectionFinal reportCessna 172F · Redlands, CAthe pilot's inadequate compensation for the existing gusty crosswind condition, and his failure to maintain directional control. Contributing factors were a crosswind and wind gusts.NTSB CHI04LA012Accident · Minor injuriesLimited investigationFinal reportCessna 172F · Columbus, NEThe student pilot's inadequate compensation for wind conditions and his failure to maintain directional control of the airplane during an aborted takeoff. Factors associated with the accident were the crosswind condition, the delayed aborted takeoff, and the…NTSB MIA03LA176Accident · No injuriesLimited investigationFinal reportCessna 172F · Fajardo, PRThe pilot's inadequate aircraft preflight resulting in the airplane being operated with water contamination in the fuel system, and the loss of engine power.NTSB CHI03LA065Accident · Minor injuriesLimited investigationFinal reportCessna 172F · Waskish, MNThe inadequate preflight planning/preparation by the pilot. Contributing factors were the snow covered takeoff area and the tailwind.NTSB MIA03LA048Accident · No injuriesLimited investigationFinal reportCessna 172F · Jacksonville, FLa total loss of engine power due to the failure the oil filter because of over-pressurization, resulting in damage to the airplane during the subsequent forced landing.NTSB ATL03LA028Accident · No injuriesLimited investigationFinal reportCessna 172F · Stuart, FLThe pilot's inflight encounter with wind shear on final approach, which resulted in an inflight loss of control and subequent uncontrolled descent into trees.NTSB DEN02LA053Accident · No injuriesLimited investigationFinal reportCessna 172F · Salt Lake City, UTthe pilot's improper in-flight planning and decisions, which resulted in fuel exhaustion. A factor contributing to the accident was the lack of suitable terrain for the forced landing.NTSB ATL02LA081Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Smithfield, NCThe pilot's inadequate in-flight planning that resulted in fuel exhaustion and the subsequent loss of engine power.NTSB CHI02LA081Accident · No injuriesLimited investigationFinal reportCessna 172F · Lynxville, WIThe pilots delayed use of carburetor heat during carburetor icing conditions, and the unsuitable terrain encountered for the forced landing. The carburetor icing conditions, the powerline, the brush, and the nose gear collapse were contributing factors.NTSB MIA01LA139Accident · No injuriesLimited investigationFinal reportCessna 172F · Fort Pierce, FLa loss of engine power due to fuel exhaustion which resulted in a forced landing, and subsequent impact with a sign and a ditch.NTSB FTW01LA075Accident · No injuriesLimited investigationFinal reportCessna 172F · Clovis, NMthe pilot's failure to maintain directional control during take off roll resulting in a ground loop. A contributing factor was the crosswind.NTSB DEN01LA055Accident · No injuriesLimited investigationFinal reportCessna 172F · Larkspur, COthe flight instructor inadvertently stalling the airplane during a forced landing. Contributing factors were fuel exhaustion due to inadvertent opening of the fuel drain, lack of familiarity with the airplane, inadequate supervision of the flight, and the…NTSB ATL01LA026Accident · Serious injuriesLimited investigationFinal reportCessna 172 F · Greenwood, MSAn in-flight fire for undetermined reasons. Finding: A factor is the maintenance modification was performed by company personnel prior to the flight.NTSB LAX01FA070Accident · 2 fatalField investigationFinal reportCessna 172F · San Luis Obispo, CAThe pilot's failure to maintain a proper climb rate to VFR conditions on-top.NTSB IAD00LA022Accident · No injuriesLimited investigationFinal reportCessna 172 · Norridgewock, MEthe student pilot's loss of directional control during the takeoff roll.NTSB FTW00LA049Accident · No injuriesLimited investigationFinal reportCessna 172 · Fort Worth, TXThe student pilot's improper flare and improper recovery from a bounced landing, which resulted in a porpoise.NTSB ANC99LA151Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Galena, AKThe pilot's failure to refuel, and the resulting fuel exhaustion. A factor was the dark night which hampered location of a nearby closed, and unlit, airstrip.NTSB ATL99LA125Accident · No injuriesLimited investigationFinal reportCessna 172P · Buchanan, GAThe loss of engine power for undetermined reasons. Factors were conditions favorable for the formation of carburetor ice during glide and cruise, and rough and uneven terrain.NTSB CHI99FA042Accident · 2 fatalField investigationFinal reportCessna 172F · Coleman, WIpilot's failure to maintain clearance from the trees and his intentional flight into IMC conditions. Factors contributing to this accident were the pilot's lack of instrument certification, his becoming lost in the poor weather, his inadequate preparation for…NTSB ATL99LA001Accident · No injuriesLimited investigationFinal reportCessna C-172F · Ball Ground, GAThe pilots failure to maintain directional control of the airplane on take-off, during gusty conditions, resulting in a collision with a tree.NTSB LAX98LA301Accident · No injuriesLimited investigationFinal reportCessna 172F · Long Beach, CAThe pilot's misjudging the flare point and failure to maintain an adequate airspeed margin, which resulted in a stall/mush and hard landing. A contributing factor was the dark night conditions.NTSB MIA98LA233Accident · No injuriesLimited investigationFinal reportCessna 172F · Spring Hill, FLThe pilot's misjudgment of distance and his delay in initiating a go around. Contributing was the pilot's improper landing flare.NTSB MIA98LA216Accident · Minor injuriesLimited investigationFinal reportCessna 172F · Tuskegee, ALThe pilot's failure to attain adequate airspeed, and his failure to abort the takeoff.NTSB MIA98WA203Accident · Serious injuriesForeign investigationCessna 172F · Grand Turk, United KingdomNTSB FTW98LA166Accident · No injuriesLimited investigationFinal reportCessna 172F · Fort Collins, COthe pilot's improper in flight planning/decision in electing to land with a known 30 knot tailwind. Factors were high winds and a tailwind.NTSB FTW98LA070Accident · Serious injuriesLimited investigationFinal reportCessna 172F · Gonzales, LAThe inadvertent stall resulting from the flight instructor's failure to maintain airspeed during his delayed recovery from the bounced landing. Factors were the student's failure to maintain the proper airspeed and the instructor's inadequate supervision…NTSB FTW98LA036Accident · No injuriesLimited investigationFinal reportCessna 172F · Hurley, NMthe student pilot's failure to adequately compensate for the wind conditions. Factors included the gusty crosswind conditions and inadequate supervision of the student pilot's solo flight by his flight instructor.NTSB ANC97LA061Accident · No injuriesLimited investigationFinal reportCessna 172 · Ninilchik, AKfailure of the pilot to maintain altitude/clearance from a closed runway, while making a low pass, which resulted in an inadvertent touchdown.NTSB NYC97FA048Accident · 1 fatalField investigationFinal reportCessna 172F · Conrad, PAVFR flight by the pilot into instrument meteorological conditions (IMC), and spatial disorientation of the pilot, which led to loss of aircraft control, an uncontrolled descent, and subsequent collision with wooded terrain. Factors relating to the accident…NTSB NYC97LA008Accident · No injuriesLimited investigationFinal reportCessna 172N · Hilton, NYthe pilot's improper soft field landing technique, which allowed a nose over during the landing rollout. Soft terrain was a related factor.NTSB MIA97FA010Accident · Minor injuriesField investigationFinal reportCessna 172F · Venice, FLinadequate maintenance servicing of the airplane during an oil change by the owner/pilot for his failure to secure the oil temperature probe securing nut. Also, inadequate maintenance of the airplane by the owner/pilot for his failure to operate the engine…NTSB IAD97LA008Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Germantown, KYimproper maintenance with the installation of an improper oil ring on the number four piston, which led to failure of both the ring and pistion, oil starvation, and subsequent loss of engine power.NTSB CHI96FA348Accident · 1 fatalField investigationFinal reportCessna 172F · Saint Clair, MNa loss of power due to the engine's #2 cylinder exhaust valve stuck open, and the pilot's failure to maintain airspeed.NTSB LAX96LA316Accident · No injuriesLimited investigationFinal reportCessna 172F · Ocotillo, CAthe pilot's failure to maintain proper runway alignment. The sun glare and proximity of rocks were related factors.NTSB CHI96LA233Accident · No injuriesLimited investigationFinal reportCessna 172 · Freeport, ILThe pilot's misjudgment of altitude and distance on final approach, and his failure to attain the proper touchdown point for landing.NTSB NYC96LA119Accident · No injuriesLimited investigationFinal reportCessna 172F · Blairstown, NJthe pilot's failure to maintain directional control due to improper compensation for wind conditions.NTSB CHI96LA006Accident · No injuriesLimited investigationFinal reportCessna 172F · Danbury, WIthe partial failure of the left magneto, the road sign, and the road embankment. A factor relating to this accident is the brush which obscured the road sign.
Back to Cessna 172F