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.
Horton, OR
THE FORK CONNECTING THE ROTORCRAFT'S BLUE BLADE TO THE MAIN ROTOR HUB SEPARATED AFTER A LONG TERM FATIGUE CRACK HAD SPREAD THROUGH MORE THAN 60% OF THE FORK CIRCUMFERENCE. THE OPERATOR FAILED TO CARRY OUT THE APPROPRIATE INSPECTION OF THE FORK UNIT AS DELINEATED IN THE FAA AIRWORTHINESS DIRECTIVE DUE IN PART TO CONFUSION OVER THE WORDING OF THE AD COUPLED WITH THE MISPERCEPTION THAT THE FORK REQUIRED ONLY A VISUAL INSPECTION RATHER THAN A DYE PENETRANT CHECK. THE MISPERCEPTION OF THE TYPE OF INSPECTION WAS BORN OUT OF A BELIEF THAT THE ORIGINAL BLADE FORK WITH ITS TEN THOUSAND SERIES SERIAL NUMBER REQUIRED ONLY A VISUAL CHECK. THE INSTALLED BLADE FORK SERIAL NUMBER WAS NO LONGER EVIDENT ON THE PART AND MANUFACTURER RECORDS HAD BEEN LOST THUS PREVENTING THE OPERATOR FROM VERIFYING THE SERIAL NUMBER AND INSTITUTING THE NECESSARY INSPECTION. STRONG GUSTY WINDS EXISTED AT THE ACCIDENT SITE ASSOCIATED WITH FRONTAL PASSAGE AT THE TIME OF THE ACCIDENT.
THE FORK CONNECTING THE ROTORCRAFT'S BLUE BLADE TO THE MAIN ROTOR HUB SEPARATED AFTER A LONG TERM FATIGUE CRACK HAD SPREAD THROUGH MORE THAN 60% OF THE FORK CIRCUMFERENCE. THE OPERATOR FAILED TO CARRY OUT THE APPROPRIATE INSPECTION OF THE FORK UNIT AS DELINEATED IN THE FAA AIRWORTHINESS DIRECTIVE DUE IN PART TO CONFUSION OVER THE WORDING OF THE AD COUPLED WITH THE MISPERCEPTION THAT THE FORK REQUIRED ONLY A VISUAL INSPECTION RATHER THAN A DYE PENETRANT CHECK. THE MISPERCEPTION OF THE TYPE OF INSPECTION WAS BORN OUT OF A BELIEF THAT THE ORIGINAL BLADE FORK WITH ITS TEN THOUSAND SERIES SERIAL NUMBER REQUIRED ONLY A VISUAL CHECK. THE INSTALLED BLADE FORK SERIAL NUMBER WAS NO LONGER EVIDENT ON THE PART AND MANUFACTURER RECORDS HAD BEEN LOST THUS PREVENTING THE OPERATOR FROM VERIFYING THE SERIAL NUMBER AND INSTITUTING THE NECESSARY INSPECTION. STRONG GUSTY WINDS EXISTED AT THE ACCIDENT SITE ASSOCIATED WITH FRONTAL PASSAGE AT THE TIME OF THE ACCIDENT.