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, NY
THE HELICOPTER WAS IN CRUISE FLIGHT WHEN A SUDDEN LOSS OF TAIL ROTOR EFFECTIVENESS OCCURRED. THE PILOT STATED THAT HE APPLIED ANTI-TORQUE PEDAL WITH NO EFFECT. THE PILOT ENTERED AN AUTOROTATION AND THE HELICOPTER CONTINUED IN A SLOW SPIN TO THE LEFT. THE PILOT STATED THAT HE UTILIZED FULL UP COLLECTIVE JUST PRIOR TO TOUCHDOWN, BUT THE HELICOPTER ROLLED ONTO ITS LEFT SIDE AFTER GROUND CONTACT AND WAS SUBSTANTIALLY DAMAGED. AN EXAMINATION OF THE WRECKAGE REVEALED THAT THE FORWARD TAIL ROTOR DRIVE BELT FAILED. THE PLIES ON THE BELT HAD SEPARATED. THE BELT HAD BEEN REPLACED AT THE LAST INSPECTION, AND HAD ACCUMULATED 57.9 HOURS SINCE NEW. THE CHANGE-OUT TIME FOR THE BELT AS RECOMMENDED BY THE COMPANY THAT PROVIDED THE KIT WAS 250 HOURS. A NEWER KEVLAR DRIVE BELT WAS RECOMMENDED BY THE COMPANY AFTER THE ACCIDENT. NO DISCREPANCIES OR UNRESOLVED OPEN ITEMS WERE FOUND IN THE MAINTENANCE LOG BOOKS.
THE FAILURE OF THE TAIL ROTOR DRIVE BELT DUE TO UNDETERMINED REASONS. THIS LED TO A LOSS OF DIRECTIONAL CONTROL AND AN AUTOROTATION.
On June 12, 1994, at 1620 eastern daylight time, N727TB, a Bellah Rotorway Executive home built helicopter, operated by the owner/pilot, impacted terrain in Johnson City, New York, and was substantially damaged during an uncontrolled descent. The descent was precipitated by a loss of control during cruise flight. The commercial pilot, the sole occupant, received minor injuries. Visual meteorological conditions prevailed and a flight plan was not filed. The personal flight was conducted under 14 CFR 91, and departed from Norwich, New York. According to the pilot, the helicopter was in cruise flight at an altitude of 2,300 feet when a sudden loss of tail rotor effectiveness occurred. The pilot stated that he applied anti-torque pedal with no effect. The pilot entered an autorotation and advised air traffic control of his situation. The helicopter continued in a "...slow spin or spiral to the left." The pilot stated that he utilized full up collective which provided "good cushioning action," but the helicopter rolled onto its left side after ground contact. The main rotor blades, tail boom, landing skids, and fuselage frame were damaged. According to an FAA Aviation Safety Inspector from Rochester, New York, an examination of the wreckage revealed that the forward tail rotor drive belt had failed. The belt was examined and its plies were separated and "shredded." The pilot reported that the belt had been replaced during the last annual inspection, and had accumulated 57.9 hours since new. The recommended change out time by the Rotorway International company for the belt was 250 hours. The pilot reported that the company subsequently recommended a new Kevlar-impregnated drive belt. No discrepancies or unresolved open items were found in the maintenance log books.