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.
Albany, OR
The pilot reported that, during the landing rollout, he applied the brakes but that the airplane failed to stop. The airplane continued about 2,600 ft down the runway, departed the runway surface, and impacted a chain link fence. Postaccident examination of the airplane revealed that the brake hydraulic fluid reservoir was empty, and an elbow fitting on the right main landing gear brake assembly hydraulic line was found broken; it could not be determined when the elbow fitting broke. The lack of hydraulic fluid rendered the brakes ineffective.
The loss of hydraulic fluid, which rendered the brakes ineffective. The reason for the loss of hydraulic fluid could not be determined based on the available evidence.
On July 7, 2013, at 1330 Pacific daylight time, a Piper PA 28-235, N8606W, overran the runway on the landing rollout on runway 34 at the Albany Municipal Airport (S12), Albany, Oregon. The pilot/owner operated the airplane under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. The pilot and passenger were not injured, and the airplane sustained substantial damage to the wings. Visual meteorological conditions prevailed for the flight, and no flight plan had been filed. The flight departed Lake County Airport (LKV), Lakeview, Oregon, at 1200, with a planned destination to S12. According to the pilot, during the landing rollout he applied the brakes, but the airplane did not stop. The airplane continued down the runway about 2,600 feet, departed the runway surface, and impacted a chain link fence. Postaccident examination by the Federal Aviation Administration (FAA) revealed that the brake fluid reservoir was empty. Further examination revealed a broken elbow fitting on the right landing gear brake assembly hydraulic line. The pilot did not complete or turn in the National Transportation Safety Board Pilot Operator/Aircraft Accident/Incident Report, Form 6120.1.