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.
Casper, WY
While on a personal cross-country flight, the pilot spent time circumnavigating thunderstorms and experienced a complete loss of power due to fuel exhaustion. He conducted a forced landing in a field which was rough and uneven. There was a road beside the field which was suitable to use as a runway for his emergency landing. The aircraft sustained substantial damage to the underside of the fuselage during the forced landing. The pilot did not have a multiengine rating, was inexperienced in the aircraft, and his last biennial flight review was conducted in a single engine aircraft 17 years prior to the accident.
The pilot's improper in-flight planning and decision making by selecting an inadequate landing area for an emergency landing when a suitable landing area was available. Factors were fuel exhaustion, inaccurate preflight planning, and lack of recent experience.
On June 26, 1998, at 1500 mountain daylight time, a Piper PA-23-160, N4132P, sustained substantial damage during a forced landing 18 miles north of Casper, Wyoming. The private pilot and his passenger were not injured. Visual meteorological conditions prevailed for this personal flight being conducted under Title 14 CFR Part 91, and no flight plan was filed. The flight departed Watertown, South Dakota, at 1100 with a reported destination of Casper. According to the pilot, he spent a considerable amount of time avoiding thunderstorms en route and exhausted his fuel supply. The pilot said when both engines lost power, he conducted a forced landing in a field. Due to rough terrain both propellers were bent, an antenna was damaged on the underside of the aircraft, and structural damage was sustained to the underside of the fuselage. The FAA (Federal Aviation Administration) inspector who went to the scene stated there was an unobstructed straight road beside the field where the pilot conducted his forced landing. According to the inspector, the road could have been used for the landing. According to the pilot's accident report, he did not receive a weather brief. He stated he checked the weather using the internet prior to departure from Watertown. According to FAA records, the pilot did not posses a multiengine rating. The pilot indicated the same in his report of the accident and, in addition, the pilot provided information that his last biennial flight review was March 11, 1982. According to the information supplied by the pilot, his total flight time was 400 hours. He said his flight time in make and model was 20 hours, all of which occurred in the last 30 days.