NTSB investigations: Cessna 172N, VA

40 cases on aircraft the registry lists as Cessna 172N. Aircraft are matched to the registry by N-number and event date, checked against the reported serial number, make and model, so older matches can be wrong.

Cases per year

19792026
NTSB investigations: Cessna 172N, VA per year, 1979–2026: 40 cases
19793
19803
19811
19821
19841
19851
19872
19881
19891
19903
19931
19942
19951
19991
20001
20011
20023
20071
20081
20093
20102
20121
20141
20161
20171
20231
20241

Latest cases

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_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c.\"mKey\" AND a.position = 1
  WHERE c.\"eventStateOrRegion\" = 'VA' AND c.\"eventCountry\" = 'USA'
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.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.

NTSB ERA24LA361Accident · No injuriesClass 3 · LimitedFinal reportCessna 172 · Lynchburg, VAA total loss of engine power for undetermined reasons.Aug 29, 2024 · N734SY · Substantial damageNTSB ERA24LA065Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Newport News, VAAn inflight collision with a bird during initial climb.Dec 11, 2023 · N733QJ · Substantial damageNTSB GAA17CA540Accident · No injuriesData collectionFinal reportCessna 172 · Lynchburg, VAThe pilot's unstabilized approach, which resulted in an aborted go-around, an aerodynamic stall, and a hard landing.Sep 16, 2017 · N5396D · Substantial damageNTSB GAA16CA460Accident · No injuriesData collectionFinal reportCessna 172 · Winchester, VAThe student pilot's incorrect pitch control during the landing flare, which resulted in a porpoise, a loss of directional control, and a runway excursion.Aug 30, 2016 · N2462E · Substantial damageNTSB ERA14CA160Accident · No injuriesData collectionFinal reportCessna 172N · Charlottesville, VAThe pilot's inadequate landing flare, which resulted in a bounced landing and substantial damage to the firewall.Mar 8, 2014 · N5423J · Substantial damageNTSB ERA12LA191Accident · No injuriesLimited investigationFinal reportCessna 172N · Flat Rock, VAThe partial loss of engine power due to the failure of the exhaust valve spring seat for reasons that could not be determined.Feb 17, 2012 · N4737D · Substantial damageNTSB ERA10CA392Accident · No injuriesData collectionFinal reportCessna 172N · Elk Creek, VAThe student pilot’s continued visual flight into instrument meteorological conditions, which resulted in an off-airport landing.Jul 31, 2010 · N172FL · Substantial damageNTSB ERA10LA377Accident · No injuriesLimited investigationFinal reportCessna 172N · Waynesboro, VAThe pilot's failure to follow the short-field takeoff procedures published in the Pilot's Operating Handbook.Jul 24, 2010 · N3480E · Substantial damageNTSB ERA10LA055Accident · No injuriesLimited investigationFinal reportCessna 172 · Luray, VAThe pilot's premature rotation and liftoff and her subsequent failure to recognize and correct for the influence of ground effect on the airplane's takeoff performance.Nov 8, 2009 · N738CD · Substantial damageNTSB ERA09LA517Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Hillsville, VAThe total loss of engine power for an undetermined reason.Sep 13, 2009 · N734TV · Substantial damageNTSB ERA09CA430Accident · No injuriesData collectionFinal reportCessna 172N · Manassas, VAThe student pilot’s failure to maintain directional control during takeoff.Jul 30, 2009 · N733BS · Substantial damageNTSB NYC08CA127Accident · No injuriesData collectionFinal reportCessna 172N · Charlottesville, VAThe pilot's improper engine starting procedures.Mar 8, 2008 · N733LE · Substantial damageNTSB ATL07CA132Accident · No injuriesData collectionFinal reportCessna C172N · Manassas, VAThe student pilot's failure to correct for a pilot-induced oscillation/porpoise, during flare/touchdown, which resulted in a hard landing.Aug 25, 2007 · N733BS · Substantial damageNTSB IAD02LA096Accident · No injuriesLimited investigationFinal reportCessna 172N · Bumpass, VAThe pilot's failure to maintain directional control during the landing. A factor was the narrow runway width.Sep 21, 2002 · N737TG · Substantial damageNTSB IAD02FA088Accident · 1 fatalField investigationFinal reportCessna 172N · Stanardsville, VAThe pilot's failure to maintain sufficient altitude/clearance while descending over mountainous terrain. A factor was the night lighting conditions.Aug 19, 2002 · N738JR · DestroyedNTSB NYC02LA121Accident · No injuriesLimited investigationFinal reportCessna 172N · Lynchburg, VAThe pilot's failure to maintain control of the airplane, a factor was the tailwind.Jun 22, 2002 · N5408E · Substantial damageNTSB NYC02LA011Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Ashland, VAThe line technician's inadvertent contact with the propeller during a hand-propped engine start.Oct 18, 2001 · N4834G · No damageNTSB IAD00LA043Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Tappahannock, VAthe pilots's inability to maintain aircraft control after a loss of consciosness.May 16, 2000 · N1655E · Substantial damageNTSB NYC99FA214Accident · 4 fatalField investigationFinal reportCessna 172N · Dyke, VAThe pilot's inadvertent flight into instrument meteorological conditions, which resulted in his inability to see the rapidly rising terrain. A factor was the pilot's inaccurate evaluation of the weather.Aug 25, 1999 · N733DH · DestroyedNTSB BFO95LA054Accident · No injuriesLimited investigationFinal reportCessna 172N · Head Waters, VAthe pilot's poor planning/decision making in the attempted departure. Contributing factors are the wet, recently mowed grass airstrip, and the embankment/downhill grade encountered during the aborted takeoff.Jun 1, 1995 · N3065E · Substantial damageNTSB BFO95FA001Accident · 1 fatalField investigationFinal reportCessna 172N · Fancy Gap, VAThe pilot's inadequate inflight planning and his failure to maintain adequate terrain clearance. Other related factors are: fog, rain, VFR flight into IMC, inexperience and mountainous terrain.Oct 9, 1994 · N734NB · DestroyedNTSB NYC94LA092Accident · No injuriesLimited investigationFinal reportCessna 172N · Fredericksburg, VAThe pilot's premature lift-off, resulting in an inadvertent stall/mush back onto the runway, and the pilot's failure to maintain directional control during the aborted takeoff, which resulted in the airplane veering off the runway and colliding with a dirt…May 24, 1994 · N737SE · Substantial damageNTSB BFO93LA170Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Tangier Island, VAFailure of the pilot to maintain control of the aircraft during a go-around. A factor related to the accident was: the crosswind condition.Sep 11, 1993 · N5347J · Substantial damageNTSB BFO91LA009Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Elkton, VAThe pilot's failure to use carburetor heat which resulted in a reduction in engine power. A factor was the rough terrain.Nov 3, 1990 · N902ZZ · Substantial damageNTSB BFO90LA068Accident · No injuriesLimited investigationFinal reportCessna 172N · Tangier Island, VAThe pilot's improper recovery from a bounced landing and premature raising of the flaps.Aug 2, 1990 · N1516E · Substantial damageNTSB BFO90FA032Accident · 2 fatalField investigationFinal reportCessna 172N · Bedford, VAThe pilot's decision to fly into known adverse weather conditions and his failure to maintain clearance above the terrain. Contributing to the accident was the pilot's self induced pressure, low ceilings, mountainous terrain and rain.Mar 17, 1990 · N76026 · DestroyedNTSB BFO89LA014Accident · No injuriesLimited investigationFinal reportCessna 172N · Ashland, VAThe pilot's failure to maintain directional control of the airplane during landing and the failure to achieve sufficient airspeed during the go-around to initiate a climb.Jan 15, 1989 · N901ZZ · Substantial damageNTSB BFO89LA001Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Sandston, VAThe plt said he was on final apch about 600 to 800 ft AGL when power loss occurred. He forced landed on an open field about 1/2 mi short of the rwy. The eng exam revealed that two teeth of the idler gear had separated. This resulted in a loss of continuity…Oct 6, 1988 · N739PE · Substantial damageNTSB BFO88FA002Accident · 1 fatalField investigationFinal reportCessna 172N · Lowmoor, VAThe acft was involved in powerline patrol over mountainous terrain at low altitude. The plt made a climbing right turn to avoid a ridge and went into a valley where he was boxed in by two ridges. He unsuccessfully tried to outclimb one of the ridges before he…Oct 9, 1987 · N3075E · DestroyedNTSB BFO87LA025Accident · No injuriesLimited investigationFinal reportCessna 172N · Charlottesville, VAAfter climbing to cruise altitude and noting that the winds were stronger than expected, the pilot elected to divert to Charlottesville. Upon entering the traffic pattern, the pilot noted that he would be landing with a crosswind from the right. The aircraft…Mar 2, 1987 · N734ZD · Substantial damageNTSB BFO85LA027Accident · No injuriesLimited investigationFinal reportCessna 172N · Charlottesville, VAThe plt reported that during an apch to land, moderate turbulence was encountered & that the winds were variable. Since the acft was low & fast, he adjusted the power & extended 10 then 20 deg of flaps. Crossing the threshold, he retarded the throttle to idle…Mar 10, 1985 · N1564E · Substantial damageNTSB ATL84LA166Accident · No injuriesLimited investigationFinal reportCessna 172N · Buckingham, VAThe acft bounced and drifted during the landing flare. The plt added power to go-around and was unable to clear the trees near the rwy.May 9, 1984 · N73787 · Substantial damageNTSB ATL82DA091Accident · No injuriesFinal reportCessna 172 · Chantilly, VAThe pilot flew into an area of high forecast winds and altered his destination as a precaution. However, he failed to ask for or take precautionary measures after landing and the aircraft was blown over while taxiing.Apr 4, 1982 · N5510D · Substantial damageNTSB ATL81DID12Accident · Serious injuriesClosedCessna 172N · Northampton Co, VAMar 10, 1981 · N6382E · Substantial damageNTSB ATL80FIA16Accident · No injuriesClosedCessna 172 · Manassas, VASep 22, 1980 · N6284D · Substantial damageNTSB IAD80FID09Accident · No injuriesClosedCessna 172 · Waynesboro, VAMar 11, 1980 · N2286E · Substantial damageNTSB IAD80DIA05Accident · No injuriesClosedCessna 172 · Leesburg, VAFeb 27, 1980 · N734QX · Substantial damageNTSB IAD80FA010Accident · Serious injuriesClosedCessna 172N · Vienna, VANov 15, 1979 · N739TJ · Substantial damageNTSB IAD79DID21Accident · No injuriesClosedCessna 172N · Lexington, VAJul 8, 1979 · N734DD · Substantial damageNTSB IAD79FID13Accident · No injuriesClosedCessna 172 · Ashland, VAApr 8, 1979 · N75964 · Substantial damage