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.
Polson, MT
The pilot was turning left base to final when the controls jammed. He applied rudder and added power in an attempt to compensate, but roll control was not regained. He reduced power and examined the cockpit area to see if anything was binding the controls. He did not identify anything in the cockpit that could have caused the binding. The airplane continued left thru two full turns (720 degrees) before the main landing gear contacted the ground, at which point the airplane cartwheeled and came to rest inverted. He egressed the airplane uninjured. The pilot stated to an FAA inspector that when he knew it was safe to approach the airplane, he checked the controls to see if they were still jammed and determined that they were no longer binding or jammed. They functioned normally. The on-scene FAA inspector examined the airplane's control system and could not identify any evidence of binding or jammed controls.
a flight control jam for undetermined reasons.
On August 3, 2007, about 0900 mountain daylight time, a Luscombe 8E, N45486, impacted terrain while turning base to runway 36 at Polson Airport, Polson, Montana. The private pilot operated the airplane under the provisions of 14 CFR Part 91. The pilot was not injured, and the airplane was substantially damaged. Visual meteorological conditions prevailed, and no flight plan had been filed. The flight originated at Livingston, Montana, about 0630. The pilot reported to the National Transportation Safety Board investigator that as he was turning left base for final the controls jammed. He applied rudder and added power in an attempt to compensate but roll control was not regained. He reduced power and examined the cockpit area to see if anything was binding the controls. He did not identify anything in the cockpit that could have caused the binding. The airplane continued left thru two full turns (720 degrees) before the main landing gear contacted the ground, at which point the airplane cartwheeled and came to rest inverted. He egressed the airplane uninjured. The pilot stated to a Federal Aviation Administration (FAA) inspector that when he knew it was safe to approach the airplane, he checked the controls to see if they were still jammed and determined that they were no longer binding or jammed. They functioned normally. The on-scene FAA inspector examined the airplane's control system and could not identify any evidence of binding or jammed controls.