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.
Bend, OR
According to the pilot, during the initial takeoff climb from runway 34, he noticed that the "controls felt sluggish compared to normal precise feeling of the gyroplane." He decided to execute a 180 degree turn back to the taxiway parallel to the runway. As soon as he began a shallow turn to the right, the gyroplane entered "a very steep diving spiral turn," and the controls "seemed totally ineffective." The gyroplane continued to descend and turn until it impacted a road running perpendicular to the runway about 50 feet north of the departure end. The pilot reported that the "cause of control malfunction is uncertain."
The malfunction of the flight controls for an undetermined reason, which resulted in a loss of control and in-flight collision with terrain.
On September 18, 2005, about 1215 Pacific daylight time, an Eiland RAF-2000 Gyro amateur-built experimental gyroplane, N4416N, collided with terrain in an uncontrolled descent following a loss of control on takeoff from Bend Municipal Airport, Bend, Oregon. The gyroplane sustained substantial damage. The private pilot sustained minor injuries, and the passenger was not injured. The gyroplane was registered to and operated by the pilot. Visual meteorological conditions prevailed for the 14 CFR Part 91 local personal flight, and no flight plan was filed. The flight was originating at the time of the accident. According to the pilot, during the initial takeoff climb from runway 34, he noticed that the "controls felt sluggish compared to normal precise feeling of the gyroplane." He decided to execute a 180 degree turn back to the taxiway parallel to the runway. As soon as he began a shallow turn to the right, the gyroplane entered "a very steep diving spiral turn," and the controls "seemed totally ineffective." The gyroplane continued to descend and turn until it impacted a road running perpendicular to the runway about 50 feet north of the departure end. The pilot reported that the "cause of control malfunction is uncertain."