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.
Carpenteria, CA
The pilot took off in VMC conditions from an airport that is on the coast. The surrounding mountains a few miles inland had been obscured by clouds and low ceilings for several hours. About 15 minutes after takeoff, the pilot contacted an approach control facility to request visual flight rules flight following. About one minute after that first contact, the pilot started giving indications that he was having problems with the weather and with finding his exact position. Within about 3 1/2 minutes after the initial contact with the controller, the pilot said that he couldn't see 'anything'. That was his last known radio transmission. His transponder squawk code disappeared from the controller's radar screen at about the same time as the last known transmission. The controller asked the pilot several times if he was VMC or VFR. The pilot responded affirmatively every time. The aircraft collided with a mountain at about the 3,300 feet level.
1) INADEQUATE WEATHER EVALUATION BY THE PILOT, 2) POOR INFLIGHT DECISION TO TRY AND CONTINUE VMC FLIGHT, AND 3) THE PILOT'S LACK OF TOTAL EXPERIENCE.
THE PILOT TOOK OFF IN VMC CONDITIONS FROM AN AIRPORT THAT IS ON THE COAST. THE SURROUNDING MOUNTAINS A FEW MILES INLAND HAD BEEN OBSCURED BY CLOUDS AND LOW CEILINGS FOR SEVERAL HOURS. ABOUT 15 MINUTES AFTER TAKEOFF, THE PILOT CONTACTED AN APPROACH CONTROL FACILITY TO REQUEST VISUAL FLIGHT RULES FLIGHT FOLLOWING. ABOUT ONE MINUTE AFTER THAT FIRST CONTACT, THE PILOT STARTED GIVING INDICATIONS THAT HE WAS HAVING PROBLEMS WITH THE WEATHER AND WITH FINDING HIS EXACT POSITION. WITHIN ABOUT 3 1/2 MINUTES AFTER THE INITIAL CONTACT WITH THE CONTROLLER, THE PILOT SAID THAT HE COULDN'T SEE 'ANYTHING'. THAT WAS HIS LAST KNOWN RADIO TRANSMISSION. HIS TRANSPONDER SQUAWK CODE DISAPPEARED FROM THE CONTROLLER'S RADAR SCREEN AT ABOUT THE SAME TIME AS THE LAST KNOWN TRANSMISSION. THE CONTROLLER ASKED THE PILOT SEVERAL TIMES IF HE WAS VMC OR VFR. THE PILOT RESPONDED AFFIRMATIVELY EVERY TIME. THE AIRCRAFT COLLIDED WITH A MOUNTAIN AT ABOUT THE 3,300 FEET LEVEL.