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.
Fulton, KY
According to the pilot, he departed on a local flight to another airport. At that airport, the pilot performed a "touch-and-go" landing and did not use the brakes. Upon returning to first airport, the pilot landed normally, except that when he applied the brakes, they did not work. The pilot attempted to abort the landing and applied full power. The airplane departed the end of the runway and impacted a ravine. Upon impact, the airplane "flipped on it's back." Due to the fact that the airplane had sustained significant impact damage, and had been moved from the accident site prior to examination, it could not determine if or how the brakes failed.
The malfunction of the brake system and the pilot's delay in aborting the landing.
On July 25, 2003, about 1950 central daylight time, an Aero-Commander 100, N4103X, was destroyed when it impacted a ravine and nosed over during an aborted landing at Fulton Airport (1M7), Fulton, Kentucky. The certificated private pilot received minor injuries and the passenger was not injured. Visual meteorological conditions prevailed, and the airplane was not operating on a flight plan. The local personal flight was conducted under 14 CFR Part 91. According to the pilot, during the taxi and engine run-up the brakes were working properly. About 1900, he departed Fulton Airport for Everett-Stewart Airport (UCY), Union City, Tennessee. At Union City, the pilot performed a "touch-and-go" landing but did not use the brakes. Upon returning to Fulton, the pilot landed normally on runway 27, except that "the aircraft seemed to not want to settle to the runway." When the pilot applied the brakes, they did not work. The pilot also tried pumping the brakes to no avail. The pilot attempted to abort the landing and applied full power. The airplane departed the end of the runway and impacted a ravine. Upon impact, the airplane "flipped on it's back." The pilot unlatched his passenger's seatbelt and they both exited the airplane. Two Federal Aviation Administration (FAA) inspectors examined the airplane after it had been removed from the accident site. The inspectors noted that one of the brake's disc pads was missing, and was never located. Due to the fact that the airplane had sustained significant impact damage, and had been moved from the accident site, they could not determine if or how the brakes failed. A review of the airplane's maintenance history revealed no discrepancies or recent work to the breaks. Runway 27 at Fulton Airport was an asphalt runway 2,700 feet long and 60 feet wide. According to the pilot, the winds at the time of the accident were calm.