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.
Council, ID
The pilot reported that the approach for landing was normal until touchdown, when the airplane bounced and became airborne. Prior to the second touchdown, a gust of wind hit the airplane, which weathervaned the airplane to the right. As the airplane touched down a second time, it traveled to the right. The pilot tried to correct with full left braking action, but the corrective action was unsuccessful and the airplane continued off the side of the runway, colliding with a dirt embankment. The wind conditions varied from calm to gusting conditions of varying intensity. The pilot reported that there were no mechanical failures or malfunctions with the airplane at the time of the accident.
The pilot's inadequate recovery from a bounced landing. Gusting wind conditions and a dirt bank adjacent to the runway edge were factors.
On August 10, 1999, approximately 1230 Pacific daylight time, a Cessna 180J airplane, N7739K, operated by Baker Aircraft Inc. of Baker City, Oregon, on a nonscheduled 14 CFR 135 air taxi flight, was substantially damaged in a ground loop on landing at Oxbow Airport, a private airport operated by the Idaho Power Company in the Hell's Canyon area of the Snake River northwest of Council, Idaho. The commercial pilot-in-command of the aircraft and his passenger, an employee of the Idaho Power Company, were uninjured. The accident flight was a local flight out of the Oxbow Airport for the purpose of conducting a game survey. The flight was receiving company flight following at the time of the accident. In a written statement, the pilot reported that upon returning to the airport, he flew along the east side of the canyon, traveling to the north to check the wind sock. The sock indicated a "slight" crosswind from the west. The pilot reversed course for landing to the south. The pilot reported that everything "appeared normal" until the touchdown, when the airplane bounced. When the airplane became airborne, a gust of wind from the west hit the airplane, which weathervaned to the right. The airplane touched down a second time and the airplane continued to the right. The pilot attempted to correct with full left braking action. The corrective action was unsuccessful and the airplane continued off the side of the runway, colliding with a dirt embankment. The airplane came to rest approximately 90 degrees to runway heading. The pilot reported on his NTSB accident report that no mechanical malfunction or failure was involved in the accident. According to an FAA inspector who responded to the accident scene, the winds at the time of the accident varied from calm to southerly gusts of unknown intensity. The FAA inspector reported that the landing on the north-south, 2,900 by 50 foot, asphalt runway was to the south (the runway slopes uphill in this direction.) The FAA inspector reported finding initial contact marks approximately 700 to 800 feet down the runway, and that the contact marks observed were indicative of a bounce on landing. He stated that the second set of runway contact marks continued for an additional 600 to 700 feet, then arced right (to the west). The aircraft came to rest with its tail blocking the runway surface. The FAA inspector reported that in his post-accident inspection of the aircraft, he found no evidence of preexisting mechanical problems with the aircraft. According to information about the airport obtained from the "AirNav" Internet airport and navigational aid database, the airport is located in the bottom of a deep narrow canyon.