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, who was the original owner and builder of this aircraft, stated that while he was decelerating during his landing rollout, he encountered a gust of wind from the left, which caused the airplane to become airborne again with the left wing high. He added power and avoided a stall, but had drifted off the runway. The left main landing gear hit a runway light, causing the airplane to ground loop, which damaged the outboard 2 feet of the left wing. The pilot stated that he would repair the wing and fly the airplane again. He stated that the damage was easy to repair and would take only a few days to complete. According to the pilot, he had approximately 2,000 hours of flight time, 700 of which was in the accident airplane. He had logged 50 hours in this airplane within the last 90 days. When asked how he could prevent this accident from happening in the future, he stated "Don't go flying."
Failure of the pilot to maintain directional control during landing.
On Saturday, July 7, 2001, at 1310 hours Pacific daylight time, a Sparks KR-2, N122MS, was substantially damaged when it struck a runway light at Gillespie Field, San Diego, California. The private pilot, who was the only occupant, was not injured. Visual meteorological conditions prevailed for the flight, which was conducted by the owner under 14 CFR Part 91. The airplane departed Brown Field, San Diego, at 1250 for the flight to Gillespie Field, where the accident occurred. No flight plan was filed. The pilot, who was the original owner and builder of this aircraft, was interviewed by an investigator from the National Transportation Safety Board shortly after the accident. He stated that while he was decelerating during his landing rollout, he encountered a gust of wind from the left, which caused the airplane to become airborne again with the left wing high. He added power and avoided a stall, but had drifted off the runway. The left main landing gear hit a runway light, causing the airplane to ground loop, which damaged the outboard 2 feet of the left wing when it contacted the ground. The pilot stated that he would repair the wing and fly the airplane again. He stated that the damage was easy to repair and would take only a few days to complete. According to the pilot, he had approximately 2,000 hours of flight time, 700 of which was in the accident airplane. He had logged 50 hours in this airplane within the last 90 days.