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.
Atlanta, ID
The plot landed on the last half of the 2,900-foot-long grass runway and was unable to bring the airplane to a stop before it ran off the end of the runway and into trees. Prior to going to the airport, the pilot had spoken with local area pilots who indicated that he should not use the first half of the runway because it was muddy and soft. The pilot indicated that the airplane and engine had no mechanical failures or malfunctions during the flight. The Federal Aviation Administration Airport/Facility Directory for the airport states in part, " that the lower 1/3 of the runway is soft and unusable during the early spring. " The performance section landing distance charts of the Cessna 180 Owners Manual listed a total landing distance of 1,842 over a 50-foot obstacle, with a 847-foot ground roll (chart correction factors applied for grass runway surface and no wind).
The pilot's misjudged speed and distance during the intentional touchdown in the last half of the runway, which resulted in a landing overrun. Contributing to the accident was the muddy runway condition.
In the pilot's written statement, he reported speaking with local area pilots prior to going to the accident airport to obtain the general conditions for the airport environment. The local area pilots told him not to land on the first half of the runway due to muddy conditions. Upon arrival, the pilot overflew the airport prior to landing. He noted two parked airplanes, with one of the them parked so that a wing was near the runway. He completed the traffic pattern and landed right after the parked airplanes. He was not able to stop the airplane and it overran the runway and impacted small trees about 50 feet from the end of the runway. The pilot indicated that the airplane and engine had no mechanical failures or malfunctions during the flight. In the remarks section of the Federal Aviation Administration Airport/Facility Directory for Graham United States Forest Service Airport (U45), Atlanta, Idaho, it states that the lower 1/3 of runway 18/36 is soft and unusable during the early spring. The runway is 2,900 feet in length and 50 feet wide.