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 FTW98FA307Accident · Serious injuriesField investigationFinal reportCessna 172N · Lincoln, TXThe #3 cylinder exhaust valve rocker arm fulcrum retaining stud backing out of its stud-tapped hole due to the improper tapping of the stud hole by unknown maintenance personnel. Contributing factors were the transmission wire, sign and gasoline pump.NTSB ATL98LA094Accident · No injuriesLimited investigationFinal reportCessna 172N · Olive Branch, MSthe student pilot's failure to maintain directional control of the airplane during takeoff.NTSB CHI98LA228Accident · No injuriesLimited investigationFinal reportCessna 172N · Stone Lake, WIthe lack of effective braking due to hydroplaning. Contributing factors to the accident were the trees off the end of the runway that made a go-around not possible and the ditch off the end of the runway.NTSB IAD98FA070Accident · 1 fatalField investigationFinal reportCessna 172N · Ocean City, MDThe pilot's failure to maintain control of the aircraft due to spatial disorientation. Contributing factors wer fog, dark night conditions, lack of recent experience, inadequate preflight planning, and flight into known adverse weather.NTSB SEA98FA088Accident · 3 fatalField investigationFinal reportCessna 172N · Prindle, WAThe pilot-in-command's failure to maintain control of the aircraft during attempted flight into instrument meteorological conditions. Factors contributing to the accident were clouds, dark night conditions, spatial disorientation, and drug impairment.NTSB CHI98LA147Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Hannibal, MOa loss of engine power due to undetermined reasons. A factor was the rough field in which the forced landing was made.NTSB MIA98LA153Accident · No injuriesLimited investigationFinal reportCessna 172N · West Palm Beach, FLthe dual student's failure to use carburetor heat while circling at a reduced power setting, and the flight instructor's failure to properly supervise the student.NTSB LAX98FA152Accident · 4 fatalField investigationFinal reportCessna 172N · Avalon, CAThe pilot's failure to maintain adequate altitude/clearance in a Blind/Box Canyon. A related factor was the mountainous/hilly terrain.NTSB SEA98LA070Accident · No injuriesLimited investigationFinal reportCessna 172N · Enumclaw, WAThe pilot's continued VFR flight into IMC conditions and his failure to maintain clearance from terrain. Clouds and mountainous terrain were a factor.NTSB FTW98LA198Accident · No injuriesLimited investigationFinal reportCessna 172N · Parker, COa fractured #1 exhaust valve rocker arm stud, which subsequently resulted in loss of engine power and a forced landing. The lack of suitable terrain in the forced landing area was a related factor.NTSB IAD98LA045Accident · No injuriesLimited investigationFinal reportCessna 172N · Stevensville, MDthe pilot's improper flare, improper recover from a bounced landing, and failure to maintain directional control.NTSB LAX98LA201Accident · No injuriesLimited investigationFinal reportCessna 172N · Santa Barbara, CAThe pilot's misjudging the landing flare and subsequent hard landing.NTSB ATL98FA060Accident · 5 fatalField investigationFinal reportCessna 172N · Marietta, GAThe failure of both pilots to see and avoid conflicting traffic, and the failure of the 172 pilot to operate the transponder as required by current regulations. Factors were the controller's failure to observe the traffic conflict, the lack of radar conflict…NTSB MIA98LA093Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Titusville, FLloss of engine power for undetermined reason(s), which resulted in a forced landing. Factors relating to the accident were: the lack of suitable terrain and obstructions in the emergency landing area.NTSB IAD98LA030Accident · No injuriesLimited investigationFinal reportCessna 172 · Rutland, VTthe pilot's improper in-flight planning/decision, which resulted in fuel exhaustion, loss of engine power, and a forced landing. Related factors were: unfavorable (headwind) conditions, and brush/small trees in the forced landing area.NTSB MIA98LA063Accident · No injuriesLimited investigationFinal reportCessna 172N · Valdosta, GAThe failure of the student to recover (pull-up) from the intentional maneuver resulting in the in-flight collision with terrain. Contributing to the accident was the ostentatious display by the student.NTSB FTW98LA069Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Mckinney, TXThe pilot's inadequate in-flight/planning decision which resulted in continued flight until fuel exhaustion. Related factors were incorrect fuel gauge readings and trees.NTSB LAX98FA052Accident · 2 fatalField investigationFinal reportCessna 172N · Lytle Creek, CAthe non-instrument rated pilot's inadvertent VFR flight into instrument meteorological conditions (IMC), and subsequent loss of aircraft control, due to spatial disorientation. Factors relating to the accident were: the adverse weather conditions (low ceiling…NTSB LAX98LA055Accident · No injuriesLimited investigationFinal reportCessna 172N · San Jose, CAthe student pilot's failure to maintain an appropriate airspeed and proper rate of descent, and his misjudged landing flare, which led to an uncontrolled porpoise and eventual collapse of the landing gear.NTSB LAX98FA043Accident · 1 fatalField investigationFinal reportCessna 172N · La Jolla, CAthe pilot's act of suicide by intentionally diving his aircraft into the ocean.NTSB FTW98LA061Accident · No injuriesLimited investigationFinal reportCessna 172N · Watkins, COloss of engine power for undertermined reason(s).NTSB LAX98LA028Accident · No injuriesLimited investigationFinal reportCessna 172N · Payson, AZThe pilot's selection of a downwind direction to land and his failure to compensate for the quartering tailwind condition.NTSB CHI98LA014Accident · 2 fatalLimited investigationFinal reportCessna 172N · Terre Haute, INThe pilot's failure to maintain adequate airspeed during a go-around attempt which resulted in an inadvertent stall.NTSB CHI98LA005Accident · No injuriesLimited investigationFinal reportCessna 172N · Sandwich, ILthe pilot's inability to maintain flying airspeed resulting in an inadvertent stall/mush. A factor contributing to this accident was the wind gust.NTSB NYC97LA189Accident · No injuriesLimited investigationFinal reportCessna 172 · Kutztown, PAthe student pilot's failure to maintain directional control of the aircraft, which resulted in an inadvertent ground swerve. Factors relating to the accident were: the student's pilot's selection of the wrong runway, the resultant tailwind, and the encounter…NTSB ATL97LA146Accident · No injuriesLimited investigationFinal reportCessna 172N · Fuquay-Varina, NCThe pilot's misjudged flare, improper level-off, and improper recovery from a bounced landing.NTSB ATL97LA140Accident · No injuriesLimited investigationFinal reportCessna 172N · Greenville, SCthe pilot's improper use of the elevator control and delayed liftoff during takeoff, which resulted in an inadvertent porpoise, collision with the runway, and collapse of the nose gear as he aborted the takeoff.NTSB LAX97LA302Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Kenwood, CAthe pilot's improper planning/decision, which resulted in fuel exhaustion and a forced landing, due to an inadequate supply of fuel.NTSB LAX97LA295Accident · No injuriesLimited investigationFinal reportCessna 172N · Prescott, AZThe pilot's inadequate recovery from a bounced landing.NTSB FTW97LA281Accident · No injuriesLimited investigationFinal reportCessna 172N · Fort Worth, TXfailure of the pilot in the Cessna 172 to maintain clearance from the Cessna 152 aircraft.NTSB CHI97LA214Accident · No injuriesLimited investigationFinal reportCessna 172 · Ottumwa, IAthe improper flare performed by the student and the inadequate recovery from the bounced landing. A factor related to the accident was the student lack of experience.NTSB ATL97LA105Accident · No injuriesLimited investigationFinal reportCessna 172N · Lakeland, FLthe student pilot's inadequate compensation for wind conditions and failure to maintain proper runway alignment during the landing, which resulted in a collision with a runway marker. The rear-quartering tailwind (crosswind) and gusts were related factors.NTSB LAX97FA286Accident · 1 fatalField investigationFinal reportCessna 172N · Cuyama, CAundetermined.NTSB FTW97FA221Accident · 2 fatalField investigationFinal reportCessna 172N · Greenbrier, ARThe pilot's failure to maintain aircraft control during a low altitude maneuver. Factors were the pilot's lack of total experience in the type of operation and inadequate training by the company management.NTSB MIA97FA176Accident · 3 fatalField investigationFinal reportCessna 172N · Comerio, PRthe pilot's improper in-flight planning/decision, which resulted in his failure to maintain sufficient altitude/clearance from obstructions on rising terrain.NTSB CHI97LA135Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Angola, INthe pilot's improper recovery from a bounced landing. Factors associated with the accident were the tailwind, the pilot's selection of runway, and the misjudged landing flare.NTSB CHI97LA141Accident · No injuriesLimited investigationFinal reportCessna 172N · Madison, WIthe pilot's inadequate compensation for wind conditions which resulted in a loss of directional control of the airplane. Factors associated with the accident were the gusty, crosswind conditions and the VASI lights.NTSB LAX97LA199Accident · No injuriesLimited investigationFinal reportCessna 172N · El Monte, CAthe student pilot's misunderstanding of the controller's clearance during an aborted touch-and-go landing.NTSB FTW97LA180Accident · No injuriesLimited investigationFinal reportCessna 172N · Las Cruces, NMThe improper installation of the throttle arm castellated nut, which resulted in a partial loss of power. A factor was the lack of suitable terrain for the forced landing.NTSB SEA97LA095Accident · No injuriesLimited investigationFinal reportCessna 172N · Pullman, WAThe pilot's failure to maintain clearance from a fuel truck parked near his taxi route. Factors include a dark night and a vehicle parked near the pilot's route of taxi.NTSB LAX97LA166Accident · No injuriesLimited investigationFinal reportCessna 172N · Chandler, AZthe pilot's encounter with crosswind gusts beyond the performance capability of the aircraft. A lack of crosswind limit information published in the Cessna 172N Pilot's Operating Handbook for landing and taxiing operations is a factor in the accident.NTSB NYC97LA077Accident · No injuriesLimited investigationFinal reportCessna 172N · Lincoln Park, NJthe student pilot's improper recovery from a bounced landing which resulted in a hard landing, collapsed nose gear, loss of directional control, and subsequent nose over.NTSB MIA97LA129Accident · No injuriesLimited investigationFinal reportCessna 172N · Lawrenceville, GAThe student pilot's failure to maintain directional control during a crosswind landing. The winds were a factor.NTSB LAX97LA152Accident · No injuriesLimited investigationFinal reportCessna 172N · Prescott, AZthe student pilot's inadequate compensation for the crosswind condition, and his failure to maintain proper runway alignment.NTSB IAD97LA063Accident · No injuriesLimited investigationFinal reportCessna 172N · Annapolis, MDThe pilot's failure to raise the flaps during the go-around. Factors involved were the high wind conditions and the pilot's failure to remove the carburetor heat.NTSB LAX97LA141Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Avalon, CAThe pilot's misjudging the airplane's altitude and distance to the runway and an excessive descent rate, which led to an undershoot, and the pilot's failure to maintain an adequate airspeed during the approach. Contributing factors were the pilot's delay in…NTSB MIA97LA105Accident · No injuriesLimited investigationFinal reportCessna 172N · St Matthews, SCthe pilot's improper decision to take off downwind with gusty wind conditions.NTSB SEA97LA080Accident · No injuriesLimited investigationFinal reportCessna 172 · Auburn, WAthe pilots' inadequate evaluation of the strong winds, when they attempted to turn to taxi with a very strong tailwind. Factors relating to the accident included the high and unfavorable winds.NTSB NYC97LA065Accident · No injuriesLimited investigationFinal reportCessna 172 · Middletown, OHthe pilot's improper decision to taxi on a motor vehicle access road at night, and his inadequate visual look out which resulted in the collision with an aluminum lamp post. A factor in this accident was the night condition.NTSB IAD97LA055Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Harrison, OHthe student pilot's failure to maintain directional control, and his improper operation of the throttle for regain control, which resulted in the airplane veering off the runway and colliding with a tree.
Back to Cessna 172N