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.
Roche Harbor, WA
During a telephone conversation, the pilot stated that shortly after touchdown (wheel landing), the aircraft drifted to the right (south) of runway centerline. The pilot applied brakes and corrective actions, however, the aircraft continued off the runway and down an embankment that parallels the runway. During the accident sequence, the aircraft's main gear separated from the airframe resulting in substantial damage to the fuselage. A FAA inspector from the Seattle, Washington, Flight Standards District Office (FSDO), visually inspected the aircraft after the accident and reported that there was no evidence found to indicate a brake failure or malfunction. Shortly after the accident, a Sheriff's Deputy from the San Juan County Sheriff's Office reported that the winds at Roche Harbor were blowing across the runway at a 30-40 degree angle and estimated that the wind speed was 10-15 knots. He also stated that the winds favored runway 24 (report attached). The 1553 METAR observation taken at Friday Harbor, Washington (6 miles southeast of the accident site), reported winds from 230 degrees true at 7 knots.
The pilot's failure to adequately compensate for wind conditions during landing.
On August 25, 2000, about 1500 Pacific daylight time, a Cessna 180H, N91464, sustained substantial damage while landing on runway 07 at Roche Harbor Airport, Roche Harbor, Washington. The commercial pilot, and the one passenger aboard the aircraft were not injured. The pilot was operating the aircraft as a visual flight rules (VFR) personal/pleasure flight under Title 14 CFR 91, when the accident occurred. Visual meteorological conditions prevailed and no flight plan was filed. The flight originated from Portland, Oregon, (PDX) approximately two hours prior to the accident. During a telephone conversation with the NTSB, the pilot stated that shortly after touchdown (wheel landing), the aircraft drifted to the right (south) of runway centerline. The pilot applied brakes and corrective actions, however, the aircraft continued off the runway and down an embankment that parallels the runway. During the accident sequence, the aircraft's main gear separated from the airframe resulting in substantial damage to the fuselage. Shortly after the accident, a Sheriff's Deputy from the San Juan County Sheriff's Office reported that the winds at Roche Harbor were blowing across the runway at a 30-40 degree angle and estimated that the wind speed was 10-15 knots. He also stated that the winds favored runway 24 (report attached). The 1553 METAR observation taken at Friday Harbor, Washington (6 miles southeast of the accident site), reported winds from 230 degrees true at 7 knots. A FAA inspector from the Seattle, Washington, Flight Standards District Office (FSDO), visually inspected the aircraft after the accident and reported that there was no evidence found to indicate a brake failure or malfunction.