Cessna 172A
NTSB investigations · 248
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 ('2072404')
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 ('2072404')
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 ANC25LA025Accident · Minor injuriesClass 3 · LimitedFinal reportCessna 172A · Fairbanks, AKThe pilot’s decision to initiate the flight despite identifying a malfunction in the carburetor heat system during the pre-takeoff engine run-up, which led to a partial loss of engine power during climb out. Contributing to the accident was maintenance…NTSB ERA24LA021Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Orangeburg, SCThe student pilot’s failure to maintain adequate clearance from a fuel truck while taxiing. Also contributing was the flight instructor’s inadequate monitoring of the student pilot.NTSB ERA22LA204Accident · Minor injuriesClass 4 · LimitedFinal reportCessna 172A · Stockbridge, GAThe flight instructor’s delayed remedial action during an unstabilized approach, which resulted in an impact with powerlines and a subsequent loss of controlNTSB ERA22LA045Accident · Minor injuriesClass 3 · LimitedFinal reportCessna 172 · Decatur, GAOil exhaustion due to an oil leak that resulted in a total loss of engine power.NTSB WPR17LA169Accident · Serious injuriesLimited investigationFinal reportCessna 172A · Enumclaw, WAThe pilot's improper approach for landing, which resulted in the airplane landing long, and his delayed decision to go around with insufficient runway remaining, which resulted in collision with an airport perimeter fence.NTSB WPR13CA252Accident · Minor injuriesData collectionFinal reportCessna 172A · Eatonville, WAA partial loss of engine power due to carburetor icing and the pilot's failure to maintain adequate airspeed during a go-around, which resulted in a stall.NTSB CEN13CA176Accident · No injuriesData collectionFinal reportCessna 172A · Vineland, MNThe pilot’s decision to attempt a touch-and-go landing on a narrow, ice-covered road with snow banks on each side.NTSB CEN11LA153Accident · Serious injuriesLimited investigationFinal reportCessna 172A · Clarendon, TXThe pilot's failure to correctly set the altimeter, which resulted in his erroneous perception that the airplane was at a safe altitude.NTSB WPR11FA005Accident · 2 fatalField investigationFinal reportCessna 172 · Panguitch, UTThe pilot's decision to conduct a low-level flight into a canyon in windy conditions at a high density altitude, which resulted in a collision with trees and terrain.NTSB WPR10LA004Accident · No injuriesLimited investigationFinal reportCessna 172A · Payson, AZThe stress corrosion cracking of the nose gear landing fork, which resulted in the fork's failure during landing.NTSB ERA09CA309Accident · No injuriesData collectionFinal reportCessna 172A · Glenburn, METhe pilot's misjudgment of distance and speed during landing.NTSB CEN09CA226Accident · No injuriesData collectionFinal reportCessna 172A · Corsicana, TXThe pilot's improper flare.NTSB WPR09LA021Accident · Minor injuriesLimited investigationFinal reportCessna 172A · Coolidge, AZA total loss of engine power due to water contamination of the fuel system. Contributing to the accident was the pilot's inadequate preflight inspection.NTSB DFW08LA217AccidentLimited investigationFinal reportCessna 172A · Albuquerque, NMThe pilot's failure to maintain proper glide angle during the landing approach which resulted in a collision with a pole. Contributing to the accident were the pilot's lack of qualification, experience and the high density altitude.NTSB MIA08CA100Accident · No injuriesData collectionFinal reportCessna 172A · Jamestown, PAThe pilot's failure to maintain control after takeoff resulting in contact with the ground. Contributing to the accident was the pilot's inadequate preflight planning resulting in a takeoff from a short, wet, soft, runway.NTSB ANC08CA064Accident · No injuriesData collectionFinal reportCessna 172 · Chugiak, AKThe pilot's failure to maintain control of the airplane during the landing roll. Contributing to the accident was an inadvertent ground loop/swerve.NTSB ANC07LA031Accident · No injuriesLimited investigationFinal reportCessna 172A · Sarasota, FLThe pilot's inadequate compensation for wind conditions, which resulted in a loss of control during landing, and collision with objects. Factors associated with the accident were wind gusts and a crosswind.NTSB DFW06CA166Accident · No injuriesData collectionFinal reportCessna 172A · Durant, OKThe pilot's failure to maintain airspeed resulting in an inadvertent stall/spin.NTSB SEA06CA041Accident · No injuriesData collectionFinal reportCessna 172A · Othello, WAThe pilot's failure to maintain directional control during the takeoff roll. A factor was the berm.NTSB LAX06LA056Accident · No injuriesLimited investigationFinal reportCessna 172A · Corona, CAfailure of both pilots to see and avoid each other during traffic pattern operations at a non-towered airport.NTSB NYC06FA025Accident · 1 fatalField investigationFinal reportCessna 172A · Pohatcong, NJThe inadequate visual lookout of the pilots in both airplanes, which resulted in a midair collision during descent.NTSB CHI04CA088Accident · Minor injuriesData collectionFinal reportCessna 172A · Springfield, MOThe pilot failed to initiate a go-around and the airplane porpoised during the hard landing. Factors associated with the accident were the excessive groundspeed and the overload failure of the nose gear.NTSB FTW02LA084Accident · No injuriesLimited investigationFinal reportCessna 172A · Albuquerque, NMthe pilot's delay in executing a go-around while conducting a simulated emergency landing, which resulted in an in flight collision with terrain.NTSB LAX01LA282Accident · Minor injuriesLimited investigationFinal reportCessna 172-A · Groveland, CAa loss of engine power due to water contamination forced the pilot to land in an unsuitable area resulting in collision with a tree.NTSB NYC00LA099Accident · No injuriesLimited investigationFinal reportCessna 172 · Sissonville, WVThe pilot's failure to maintain runway alignment during takeoff. A factor in the accident was wind gusts.NTSB LAX00LA062Accident · Minor injuriesLimited investigationFinal reportCessna 172A · Dos Palos, CAA partial loss of engine power due to the failure of maintenance personnel to properly install and safety the throttle arm to the carburetor throttle shaft.NTSB LAX00LA053Accident · No injuriesLimited investigationFinal reportCessna 172A · Shoshone, CAThe pilot's inadequate compensation for the existing strong and gusting wind conditions and his subsequent failure to maintain directional control.NTSB ATL99LA123Accident · No injuriesLimited investigationFinal reportCessna 172 · Houston, MSThe pilot's failure to switch the magneto switch to the both position before attempting a takeoff that resulted in the loss of engine power and resulted in the subsequent collision with trees.NTSB FTW98LA254Accident · No injuriesLimited investigationFinal reportCessna 172A · Ten Sleep, WYThe student pilot's failure to select a proper touchdown point. A factor was his lack of recent experience conducting solo flight operations.NTSB LAX98LA163Accident · No injuriesLimited investigationFinal reportCessna 172A · Van Nuys, CAThe pilot's failure to maintain obstacle clearance due to his inadequate visual lookout and selection of the wrong taxi route. Contributing factors were the pilot's diverted attention while taxiing in the vicinity of a construction area.NTSB ANC98LA031Accident · No injuriesLimited investigationFinal reportCessna 172A · Paxson, AKThe pilots failure to maintain terrain clearance while flying into a box canyon, and an inadvertent stall during his attempt to reverse direction.NTSB FTW98LA003Accident · No injuriesLimited investigationFinal reportCessna 172A · Grand Junction, COEncounter with high gusting winds while standing with the engine runningNTSB SEA97LA152Accident · Minor injuriesLimited investigationFinal reportCessna 172A · Ogden, UTThe fracture of the no. 4 exhaust valve and subsequent loss of engine power. Factors contributing to the accident include a congested landing area, and rough terrain.NTSB IAD97LA009Accident · 1 fatalLimited investigationFinal reportCessna 172A · Lebanon, OHimproper aircraft handling by the tow pilot and/or the glider pilots, which allowed the tow plane and glider to get out of position with one another; and failure of the aircrews (in both aircraft) to ensure a timely release of the glider tow rope.NTSB NYC96LA144Accident · Serious injuriesLimited investigationFinal reportCessna 172A · Pleasant Valley, NYfailure of the pilot to maintain obstacle clearance from trees during a precautionary landing. His becoming lost was a related factor.NTSB LAX95LA316Accident · No injuriesLimited investigationFinal reportCessna 172A · Weed, CAthe flight instructor's failure to maintain directional control of the aircraft.NTSB ANC95LA124Accident · Serious injuriesLimited investigationFinal reportCessna 172A · Chickaloon, AKThe pilot's inadvertent encounter with adverse weather conditions and failure to maintain sufficient altitude/clearance from the terrain to compensate for such conditions. Factors related to the accident were: downdrafts, the proximity of mountainous terrain,…NTSB ANC95FA104Accident · 2 fatalField investigationFinal reportCessna 172A · Naknek, AKInadequate visual lookout by the pilot of the Piper PA-18. The PA-18 pilot's diverted attention was a related factor.NTSB LAX95LA181Accident · Minor injuriesLimited investigationFinal reportCessna 172A · Colusa, CAthe pilot's selection of an inadequate en route cruise altitude for the aerial observation flight, and his failure to identify and stop an inadvertent descent while flying over flooded terrain at a very low altitude. Lack of pilot experience in low level…NTSB LAX93LA273Accident · Minor injuriesLimited investigationFinal reportCessna 172A · Moccasin, CAFuel exhaustion due to the pilot's failure to perform fuel consumption calculations. Factors related to this accident were: the pilot's inadequate preflight or inflight planning and preparation.NTSB SEA91LA080Accident · No injuriesLimited investigationFinal reportCessna 172A · Hood River, ORAn inadequately planned approach which resulted in a hard landing. Factors to the accident were rough water landing conditions, poor supervision by the CFI, and the overload condition to the float assembly.NTSB BFO90LA044Accident · No injuriesLimited investigationFinal reportCessna 172A · Pocomoke, MDThe pilot's misjudgement of distance and speed during the approach to land, and his failure to attain the proper touchdowwn point during the landing. The ditch was a related factor.NTSB NYC90LA096Accident · No injuriesLimited investigationFinal reportCessna 172A · Mt. Pleasant, PAThe pilot failed to maintain directional control during takeoff, a premature lift-off, and an inadvertent stall/mush. A factor in the accident was the unfavorable wind.NTSB ATL90LA096Accident · No injuriesLimited investigationFinal reportCessna 172A · Villa Rica, GAFuel starvation to the engine, initiated by the combination of a blocked fuel tank vent line and a malfunctioning fuel filler cap. A factor in the accident was the pilot's inadequate preflight inspection, in that he did not detect the fuel vent line blockage.NTSB MIA90LA066Accident · No injuriesLimited investigationFinal reportCessna 172A · Pahokee, FLLoss of engine power for am undetermined reason.NTSB SEA90LA033Accident · No injuriesLimited investigationFinal reportCessna 172A · Reno, NVThe pilot's improper use of the flight controls. Factors in the accident were the high, gusty wind conditions, the pilot's self induced pressure to arrive at work on time, and his lack of total pilot experience.NTSB BFO89LA044Accident · No injuriesLimited investigationFinal reportCessna 172A · Madison Heights, VAStudent pilot's failure to maintain proper airspeed during the landing attempt which resulted in the initiation of a go-around. Contributing factors to the accident were the pilot's poor preflight planning and his becoming disoriented during the flight. Also…NTSB FTW89LA063Accident · No injuriesLimited investigationFinal reportCessna 172 · Bastrop, TXInadequate preflight planning and preparation by the pilot which resulted in fuel exhaustion. Contributing to the accident were the low ceilings and fog.NTSB FTW88LA117Accident · Minor injuriesLimited investigationFinal reportCessna 172A · Cleveland, TXThis acft was damaged when it collided with a ditch and flipped over. The acft's battery was dead and the plt hand propped the eng without the benefit of chocks or an experienced individual in the cockpit. The eng started and as the plt was attempting to…NTSB CHI88LA070Accident · No injuriesLimited investigationFinal reportCessna 172A · Crivitz, WIThe aircraft did not accelerate as anticipated by the pilot, who was attempting to takeoff from a wet sod strip. The pilot elected to abort the takeoff, however was unable to stop on the remaining runway, exited the departure end, struck a snow bank and nosed…
Back to Cessna 172A