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 LAX95LA295Accident · No injuriesLimited investigationFinal reportCessna 172F · Bradley, CAfuel exhaustion due to the pilot's failure to refuel prior to takeoff and his delayed decision to proceed to his alternate airport. The night light conditions and the lack of a suitable emergency landing area were factors.NTSB CHI95LA252Accident · No injuriesLimited investigationFinal reportCessna 172F · Oshkosh, WIthe failure of the pilot of the Acro II, N40LF, to maintain clearance from the Cessna 172, N5542R.NTSB CHI95LA230Accident · Minor injuriesLimited investigationFinal reportCessna 172F · Wyandotte, INthe number three intake valve became stuck (seized), which resulted in a loss of engine power. The lack of suitable terrain for a forced landing was a related factor.NTSB SEA95LA131Accident · No injuriesLimited investigationFinal reportCessna 172F · Homedale, IDThe pilot misjudged distance and altitude during the approach. The downdraft was a factor.NTSB LAX95LA193Accident · No injuriesLimited investigationFinal reportCessna 172F · Boonville, CAa loss of engine power for undetermined reasons.NTSB BFO95FA050Accident · 1 fatalField investigationFinal reportCessna 172F · Tappahanock, VAThe student pilot's misjudgment of distance/speed during the approach to land, and her failure to go around while there was still sufficient runway remaining. Factors related to the accident were: inadequate supervision by the flight instructor, the student's…NTSB ATL95FA079Accident · 1 fatalField investigationFinal reportCessna 172F · Seneca, SCThe pilot's inadequate visual lookout while maneuvering near utility lines, which resulted in a collision with the wires.NTSB ATL95LA029Accident · No injuriesLimited investigationFinal reportCessna 172F · Carrollton, GAThe pilot's inadvertent collision with trees, adjacent to the taxiway, while attempting to avoid a deer that crossed the taxiway.NTSB LAX95LA025Accident · No injuriesLimited investigationFinal reportCessna 172F · Tonopah, NVthe pilot's excessive taxi speed and improper remedial action after the nose gear began to shimmy. The nose gear shimmy (nose gear vibration) and the berm were factors in this accident.NTSB CHI95LA023Accident · No injuriesLimited investigationFinal reportCessna 172F · Cross Plains, WIthe pilot's failure to use carburetor heat. Factors were carburetor icing conditions and rough/uneven terrain.NTSB MIA95LA006Accident · No injuriesLimited investigationFinal reportCessna 172-F · Clearwater, FLThe student pilot's failure to adequately compensate for the crosswind condition. Contributing to the accident was the pilot's lack of total experience.NTSB MIA95LA005Accident · Minor injuriesLimited investigationFinal reportCessna 172F · Indiantown, FLThe improper landing flare by the pilot resulting in the hard landing.NTSB BFO94LA095Accident · Minor injuriesLimited investigationFinal reportCessna 172 · York, PAthe loss of total engine power for undetermined reasons.NTSB LAX94LA192Accident · No injuriesLimited investigationFinal reportCessna 172F · Arlington, CAFailure of the certified flight instructor to properly supervise the student pilot and perform the appropriate remedial action before the airplane descended to an altitude too low for recovery. Factors were the student pilot's handling of the airplane which…NTSB FTW94LA011Accident · No injuriesLimited investigationFinal reportCessna 172F · Co. Springs, COAn encounter with wake turbulence during the landing flare. A factor was lack of total pilot experience.NTSB MIA93WA201Accident · Minor injuriesForeign investigationCessna 172F · Long Island, Turks & Caicos IslandsNTSB CHI93LA359Accident · No injuriesLimited investigationFinal reportCessna 172F · Indianapolis, INThe failure of the left magneto, which resulted in a partial loss of engine power.NTSB BFO93LA112Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Normalville, PAThe presence of carburetor icing conditions, which caused a total loss of engine power. A factor related to the accident was the pilot's delayed use of carburetor heat and rough terrain.NTSB CHI93FA218Accident · 1 fatalField investigationFinal reportCessna 172F · Miami, MOthe pilot's failure to maintain aircraft control.NTSB ATL93LA103Accident · Minor injuriesLimited investigationFinal reportCessna 172F · Ravenel, SCThe continuation of the landing attempt into the short sod field without the use of flaps and the use of excessive airspeed by the pilot. Factors in the accident were the failure of the aircraft flaps to extendNTSB NYC93LA010Accident · Serious injuriesLimited investigationFinal reportCessna 172F · Wash. Ct. House, OHAn inadvertent stall after the pilot failed to attain flying speed due to a premature liftoff.NTSB DEN92LA087Accident · No injuriesLimited investigationFinal reportCessna 172F · Folsom, NMCarburetor heat not used and improper use of throttle and mixture control. A factor was: the lack of suitable terrain for a forced landing.NTSB FTW92LA074Accident · Minor injuriesLimited investigationFinal reportCessna 172F · Mc Alester, OKInadvertent stall. A factor was a total power loss due to fuel exhaustion.NTSB CHI93LA381Accident · No injuriesLimited investigationFinal reportCessna 172 · Union Center, SDImproper planning/decision by the pilot, and his failure to abort the takeoff, while there was sufficient runway remaining. Factors related to the accident were: the soft runway condition & fence at the end of the runway.NTSB CHI90LA268Accident · Minor injuriesLimited investigationFinal reportCessna 172F · Huntington, INThe student pilot's improper preflight planning ensuring sufficient fuel for the intended flight.NTSB CHI90LA153Accident · No injuriesLimited investigationFinal reportCessna 172 · Millersburg, OHFailure of the pilot to maintain directional control during a go-around attempt. The pilots lack of total aviation experience and his motion sickness are factors associated with the accident.NTSB BFO90LA020Accident · No injuriesLimited investigationFinal reportCessna 172 · Staunton, VAThe pilot's failure to maintain directional control of the airplane during a crosswind landing.NTSB ATL89FA163Accident · 1 fatalField investigationFinal reportCessna 172F · Vernon, ALImproper maintenance of the spark plugs by the pilot/mechanic which resulted in a partial loss of engine power, and the pilot's failure to clear trees during an emergency landing in an open field resulting in an inadvertent stall.NTSB ATL89LA132Accident · No injuriesLimited investigationFinal reportCessna 172F · Elkin Arpt., NCThe failure of the pilot to properly compensate for the gusty wind conditions during takeoff and the delay in his decision to abort the takeoff before colliding with trees. Contributing to the accident were the gusty wind conditions and the pilot's lack of…NTSB DEN89LA105Accident · No injuriesLimited investigationFinal reportCessna 172F · Morgan, UTInadequate servicing of the aircraft by the pilot, partial blockage of the fuel line and fuel filter, and fuel starvation. Contributing factors were: the downward sloping runway and a fence.NTSB NYC89LA102Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Honesdale, PAThe loss of directional control by the pilot during landing.NTSB FTW89LA060Accident · No injuriesLimited investigationFinal reportCessna 172 · Jacksboro, TXFailure of the pilot to go around, when she did not attain the proper touchdown point (landed long) and had excessive airspeed to stop on the runway. A factor related to the accident was the unfavorable wind condition (sudden wind shift).NTSB LAX89FA113Accident · 1 fatalField investigationFinal reportCessna 172F · Safford, AZFailure of the pilot to maintain proper airspeed while on final approach resulting in an aerodynamic stall. Contributing to the accident was the pilot's delayed use of wing flaps.NTSB BFO89LA017Accident · Serious injuriesLimited investigationFinal reportCessna 172F · Bruceton Mills, WVThe power loss occurred because of carburetor ice which obstructed airflow to the induction system. Contributing to the accident was the carburetor icing conditions, the highway and the ditch which was contacted.NTSB MIA88LA272Accident · No injuriesLimited investigationFinal reportCessna 172F · Lake Wales, FLThe plt aborted the takeoff from the 'thick, wet' grass strip because the acft was not accelerating 'adequately.' He applied the brakes but it went off the departure end of the rwy, collided with a fence, tree, and dirt mound before coming to rest. There was…NTSB LAX88LA310Accident · No injuriesLimited investigationFinal reportCessna 172F · Fairfield, CAThe pilot performed a soft field takeoff on a grass strip in winds gusting to 34 KTS. The airplane would not accelerate in ground effect, nor would it climb. Feeling that he could not out-climb objects in his path, the pilot turned to the right. As he turned…NTSB CHI88LA212Accident · Serious injuriesLimited investigationFinal reportCessna 172F · Crandon, WIDuring cruise flight in deteriorating meteorological conditions, the pilot experienced a total loss of engine power. The pilot performed emergency procedures, was unable to restart the engine, and executed a forced landing in a clover field. The aircraft…NTSB ATL88LA182Accident · Minor injuriesLimited investigationFinal reportCessna 172F · Shellman, GAThe plt was making a personal flt to a pvt uncharted airstrip on a coastal island. Approaching his destination, the plt cancelled his VFR flt plan with fss. The plt stated that he approached the soft 2500 foot strip high and ballooned at touchdown. He landed…NTSB FTW88FA100Accident · Serious injuriesField investigationFinal reportCessna 172F · Golden, TXAcft was operating on an aerial photography flt at 200 to 500' AGL and 70 to 80 mph. The commercial plt stated that as he was in a bank the acft seemed to be 'pushed' into the 60 to 80' trees over which he was flying and that it 'fell out of the air'. He also…NTSB ATL88LA152Accident · No injuriesLimited investigationFinal reportCessna 172F · Walland, TNThe pilot attempted to abort a takeoff after experiencing a sudden gust of wind at liftoff. The aircraft collided with a fence and ditch which caused substantial airframe damage. The pilot reported the winds gusting to 15 knots. There was no reported aircraft…NTSB FTW88LA087Accident · Minor injuriesLimited investigationFinal reportCessna 172E · Leona, TXThe plt planned his apch to land about 1000 ft down the 3400 ft dirt rwy because the first 1000 ft was wet and soft. The last 400 ft was also wet and soft. The wind was calm and the apch speed was high. During the flare, the acft ballooned and floated past…NTSB ATL88LA116Accident · No injuriesLimited investigationFinal reportCessna 172F · Myrtle Beach, SCThe pilot reported that the airplane began to sink rapidly about 100 ft above the rwy threshold. He added pwr and initiated a flare. Upon touchdown, the airplane pitched down and rolled rt. The airplane subseqeuntly skidded off of the rt side of the rwy and…NTSB CHI88LA065Accident · No injuriesLimited investigationFinal reportCessna 172F · Brighton, MINTSB CHI88LA050Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Red Lake Falls, MNNTSB NYC88LA061Accident · No injuriesLimited investigationFinal reportCessna 172 · Concord, NHThe aircraft was landing at Concord municipal airport, and during landing roll, the aircraft veered to the left leaving the runway surface and nosed over in the field between the taxiway and runway 35.NTSB ATL88LA051Accident · No injuriesLimited investigationFinal reportCessna 172F · Eden, NCThe student plt attempted to land in a farm pasture adjacent to his brother's farm. The airplane ldg gear 'dug in' on ldg, and the airplane nosed over. The student plt described the terrain as 'wet & soggy'. The student did not have an instructor's…NTSB MKC88LA008Accident · No injuriesLimited investigationFinal reportCessna 172F · Lamoni, IAThe pilot said he was too high on final and went around. He stated that, when he was on short final during the next approach, he thought he was still too high and put down full flaps. The airplane stalled and touched down short of the runway. The nosegear was…NTSB ATL88LA002Accident · Minor injuriesLimited investigationFinal reportCessna 172F · Grand Bay, ALThe engine lost pwr shortly after t/o. the engine regained pwr as the plt was about to make a forced ldg in a field. He aborted the ldg attempt and attempted to make it back to the airstrip. The engine subsequently lost pwr again. The plt stretched his glide…NTSB MKC87LA098Accident · No injuriesLimited investigationFinal reportCessna 172F · Blythville, ARThe eng started to slow down ten miles from the destination arpt and despite emergency measures, it stopped two miles out. The forced landing was in a plowed field and when the nose wheel dug in, the acft flipped forward to the inverted position. The…NTSB MKC86LA127Accident · No injuriesLimited investigationFinal reportCessna 172F · Jefferson City, MOThe runway was under construction with a new section being added to the old runway. This construction was covered in a published NOTAM. The pilot had been making touch and go landings and was making a full stop landing when he landed on the new portion of the…
Back to Cessna 172F