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.
Johnson City, TN
The student pilot was returning to his home airport from a cross-country solo flight. The winds were favoring the opposite direction runway, and he touched down “a little fast” with 20º of flaps extended about 1,000 feet down the 3,000-foot-long runway. He applied the brakes and the airplane veered to the right (he thought the left brake had failed). He then shut off the carburetor heat, retracted the flaps, and added power to abort the landing with about 300 feet of pavement remaining. He was able to get airborne before the end of the runway but was in ground effect. The airplane flew over a road, impacted a tree with the right wing while airborne, hit a truck, and the corner of a detached garage. The airplane then rolled a short distance, nosed over, and came to rest. The airplane’s fuselage, wings, and empennage were substantially damaged during the accident sequence. Postaccident testing revealed that both the left and right wheel brakes were functional.
The student pilot’s excessive airspeed during the landing approach and his delayed remedial action, which resulted in the airplane striking obstacles during an aborted landing. Contributing was the pilot’s decision to land with a tailwind.
The student pilot was returning to his home airport from a cross-country solo flight. The winds were favoring the opposite direction runway, and he touched down “a little fast” with 20º of flaps extended about 1,000 feet down the 3,000-foot-long runway. He applied the brakes and the airplane veered to the right (he thought the left brake had failed). He then shut off the carburetor heat, retracted the flaps, and added power to abort the landing with about 300 feet of pavement remaining. He was able to get airborne before the end of the runway but was in ground effect. The airplane flew over a road, impacted a tree with the right wing while airborne, hit a truck, and the corner of a detached garage. The airplane then rolled a short distance, nosed over, and came to rest. The airplane’s fuselage, wings, and empennage were substantially damaged during the accident sequence. Postaccident testing revealed that both the left and right wheel brakes were functional.