# NTSB investigations: Cessna 172N: In flight collision with object NTSB aviation accident and incident investigations since 1962: the probable cause, findings, aircraft, crew, weather and docket of each, linked to the FAA registry and the FAA’s own reports. Page 1 of 2 · 92 cases ## Latest cases - [NTSB DEN07CA043](https://openairdocs.org/ntsb/DEN07CA043.md): Cessna 172N · Cottonwood Fall, KS · Accident · No injuries · Data collection · Final report · Dec 24, 2006 · N4811G · Substantial damage > the pilot's failure to maintain clearance from the fence. Contributing to the accident was the pilot's inability to properly identify the runway environment, and the improper in-flight decision to initiate a go-around. - [NTSB MIA06CA134](https://openairdocs.org/ntsb/MIA06CA134.md): Cessna 172N · Pensacola, FL · Accident · Minor injuries · Data collection · Final report · Sep 3, 2006 · N1210F · Substantial damage > The student pilot's failure to raise the wing flaps for a go-around resulting in the airplane not climbing and an in-flight collision with trees. - [NTSB DFW06FA187](https://openairdocs.org/ntsb/DFW06FA187.md): Cessna 172N · Petal, MS · Accident · 2 fatal · Field investigation · Final report · Jul 19, 2006 · N738KE · Destroyed > The pilot's improper use of flaps, which resulted in an impact with trees during takeoff-initial climb. - [NTSB NYC06FA154](https://openairdocs.org/ntsb/NYC06FA154.md): Cessna 172N · Newry, ME · Accident · 4 fatal · Field investigation · Final report · Jun 22, 2006 · N572BA · Destroyed > The flight instructor's failure to maintain altitude/clearance while maneuvering, which resulted in an impact with trees. - [NTSB LAX06CA125](https://openairdocs.org/ntsb/LAX06CA125.md): Cessna 172N · Compton, CA · Accident · Minor injuries · Data collection · Final report · Mar 7, 2006 · N739NU · Substantial damage > control interference by the student pilot during a go-around that resulted in an in-flight collision with power lines. - [NTSB MIA06CA009](https://openairdocs.org/ntsb/MIA06CA009.md): Cessna 172N · Punta Gorda, FL · Accident · No injuries · Data collection · Final report · Oct 2, 2005 · N952AC · Substantial damage > The in-flight collision with a bird resulting in substantial damage to the airplane. - [NTSB DFW05CA091](https://openairdocs.org/ntsb/DFW05CA091.md): Cessna 172N · Rio Grande City, TX · Accident · No injuries · Data collection · Final report · Mar 18, 2005 · N6372D · Substantial damage > The pilot's failure to maintain clearance from objects, and his improper compensation for wind conditions while landing. A contributing factor was the gusty wind condition. - [NTSB ATL04FA099](https://openairdocs.org/ntsb/ATL04FA099.md): Cessna 172N · Moselle, MS · Accident · 3 fatal · Field investigation · Final report · Apr 24, 2004 · N75812 · Substantial damage > The pilot's failure to maintain clearance and his inadequate visual look-out while maneuvering resulting in an in-flight collision with a radio tower. - [NTSB ATL04CA089](https://openairdocs.org/ntsb/ATL04CA089.md): Cessna 172N · Statesboro, GA · Accident · No injuries · Data collection · Final report · Apr 3, 2004 · N4874G · Substantial damage > The pilot's failure to establish a positive climb and his failure to maintain clearance during a go-around, which resulted in an in-flight collision with trees. A factor was the gusting winds. - [NTSB SEA04LA048](https://openairdocs.org/ntsb/SEA04LA048.md): Cessna 172N · Gig Harbor, WA · Accident · No injuries · Limited investigation · Final report · Mar 3, 2004 · N75844 · Substantial damage > The pilot's failure to follow the published IFR procedure resulting in failure to maintain clearance from objects during an instrument approach. Trees and an inoperative glide slope receiver were factors. - [NTSB NYC04CA076](https://openairdocs.org/ntsb/NYC04CA076.md): Cessna 172N · Youngstown, OH · Accident · No injuries · Data collection · Final report · Feb 23, 2004 · N738EK · Substantial damage > An inadvertent collision with a deer while landing. - [NTSB NYC04CA032](https://openairdocs.org/ntsb/NYC04CA032.md): Cessna 172N · Philippi, WV · Accident · Minor injuries · Data collection · Final report · Nov 9, 2003 · N738UL · Substantial damage > The pilot's improper decision to depart from a runway of insufficient length. Factors in the accident were the turf runway and tailwind condition. - [NTSB IAD03FA005](https://openairdocs.org/ntsb/IAD03FA005.md): Cessna 172N · Mount Sterling, KY · Accident · 2 fatal · Field investigation · Final report · Oct 15, 2002 · N6413J · Destroyed > The failure of the pilot to follow the published instrument approach procedure, which resulted in an early descent into an antenna tower. A factor was the low ceiling. - [NTSB IAD02FA088](https://openairdocs.org/ntsb/IAD02FA088.md): Cessna 172N · Stanardsville, VA · Accident · 1 fatal · Field investigation · Final report · Aug 19, 2002 · N738JR · Destroyed > The pilot's failure to maintain sufficient altitude/clearance while descending over mountainous terrain. A factor was the night lighting conditions. - [NTSB SEA02FA125](https://openairdocs.org/ntsb/SEA02FA125.md): Cessna 172N · Otis, OR · Accident · 2 fatal · Field investigation · Final report · Jul 6, 2002 · N738QT · Destroyed > The pilot's failure to maintain adequate clearance with power lines while conducting low altitude flight resulting in a loss of control and subsequent collision with terrain. Contributing factors were the pilot's low altitude flight and the power lines. - [NTSB FTW02LA063](https://openairdocs.org/ntsb/FTW02LA063.md): Cessna 172N · Durango, CO · Accident · Serious injuries · Limited investigation · Final report · Jan 9, 2002 · N3535E · Substantial damage > the pilot's failure to maintain clearance with the trees and mountainous terrain while maneuvering. A contributing factor was the pilot's delay in taking remedial action. - [NTSB MIA01LA207](https://openairdocs.org/ntsb/MIA01LA207.md): Cessna 172N · Covington, GA · Accident · Minor injuries · Limited investigation · Final report · Aug 2, 2001 · N3467E · Substantial damage > The flight instructor's improper monitoring of the dual student during a simulated engine out approach and her delayed decision to initiate a go-around resulting in the airplane colliding with trees at the departure end of the runway during the go-around. - [NTSB CHI01FA130](https://openairdocs.org/ntsb/CHI01FA130.md): Cessna 172N · Wichita, KS · Accident · 2 fatal · Field investigation · Final report · May 6, 2001 · N733RK · Destroyed > the student pilot not maintaining clearance from the tower support wire during the practice emergency landing maneuver and the instructor pilot's inadequate supervision of the student pilot. Factors relating to the accident were the static wire and the low… - [NTSB DEN00FA149](https://openairdocs.org/ntsb/DEN00FA149.md): Cessna 172N · Kamas, UT · Accident · 1 fatal · Field investigation · Final report · Aug 13, 2000 · N734UD · Destroyed > The pilot's improper inflight decision to enter a valley at low altitude and attempt a climb towards rising terrain. A factor was exceeding the airplane's climb performance. - [NTSB LAX00LA152](https://openairdocs.org/ntsb/LAX00LA152.md): Cessna 172N · Lakeport, CA · Accident · No injuries · Limited investigation · Final report · Apr 11, 2000 · N6104G · Substantial damage > The pilot's decision to continue with a high, steep, and fast approach, which resulted in a touchdown beyond the halfway point of the runway and the inability to stop on the remaining pavement, and, his delayed decision to initiate a landing abort. Also… - [NTSB MIA00LA074](https://openairdocs.org/ntsb/MIA00LA074.md): Cessna 172N · Lincolnton, GA · Accident · No injuries · Limited investigation · Final report · Jan 25, 2000 · N2469E · Substantial damage > The pilot's failure to remove ice from the wings prior to takeoff resulting in the aircraft not climbing after takeoff and colliding with a tree. - [NTSB CHI00LA021](https://openairdocs.org/ntsb/CHI00LA021.md): Cessna 172N · Crandon, WI · Accident · No injuries · Limited investigation · Final report · Oct 25, 1999 · N4776E · Substantial damage > the deer that ran out onto the runway and collided with the airplane. A factor associated with the accident was the night lighting conditions. - [NTSB NYC99FA213](https://openairdocs.org/ntsb/NYC99FA213.md): Cessna 172N · Sussex, NJ · Accident · 3 fatal · Field investigation · Final report · Aug 29, 1999 · N737CJ · Substantial damage > The pilot's improper decision to takeoff with a tailwind. Factor's in this accident were the tailwind condition and pressure to depart caused by other airplanes performing successful downwind departures. - [NTSB SEA99LA077](https://openairdocs.org/ntsb/SEA99LA077.md): Cessna 172N · Covington, WA · Accident · Minor injuries · Limited investigation · Final report · May 27, 1999 · N5120D · Substantial damage > The student pilot's inadequate recovery from a bounced landing, and his subsequent improper execution of the go-around procedure, resulting in collision with trees off the departure end of the runway. Factors included the student pilot's lack of total… - [NTSB MIA99LA148](https://openairdocs.org/ntsb/MIA99LA148.md): Cessna 172N · Eagleville, TN · Accident · No injuries · Limited investigation · Final report · May 4, 1999 · N739EW · Substantial damage > The dual's student failure to maintain adequate altitude/clearance from the wire during takeoff/initial climb. Also causal was the certified flight instructor's inadequate supervision. - [NTSB FTW99LA114](https://openairdocs.org/ntsb/FTW99LA114.md): Cessna 172N · Cleburne, TX · Accident · No injuries · Limited investigation · Final report · Apr 6, 1999 · N734SV · Substantial damage > The pilot's failure to maintain adequate altitude/ clearance from the wires. - [NTSB ATL99FA020](https://openairdocs.org/ntsb/ATL99FA020.md): Cessna 172N · Concord, NC · Accident · Serious injuries · Field investigation · Final report · Nov 17, 1998 · N92KK · Substantial damage > The pilot's improper in-flight decision and his failure to maintain clearance during approach that resulted in collision with utility lines. Related factors were dark night, trees and low ceilings. - [NTSB NYC99FA015](https://openairdocs.org/ntsb/NYC99FA015.md): Cessna 172N · Linden, NJ · Accident · 1 fatal · Field investigation · Final report · Oct 25, 1998 · N6214F · Destroyed > The pilot's failure to maintain clearance from the power lines. A factor was sunglare. - [NTSB FTW98FA358](https://openairdocs.org/ntsb/FTW98FA358.md): Cessna 172N · Cord, AR · Accident · 1 fatal · Field investigation · Final report · Aug 15, 1998 · N6323G · Substantial damage > The pilot's performance of low altitude flight and his failure to maintain obstacle clearance. - [NTSB IAD98LA087](https://openairdocs.org/ntsb/IAD98LA087.md): Cessna 172N · Lebanon, OH · Accident · No injuries · Limited investigation · Final report · Aug 1, 1998 · N733LK · Substantial damage > The pilot's delay in aborting the landing, which resulted in inadequate obstacle (car) clearance during initial takeoff climb. A contributing factor is the pilot's decision to perform a tailwind landing. - [NTSB MIA97FA176](https://openairdocs.org/ntsb/MIA97FA176.md): Cessna 172N · Comerio, PR · Accident · 3 fatal · Field investigation · Final report · Jun 2, 1997 · N4752D · Destroyed > the pilot's improper in-flight planning/decision, which resulted in his failure to maintain sufficient altitude/clearance from obstructions on rising terrain. - [NTSB SEA97LA059](https://openairdocs.org/ntsb/SEA97LA059.md): Cessna 172N · Madras, OR · Accident · Serious injuries · Limited investigation · Final report · Feb 7, 1997 · N5618J · Substantial damage > The pilot's inadvertent visual flight rules (VFR) flight into instrument meteorological conditions (IMC). Factors include the pilot's improper decision to fly under a low ceiling while in mountainous/hilly terrain, and his encounter with fog and low clouds… - [NTSB FTW97LA085](https://openairdocs.org/ntsb/FTW97LA085.md): Cessna 172N · Steamboat Spgs, CO · Accident · No injuries · Limited investigation · Final report · Jan 17, 1997 · N739QE · Destroyed > Failure of the flight instructor and the dual student to maintain an adequate visual lookout. Factors were the flight instructor's inadequate supervision of the flight, inadequate altitude in which to clear obstacles, and the dual student's lack of… - [NTSB MIA97LA007](https://openairdocs.org/ntsb/MIA97LA007.md): Cessna 172N · Fruitland Park, FL · Accident · No injuries · Limited investigation · Final report · Oct 19, 1996 · N5155E · Substantial damage > The pilot's inadequate compensation for wind conditions and failure to maintain proper runway alignment during takeoff. The unfavorable wind condition was a related factor. - [NTSB LAX96LA304](https://openairdocs.org/ntsb/LAX96LA304.md): Cessna 172N · Fullerton, CA · Accident · No injuries · Limited investigation · Final report · Aug 10, 1996 · N42ES · Substantial damage > the pilot's misjudged glide path and delayed remedial action by not promptly initiating a go-around. A contributing factor was the pilot's lack of experience flying the airplane. - [NTSB ATL96FA094](https://openairdocs.org/ntsb/ATL96FA094.md): Cessna 172N · Arlington, TN · Accident · 1 fatal · Field investigation · Final report · Jun 14, 1996 · N73941 · Substantial damage > The pilot's failure to maintain clearance above the trees. A factor was the dark night. - [NTSB CHI96LA156](https://openairdocs.org/ntsb/CHI96LA156.md): Cessna 172N · Crystal Lake, IL · Accident · Minor injuries · Limited investigation · Final report · May 13, 1996 · N738CS · Substantial damage > the pilot not flying a proper glidepath for the displaced runway threshold. - [NTSB SEA96LA035](https://openairdocs.org/ntsb/SEA96LA035.md): Cessna 172N · Pacific City, OR · Accident · No injuries · Limited investigation · Final report · Dec 24, 1995 · N738ME · Substantial damage > The pilot's delay in aborting the landing, which resulted in his failure to clear the perimeter fence. Factors relating to the accident were: the tailwind, and the pilot's failure to land at the proper touchdown point. - [NTSB LAX95FA198](https://openairdocs.org/ntsb/LAX95FA198.md): Cessna 172N · Lovelock, NV · Accident · 4 fatal · Field investigation · Final report · May 28, 1995 · N4773E · Destroyed > the pilot's intentional flight at low altitude and subsequent collision with transmission wires during dusk light conditions. - [NTSB MIA95FA070](https://openairdocs.org/ntsb/MIA95FA070.md): Cessna 172N · Mintonville, KY · Accident · 2 fatal · Field investigation · Final report · Feb 2, 1995 · N734KV · Destroyed > The flightcrew's intentional VFR flight into known instrument meteorological conditions. A factor was the inadequate altitude to prevent an inadvertent collision with an obstruction. - [NTSB SEA95FA037](https://openairdocs.org/ntsb/SEA95FA037.md): Cessna 172N · Blyn, WA · Accident · 3 fatal · Field investigation · Final report · Jan 14, 1995 · N1535E · Destroyed > The pilot's VFR flight into instrument meteorological conditions. Factors in the accident were the weather conditions and the dark night. - [NTSB BFO95FA001](https://openairdocs.org/ntsb/BFO95FA001.md): Cessna 172N · Fancy Gap, VA · Accident · 1 fatal · Field investigation · Final report · Oct 9, 1994 · N734NB · Destroyed > The 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. - [NTSB NYC94LA132](https://openairdocs.org/ntsb/NYC94LA132.md): Cessna 172N · Chatham, MA · Accident · No injuries · Limited investigation · Final report · Jul 21, 1994 · N76090 · Substantial damage > The pilot's failure to see and avoid the birds. The presence of the birds at the airport was a contributing factor. - [NTSB SEA94LA113](https://openairdocs.org/ntsb/SEA94LA113.md): Cessna 172N · Monarch, MT · Accident · Minor injuries · Limited investigation · Final report · Apr 30, 1994 · N739CW · Substantial damage > Poor in flight planning/decision. A factor to the accident was downdrafts. - [NTSB LAX94LA176](https://openairdocs.org/ntsb/LAX94LA176.md): Cessna 172N · Gasquet, CA · Accident · Serious injuries · Limited investigation · Final report · Apr 3, 1994 · N6290D · Destroyed > The failure of the pilot to adequately compensate for the cross- wind conditions, and to maintain proper alignment with the runway. - [NTSB SEA94LA070](https://openairdocs.org/ntsb/SEA94LA070.md): Cessna 172 · Casper, WY · Accident · No injuries · Limited investigation · Final report · Mar 2, 1994 · N733WS · Substantial damage > The pilot's failure to maintain proper alignment with the runway. The crosswind was of factor. - [NTSB MIA93LA132](https://openairdocs.org/ntsb/MIA93LA132.md): Cessna 172N · Immokalee, FL · Accident · No injuries · Limited investigation · Final report · Apr 12, 1993 · N6542J · Substantial damage > The decision of the pilot to buzz and his failure to maintain adequate visual lookout. - [NTSB CHI92FA254](https://openairdocs.org/ntsb/CHI92FA254.md): Cessna 172N · Marquette, MI · Accident · 1 fatal · Field investigation · Final report · Aug 25, 1992 · N738HM · Destroyed > The pilot's failure to maintain proper altitude during the approach. - [NTSB MIA92LA148](https://openairdocs.org/ntsb/MIA92LA148.md): Cessna 172N · Sanford, FL · Accident · Minor injuries · Limited investigation · Final report · Jul 11, 1992 · N2135E · Substantial damage > Inadequate visual lookout by both pilots, which resulted in their failure to see-and-avoid of the power line. The proximity of the power line was a related factor. - [NTSB SEA92FA013](https://openairdocs.org/ntsb/SEA92FA013.md): Cessna 172N · Columbus, MT · Accident · 3 fatal · Field investigation · Final report · Oct 18, 1991 · N733QL · Destroyed > The pilot in command's operation at too low an altitude over the river and his failure to maintain adequate clearance from the power lines. Factors contributing to the accident were the wires crossing the river and the pilot in command's poor judgement in… Next page: https://openairdocs.org/ntsb.md?model=2072434&occurrence=220&page=2 ## The whole list in SQL Runs in DuckDB 1.2 or later on the release's Parquet files over HTTPS: ```sql 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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072434') AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 220)) ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC ``` This list as a web page: https://openairdocs.org/ntsb?model=2072434&occurrence=220 --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.