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.
Grass Valley, CA
The pilot reported that, while en route, he noticed a loose camlock screw on the engine cowling and decided to land the airplane at the nearest airport. He added that, during the landing, he applied the brakes, but they had "minimal effect." As the airplane slowed "very slightly," he determined he could make the taxiway turn. But, he added that, "the left steering did not [a]ffect direction." The airplane exited the runway and went over the runway embankment. The airplane sustained substantial damage to the left wing. The pilot reported that the brakes failed to slow the airplane to a complete stop, and the nosewheel failed to turn. A local mechanic examined the brakes following the accident and found no anomalies. The airport manager reported that marks on the runway showed that the airplane had touched down about 1,000 to 1,500 ft beyond the approach end of the runway. Additionally, there was about a 15- ft-long skid mark showing a skidding left turn before the airplane exited the runway. Pictures submitted by the Federal Aviation Administration inspector showed the skid marks turning left while exiting the end of the runway. The airport supplement stated that runway 25 sloped downhill to the west.
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Landing flare-Not attained/maintained - C
The pilot reported that, while enroute, he noticed a loose camlock screw on the engine cowling and decided to land the airplane at the nearest airport. He added that, during the landing, he applied the brakes, but they had "minimal effect". As the airplane slowed "very slightly", he determined he could make the taxiway turn. But, he added that, "the left steering did not effect direction", the airplane exited the runway, and went over the runway embankment. The airplane sustained substantial damage to the left wing. The pilot reported that the brakes failed to slow the airplane to a complete stop, and the nose wheel failed to turn. A local mechanic inspected the brakes following the accident and found no anomalies. The airport manager reported that, marks on the runway showed the airplane touched down approximately 1000 to 1500 ft beyond the approach end of the runway. Additionally, there was approximately a 150 ft. long skid mark showing a skidding left turn before the airplane exited the runway. Pictures submitted by the Federal Aviation Administration inspector showed the skid marks turning left while exiting the end of the runway. The airport supplement states, runway 25 slopes downhill to west.