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.
Temple City, CA
A twin Cessna collided with a single engine Cessna from the single engine Cessna's 7 o'clock position. The single engine Cessna crashed and the twin Cessna landed without further incident. Both airplanes were conducting visual flight rules personal flights to Van Nuys, CA. The single engine Cessna 172 was receiving traffic advisories from Burbank TRACON. The twin engine Cessna had departed Fullerton and was flying a circuitous route to Van Nuys in order to avoid the airport radar service area. The single engine Cessna was transponder equipped but without Mode C capability. The twin engine Cessna was equipped with, and using, a transponder with Mode C capability. The radar data study revealed that the twin engine Cessna was displayed on the controller's radar scope for about 4 minutes before the collision. The controller did not warn the single engine Cessna pilot of the converging traffic. The TRACON was not programmed to alert the controller of a conflict between a tracked (C-172) and untracked (C-411) target.
PILOT OF N63CA IMPROPER VISUAL LOOK-OUT. CONTRIBUTING TO THIS ACCIDENT WAS THE CONTROLLER'S FAILURE TO OBSERVE THE FASTER MOVING AIRPLANE APPROACHING THE SINGLE ENGINE CESSNA FROM THE REAR.
A TWIN CESSNA COLLIDED WITH A SINGLE ENGINE CESSNA FROM THE SINGLE ENGINE CESSNA'S 7 O'CLOCK POSITION. THE SINGLE ENGINE CESSNA CRASHED AND THE TWIN CESSNA LANDED WITHOUT FURTHER INCIDENT. BOTH AIRPLANES WERE CONDUCTING VISUAL FLIGHT RULES PERSONAL FLIGHTS TO VAN NUYS, CA. THE SINGLE ENGINE CESSNA 172 WAS RECEIVING TRAFFIC ADVISORIES FROM BURBANK TRACON. THE TWIN ENGINE CESSNA HAD DEPARTED FULLERTON AND WAS FLYING A CIRCUITOUS ROUTE TO VAN NUYS IN ORDER TO AVOID THE AIRPORT RADAR SERVICE AREA. THE SINGLE ENGINE CESSNA WAS TRANSPONDER EQUIPPED BUT WITHOUT MODE C CAPABILITY. THE TWIN ENGINE CESSNA WAS EQUIPPED WITH, AND USING, A TRANSPONDER WITH MODE C CAPABILITY. THE RADAR DATA STUDY REVEALED THAT THE TWIN ENGINE CESSNA WAS DISPLAYED ON THE CONTROLLER'S RADAR SCOPE FOR ABOUT 4 MINUTES BEFORE THE COLLISION. THE CONTROLLER DID NOT WARN THE SINGLE ENGINE CESSNA PILOT OF THE CONVERGING TRAFFIC. THE TRACON WAS NOT PROGRAMMED TO ALERT THE CONTROLLER OF A CONFLICT BETWEEN A TRACKED (C-172) AND UNTRACKED (C-411) TARGET.