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.
Austin, TX
The flight had been vectored for runway 13R by approach control from the point of initial contact. It was then handed off to tower; there was no verbal coordination between approach and tower. A military transport helicopter executed an approach to the same runway ahead of the accident airplane, and terminated at about a 300-ft hover over the runway. The pilot of the accident airplane requested vectors for separation; tower responded separation '...should be just fine....' Shortly thereafter, while the airplane was over the threshold of runway 13R, the pilot requested confirmation that she was supposed to be behind the helicopter. The tower responded '...you were cleared to land on the left runway.' The pilot responded 'Okay understand we were one three right.' As the airplane was flaring, it encountered vortex turbulence from the helicopter and control was lost. The tower never issued the accident airplane a landing clearance to either runway, nor was a clearance to land requested by the pilot.
THE APPROACH CONTROLLER'S FAILURE TO PROPERLY SEQUENCE ARRIVING TRAFFIC, AND THE TOWER CONTROLLER'S FAILURE TO SEQUENCE AND SEPARATE LANDING TRAFFIC. FACTORS IN THE ACCIDENT WERE: THE PILOT'S FAILURE TO OBTAIN A LANDING CLEARANCE AND THE NIGHT LIGHT CONDITIONS.
THE FLT HAD BEEN VECTORED FOR RUNWAY 13R BY APPROACH CONTROL FROM THE POINT OF INITIAL CONTACT. IT WAS THEN HANDED OFF TO TOWER; THERE WAS NO VERBAL COORDINATION BETWEEN APPROACH & TOWER. A MILITARY TRANSPORT HELICOPTER EXECUTED AN APPROACH TO THE SAME RUNWAY AHEAD OF THE ACCIDENT AIRPLANE, AND TERMINATED AT ABOUT A 300-FT HOVER OVER THE RUNWAY. THE PILOT OF THE ACCIDENT AIRPLANE REQUESTED VECTORS FOR SEPARATION; TOWER RESPONDED SEPARATION '...SHOULD BE JUST FINE....' SHORTLY THEREAFTER, WHILE THE AIRPLANE WAS OVER THE THRESHOLD OF RUNWAY 13R, THE PILOT REQUESTED CONFIRMATION THAT SHE WAS SUPPOSED TO BE BEHIND THE HELICOPTER. THE TOWER RESPONDED '...YOU WERE CLEARED TO LAND ON THE LEFT RUNWAY.' THE PILOT RESPONDED 'OKAY UNDERSTAND WE WERE ONE THREE RIGHT.' AS THE AIRPLANE WAS FLARING, IT ENCOUNTERED VORTEX TURBULENCE FROM THE HELICOPTER AND CONTROL WAS LOST. THE TOWER NEVER ISSUED THE ACCIDENT AIRPLANE A LANDING CLEARANCE TO EITHER RUNWAY, NOR WAS A CLEARANCE TO LAND REQUESTED BY THE PILOT.