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.
San Martin, CA
The pilot was conducting a post-maintenance check flight of the aircraft following an annual inspection completed the prior day. During repairs associated with the annual inspection, the three engine control cables were replaced. While in cruise flight the engine lost power and the pilot attempted to glide to an emergency landing. He overshot the 3,100-foot-long runway and went off the departure end. When the engine was uncowled, the bolt which connects the throttle control to the throttle body actuator arm was missing. The bolt was found in the bottom of the cowling, but the nut was not located. The bolt did not comply with an applicable Airworthiness Directive. The pilot opined that after the throttle control separated, the engine may not have gone completely to the idle power position and the resulting partial engine power may have contributed to the landing overshoot. The pilot stated that he was wearing a headset and could not hear the engine well enough to detect a partial power condition.
Installation of improper connecting hardware by maintenance personnel, and, the inadequate inspection of the installed hardware by inspection personnel resulting in separation of the engine throttle linkage.
On August 29, 1997, at 1510 hours Pacific daylight time, a Cessna T210M, N761HQ, overshot the landing runway and impacted a fence and terrain at South County Airport, San Martin, California. The aircraft was substantially damaged, and the airline transport pilot was not injured. Visual meteorological conditions prevailed for the post-maintenance check flight. The flight departed from the San Jose International Airport about 1430. The pilot told an inspector from the San Jose Flight Standards District Office that he was conducting the check flight of the aircraft following an annual inspection, which was completed the prior day. While in cruise flight, the engine lost power and he attempted to glide to runway 32 for an emergency landing. He overshot the 3,100-foot-long runway and went off the departure end. The inspector reported that when the engine was uncowled, the bolt which connects the throttle control to the throttle body actuator arm was missing. The bolt was found in the bottom of the cowling, but the nut was not located. Subsequent investigation revealed that, during maintenance associated with the inspection, the throttle, propeller and mixture control cables had been replaced. The bolt found in the bottom of the cowling was an improper type that did not comply with an applicable Airworthiness Directive. In his report to the Safety Board, the pilot stated that after the throttle control separated, the engine may not have gone completely to the idle power position and the resulting partial engine power may have contributed to the landing overshoot. The pilot stated that he was wearing a headset and could not hear the engine well enough to detect a partial power condition.