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.
Fullerton, CA
After entering the downwind leg for runway 24, the local controller instructed the flight to extend the downwind leg. Three minutes later, when the airplane was about 4 miles east of the airport, the local controller cleared the flight to turn base followed by a clearance to land. The prevailing visibility was about 4 miles with haze. The pilot was unable to see the airport because of the sun glare mixed with the haze and used the localizer for guidance to the airport. The pilot maintained the base leg altitude until he could readily identify the runway which he did when the airplane was about a mile east of the airport. The pilot immediately began the descent, but when he flared the airplane for landing it began to float. The airplane touched down beyond midfield, bounced three times and the pilot applied hard braking. The airplane swerved to the right, exited the runway, and collided with the fence that traverses north and south at the airport boundary.
WAS THE PILOT'S POORLY PLANNED APPROACH. CONTRIBUTING TO THIS ACCIDENT WAS THE PREVAILING HAZE/SMOKE, THE PILOT'S FAILURE TO ATTAIN A PROPER GLIDEPATH, PROPER TOUCH DOWN POINT AND EXCESSIVE FINAL APPROACH AIRSPEED.
AFTER ENTERING THE DOWNWIND LEG FOR RUNWAY 24, THE LOCAL CONTROLLER INSTRUCTED THE FLIGHT TO EXTEND THE DOWNWIND LEG. THREE MINUTES LATER, WHEN THE AIRPLANE WAS ABOUT 4 MILES EAST OF THE AIRPORT, THE LOCAL CONTROLLER CLEARED THE FLIGHT TO TURN BASE FOLLOWED BY A CLEARANCE TO LAND. THE PREVAILING VISIBILITY WAS ABOUT 4 MILES WITH HAZE. THE PILOT WAS UNABLE TO SEE THE AIRPORT BECAUSE OF THE SUN GLARE MIXED WITH THE HAZE AND USED THE LOCALIZER FOR GUIDANCE TO THE AIRPORT. THE PILOT MAINTAINED THE BASE LEG ALTITUDE UNTIL HE COULD READILY IDENTIFY THE RUNWAY WHICH HE DID WHEN THE AIRPLANE WAS ABOUT A MILE EAST OF THE AIRPORT. THE PILOT IMMEDIATELY BEGAN THE DESCENT, BUT WHEN HE FLARED THE AIRPLANE FOR LANDING IT BEGAN TO FLOAT. THE AIRPLANE TOUCHED DOWN BEYOND MIDFIELD, BOUNCED THREE TIMES AND THE PILOT APPLIED HARD BRAKING. THE AIRPLANE SWERVED TO THE RIGHT, EXITED THE RUNWAY, AND COLLIDED WITH THE FENCE THAT TRAVERSES NORTH AND SOUTH AT THE AIRPORT BOUNDARY.