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.
Indian Head, MD
According to the pilot, he received a weather briefing that stated there was a convective SIGMET (significant meteorological information) over the airport and the storm would be arriving in about one hour. After receiving the briefing, the pilot performed a preflight check on the airplane, and proceeded to take off on a local solo flight. The pilot stated that during different phases of each traffic pattern, he had difficulty due to the gusty wind conditions. After initiating a go-around on the original departure runway, the pilot elected to set up for a long approach to a different runway. While on final approach, the airplane encountered gusty conditions and the pilot attempted to compensate for a crosswind. During touchdown, the airplane bounced several times, overran the end of the runway, and collided with a small ditch resulting in damage to the firewall. The pilot reported that there were no mechanical failures or malfunctions with the airplane. The recorded wind conditions about the time of the accident at an airport 8 miles away indicated a velocity of 10 knots, gusting to 18 knots.
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Descent/approach/glide path-Not attained/maintained - C
According to the pilot, he received a weather briefing that stated there was a convective SIGMET (significant meteorological information) over the airport and the storm would be arriving in about one hour. After receiving the briefing, the pilot preflighted the airplane, and proceeded to take off of runway 18 on a local solo flight. The pilot stated that during different phases of each traffic pattern, he had a difficult time due to the gusty wind conditions. On final approach to runway 18, he realized that the airspeed and altitude of the airplane were too high and he initiated a go-around. The pilot stated that he recognized "the difficultly landing in gusty conditions" and requested assistance over the UNICOM frequency. A pilot, who was required to monitor the solo flight, advised the student pilot to fly away from the airport and set up for a long final approach to runway 36. On final approach, the pilot of the accident airplane stated that he "continued to encounter gusty conditions" and was advised to lower the left wing of the airplane to compensate for the crosswind. The pilot stated when the airplane first touched down, it was a "rough landing," and "the airplane bounced a few times." The airplane overran the end of the runway and hit a small ditch damaging the firewall. The pilot did not report any mechanical failures or malfunctions of the airplane. Winds, recorded at an airport 8 miles to the northwest about the time of the accident, were from 260 degrees at 10 knots, gusting to 18 knots.