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.
Yellow Pine, ID
The airplane was high and fast on the approach to the runway. When the pilot flared for landing, the airplane floated and he tried to force it on the ground. The airplane began to porpoise, contacting the ground twice before settling onto the runway for the third and final time. The pilot thought that the nose wheel was damaged when the airplane contacted the runway the second time, so he decided not to go around. The airplane sustained structural damage to the firewall. The pilot reported that there were no preimpact mechanical malfunctions or failures with the airframe or engine.
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Descent/approach/glide path-Not attained/maintained - C
In the pilot's written statement he reported that he was flying northbound in a canyon to land back to the south (runway 17). He said that while on the left downwind leg, at 5,800 feet, he turned "one ridge too soon, which put me a little high." He noted his airspeed as 70 miles per hour (mph); however, as he descended the airspeed increased to 90 mph. The pilot stated that the airspeed was fast, but he still had a lot of runway to work with. He decided to land and when he flared the airplane floated. Even though the airspeed was bleeding off, he tried to force the landing. After touchdown the airplane began to porpoise. On the second bounce, the nose wheel touched down first; he wasn't sure if it would be worse to take off with a damaged nose wheel or try to land. The third time it touched down, the pilot stated that he flew the airplane straight down the runway until it stopped on the right side of the runway. The airplane sustained structural damage to the firewall. The pilot reported that there were no preimpact mechanical malfunctions or failures with the airframe or engine. In the section titled RECOMMENDATION (How could this accident have been prevented) of the pilot's written report (NTSB Pilot/Operator Report, Form 6120.1), the pilot stated that he should have flown with a pilot familiar with the area, and he should have taken a course in mountain flying. The pilot also reported that when he knew that he was high, to go around and set up for a better approach.