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.
Beaver, UT
The stall warning was activating 15 knots higher than it was supposed to while the airplane was in a climb. The pilot advised ARTCC that he was experiencing wind shear. He was told there was no reported wind shear in the area and to maintain 13,000 feet. The pilot was unable to maintain 13,000 feet, and descended to 12,000 feet, then to the minimum en route altitude of 11,000 feet. Unable to maintain this altitude, the pilot descended to 10,500 feet, cancelled his IFR flight plan, and descended further to 9,500 feet, at which point radio communications with ARTCC were lost. The airplane was yawing and "the ball (turn coordinator) was in the right side." The pilot held "full right aileron deflection to keep the [air]plane from turning." He attempted to make a precautionary landing at an airport. A left crosswind aided in keeping the airplane on track, but he was "unable to use the rudder to straighten out the [air]plane to land." At 100 feet above the ground, the pilot attempted a go-around. With flaps up, landing gear down, and full power applied, the airplane would not climb but descended slowly instead. The pilot made a forced landing in an open field 1 mile south of the airport. In the ensuing landing, both wings were damaged, the aft portion of the fuselage was wrinkled, and the main gear was torn off. An inspection of the aircraft after the accident disclosed no anomalies with the flight control system or the engine. Flight control continuity was confirmed.
the pilot's selection of unsuitable terrain on which to make a forced landing. Contributing factors were mountain waves (wind shear) and crosswind.
On June 1, 2002, approximately 1420 mountain daylight time, a Piper PA-28R-201, N171M, was substantially damaged when it struck terrain during a precautionary landing at Beaver, Utah. The private pilot received no injuries, but his passenger received minor injuries. Day visual meteorological conditions prevailed, and an IFR flight plan had been filed for the cross-country flight being conducted under Title 14 CFR Part 91. The flight originated in San Diego, California, at 0930 Pacific daylight time, and was en route to Logan, Utah. In an unsigned statement written in third person and submitted along with the accident report, the writer said the stall warning was activating 15 knots higher than it was supposed to while the airplane was in a climb. The pilot advised Los Angeles Air Route Traffic Control Center (ARTCC) that he was experiencing wind shear. ARTCC said there was no reported wind shear in the area and to maintain 13,000 feet. The pilot was unable to maintain 13,000 feet, and descended to 12,000 feet, then to the minimum en route altitude of 11,000 feet. Unable to maintain this altitude, the pilot descended to 10,500 feet, cancelled his IFR flight plan, and descended further to 9,500 feet, at which point radio communications with ARTCC were lost. A United Air Lines flight relayed communications between N171M and ARTCC. The writer said the airplane was yawing and "the ball (turn coordinator) was in the right side." The pilot held "full right aileron deflection to keep the [air]plane from turning." He attempted to make a precautionary landing on runway 13 at Beaver Municipal Airport. A left crosswind aided in keeping the airplane on track, but the pilot was "unable to use the rudder to straighten out the [air]plane to land." At 100 feet above the ground, the pilot attempted a go-around. With flaps up, landing gear down, and full power applied, the airplane would not climb but descended slowly instead. The pilot made a forced landing in an open field 1 mile south of the airport. In the ensuing landing, both wings were damaged, the aft portion of the fuselage was wrinkled, and the main gear was torn off. A statement given to the Beaver County Sheriff's Office was similar to the one submitted with the accident report. An inspection of the aircraft after the accident disclosed no anomalies with the flight control system or the engine. Flight control continuity was confirmed. Calm winds were recorded at Milford, Utah, located 21 miles west-northwest of the accident site, 26 minutes before the accident.