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.
Glendale, AZ
THE USAF KC-135 WAS ON AN IFR FLT PLAN & EXECUTING A TACAN 3L APCH TO LUKE AFB. THE AA-1 HAD DEPARTED SKY HARBOUR ARPT &HAD BEEN RELEASED BY PHOENIX TRSA. THE AA-1 WAS HEADING WESTERLY IN AIRSPACE DESIGNATED AS A SPECIAL TRAFFIC AREA & WAS REQUIRED TO HAVE BEEN AT OR BELOW 2,000 FT MSL. A PLT OF ANOTHER ACFT WHO WAS TRAILING THE AA-1 STATED THAT A LOW BROKENCLOUD COVER WAS ENCOUNTERED & HE HAD TO DESCEND TO ABOUT 2,000 FT TO REMAIN 500 FT BELOW THE BASES. HE STATED THE PLT OFTHE AA-1 DID NOT DESCEND BUT APPEARED TO BE SKIMMING ALONG IN & OUT OF THE BASES OF THE CLOUDS. HE NOTICED THE KC-135 DESCENDING THROUGH THE CLOUD DECK FOLLOWED IMMEDIATELY BY THE COLLISION. THE COLLISION OCCURRED ABOUT 5 MI SOUTH OF LUKE AFB AT AN ALTITUDE OF 2,500 FT MSL. THE LOGBOOK OF THE AA-1 PLT INDICATES THIS WAS HIS FIRST TRIP TO THE PHOENIX AREA. LUKE AFB WAS DEPICTED ON THE NORTH SIDE OF THE SECTIONAL CHART ONLY. VOR AIRWAY #16 WAS SPLIT ALONG AN E-W LINE WITH THE NORTHERN & SOUTHERN HALVES BEING DEPICTED ON EACH SIDE OF THE CHART.
THE USAF KC-135 WAS ON AN IFR FLT PLAN & EXECUTING A TACAN 3L APCH TO LUKE AFB. THE AA-1 HAD DEPARTED SKY HARBOUR ARPT &HAD BEEN RELEASED BY PHOENIX TRSA. THE AA-1 WAS HEADING WESTERLY IN AIRSPACE DESIGNATED AS A SPECIAL TRAFFIC AREA & WAS REQUIRED TO HAVE BEEN AT OR BELOW 2,000 FT MSL. A PLT OF ANOTHER ACFT WHO WAS TRAILING THE AA-1 STATED THAT A LOW BROKENCLOUD COVER WAS ENCOUNTERED & HE HAD TO DESCEND TO ABOUT 2,000 FT TO REMAIN 500 FT BELOW THE BASES. HE STATED THE PLT OFTHE AA-1 DID NOT DESCEND BUT APPEARED TO BE SKIMMING ALONG IN & OUT OF THE BASES OF THE CLOUDS. HE NOTICED THE KC-135 DESCENDING THROUGH THE CLOUD DECK FOLLOWED IMMEDIATELY BY THE COLLISION. THE COLLISION OCCURRED ABOUT 5 MI SOUTH OF LUKE AFB AT AN ALTITUDE OF 2,500 FT MSL. THE LOGBOOK OF THE AA-1 PLT INDICATES THIS WAS HIS FIRST TRIP TO THE PHOENIX AREA. LUKE AFB WAS DEPICTED ON THE NORTH SIDE OF THE SECTIONAL CHART ONLY. VOR AIRWAY #16 WAS SPLIT ALONG AN E-W LINE WITH THE NORTHERN & SOUTHERN HALVES BEING DEPICTED ON EACH SIDE OF THE CHART.