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.
Tucson, AZ
Witnesses reported that the aircraft landed fast on the main wheels, began veering left off the runway, became airborne, touched down in a dirt area, became airborne again, went through a chain link fence, and collided with an occupied security truck in the Arizona Air National Guard compound. The airport was using runway 11 for takeoffs and landings. During initial contact with the Tucson Air Traffic Control Tower, the pilot had requested runway 3 for landing, and, the tower issued the requested clearance, along with the wind direction and speed of 280 degrees at 7 knots. The airframe and engine were examined following recovery with no discrepancies noted.
The pilot's selection of the wrong runway for the wind conditions, his inadequate compensation for the existing quartering tailwind condition, and, his failure to maintain directional control.
On August 18, 1998, at 1736 hours mountain standard time, a Silvaire Luscombe 8F, N1616Z, veered off runway 3 while landing at the Tucson, Arizona, International Airport. The aircraft, which was destroyed, damaged an Air National Guard (ANG) fence, and substantially damaged an ANG security truck. The commercial pilot sustained serious injuries and the driver of the truck incurred minor injuries. The aircraft was owned and operated by the pilot under the provisions of 14 CFR Part 91 of the Federal Aviation Regulations. Visual meteorological conditions prevailed and included winds from 280 degrees at 8 knots. The flight originated from Falcon Field, Mesa, Arizona at 1630. There was no flight plan filed for the personal flight. The pilot is a military aviator with the Arizona Air National Guard, stationed at the Tucson Airport, and flies the F-16. In his written report, the pilot stated that during contact with the Tucson Air Traffic Control Tower, he had requested runway 3 for landing. The tower issued the requested clearance along with the wind direction and speed, which was 280 degrees at 7 knots. He said that just before the tail wheel touched the ground, the plane veered left and he applied right rudder to no avail. He went on to state that he applied full power for a go-around, rotated the aircraft, but the engine did not respond and he was unable to make a successful climb. He clipped the fence and collided with the roof of a parked security truck behind the first row of F-16's. Witnesses reported that the aircraft landed fast on the main wheels, began veering left off the runway, became airborne, touched down in a dirt area, became airborne again, went through a chain link fence, and collided with an occupied security truck in the Arizona Air National Guard compound. Following recovery of the aircraft to a salvage facility in Phoenix, Arizona, the Safety Board examined the airframe and engine. No discrepancies were noted with the airframe. With a supply of fuel plumbed into the aircraft fuel lines at the wing root, the engine was started and found to respond to throttle inputs.