Cessna 172P

NTSB investigations · 844

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 ('2072436')
  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.

NTSB MIA03FA043Accident · 4 fatalField investigationFinal reportCessna 172P · Edgewater, FLThe pilot's inflight loss of control and the pilot's failure to recover from the resultant dive for unknown reasons which resulted in flight beyond the design stress limits of the airplane and subsequent in flight airframe breakup.Jan 18, 2003 · N65906 · DestroyedNTSB SEA03FA013Accident · 2 fatalField investigationFinal reportCessna 172P · Malaga, WAThe pilot's attempted VFR flight into IMC resulting in the aircraft colliding with trees and up sloping terrain. Contributing factors were clouds, trees, and uphill terrain. The pilot’s performance and judgment were likely impaired by the effects of…Nov 26, 2002 · N65564 · DestroyedNTSB DEN03LA003Accident · No injuriesLimited investigationFinal reportCessna 172P · Broomfield, COthe pilot misjudging the clearance between the airplane and a fixed object during taxi. Contributing factors were the pilot's attention being diverted and sunglare.Oct 6, 2002 · N65312 · Substantial damageNTSB CHI02LA280Accident · No injuriesLimited investigationFinal reportCessna 172P · Sturtevant, WIThe proper touchdown point not attained and the approach speed not obtained/maintained by the pilot.Sep 16, 2002 · N54091 · Substantial damageNTSB ATL02LA168Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Mocksville, NCThe pilot's failure to maintain airspeed during the takeoff and initial climb which resulted in an inadvertent stall and the subsequent collision with trees.Sep 10, 2002 · N62602 · Substantial damageNTSB CHI02LA255Accident · No injuriesLimited investigationFinal reportCessna 172P · Buffalo City, WIThe malfunction of the seat positioning system for undetermined reasons, which resulted in the loss of directional control. A factor to the accident was the descending embankment.Aug 19, 2002 · N381J · Substantial damageNTSB LAX02LA237Accident · No injuriesLimited investigationFinal reportCessna 172P · Creston, CAthe pilot's inadequate in-flight planning/decision, which resulted in fuel exhaustion and loss of engine power. A factor in the accident was the dark night conditions.Jul 26, 2002 · N5268K · Substantial damageNTSB LAX02LA241Accident · No injuriesLimited investigationFinal reportCessna 172P · Mesa, AZthe pilot of the other airplane'ss use of an excessive taxi speed and too close of a spacing interval to the Cessna 152, which resulted in an on-ground collision when the Cessna 152 abruptly stopped.Jul 25, 2002 · N97056 · 2 aircraft · Minor damageNTSB ATL02LA140Accident · No injuriesLimited investigationFinal reportCessna 172P · Merritt Island, FLThe pilot's improper recovery after a bounced landing and improper landing flare which resulted in the airplane colliding with the runway.Jul 12, 2002 · N54119 · Substantial damageNTSB CHI02LA102Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Council Bluffs, IAThe student pilot's failure to maintain control of the airplane and the subsequent inadvertent stall. A factor associated with the accident was the student's lack of total experience.Apr 9, 2002 · N53066 · Substantial damageNTSB FTW02LA147Accident · No injuriesLimited investigationFinal reportCessna 172P · McKinney, TXthe student pilot's failure to properly recover from a bounced landing which resulted in the airplane porpoising. A contributing factor was the student pilot's improper landing flare which resulted in a bounced landing.Apr 8, 2002 · N99341 · Substantial damageNTSB ATL02LA073Accident · No injuriesLimited investigationFinal reportCessna 172P · Pensacola, FLThe pilot's inadequate compensation for a crosswind and his failure to maintain directional control during the landing roll. Contributing to the accident was the pilot's decision to land with a tailwind.Apr 4, 2002 · N64079 · Substantial damageNTSB IAD02LA038Accident · No injuriesLimited investigationFinal reportCessna 172P · Ocean City, NJThe pilot's inadequate compensation for wind and his failure to maintain directional control.Mar 24, 2002 · N9847L · Substantial damageNTSB IAD02FA037Accident · 4 fatalField investigationFinal reportCessna 172P · Ocean City, MDThe pilot's spatial disorientation, which resulted in his subsequent loss of control of the airplane. A factor was the dark night, over water visual conditions.Mar 16, 2002 · N96811 · DestroyedNTSB NYC02LA070Accident · No injuriesLimited investigationFinal reportCessna 172P · Coatesville, PAThe student pilot's loss of aircraft control which resulted in a hard landing, and the CFI's delayed remedial action. Factors related to the accident were the fatigue cracks which initiated at the attachment hole on the landing gear strut, and the crosswind…Mar 2, 2002 · N65021 · Substantial damageNTSB CHI02LA078Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Dowagiac, MIThe pilot's inadequate compensation for the wind conditions that resulted in directional control not being maintained during the landing roll. Factors to the accident were the pilot's inadequate in-flight decision to attempt the landing with a gusting 20 knot…Feb 18, 2002 · N66986 · Substantial damageNTSB MIA02LA051Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Levittown, PRthe failure of maintenance personnel to comply with aircraft manufacturer's inspection procedures, resulting in corrosion and separation of the aileron control cable in flight and the subsequent forced landing in a swamp.Jan 26, 2002 · N99295 · Substantial damageNTSB MIA02LA009Accident · No injuriesLimited investigationFinal reportCessna 172P · Knoxville, TNThe pilot's inattentive preflight inspection, non-compliance with the prestart checklist, decision to leave the cockpit unattended with engine running, and his inadvertent deactivation of the parking brake as he exited to remove a wheel chock, resulting in…Oct 15, 2001 · N52685 · Substantial damageNTSB IAD01LA104Accident · No injuriesLimited investigationFinal reportCessna 172P · Augusta, METhe pilot's failure to maintain the proper distance from a sign post during taxi.Sep 2, 2001 · N65057 · Substantial damageNTSB NYC01LA188Accident · No injuriesLimited investigationFinal reportCessna 172P · Odenton, MDA loss of engine power for undetermined reasons.Jul 25, 2001 · N52266 · Substantial damageNTSB NYC01LA185Accident · No injuriesLimited investigationFinal reportCessna 172 · Dayton, OHThe pilot excessive flare, which resulted in a hard landing.Jul 23, 2001 · N52012 · Substantial damageNTSB ATL01LA076Accident · No injuriesLimited investigationFinal reportCessna 172P · Cedar Key, FLThe pilot's improper in-flight decision to abort the landing resulted in the collision with water. A factor was the variable wind condition.Jul 7, 2001 · N52452 · Substantial damageNTSB NYC01LA163Accident · No injuriesLimited investigationFinal reportCessna 172P · Stevensville, MDThe pilot's improper flare and his improper recovery from a bounced landing.Jul 2, 2001 · N54576 · Substantial damageNTSB ANC01LA064Accident · No injuriesLimited investigationFinal reportCessna 172P · Anchorage, AKThe pilot's selection of an unsuitable taxi area during taxi. A factor associated with the accident was a tree.May 21, 2001 · N98426 · Substantial damageNTSB SEA01LA092Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Grants Pass, ORThe pilot's failure or inability to maintain proper runway alignment during landing. Factors included gusty crosswind conditions and the pilot's lack of experience in crosswind landings.May 12, 2001 · N62961 · Substantial damageNTSB FTW01LA123Accident · No injuriesLimited investigationFinal reportCessna 172P · Pleasanton, TXthe student pilot's failure to maintain directional control during the landing flare/touchdown. Contributory factors were the gusty wind and the student pilot's lack of total flight experience.Apr 29, 2001 · N64776 · Substantial damageNTSB LAX01LA150Accident · No injuriesLimited investigationFinal reportCessna 172P · Torrance, CAThe failure of the pilot-in-command to execute a proper landing flare, which resulted in an improper touchdown attitude and a subsequent loss of directional control. A factor in the accident was the difference between landing characteristics of the Katana and…Apr 19, 2001 · N97984 · Substantial damageNTSB IAD01LA040Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Williamsport, PAThe pilot's premature raising of flaps resulting in his failure to establish a climb and his failure to maintain directional control.Apr 5, 2001 · N65630 · Substantial damageNTSB DEN01LA081Accident · No injuriesLimited investigationFinal reportCessna 172P · Rangely, COthe pilot's improper use of aileron and his failure to maintain directional control during landing. A contributing factor was the direct gusty crosswind.Mar 31, 2001 · N54663 · Substantial damageNTSB NYC01LA078Accident · No injuriesLimited investigationFinal reportCessna 172P · Miamisburg, OHThe pilot's failure to attain the proper touchdown point. Factors included the nighttime conditions, and the pilot's improper decision to leave the runway lighting at high intensity.Feb 9, 2001 · N62332 · Substantial damageNTSB FTW01FA058Accident · 2 fatalField investigationFinal reportCessna 172P · Platter, OKthe failure of both pilots to maintain a visual lookout, which resulted in a mid-air collision over a lake. A contributing factor to the accident was the sun glare from the setting sun.Feb 6, 2001 · N96621 · 2 aircraft · Substantial damageNTSB CHI01LA072Accident · No injuriesLimited investigationFinal reportCessna 172P · Prairie Du Sac, WIthe improper trim setting and the pilot failed to maintain control of the airplane. A factor was the snowbank.Jan 21, 2001 · N53118 · Substantial damageNTSB IAD01LA024Accident · No injuriesLimited investigationFinal reportCessna 172P · Concord, NHThe flight instructor's improper decision to land downwind on the snow and ice covered runway with a tailwind, and his failure to perform a go-around. Factors in the accident were the tailwind and the snow and ice on the runway.Jan 7, 2001 · N54931 · Substantial damageNTSB DEN01LA024Accident · No injuriesLimited investigationFinal reportCessna 172P · Leadville, COthe student pilot's failure to maintain directional control during landing roll. A contributing factor was the snow bank next to the runway.Dec 14, 2000 · N127FR · Substantial damageNTSB MIA01WA033Accident · Serious injuriesForeign investigationCessna 172P · Port Au Prince, HaitiNov 24, 2000 · N84FR · Substantial damageNTSB MIA01LA024Accident · No injuriesLimited investigationFinal reportCessna 172P · Inverness, FLa loss of directional control on landing due to the pilot's failure to execute a proper flare and recovery from the resultant bounced landing, causing the airplane to depart the runway, enter the uneven grass infield, and sustain a nose over.Nov 4, 2000 · N54729 · Substantial damageNTSB SEA01LA012Accident · No injuriesLimited investigationFinal reportCessna 172P · Waldron Island, WAThe pilot's improper distance/speed during the approach, which lead to an overrun during the landing roll and subsequent collision with trees. A factor was the trees beyond the upwind end of the runway.Nov 2, 2000 · N65923 · Substantial damageNTSB MIA01LA013Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Knoxville, TNThe pilot's failure to maintain Vs during takeoff/initial climb, which resulted in an inadvertent stall/mush, an uncontrolled descent, and an impact with the ground. Factors in the accident were the pilot's improper preflightplanning/preparation and failure…Oct 22, 2000 · N53512 · Substantial damageNTSB LAX01LA021Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Half Moon Bay, CAA local windshear condition that exceeded the airplane's climb performance capability during landing approach and resulted in the runway overrun during an attempted go-around.Oct 22, 2000 · N5226K · Substantial damageNTSB CHI00LA309Accident · No injuriesLimited investigationFinal reportCessna 172P · Wheeling, ILThe student pilot's inadequate compensation for the crosswind that resulted in the failure to maintain directional control of the airplane. Factors associated with the accident were the crosswind, the ditch, the student's lack of experience, and the poor…Sep 26, 2000 · N98629 · Substantial damageNTSB SEA00LA179Accident · No injuriesLimited investigationFinal reportCessna 172P · Friday Harbor, WAThe Cessna 172 pilot's failure to maintain clearance with the Cessna 182. Factors included aircraft parked/standing on the taxiway and the refueling area, and a congested/confined taxiway.Sep 12, 2000 · N53201 · 2 aircraft · Substantial damageNTSB NYC00LA256Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Cross Keys, NJThe operator's inadequate 100-hour inspection of the airplane, and the pilot's continued operation with known deficiencies in equipment.Sep 8, 2000 · N9594L · Substantial damageNTSB SEA00LA177Accident · No injuriesLimited investigationFinal reportCessna 172P · Auburn, WADamage to aircraft under unknown circumstances.Sep 3, 2000 · N531PC · Substantial damageNTSB FTW00LA240Accident · No injuriesLimited investigationFinal reportCessna 172P · San Antonio, TXThe pilot's failure to maintain control during landing. A factor was the reported wind gust.Aug 21, 2000 · N98873 · Substantial damageNTSB IAD00LA068Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Princeton, NJthe student pilot's failure to maintain control of the airplane during the aborted landing.Jul 29, 2000 · N65827 · Substantial damageNTSB MIA00LA223Accident · No injuriesLimited investigationFinal reportCessna 172P · Jesup, GAThe failure of the student pilot to maintain directional control during takeoff resulting in an excursion off the runway and collision with adjacent foliage. A factor in the accident was the student's decision to takeoff downwind.Jul 18, 2000 · N51996 · Substantial damageNTSB DEN00LA121Accident · No injuriesLimited investigationFinal reportCessna 172P · Price, UTThe pilot's failure to maintain directional control of the aircraft during landing roll. Factors were strong and gusty winds.Jul 3, 2000 · N51208 · Substantial damageNTSB LAX00FA178Accident · 4 fatalField investigationFinal reportCessna 172P · Chester, CAThe pilot's encounter with a wind shear at low altitude, which resulted in a loss of control and a stall/spin. Factors in the accident were the high density altitude and the pilot's lack of experience and training in high density altitude operations. The…Apr 28, 2000 · N216PB · DestroyedNTSB SEA00LA067Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Seattle, WAThe pilot's failure to attain proper alignment with the landing runway, and her failure to maintain proper glide path for the landing runway, resulting in an encounter with vortex turbulence from a preceding heavy aircraft landing on a parallel runway and…Apr 11, 2000 · N38GF · Substantial damageNTSB DEN00LA070Accident · No injuriesLimited investigationFinal reportCessna 172P · Fort Collins, COOn ground loss of control resulting in collision with airport markings due to inadequate compensation for wind conditions during landing roll. Factors were inaccurate in flight planning by landing with a tail wind component and lack of total pilot experience.Apr 8, 2000 · N65312 · Substantial damage
Back to Cessna 172P