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.
Hillsboro, OR
The student pilot reported that the airplane was trailing about 30 seconds behind two Life Flight helicopters on final approach for landing. About 500 feet before the end of the runway, the helicopters turned to the right toward the ramp area. The student pilot, who was on the flight controls at the time, stated that the approach was continued and at about 100-150 feet AGL and 60 knots airspeed, the airplane suddenly rolled to the right about 90 degrees. The flight instructor took over the controls and righted the aircraft, however, it continued to settle to the ground in a nose down attitude. The airplane collided with the ground about 200 feet short of the end of the runway and slid about 60 feet before coming to rest. Inspection of the flight control system did not reveal a mechanical failure or malfunction. The operator of the aircraft stated that he believed that wake turbulence from the helicopters contributed to the aircraft's sudden roll and subsequent collision with the ground.
An inadequately planned approach. The encounter of wake turbulence and not being able to maintain aircraft control were factors.
On August 9, 2000, at 1832 Pacific daylight time, a Cessna 152, N6434H, registered to and operated by Hillsboro Aviation as a 14 CFR Part 91 instructional flight, collided with the ground short of the runway 02 at Hillsboro, Oregon. Visual meteorological conditions prevailed at the time and no flight plan was filed for the local flight. The aircraft was substantially damaged. The flight instructor was seriously injured, while the student pilot received minor injuries. The student pilot reported that the aircraft was trailing about 30 seconds behind two Life Flight helicopters (Bell 230 and BK 117) on final approach to runway 02. After the helicopters crossed over the airport boundary fence (about 500 feet before the end of the runway) they made a right turn for landing on the ramp. The student stated that he was on the controls at the time, and at about 100-150 feet above ground level and 60 knots, the aircraft suddenly rolled to the right about 90 degrees. The flight instructor took over the controls and righted the aircraft, however, it continued to settle to the ground in a nose down attitude. The aircraft collided with the ground about 200 feet short of the end of the runway and slid about 60 feet before coming to rest. In a written statement that was attached to the NTSB Pilot/Operator Aircraft Accident Report Form 6120.1/2, which was signed by the school director from Hillsboro Aviation, it indicated that, "It is believed wake turbulence from the helicopters may have contributed to the accident." The Federal Aviation Administration Inspector from the Portland-Hillsboro Flight Standards District Office responded to the accident site. The inspector reported that control continuity was established throughout the flight control system. No evidence of a mechanical failure or malfunction was found.