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.
Somerville, NJ
The pilot stated that she departed from runway 26, and flew over a local golf course, then turned to return to the departure airport where she entered the traffic pattern on the downwind leg for runway 26, flying between 75 and 80 knots. She descended to 800 feet and prior to turning base leg she slowed to between 65 and 70 knots, which she maintained on base and final. She turned onto base leg and descended to 500 feet and at that altitude turned onto final approach for runway 26 slowing at touchdown. She performed a wheel landing a few feet farther along the runway than typical or "a little long" which she described as abeam the western edge of the hangars. The airplane travelled onto a portion of the runway that causes undulations and with aft stick applied after encountering the undulations, she tapped the brakes. The airplane then nosed over. She further reported that there was nothing mechanically wrong with the airplane that caused the nose over, and the area of the runway where the undulations were located also was not the cause of the accident. Various video recordings depicted the approach and nose-over sequence; however, the actual touchdown point was not captured. An individual at the accident airport provided a reference for where the airplane came to rest, which was located before a diagonal line that is visible in a Google Earth image. Plotting on Google Earth of the pilot reported touchdown point indicates that position was located about 800 down the 2,200 foot long grass runway, which has the west 500 feet described as being unsuitable for takeoff or landing due to uneven surface. Therefore, the pilot reported touchdown point occurred nearly halfway down the usable length of runway. Although the exact location where the airplane came to rest was not documented, based on video recording, that was located about 500 feet from the pilot reported touchdown point.
The pilot's failure to maintain aircraft control while applying wheel brakes during landing roll resulting in the airplane nosing over.
The pilot stated that she departed from runway 26, and flew over a local golf course, then turned to return to the departure airport where she entered the traffic pattern on the downwind leg for runway 26, flying between 75 and 80 knots. She descended to 800 feet and prior to turning base leg she slowed to between 65 and 70 knots, which she maintained on base and final. She turned onto base leg and descended to 500 feet and at that altitude turned onto final approach for runway 26 slowing at touchdown. She performed a wheel landing a few feet farther along the runway than typical or "a little long" which she described as abeam the western edge of the hangars. The airplane travelled onto a portion of the runway that causes undulations and with aft stick applied after encountering the undulations, she tapped the brakes. The airplane then nosed over. She further reported that there was nothing mechanically wrong with the airplane that caused the nose over, and the area of the runway where the undulations were located also was not the cause of the accident. Various video recordings depicted the approach and nose-over sequence; however, the actual touchdown point was not captured. An individual at the accident airport provided a reference for where the airplane came to rest, which was located before a diagonal line that is visible in a Google Earth image. Plotting on Google Earth of the pilot reported touchdown point indicates that position was located about 800 down the 2,200 foot long grass runway, which has the west 500 feet described as being unsuitable for takeoff or landing due to uneven surface. Therefore, the pilot reported touchdown point occurred nearly halfway down the usable length of runway. Although the exact location where the airplane came to rest was not documented, based on video recording, that was located about 500 feet from the pilot reported touchdown point.