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.
Toledo, WA
The pilot reported that after parachutists (skydivers) jumped from 13,000 feet, he returned to the airport. While on base leg for landing, two radio-controlled model airplanes were observed flying near the approach end of the runway. The model airplanes swung wide and blocked the first 2,000 feet of the approach end of the runway; thus, moving the available touchdown zone closer to the departure end of the runway. The pilot continued the approach until his airplane was over the last 1/3 of the runway before he initiated a go-around. During the go-around, the engine lost power, and the pilot made a forced landing. The airplane touched down at the departure end of the runway, then it ran off the end and went into a ditch. Postaccident examination revealed no mechanical failure or malfunction.
loss of engine power for undetermined reason(s). Factors relating to the accident were: the pilot's need to maneuvering to avoid obstructions near the approach end of the runway, and a ditch in the emergency landing area.
On June 21, 1996, at 1945 Pacific daylight time, a Cessna 182A, N9975B, registered to and operated by Verticle Ventures Inc. as a 14 CFR Part 91 business flight, collided with a ditch during a forced landing after the engine experienced a loss of power during a go-around at the Toledo Airport, Toledo, Washington. Visual meteorological conditions prevailed at the time and no flight plan was filed. The airplane was substantially damaged and the commercial pilot, the sole occupant, was not injured. The pilot reported that he had just dropped parachutists from 13,000 feet and was returning to the airport. The pilot stated that while on final approach to runway 23, he did not like how the airplane was set up for the landing and opted to go-around. During the go-around, the engine lost power. The pilot stated that he forced landed the airplane near the end of the runway. During the landing roll, a main landing gear collapsed and the airplane slid sideways into a ditch. The pilot further stated that radio controlled model aircraft were flying near the approach end of the runway. The model airplanes were supposed to use only 1,000 feet of the approach end of the runway, however, the pilot stated that while he was on the base leg, two of the model airplanes swung wide and blocked the first 2,000 feet of the runway, thus moving the pilot closer to the departure end of the runway. The pilot's diagram of the events indicates that he was approximately 2/3 of the way down the runway when the go-around was started and 500 feet from the end of the runway when the engine lost power. Initial inspection of the airplane determined that there was minor damage; however, after closer examination, structural damage was found. The National Transportation Safety Board was notified of this damage on July 17, 1996. After the accident, the engine was inspected. During the inspection, there was no evidence found to indicate a mechanical failure or malfunction.