# NTSB investigations: Cessna 172P: 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.

## Latest cases

- [NTSB LAX06CA281](https://openairdocs.org/ntsb/LAX06CA281.md): Cessna 172P · Spanish Springs, NV · Accident · No injuries · Data collection · Final report · Sep 1, 2006 · N97306 · Substantial damage
  > the pilot's failure to initiate a timely go-around and to attain an adequate climb rate. Factors in the accident were the high density altitude and the likely quartering tail wind that may have affected the aircraft's climb gradient.
- [NTSB ATL06CA043](https://openairdocs.org/ntsb/ATL06CA043.md): Cessna 172P · Birmingham, AL · Accident · No injuries · Data collection · Final report · Feb 2, 2006 · N902NS · Substantial damage
  > An in-flight collision with a deer during a go around, which resulted in damage to the left main landing gear and subsequent collapse of the left main landing gear.
- [NTSB DEN04LA123](https://openairdocs.org/ntsb/DEN04LA123.md): Cessna 172P · Spanish Fork, UT · Accident · Serious injuries · Limited investigation · Final report · Aug 13, 2004 · N6249K · Destroyed
  > the pilot's improper inflight planning and decision making, and his failure to maintain terrain clearance. Contributing factors were his intentional low altitude flight and maneuvering, the aircraft's climb performance being exceeded, and the trees.
- [NTSB CHI03LA212](https://openairdocs.org/ntsb/CHI03LA212.md): Cessna 172P · Pinckneyville, IL · Accident · No injuries · Limited investigation · Final report · Jul 14, 2003 · N98395 · Substantial damage
  > The planned approach not maintained by the pilot and the delayed remedial action by the certified flight instructor. A contributing factor to the accident was the approach light.
- [NTSB MIA03FA066](https://openairdocs.org/ntsb/MIA03FA066.md): Cessna 172P · Osteen, FL · Accident · 1 fatal · Field investigation · Final report · Feb 25, 2003 · N97890 · Destroyed
  > The intentional suicidal act by the pilot-in-command resulting in the in-flight collision with trees then the ground.
- [NTSB CHI00LA017](https://openairdocs.org/ntsb/CHI00LA017.md): Cessna 172 · Waukon, IA · Accident · No injuries · Limited investigation · Final report · Oct 27, 1999 · N52569 · Substantial damage
  > the pilot failed to maintain directional control of the airplane during the aborted landing. Factors relating to the accident included the crosswinds, the fence, and the trees.
- [NTSB MIA99LA182](https://openairdocs.org/ntsb/MIA99LA182.md): Cessna 172P · Seymour, TN · Accident · Minor injuries · Limited investigation · Final report · Jun 13, 1999 · N5494K · Substantial damage
  > The failure of the pilot to perform a go-around earlier resulting in a long landing, insufficient runway remaining to stop, and subsequent in flight collision with a marked power line during an aborted landing.
- [NTSB NYC98LA012](https://openairdocs.org/ntsb/NYC98LA012.md): Cessna 172P · Pittsfield, MA · Accident · No injuries · Limited investigation · Final report · Oct 14, 1997 · N62264 · Substantial damage
  > The pilot's poor in-flight decision to continue VFR flight in IFR conditions. Factor's in this accident were the pilot's inadequate pre-flight planning, and fog.
- [NTSB IAD97LA046](https://openairdocs.org/ntsb/IAD97LA046.md): Cessna 172P · Chesapeake, OH · Accident · No injuries · Limited investigation · Final report · Feb 4, 1997 · N62332 · Substantial damage
  > the pilot's failure to maintain proper altitude during the approach at night. Related factors were: darkness, and the pilot's lack of night flying experience.
- [NTSB FTW96LA128](https://openairdocs.org/ntsb/FTW96LA128.md): Cessna 172P · Iowa, LA · Accident · Serious injuries · Limited investigation · Final report · Feb 22, 1996 · N775NA · Substantial damage
  > the pilot's selection of the wrong runway for landing, his delay in initiating a go-around (aborted landing), and his failure to maintain clearance from the transmission lines. Factors relating to the accident were: the pilot's improper weather evaluation,…
- [NTSB FTW96FA058](https://openairdocs.org/ntsb/FTW96FA058.md): Cessna 172P · Hallett, OK · Accident · 3 fatal · Field investigation · Final report · Dec 2, 1995 · N98003 · Destroyed
  > The flight instructor's intentional low altitude flight maneuver. Factors were the static wire and the bright night condition.
- [NTSB ANC95LA149](https://openairdocs.org/ntsb/ANC95LA149.md): Cessna 172 · Soldotna, AK · Accident · Serious injuries · Limited investigation · Final report · Aug 24, 1995 · N96911 · Substantial damage
  > The pilot's improper in-flight planning/decision, and his failure to maintain sufficient altitude to assure clearance from obstructions. The downdraft was a related factor.
- [NTSB FTW95LA052](https://openairdocs.org/ntsb/FTW95LA052.md): Cessna 172P · Blanco, TX · Accident · No injuries · Limited investigation · Final report · Nov 21, 1994 · N65275 · Substantial damage
  > The pilot's use of unsuitable terrain for takeoff. Factors were the uphill terrain, the long vegetation, and short takeoff area available.
- [NTSB CHI94LA289](https://openairdocs.org/ntsb/CHI94LA289.md): Cessna 172 · Plato Center, IL · Accident · No injuries · Limited investigation · Final report · Aug 28, 1994 · N97618 · Substantial damage
  > The pilot's attempt to take off on a short runway with a gross weight which exceeded the maximum allowable weight and an improper flap setting. A factor was the location of obstructions (trees) at the departure end of the runway.
- [NTSB SEA94LA178](https://openairdocs.org/ntsb/SEA94LA178.md): Cessna 172P · Easton, WA · Accident · Serious injuries · Limited investigation · Final report · Jul 13, 1994 · N65857 · Substantial damage
  > Improper planning/decision by the pilot-in-command, and inadequate supervision by the check pilot, which resulted in their failure to remain clear of trees during takeoff. Factors related to the accident were: a downdraft and the proximity of trees to the…
- [NTSB LAX94LA061](https://openairdocs.org/ntsb/LAX94LA061.md): Cessna 172P · Panoche, CA · Accident · Minor injuries · Limited investigation · Final report · Nov 28, 1993 · N65922 · Substantial damage
  > the pilot's improper approach speed and glide path, and his delayed initiation of a go-around. A factor in the accident was the wind shear condition created by the hills immediately off the departure end of the dirt airstrip.
- [NTSB BFO93LA156](https://openairdocs.org/ntsb/BFO93LA156.md): Cessna 172P · Pembroke, VA · Accident · 1 fatal · Limited investigation · Final report · Sep 4, 1993 · N50927 · Destroyed
  > The pilot's failure to maintain proper altitude while manuevering in mountainous terrain.
- [NTSB FTW93LA217](https://openairdocs.org/ntsb/FTW93LA217.md): Cessna 172P · Cookson, OK · Accident · No injuries · Limited investigation · Final report · Jul 24, 1993 · N65709 · Substantial damage
  > The pilot's improper flare and his failure to maintain directional control during the aborted landing.
- [NTSB DEN93FA008](https://openairdocs.org/ntsb/DEN93FA008.md): Cessna 172P · Woody Creek, CO · Accident · 1 fatal · Field investigation · Final report · Oct 24, 1992 · N63016 · Destroyed
  > Aircraft climb performance exceeded. Factors were: the pilot's lack of experience in mountain flying, and the high density altitude conditions.
- [NTSB SEA92LA206](https://openairdocs.org/ntsb/SEA92LA206.md): Cessna 172P · Leavenworth, WA · Accident · Minor injuries · Limited investigation · Final report · Sep 18, 1992 · N62036 · Destroyed
  > The premature lift off by the pilot. Factors relating to the accident were the soft, rough turf airstrip and the high obstructions at the end of the runway.
- [NTSB LAX92LA306](https://openairdocs.org/ntsb/LAX92LA306.md): Cessna 172P · Kernville, CA · Accident · Serious injuries · Limited investigation · Final report · Jul 19, 1992 · N5247K · Destroyed
  > The pilot's selection of the wrong runway; poorly planned approach; failure to attain the proper touch down point; and delay in executing the go-around. Contributing to this accident was the existing tailwind and crosswind.
- [NTSB CHI92LA173](https://openairdocs.org/ntsb/CHI92LA173.md): Cessna 172P · Ladysmith, WI · Accident · Serious injuries · Limited investigation · Final report · Jun 13, 1992 · N52142 · Destroyed
  > Failure of the pilot to attain a proper touchdown point and the attempted abort of the precautionary landing attempt.
- [NTSB BFO92FA069](https://openairdocs.org/ntsb/BFO92FA069.md): Cessna 172P · Princeton, NJ · Accident · 2 fatal · Field investigation · Final report · May 19, 1992 · N55110 · Destroyed
  > The pilot's failure to maintain clearance over an obstacle. Contributing factors were a tailwind, dark night, and premature raising of the flaps.
- [NTSB ATL91LA139](https://openairdocs.org/ntsb/ATL91LA139.md): Cessna 172P · Sylva, NC · Accident · No injuries · Limited investigation · Final report · Jul 22, 1991 · N52433 · Substantial damage
  > The pilot's improper in-flight planning, and his failure to maintain a proper altitude while maneuvering in the canyon. Factor(s) in this accident were: the mountainous, box canyon conditions, the high density altitude, and the downdraft conditions at the…
- [NTSB BFO91LA016](https://openairdocs.org/ntsb/BFO91LA016.md): Cessna 172P · Axton, VA · Accident · 1 fatal · Limited investigation · Final report · Dec 2, 1990 · N55276 · Destroyed
  > The pilot's failure to maintain adequate clearance with an obstacle. Contributing was an unmarked powerline and the pilot's lack of familiarity with the geographical area.
- [NTSB ATL89LA183](https://openairdocs.org/ntsb/ATL89LA183.md): Cessna 172P · Cincinnati, OH · Accident · No injuries · Limited investigation · Final report · Jul 22, 1989 · N52896 · Substantial damage
  > The pilot's improper go-around procedure of fully retracting the flaps which resulted in the airplane mushing into trees. Contributing factor(s) was: a misjudgement of flare height above the runway and failure to remove the carburetor heat which may have…
- [NTSB MKC89LA015](https://openairdocs.org/ntsb/MKC89LA015.md): Cessna 172 · Blue Springs, MO · Accident · No injuries · Limited investigation · Final report · Oct 22, 1988 · N50932 · Substantial damage
  > The plt said, while cruising over a water reservoir at about 500 feet AGL, he collided with two waterfowl, believed to be geese. One struck the wing tip, the other near the wing root. Acft control remained constant with no control problems encountered, and…
- [NTSB FTW88FA162](https://openairdocs.org/ntsb/FTW88FA162.md): Cessna 172P · Marietta, OK · Accident · 1 fatal · Field investigation · Final report · Sep 5, 1988 · N99144 · Destroyed
  > The plt elected to land on rwy 17 with wind from 300 degrees at 6 knots. During the second go-around the airplane's left wing struck a tree at a point 30 feet above the ground and the aircraft ended up inverted in a parking lot. Plt stated he had landed at…
- [NTSB NYC88FA202](https://openairdocs.org/ntsb/NYC88FA202.md): Cessna 172P · Post Mills, VT · Accident · 2 fatal · Field investigation · Final report · Aug 3, 1988 · N62541 · Destroyed
  > The plt flew the acft to an arpt with two turf rwys. Rwy 5/23 was 2300' long & rwy 4/22 was 2600' long. After attending a meeting which ended at 1600 EDT, the plt elected to wait until later in the day to takeoff after the air had cooled. Subsequently, he…
- [NTSB LAX88FA240](https://openairdocs.org/ntsb/LAX88FA240.md): Cessna 172P · Descanso, CA · Accident · 1 fatal · Field investigation · Final report · Jun 30, 1988 · N51234 · Destroyed
  > Pilot's poor judgment and intentional decision to low fly the aircraft below the minimum safe altitude.
- [NTSB NYC88LA079](https://openairdocs.org/ntsb/NYC88LA079.md): Cessna 172P · East Hampton, NY · Accident · 1 fatal · Limited investigation · Final report · Feb 11, 1988 · N52535 · Destroyed
  > The flight departed East Hampton airport for a pleasure flt. Shortly thereafter, the pilot called on frequency 122.7 stating that he had struck some birds and could not maintain control of the aircraft. There as no further transmission as to his location, and…
- [NTSB BFO87FA050](https://openairdocs.org/ntsb/BFO87FA050.md): Cessna 172P · Whitemarsh, MD · Accident · Minor injuries · Field investigation · Final report · Aug 2, 1987 · N54905 · Substantial damage
  > The pilot stated that he touched down near the end of the 22OO foot runway. However, witnesses said he landed so FAR down the runway that they did not believe he could stop on the runway. The pilot delayed his go around attempt to the point where it was not…
- [NTSB ATL87LA002](https://openairdocs.org/ntsb/ATL87LA002.md): Cessna 172P · East Liverpool, OH · Accident · Minor injuries · Limited investigation · Final report · Oct 9, 1986 · N54067 · Substantial damage
  > Rwy repair was in progress. The rwy was closed & battery powered lights were left to mark a 5 inch deep ditch that crossed the runway. Arpt & rwy lights were left off. The FBO continued to rent acft for operations from the arpt. The plt departed on a 28 mi…
- [NTSB ATL86FA212](https://openairdocs.org/ntsb/ATL86FA212.md): Cessna 172 · Bridgeport, WV · Accident · 2 fatal · Field investigation · Final report · Jul 28, 1986 · N96701 · Destroyed
  > The aircraft collided with a tree while on final approach to runway 21. The flight had been cleared for the approach after the pilot reported having the airport in sight. There was no current weather observation available at that time, but a local air taxi…
- [NTSB LAX86LA117](https://openairdocs.org/ntsb/LAX86LA117.md): Cessna 172P · Ontario, CA · Accident · No injuries · Limited investigation · Final report · Feb 12, 1986 · N55386 · Substantial damage
  > The owner/plt (PIC) was on a flt for night & instrument currency requirements. He was flying the acft from the left front seat while a commercial plt (cp) was occupying the rgt front seat. Drg an ILS rwy 26L final apch at Ontario, CA, the PIC & cp discussed a…
- [NTSB ATL86LA068](https://openairdocs.org/ntsb/ATL86LA068.md): Cessna 172P · Alexander City, AL · Accident · Minor injuries · Limited investigation · Final report · Feb 1, 1986 · N52238 · Substantial damage
  > The acft was observed to make one takeoff and landing from an umimproved pasture. The second takeoff attempted was unsuccessful and the acft collided with a tree and crashed to the ground. The plt did not report any mechanical problems with the acft. There…
- [NTSB CHI85LA164](https://openairdocs.org/ntsb/CHI85LA164.md): Cessna 172P · Phillipsburg, OH · Accident · Minor injuries · Limited investigation · Final report · Apr 13, 1985 · N55211 · Substantial damage
  > During a night VFR approach to a strange airport the acft struck power lines located one-half mile from the end of the rwy. The plt stated that she was unaware of the wires & was not aware that her acft had collided with them until her forward progress was…
- [NTSB FTW84FA408](https://openairdocs.org/ntsb/FTW84FA408.md): Cessna 172P · Webbers Falls, OK · Accident · 2 fatal · Field investigation · Final report · Sep 26, 1984 · N52270 · Destroyed
  > Acft struck electrical transmission line 80' above water while flying under the line during a wildlife survey. The acft's mission was to conduct a duck count along a river in a nat'l wildlife refuge which required low, slow maneuvering. The ex-ag pilot was…
- [NTSB ATL84LA271](https://openairdocs.org/ntsb/ATL84LA271.md): Cessna 172P · Biloxi, MS · Accident · Minor injuries · Limited investigation · Final report · Aug 24, 1984 · N55384 · Destroyed
  > Prior to departure the pilot determined that his destination, a grass runway, was dry. His first approach to this field resulted in a go-around because he would have landed long. The second approach resulted in a landing, but because his wheels began to slide…
- [NTSB LAX84LA148](https://openairdocs.org/ntsb/LAX84LA148.md): Cessna 172 · Oakland, CA · Accident · No injuries · Limited investigation · Final report · Jan 20, 1984 · N54042 · Substantial damage
  > The acft collided with wires during a descent through the clouds. The student plt had found himself on top of an overcast and managed to descend through it but in doing so a power line was hit. The plt climbed back on top and continued to destination without…
- [NTSB MIA83LA161](https://openairdocs.org/ntsb/MIA83LA161.md): Cessna 172P · Pensacola, FL · Accident · No injuries · Limited investigation · Final report · Jun 18, 1983 · N64079 · Substantial damage
  > The plt reported that he descended to aprx 50 ft AGL to demonstrate flt at low altitude to his passengers. While flying over a pasture at this altitude, the acft struck a pine tree, damaging the right wing. The plt experienced no control problems & returned…
- [NTSB FTW83LA352](https://openairdocs.org/ntsb/FTW83LA352.md): Cessna 172N · Morrilton, AR · Accident · Minor injuries · Limited investigation · Final report · Apr 28, 1983 · N54174 · Substantial damage
  > The acft collided with trees on the final approach to land at night. The plt had canceled his IFR clearance. During the approach the plt had the rwy in sight and asked memphis center how FAR he was from the arpt. When he was informed he WAS3 miles south he…
- [NTSB LAX83LA054](https://openairdocs.org/ntsb/LAX83LA054.md): Cessna 172P · Dateland, AZ · Accident · No injuries · Limited investigation · Final report · Dec 6, 1982 · N55299 · Substantial damage
  > During takeoff, the pilot was using the right side of a private strip to avoid an area of mud. At lift-off speed, the right wing tip struck a power pole near the right side of the runway and veered toward an irrigation ditch. The pilot was able to clear over…
- [NTSB ATL83FKM01](https://openairdocs.org/ntsb/ATL83FKM01.md): Cessna 172P · Near Maider, NC · Accident · 1 fatal · Final report · Nov 27, 1982 · N53460 · Destroyed
  > The pilot crashed into trees 6 miles east of maiden, NC in deteriorating weather. Witnesses described the weather as rainy and foggy in the area of crash. Some heard the aircraft flying low before colliding with trees. The pilot was off course for statesville…
- [NTSB NYC83LA008](https://openairdocs.org/ntsb/NYC83LA008.md): Cessna 172P · Grahamsville, NY · Accident · No injuries · Limited investigation · Final report · Oct 10, 1982 · N54177 · Substantial damage
  > The pilot and two passengers departed on a local sightseeing flight with full fuel tanks. About one hour after takeoff, the pilot flew over the passengers' house to take pictures. While a passenger was photographing the house, the pilot's attention was…
- [NTSB ANC82DAG46](https://openairdocs.org/ntsb/ANC82DAG46.md): Cessna 172 · Quinhagak, AK · Accident · No injuries · Final report · Aug 25, 1982 · N53145 · Substantial damage
  > The pilot reported that he landed on a gravel bar about 900 ft long with a passenger to go fishing. Later, he took off to the west with a slight head wind. Near the end of the gravel bar was a tree with branches sticking out of the water. As the pilot took…
- [NTSB CHI82DA251](https://openairdocs.org/ntsb/CHI82DA251.md): Cessna 172P · Washington Island, WI · Accident · Serious injuries · Final report · Jul 17, 1982 · N64947 · Destroyed
  > During arrival, the pilot made an approach to runway 14 for a night landing. After flaring to land, the aircraft was observed to float. The pilot stated that he had come in high, and during a go-around, the aircraft did not seem to climb properly, then…
- [NTSB DEN82FTC04](https://openairdocs.org/ntsb/DEN82FTC04.md): Cessna 172P · Osage, WY · Accident · 1 fatal · Final report · May 27, 1982 · N64093 · Destroyed
  > The aircraft departed gillette, Wyoming on a pipeline patrol mission. This was the pilot's first pipeline patrol over the line that he was patrolling. During the flight, the aircraft struck three powerlines and crashed. The passenger stated that he saw the…
- [NTSB ATL82DA143](https://openairdocs.org/ntsb/ATL82DA143.md): Cessna 172P · Jonesboro, GA · Accident · No injuries · Final report · May 25, 1982 · N54527 · Substantial damage
  > The pilot stated that after applying brakes on landing roll the aircraft began to hydroplane on water that was on the runway. He elected to raise the flaps and apply full power in a attempt to go-around but was unable to clear trees off the end of the runway.

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