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
According to the pilot, on short final approach in his low performance airplane, he realized that his approach path was too high, so he attempted to go around. After full engine power was applied, he recognized that he had insufficient distance from the approaching trees and terrain to perform a go-around. Therefore, he aborted the maneuver and forced the airplane onto the ground in a clearing beyond the departure end of the runway. The airplane impacted the ground hard, breaking the wing and fuselage structure. The pilot reported that he was unfamiliar with the airport, and he had not read the Federal Aviation Administration’s published remarks for the airport in its Airport Facility Directory. The remarks state, in part, that the airport is recommended for use by “mountain proficient pilots using high performance aircraft.” It also states “no go-around due to rising terrain and trees.” Nine-thousand foot mountains are located within 5 miles from northwest through southeast of the 5,500-foot mean sea level airport.
The pilot’s misjudgment of his final approach path. Contributing to the accident was the pilot’s inadequate preflight planning.
According to the pilot, on short final approach to runway 34 in his 145-horsepower Cessna 172F, he realized that his approach path was too high, so he attempted to go around. After full engine power was applied, he recognized that he had insufficient distance from the approaching trees and terrain to perform a go-around. Therefore, he aborted the maneuver and forced the airplane onto the ground in a clearing beyond the departure end of the runway. The airplane impacted the ground hard, breaking wing and fuselage structure. The pilot reported to the National Transportation Safety Board investigator that he was unfamiliar with the airport, and he had not read the Federal Aviation Administration’s published remarks for the airport in its Airport Facility Directory. The remarks state, in pertinent part, that the airport is recommended for use by “mountain proficient pilots using high performance aircraft.” It also states “no go-around due to rising terrain and trees.” Nine thousand foot mountains are located within 5 miles from northwest through southeast of the 5,500-foot mean sea level airport.