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 Diego, CA
The pilot stated he had experienced insufficient pitch control on landing at Tucson, Arizona, prior to the accident. He reported that he 'found play in the elevator control,' and was advised over the telephone by Velocity Inc. to add washers or spacers to the rear of the torque tube to remove the play. With the aid of a local pilot in Tucson, he added the washers and spacers to the rear of the torque tube. The pilot further stated that upon attempting to flare at Montgomery Field, 'the nose would not come up.' The aircraft bounced, veered off the runway, skidded across a grass area, and collided tail first with a parked Cessna 340. According to the pilot, on January 2, 1999, builders from Velocity Inc. inspected the airplane, and found that 'the front bearing of the aileron torque tube had come loose, thus preventing a full elevator down deflection.'
The pilot's inadequate modification to the control systems, which resulted in a restricted elevator control.
On December 29, 1998, at 1547 hours Pacific standard time, a Velocity 173E-RG, N466MF, veered off runway 28L on landing at Montgomery Field, San Diego, California, and collided with a parked Cessna 340, N6241X. The aircraft and the parked and unoccupied Cessna 340 sustained substantial damage. The private pilot and his two passengers were not injured. Visual meteorological conditions prevailed for the personal flight from Ryan Field in Tucson, Arizona, to Montgomery Field. This was the last leg of a cross-country flight, which originated the day before in Tampa, Florida. No flight plan was filed. The pilot stated that he had experienced insufficient pitch control on landing at Tucson prior to the accident. He reported that he "found play in the elevator control," and was advised over the telephone by the aircraft designer, Velocity Inc., to add washers or spacers to the rear of the torque tube to remove the play. With the aid of a local pilot in Tucson, he added the washers and spacers to the rear of the torque tube. The pilot further stated that upon attempting to flare, "the nose would not come up." The aircraft bounced, veered off the runway, skidded across a grass area, and collided tail first with the parked Cessna 340. According to the pilot, "on January 2, 1999, several Velocity builders inspected the airplane and found that the front bearing of the aileron torque tube had come loose, thus preventing a full elevator down deflection."