Cessna R172E
NTSB investigations · 63
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 ('2072413')
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 ('2072413')
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 CEN24LA270Incident · No injuriesClass 3 · LimitedFinal reportCessna R172E · Hillrose, COThe binding of the left flap due to improper maintenance.NTSB ERA24LA179Accident · No injuriesClass 3 · LimitedFinal reportCessna R172 · Rocky Mount, NCThe pilot and mechanic’s failure to identify and completely eliminate the water and debris contamination present in the airplane’s fuel system before embarking on the flight, which resulted in a total loss of engine power.NTSB WPR23LA365Accident · No injuriesClass 4 · LimitedFinal reportCessna R172E · Alamogordo, NMFailure of the pilot to maintain control of the airplane during the landing.NTSB CEN23LA027Accident · No injuriesClass 3 · LimitedFinal reportCessna R172E · Aguilar, COFailure of the engine cylinder assembly, which resulted in a loss of engine power during cruise flight and an impact with a fence during the forced landing.NTSB CEN19LA107Accident · Serious injuriesLimited investigationFinal reportCessna R172E · Loveland, COAn inflight loss of control on landing approach due to encountering a down-draft, and the pilot's failure to take timely action to abandon the approach and perform a go-around.NTSB CEN18LA335Accident · No injuriesLimited investigationFinal reportCessna R172E · Colorado Springs, COThe airplane’s failure to maintain a climb after takeoff, which resulted in a forced landing on unsuitable terrain; the reason for the airplane’s failure to climb could not be determined based on the available evidence.NTSB GAA15CA030Accident · No injuriesData collectionFinal reportCessna R172E · Fort Meade, MDThe flight instructor's decision to land the airplane without sufficient runway to stop, resulting in a runway excursion and substantial damage to the right wing of the airplane.NTSB WPR13CA381Accident · Minor injuriesData collectionFinal reportCessna 172E · Meeteetse, WYThe student pilot's inadequate preflight planning and failure to maintain clearance from rising terrain, which resulted in controlled flight into terrain. Contributing to the accident was the pilot's lack of situational awareness.NTSB CEN12LA171Accident · Minor injuriesLimited investigationFinal reportCessna R172E · Denver, COThe pilot's improper decision to taxi in wind conditions that exceeded the airplane’s capability.NTSB CEN10CA267Accident · No injuriesData collectionFinal reportCessna R172E · Alamogordo, NMAn unknown event that resulted in damage to the airplane's firewall.NTSB CEN09CA037Accident · Serious injuriesData collectionFinal reportCessna R172E · Palo Pinto, TXThe pilot's intentional low-level flight and failure to maintain a visual lookout.NTSB LAX07CA162Accident · No injuriesData collectionFinal reportCessna R172E · Dayton, NVThe pilot's misjudged flare, which resulted in a hard landing.NTSB DEN06CA077Accident · No injuriesData collectionFinal reportCessna R172E (T-41C) · Albuquerque, NMthe pilot's failure to maintain aircraft control. A contributing factor was the wind gust.NTSB NYC05CA132Accident · No injuriesData collectionFinal reportCessna R172E · Patuxent River, MDThe pilot's improper recovery from a bounced landing, resulting in a hard landing.NTSB DEN03TA103Accident · No injuriesFinal reportCessna R172E · Albuquerque, NMthe student pilot's inadvertent encounter with the jet blast and the subsequent inability to maintain aircraft control.NTSB IAD02LA077Accident · No injuriesLimited investigationFinal reportCessna 172 · Barre, VTThe pilot's failure to maintain airspeed during a go-around attempt, which resulted in an inadvertent stall and a subsequent impact with trees. A factor was the pilot's delayed initiation of the go-around.NTSB ATL02LA122Accident · No injuriesLimited investigationFinal reportCessna 172R · N Myrtle Beach, SCThe pilot's failure to maintain airspeed during a banner tow pickup resulting in an inadvertent stall and uncontrolled descent and collision with terrain.NTSB MIA02LA057Accident · Serious injuriesLimited investigationFinal reportCessna R172E · River Ranch, FLThe reported loss of engine power due to undetermined reasons. Contributing factors in the accident were an improper flap setting, excessive landing speed, and terrain consisting of berms.NTSB DEN01LA046Accident · No injuriesLimited investigationFinal reportCessna R172E · Colorado Spring, COthe student pilot's inadequate compensation for the crosswind during landing roll. A contributing factor was the cross wind weather condition.NTSB DEN01LA029Accident · No injuriesLimited investigationFinal reportCessna 172E · Salt Lake City, UTthe lack of suitable terrain for a forced landing. A factor was a total power loss due to a connecting rod failure.NTSB ATL99LA116Accident · Minor injuriesLimited investigationFinal reportCessna R172-E · Chiefland, FLPremature fuel exhaustion due to a cracked fuel line. Contributing to the severity of the accident was the electrical service drop line, which crossed the roadway.NTSB LAX98LA014Accident · No injuriesLimited investigationFinal reportCessna R172E · North Las Vegas, NVThe pilot of the Stinson AT-19, N88793, inadequate visual lookout and his failure to perform clearing S-turns while taxiing. A related factor was the inherent forward visual restriction of the aircraft's conventional landing gear design.NTSB MIA97LA230Accident · No injuriesLimited investigationFinal reportCessna R172E · Mary Esther, FLThe loss of engine power for undetermined reasons.NTSB CHI95LA177Accident · Minor injuriesLimited investigationFinal reportCessna R172E · Plato Center, ILthe pilot's excessive pull-up during a downwind banner pick-up resulting in a stall. A factor related to the accident was the tailwind.NTSB FTW95FA147Accident · 1 fatalField investigationFinal reportCessna R172E · Gladewater, TXThe pilot's failure to maintain an airspeed above stall speed, resulting in an inadvertent stall. A factor was the pilot's performance of an abrupt maneuver immediately after takeoff.NTSB DEN93LA018Accident · No injuriesLimited investigationFinal reportCessna 172E · Ramah, COA total loss of engine power due to mechanical failure of the number one connecting rod. A factor was: a forced landing onto unsuitable terrain.NTSB DEN92LA053Accident · No injuriesLimited investigationFinal reportCessna R172E · Colorado Spring, COThe pilot did not maintain clearance and the airplane collided with a fence post.NTSB CHI89LA185Accident · No injuriesLimited investigationFinal reportCessna C172R · Frankenmuth, MIThe pilot's failure to maintain control of the aircraft during takeoff as a result of a diversion of attention due to a possible engine problem.NTSB SEA89LA142Accident · No injuriesLimited investigationFinal reportCessna 172E · Yerington, NVThe pilot's failure to maintain adequate airspeed during a landing go-around in high density altitude conditions.NTSB ATL89LA170Accident · No injuriesLimited investigationFinal reportCessna R172E · Birmingham, ALImproper flare by the pilot, which resulted in a hard landing. The fact that the pilot was asked twice to expedite the landing created pressure on the pilot and was considered to be a factor.NTSB LAX89LA194Accident · Minor injuriesLimited investigationFinal reportCessna R172E · Young, AZThe pilots decision to land at the restricted airport which had a tree located 20 feet from the centerline of the runway and his failure to maintain proper alignment with the centerline once he made the decision to land there.NTSB ATL89LA037Accident · Minor injuriesLimited investigationFinal reportCessna R172E · Lawrenceville, GAImproper repair and/or modification of the carburetor airbox by unknown person(s), and the subsequent failure of maintenance personnel to detect the improper repair/modification during annual inspection(s), which led to a loss of power due to carburetor…NTSB MKC85LA019Accident · No injuriesLimited investigationFinal reportCessna R172E · Junction City, KSPilot was experiencing communications difficulties, diverted from destination to nearby uncontrolled arpt due to traffic considerations. Plt was unable to contact UNICOM and elected to circle for traffic and wind evaluation. Best runway for wind direction was…NTSB DEN84FA251Accident · 2 fatalField investigationFinal reportCessna R172E · Farmington, NMAfter being airborne 1 hour and 10 minutes the traffic surviellance flt was cancelled. The plt transmitted to the policeunits on the ground that he would 'buzz' them as he left the area. During this pass the acft struck a high voltage transmission line 88.9…NTSB LAX84LA347Accident · No injuriesLimited investigationFinal reportCessna R172E · Payson, AZThe purpose of the flight was to give the pvt plt a recurrency checkride as required by the civil air patrol. The commercial rated check plt is not a CFI. According to the check plt the pvt plt was attempting a touch and go landing. The pvt plt flared too…NTSB FTW83FPJ02Accident · Serious injuriesFinal reportCessna R172E · Little, OKThe acft had been landed twice to check for leaking fluid on the windshield. When the fuel pressure went to zero and theengine quit the leak was confirmed to be acft fuel. During a forced landing the acft struck a fence and the nose gear collapsed. The…NTSB ANC83FA059Accident · Minor injuriesField investigationFinal reportCessna T-41B (R-172E) · Healy, AKThe plt reported that while cruising at 4000 ft MSL, the eng power began to fluctuate, then this was followed by a banging noise, rough eng operation & a decline in power output. He had turned to land into the wind when the eng power increased & stabilized.…NTSB NYC82DA159Accident · No injuriesFinal reportCessna R172E · Latham, NYPilot reduced power to idle on final approach and when he tried to add power there was no response. No reason for failure was found.NTSB LAX80FJA11Accident · 2 fatalClosedCessna 172E · Lanai City, HINTSB FTW80DQD03Accident · Serious injuriesClosedCessna R172 · El Paso, TXNTSB SEA80FYM05Accident · Minor injuriesClosedCessna R172E · Grass Valley, IDNTSB IAD80DID02Accident · No injuriesClosedCessna T-41 · Richmond, VANTSB NYC80FHM02Accident · Serious injuriesClosedCessna 172 · E.Fishkill, NYNTSB FTW79FA092Accident · 7 fatalClosedCessna R172 · Ashdown, ARNTSB DEN79FTC14Accident · Minor injuriesClosedCessna 172E · Rawlins, WYNTSB MIA79FLG13Accident · Minor injuriesClosedCessna R172E · Clover, SCNTSB MKC78DCG27Accident · No injuriesClosedCessna R172E · Ludlow, MONTSB MKC78DCQ15Accident · Minor injuriesClosedCessna R172E · Wichita, KSNTSB FTW77DQD21Accident · No injuriesClosedCessna 172E · El Paso, TXNTSB MIA77FKQ10Accident · Minor injuriesClosedCessna R172E · Newton, MS
Back to Cessna R172E