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.
Pittsburg, OR
The pilot reported that he first over flew runway 12, which is 1,050 feet in length, and determined that the windsock was indicating calm wind. The approach for landing was made at 65 mph with full flaps extended. The aircraft touched down about 50 to 100 feet from the threshold. The pilot reported that "... it didn't look good for stopping so I initiated a go-around. Rotation was a split second too late and the aircraft contacted some brush at the very end of the strip." The pilot reported that there was something hard in the brush which struck the outboard leading edge of the right side horizontal stabilizer. The pilot continued the flight to his destination and landed without further incident. Inspection of the right side horizontal stabilizer found a circular indentation to the outboard leading edge. Skin wrinkles were noted on the top and bottom surfaces.
The pilot's failure to maintain clearance from an object (pole) during an aborted landing. The pilot's delayed decision to abort the landing and a pole were factors.
On August 17, 2004, at 1800 Pacific daylight time, a Cessna 180J, N52096, registered to and operated by the pilot as a 14 CFR Part 91 personal flight, collided with a post during the aborted landing from Pittsburg Airport, Pittsburg, Oregon. Visual meteorological conditions prevailed at the time and no flight plan was filed. The aircraft was substantially damaged and the airline transport pilot and his passenger were not injured. The flight originated from Cottonwood, Idaho, about one hour prior to the accident. In a written statement, the pilot reported that he first over flew runway 12, which is 1,050 feet in length, and determined that the windsock was indicating calm wind. The approach for landing was made at 65 mph with full flaps extended. The aircraft touched down about 50 to 100 feet from the threshold. The pilot reported that "... it didn't look good for stopping so I initiated a go-around. Rotation was a split second too late and the aircraft contacted some brush at the very end of the strip." The pilot reported that there was something hard in the brush which struck the outboard leading edge of the right side horizontal stabilizer. The pilot continued the flight back to Cottonwood, stating that, "a lot of right rudder was required to center the ball and the elevator trim was inoperative." The aircraft landed without further incident at Cottonwood. Inspection of the right side horizontal stabilizer found a circular indentation to the outboard leading edge. Skin wrinkles were noted on the top and bottom surfaces.