Skip to content

SEA05CA080

2005-04-09 · Yamhill, Oregon, United States · None · 1 aircraft · Status: Completed

Airport OR05

Current FAA registration · N8400L

Make / Model
CESSNA 172I
Year of manufacture
1968 · 37 years old at event
Engine
LYCOMING 0-320 SERIES (180 hp)
Seats / Engines
4 seats · 1 engine
Last airworthiness date
19680308
ADS-B equipped
Yes — Mode-S AB823C

Source: FAA Aircraft Registry (releasable master file).

Aircraft involved

Probable cause & findings

The pilot's failure to maintain aircraft control while on final approach for landing. A crosswind, a fence post and the pilot's inadequate compensation for the crosswind condition were contributing factors.

Factual narrative

On April 9, 2005, about 0930 Pacific daylight time, a Cessna 172I, N8400L, registered to and flown by the pilot as a 14 CFR Part 91 personal flight, collided with a fence post and subsequently the terrain during landing at Flying M Airport, Yamhill, Oregon. Visual meteorological conditions prevailed at the time and no flight plan was filed. The aircraft was substantially damaged and the private pilot and his passenger were not injured. The flight originated from Salem, Oregon, about 15 minutes prior to the accident. In a written statement, the pilot reported that he was approaching the airstrip from the east for a landing on runway 25. The pilot noted, via the wind sock, that the wind was out of the north at about 5 miles per hour, but variable. The pilot stated that he had just started the flare when the airplane "did a sharp shift to the left, just to the side of the runway." The pilot attempted to correct for the crosswind, however, the airplane continued to move further off to the south side of the runway towards a fence which was located about 25 feet away. The left horizontal stabilizer collided with a fence post about the same time the wheels touched the surface. Due to a vehicle that was on the road that runs parallel to the runway and in close proximity to the airplane, the pilot added full power in an attempt to avoid the car. The airplane traveled up an incline back to the runway surface and toward trees off the north side of the airstrip. The airplane collided with several small trees and eventually traveled into a culvert and tipped over onto its nose, coming to rest in about three feet of water. The pilot reported no mechanical failure or malfunction with the airplane at the time of the accident. In a written statement, the pilot reported that he was approaching the airstrip from the east for a landing on runway 25. The pilot noted, via the wind sock, that the wind was out of the north at about 5 miles per hour, but variable. The pilot stated that he had just started the flare when the airplane "did a sharp shift to the left, just to the side of the runway." The pilot attempted to correct for the crosswind, however, the airplane continued to move further off to the south side of the runway towards a fence which was located about 25 feet away. The left horizontal stabilizer collided with a fence post about the same time the wheels touched the surface. Due to a vehicle that was on the road that runs parallel to the runway and in close proximity to the airplane, the pilot added full power in an attempt to avoid the car. The airplane traveled up an incline back to the runway surface and toward trees off the north side of the airstrip. The airplane collided with several small trees and eventually traveled into a culvert and tipped over onto its nose, coming to rest in about three feet of water. The pilot reported no mechanical failures or malfunctions with the airplane at the time of the accident. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12

Verbatim from NTSB's published report. Source file NTSB_2005_SEA05CA080.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.

Related research

Matched on aircraft type. All research papers