Cessna 172N
NTSB investigations · 1,815
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 ('2072434')
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 ('2072434')
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 NYC93LA163Accident · No injuriesLimited investigationFinal reportCessna 172 · Hope Valley, RIThe engine failure as the result of ingestion of pieces of carburetor into the cylinders, and the subsequent forced landing and nose over during the landing roll after encountering soft terrain.NTSB NYC93FA158Accident · 1 fatalField investigationFinal reportCessna 172N · Lincoln Park, NJThe failure of both pilots to maintain adequate visual lookout while in the airport traffic pattern, which resulted in an in-flight collision.NTSB NYC93LA146Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Leeds, METhe loss of engine power for undetermined reasons.NTSB SEA93LA167Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Monroe, WAThe improper inflight decision by the PIC and his failure to attain proper runway alignment. Factors relating to the accident were the dark night light conditions, unavailability of runway lights, and lack of recent night flight time by the PIC.NTSB FTW93LA216Accident · No injuriesLimited investigationFinal reportCessna 172N · Purcell, OKThe lack of suitable terrain onto which to execute the forced landing which was neccesitated by the partial power loss. The power loss was a result of the fatigue failure of the exhaust valve rocker arm attachment stud. A factor was the night conditions.NTSB CHI93FA272Accident · Serious injuriesField investigationFinal reportCessna 172N · Long Grove, ILThe pilot-in-command's failure to refuel the airplane prior to fuel exhaustion. Related factors to the accident were: inadequate certification/approval of the STC by the FAA, inadequate performance data, and unavailable fuel consumption information.NTSB MIA93LA158Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Atlantic Ocean (Atlantic Ocean)Total loss of engine power due to fuel exhaustion. Contributing to the accident was inaccurate fuel comsumption calculations by the pilot-in-command.NTSB LAX93LA284Accident · No injuriesLimited investigationFinal reportCessna 172N · Alturus, CAThe pilot's delay in aborting the takeoff. The pilot's premature rotation and his failure to follow the procedures in the airplane flight manual regarding use of the mixture control, the high density altitude condition and the pilot's lack of total flight…NTSB LAX93LA280Accident · No injuriesLimited investigationFinal reportCessna 172N · Truckee, CAThe partial loss of engine power during the takeoff initial climb for undetermined reasons. A factor in the accident was the unsuitable nature of the terrain for a forced landing.NTSB NYC93LA136Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Voluntown, CTThe pilot's failure to achieve the proper touchdown point which resulted in an overrun of the runway and collision with trees. A factor is the pilot's improper compensation for the wind condition.NTSB CHI93LA229Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Point Lookout, MOThe pilot in command's failure to maintain proper glide path, and her failure to attain the proper touch down Point.NTSB CHI93LA221Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Rapid City, SDThe pilot in command's inadequate compensation for wind conditions.NTSB DEN93LA068Accident · No injuriesLimited investigationFinal reportCessna 172N · Livermore, COA partial power loss when the rocker box for one cylinder disengaged. A factor was: unsuitable terrain for a forced landing.NTSB CHI93LA196Accident · No injuriesLimited investigationFinal reportCessna 172N · St. James, MIThe pilot landed too long on a wet runway.NTSB LAX93FA223Accident · 2 fatalField investigationFinal reportCessna 172N · Lompoc, CAVFR flight by the pilot into instrument meteorological conditions (IMC), and his failure to maintain proper altitude (or clearance) from mountainous terrain. Factors relating to the accident were: the low ceiling, fog, drizzle, obscuration, and mountainous…NTSB LAX93LA225Accident · 1 fatalLimited investigationFinal reportCessna 172N · Page, AZthe pilot's selection of an inadequate cruise altitude. A factor in the accident was the high winds and turbulence in the vicinity of the cliffs.NTSB DEN93LA061Accident · No injuriesLimited investigationFinal reportCessna 172N · Buena Vista, COA downdraft and the pilot's failure to maintain directional control of the airplane. Factors were: a crosswind and the inadvertent selection of additional flaps.NTSB MIA93FA127Accident · 4 fatalField investigationFinal reportCessna 172N · Deerfield Beach, FLFailure of the pilot-in-command to maintain airspeed (vso). The low altitude at the time of the aerodynamic stall was a factor.NTSB BFO93LA091Accident · No injuriesLimited investigationFinal reportCessna 172N · Petersburg, OHThe pilot's failure to attain the proper touchdown point while attempting to land on a wet grass strip, and his failure to perform a go around. The wet grass runway was a factor.NTSB ATL93LA091Accident · No injuriesLimited investigationFinal reportCessna 172 · Wilmington, NCThe ground personnel's failure to ensure that the airplane was clear of obstructions which resulted in the right wing colliding with a utility pole. A factor was the pilot's inadequate visual lookoutNTSB BFO93LA075Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Falmouth, KYThe pilot's failure to maintain directional control of the airplane during the landing roll, which resulted in an inadvertent swerve, and his delayed remedial action.NTSB ANC93LA059Accident · No injuriesLimited investigationFinal reportCessna 172 · Kasigluk, AKThe pilot's poor judgement in attempting a takeoff from a narrow, wet, soft gravel runway with a crosswind. The runway conditions and the crosswind were factors in the accident.NTSB LAX93LA193Accident · No injuriesLimited investigationFinal reportCessna 172N · Santa Monica, CAThat the pilot misjudged the flare and failed to properly recover from the ensuing bounced landing. The pilot's failure to attain the proper touchdown point was a factor.NTSB NYC93LA090Accident · No injuriesLimited investigationFinal reportCessna 172 · Columbus, OHThe improper flare by the pilot allowing the airplane to balloon and land hard. A factor in this accident was pilot's lack of recent flying experience.NTSB LAX93LA183Accident · No injuriesLimited investigationFinal reportCessna 172N · Needles, CAthe total loss of engine power due to the failure of the magneto in the ignition system. The magneto failure resulted from the operator's lack of voluntary compliance with the manufacturers suggested overhaul cycle.NTSB LAX93LA176Accident · No injuriesLimited investigationFinal reportCessna 172N · Flagstaff, AZThe pilot's poor aircraft handling techniques, his failure to correctly configure the carburetor heat control during the go around, and, his failure to maintain an adequate airspeed which resulted in an inadvertent stall mush condition. Factors in the…NTSB MIA93LA132Accident · No injuriesLimited investigationFinal reportCessna 172N · Immokalee, FLThe decision of the pilot to buzz and his failure to maintain adequate visual lookout.NTSB NYC93LA078Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Durham, NHImproper planning/decision by the pilot, which resulted in fuel exhaustion and loss of engine power. Factors related to the accident were flight into adverse weather conditions, failure to obtain inflight weather information, and pilot fatigue.NTSB FTW93FA096Accident · 1 fatalField investigationFinal reportCessna 172N · Katy, TXThe pilot's failure to maintain control of the airplane for undetermined reasonsNTSB FTW93LA094Accident · No injuriesLimited investigationFinal reportCessna 172N · Houston, TXFuel starvation power loss due to carburetor restriction from a foreign object, the inadequate inspection and improper overhaul of the carburetor by other maintenance personnelNTSB DEN93LA029Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Broomfield, CORudder control interference.NTSB MIA93LA079Accident · No injuriesLimited investigationFinal reportCessna 172N · Bunnell, FLImproper procedures by the other pilot for his failure to perform 's' turns while taxiing.NTSB LAX93LA102Accident · No injuriesLimited investigationFinal reportCessna 172N · Sedona, AZThe pilots inadequate compensation for the existing wind conditions and his delay in executing a go around. A factor in the accident was the pilot's lack of total experience.NTSB FTW93LA065Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Santa Fe, NMThe pilot's failure to maintain directional control. A factor was the snow conditionsNTSB CHI93LA065Accident · No injuriesLimited investigationFinal reportCessna 172N · Warren, MNThe student pilot's failure to maintain directional control.NTSB FTW93LA045Accident · No injuriesLimited investigationFinal reportCessna 172N · Tryon, OKPower loss due to fuel starvation and the pilots improper selection of the off position on the fuel selector. A factor was the lack of suitable terrain for the forced landing.NTSB LAX93FA046Accident · 2 fatalField investigationFinal reportCessna 172N · Tehachapi, CAThe pilot's decision to cruise at an altitude inadequate to ensure terrain clearance. Factors which contributed to the accident were: the pilot's failure to obtain a preflight weather briefing, the dark night, and likely instrument meteorological conditions.NTSB MIA93LA016Accident · No injuriesLimited investigationFinal reportCessna 172N · Ormond Beach, FLA fire of an undetermined source which erupted in the left cabin area during takeoff.NTSB CHI93LA022Accident · No injuriesLimited investigationFinal reportCessna 172N · Ankeny, IAThe pilot's improper recovery for a bounced landing.NTSB NYC93LA033Accident · No injuriesLimited investigationFinal reportCessna 172N II · Waverly, OHAn unavoidable collision with a deer.NTSB ATL93LA005Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Apex, NCThe pilot's improper in-flight planning and his inadequate compensation for wind conditions, which resulted in the overrun of the runway. Factors were the tail wind conditions, and the downhill, grass runway.NTSB DEN93LA002Accident · No injuriesLimited investigationFinal reportCessna 172N · Englewood, COFailure of the pilot in command to maintain directional control during landing roll. A factor was excessive airspeed during landing.NTSB DEN92LA094Accident · No injuriesLimited investigationFinal reportCessna 172N · Fort Collins, COThe pilot's failure to maintain directional control of the airplane. A factor was: crosswind.NTSB BFO92LA142Accident · No injuriesLimited investigationFinal reportCessna 172N · Havre De Grace, MDThe pilot's improper use of carburetor heat control resulting in a total loss of engine power. Factors contributing to the accident include the existence of weather conditions conducive to carburetor icing and the rough terrain on which the aircraft was…NTSB CHI92LA277Accident · No injuriesLimited investigationFinal reportCessna 172N · Geneseo, ILThe pilot's attempted operation of the airplane with a known defficiency in the equipment.NTSB ANC92LA166Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Seldovia, AKThe failure of the pilot to perform a go around when a tail wind was encountered prior to touch down. Factors related to the accident were: the tailwind and the downdraft.NTSB LAX92LA382Accident · No injuriesLimited investigationFinal reportCessna 172N · Fillmore, CAThe first pilot's poor inflight decision to fly into a box canyon. Contributing to this accident was the box canyon and the downdraft.NTSB LAX92LA380Accident · No injuriesLimited investigationFinal reportCessna 172N · Stanfield, AZThe cfi's poor in-flight decision to demonstrate the simulated engine out emergency landing at too low an altitude and misjudging the altitude during the circling maneuver.NTSB SEA92LA193Accident · No injuriesLimited investigationFinal reportCessna 172N · Snohomish, WAInadequate visual lookout by the other pilot.NTSB CHI92FA254Accident · 1 fatalField investigationFinal reportCessna 172N · Marquette, MIThe pilot's failure to maintain proper altitude during the approach.
Back to Cessna 172N