Overall Trends
Total, fatal, and serious accidents in the selected range.
Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.
Fast key and full-text search with live filters, watches, and precise metadata.
Use quotes for exact phrase matches (for example "fuel selector valve").
Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.
Major cases, deep-report coverage, and investigation media across decades of NTSB history.
Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.
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.
Mcminnville, OR
The pilot, who was landing in gusty crosswinds, had already made one landing and was on the landing roll of his second when he encountered crosswinds that lifted the aircraft's left wing in the air. At the same time as the wing was being lifted, the aircraft started drifting toward the right side of the runway. As the pilot attempted to get the wing down using aileron deflection, and tried to get the aircraft heading straight down the runway, it felt to him like the aircraft was going to cartwheel. He therefore decided to let the aircraft go off the side of the runway in the direction it was headed. After departing the runway, the aircraft encountered soft terrain, whereupon the nose gear dug in and the aircraft nosed over. According to the pilot, except for a minor nose wheel shimmy, there did not seem to be any problems with the aircraft's controls.
The pilot's inadequate compensation for wind conditions and his failure to maintain directional control during the landing roll. Factors include gusty crosswinds and soft terrain in the area where the aircraft departed the side of the runway.
On February 8, 2003, approximately 1300 Pacific standard time, a Cessna 172N, N734KU, nosed over during the landing roll at McMinnville Municipal Airport, McMinnville, Oregon. The private pilot, who was the sole occupant, was not injured, but the aircraft, which is owned and operated by Starks Twin Oaks Airpark, Inc., sustained substantial damage. The 14 CFR Part 91 personal pleasure flight, which was being conducted in the VFR pattern at McMinnville, was being operated in visual meteorological conditions. No flight plan had been filed, and there was no report of an ELT activation. According to the pilot, who was landing in gusty crosswinds, he had already made one landing and was on the landing roll of his second when he encountered crosswinds that lifted the aircraft's left wing in the air. At the same time as the wing was being lifted, the aircraft started drifting toward the right side of the runway. As the pilot attempted to get the wing down using aileron deflection, and tried to get the aircraft heading straight down the runway, it felt to him like the aircraft was going to cartwheel. He therefore decided to let the aircraft go off the side of the runway in the direction it was headed. After departing the runway, the aircraft encountered soft terrain, whereupon the nose gear dug in and the aircraft nosed over. According to the pilot, except for a minor nose wheel shimmy, there did not seem to be any problems with the aircraft's controls.