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.
Pacific City, OR
At the end of a cross country pleasure flight, the pilot set-up for a landing on runway 14. While on downwind, the pilot noted that the wind sock was limp, so he decided to make a 180 degree turn and land on runway 32. After the airplane touched down, the pilot felt the airplane being pushed by a tailwind. The airplane became airborne and the pilot forced the airplane back to the runway. The pilot applied brakes; however, the airplane began to skid. Seeing that he was running out of runway to stop, and anticipating an accident, the pilot applied full power to clear a two foot fence at the end of the runway, and a public road that runs perpendicular to the runway; however, the left horizontal stabilizer contacted the fence. The airplane continued over the road and the left wing contacted, and was separated by, a car parked next to a building approximately 100 feet from the end of the runway. The airplane continued along the side of the building, contacting the northeast corner. The airplane then came to rest on its left side.
THE PILOT SELECTED THE WRONG RUNWAY RELATIVE TO THE WIND AND THEN DELAYED IN ABORTING THE LANDING. THE TAILWIND WAS A FACTOR.
AT THE END OF A CROSS COUNTRY PLEASURE FLIGHT, THE PILOT SET-UP FOR A LANDING ON RUNWAY 14. WHILE ON DOWNWIND, THE PILOT NOTED THAT THE WIND SOCK WAS LIMP, SO HE DECIDED TO MAKE A 180 DEGREE TURN AND LAND ON RUNWAY 32. AFTER THE AIRPLANE TOUCHED DOWN, THE PILOT FELT THE AIRPLANE BEING PUSHED BY A TAILWIND. THE AIRPLANE BECAME AIRBORNE AND THE PILOT FORCED THE AIRPLANE BACK TO THE RUNWAY. THE PILOT APPLIED BRAKES; HOWEVER, THE AIRPLANE BEGAN TO SKID. SEEING THAT HE WAS RUNNING OUT OF RUNWAY TO STOP, AND ANTICIPATING AN ACCIDENT, THE PILOT APPLIED FULL POWER TO CLEAR A TWO FOOT FENCE AT THE END OF THE RUNWAY, AND A PUBLIC ROAD THAT RUNS PERPENDICULAR TO THE RUNWAY; HOWEVER, THE LEFT HORIZONTAL STABILIZER CONTACTED THE FENCE. THE AIRPLANE CONTINUED OVER THE ROAD AND THE LEFT WING CONTACTED, AND WAS SEPARATED BY, A CAR PARKED NEXT TO A BUILDING APPROXIMATELY 100 FEET FROM THE END OF THE RUNWAY. THE AIRPLANE CONTINUED ALONG THE SIDE OF THE BUILDING, CONTACTING THE NORTHEAST CORNER. THE AIRPLANE THEN CAME TO REST ON ITS LEFT SIDE.