# NTSB SEA05CA080: Cessna 172, N8400L, Yamhill, OR, April 9, 2005 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: April 9, 2005, 09:30 local (16:30 UTC) - Place: Yamhill, OR - Coordinates: 45.360539, -123.35526 - Nearby events: https://openairdocs.org/map.md?lat=45.3605&lon=-123.3553&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report July 7, 2005 - Report: Approved by Office Director - NTSB case key (mKey): 61284 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=SEA05CA080 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/61284/pdf - Page: https://openairdocs.org/ntsb/SEA05CA080 ## Probable cause 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. ## Analysis 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. ## 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. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of control - in flight, approach - vfr pattern - final approach - aircraft control - not maintained, pilot in command (cause) - weather condition - crosswind (contributing factor) - compensation for wind conditions - inadequate, pilot in command (contributing factor) - On ground/water collision with object, landing - object - fence post (contributing factor) - object - tree(s) ## Aircraft - Registration: [N8400L](https://openairdocs.org/aircraft/N8400L), registered now, S/N 17256600, built 1968 (OpenAirDocs) - Reported make and model: Cessna 172 - Registry model: [Cessna 172I](https://openairdocs.org/model/cessna-172i) (registry code 2072426) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17256600 - Engines: Lycoming O-320-E2D reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Registered owner: William C. Burwell - Airworthiness certificate: Standard, Normal - Departed: SLE, Salem, OR - Destination: OR05, Yamhill, OR - Airport: OR05, Flying M Airport, runway 25 ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 66; private; airplane ratings: single-engine land; medical: class 3; flight hours: 572 total, 470 in this make and model ## Weather - Conditions: Visual (VMC), Day ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20050409005109A](https://openairdocs.org/incident/20050409005109A), Apr 9, 2005: Cessna 172I, Yamhill, OR, Substantial damage. (-23) N8400L crashed on landing at the Flying m ranch airport. [privacy data omitted] The pilot-in-command, attempted to land east on the runway but touched… From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- 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.