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.
Traer, IA
The airplane was substantially damaged when it departed the runway (2,555 feet by 100 feet, turf) during landing and encountered an irrigation ditch. The pilot reported that after takeoff he intended to track a Very-High-Frequency Omni Range (VOR) navigation station to an intermediate fuel stop before continuing to his final destination. About 4 hours into the flight he attempted to contact air traffic control in order to verify his position; however, he was unable to establish contact. At that point, he began "to lose confidence in [his] present position" and decided to establish a heading he believed was toward his intermediate fuel stop. After an additional hour of flight, he became concerned about his remaining fuel and contacted a Flight Service Station (FSS). He informed them that he was "lost and short on fuel." The FSS located the flight and provided vectors to a nearby alternate airport. Upon landing at the alternate airport "the aircraft went into a skid, hit a runway cone and came to a stop across from the end of the runway. Just a few feet beyond [an] irrigation ditch." The pilot noted that he did not have experience landing on grass runways. The pilot did not indicate any failures or malfunctions associated with the aircraft's flight control system or engine. He did note the possibility of an "intermittent radio transmission failure" as a possible factor contributing to his becoming lost prior to the accident.
The pilot's failure to maintain control of the airplane during landing on the grass airstrip. A contributing factor was the pilot's limited experience operating on grass runways. Additional factors were the runway cone struck during landing and the irrigation ditch encountered during the runway excursion.
The airplane was substantially damaged when it departed runway 17 (2,555 feet by 100 feet, turf) during landing and encountered an irrigation ditch. The pilot reported that after takeoff he intended to track a Very-High-Frequency Omni Range (VOR) navigation station to an intermediate fuel stop before continuing to his final destination. About 4 hours into the flight he attempted to contact air traffic control in order to verify his position; however, he was unable to establish contact. At that point, he began "to lose confidence in [his] present position" and decided to establish a heading he believed was toward his intermediate fuel stop. After an additional hour of flight, he became concerned about his remaining fuel and contacted a Flight Service Station (FSS). He informed them that he was "lost and short on fuel." The FSS located the flight and provided vectors to a nearby alternate airport. Upon landing at the alternate airport "the aircraft went into a skid, hit a runway cone and came to a stop across from the end of the runway. Just a few feet beyond [an] irrigation ditch." The pilot noted that he did not have experience landing on grass runways. The pilot did not indicate any failures or malfunctions associated with the aircraft's flight control system or engine. He did note the possibility of an "intermittent radio transmission failure" as a possible factor contributing to his becoming lost prior to the accident.