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.
Avalon, CA
A witness reported that the pilot's first landing attempt was too high, and the airplane went around. During the second landing attempt, the airplane was "still too high and came in too fast." The airplane touched down past the runway midpoint, and as the airplane neared the end of the runway, the witness heard the engine "rev up" and saw the airplane depart the runway in a "very nose high" pitch attitude. The airplane subsequently collided with terrain about 1,000 ft beyond the departure end of the runway and about 75 to 100 ft below the runway surface elevation. The pilot reported that he did not recall the events of the accident, but stated that there were no mechanical anomalies with the airplane. The accident is consistent with the pilot's delayed decision to conduct a go-around following an unstable approach and long landing, which resulted in the airplane having insufficient airspeed to climb after the attempted go-around and impact with terrain.
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Descent/approach/glide path-Not attained/maintained - C
On July 25, 2018, about 0930 Pacific daylight time, a Piper PA-32-300, N4747H, was substantially damaged when it was involved in an accident in Avalon, California. The private pilot sustained serious injuries and the two passengers sustained minor injuries. The airplane was operated by the pilot as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot reported that he did not remember the accident but did state there were no mechanical failures or malfunctions with the airplane prior to the accident. The airport manager reported that when the airplane was on downwind, he advised the pilot of the wind which was 330° at 4 knots. He stated that the pilot's first landing attempt was too high, and the airplane went around. On the second landing attempt the airplane was "still too high and came in too fast" but touched down past about midfield. As the airplane neared the end of the runway, he heard the engine "rev up" and observed the airplane depart the runway in a "very nose high" pitch attitude. The airplane subsequently collided with terrain about 1,000 ft beyond the departure end of the runway and about 75 to 100 ft below the runway surface elevation in a nose low attitude.