Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

April 9, 2005 · Cessna 172 · N8400L

Yamhill, OR

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
April 9, 2005
Injury Outcomes
No injuries (2 uninjured)
Location
Yamhill, OR
Aircraft
Cessna 172
Tail Number
N8400L
Injuries
None
Aircraft Damage
Substantial
NTSB Number
SEA05CA080

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.

NTSB 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.

Full 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.

Flight

Event TypeAccident
Event Time09:30 PDT
Nearest AirportFlying M Airport (0nm)
Runway25
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo

Aircraft

AircraftCessna 172
Tail NumberN8400L
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320-E2D · Reciprocating

People & Injuries

Injury SummaryNo injuries (2 uninjured)
Fatal0
Serious0
Minor0
Uninjured2
Total2
Crew 1Age 66 · Third Class

Conditions

ConditionsVMC
LightDaylight
WindCalm
CeilingNone
Temperature / Dew Point0 C / 0 C
Altimeter0

Appendix: Source Data