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.
Philadelphia, MS
The pilot reported that the airplane touched down on the first third of the 4,000-foot-long asphalt runway. After touchdown he was unable to move the throttle control forward or back. He applied brake pressure; however, the airplane departed the end of the runway and struck a moving vehicle before stopping upright on a road. Postaccident examination of the airframe and engine, which included the throttle control, did not reveal evidence of mechanical malfunctions. There were no known witnesses to the landing and the airplane's touchdown point on the runway could not be determined. The reason for the throttle malfunction could not be determined.
A throttle control malfunction during landing for undetermined reasons, resulting in a runway overrun.
On July 26, 2010, about 1320 central daylight time, a Beech K35, N6035E, registered to a private individual, was substantially damaged while landing at Barrett Field (MS96), Philadelphia, Mississippi. The commercial pilot was not injured. Visual meteorological conditions prevailed and no flight plan was filed for the personal flight conducted under the provisions of 14 Code of Federal Regulations Part 91. The flight originated from the Monroe County Airport, Aberdeen, Mississippi. According to information provided by a Federal Aviation Administration (FAA) inspector, the pilot reported that the airplane was landing on runway 6, a 4,000-foot-long, by 70-foot-wide, asphalt runway, when he experienced a stuck throttle. The airplane touched down on the first one-third of the runway and the pilot was unable to move the throttle control forward or back. He applied brake pressure; however, the airplane departed the end of the runway, and struck a moving vehicle before stopping upright on a road. Both wings, the fuselage, and nose gear were substantially damaged. Examination of the airframe and engine by an FAA inspector who responded to the accident site did not reveal evidence of mechanical malfunctions. The throttle was observed in the aft position, and could be moved freely. There were no known witnesses to the landing and the airplane's touchdown point on the runway could not be determined.