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.
Stanwood, WA
The pilot stated that he did not check his fuel level before a local flight because he was in a 'rush.' About 2 hours after departure, the airplane 'ran out of fuel' and the engine stopped producing power. During a forced landing, the airplane overran a suitable landing area, struck a fence, hit a stop sign, and came to a stop near a house.
failure of the pilot to perform an adequate preflight inspection, which led to fuel exhaustion and subsequent loss of engine power. A factor relating to the accident was: the pilot's failure to attain the proper touchdown point on suitable terrain during the forced landing.
On October 6, 1996, about 1545 Pacific daylight time, a Crouch Avid Mark IV home built airplane, operated by the owner/pilot, collided with a fence during an emergency landing and was substantially damaged near Stanwood, Washington. The emergency landing was precipitated by a loss of engine power during cruise. The commercial pilot and his passenger were not injured. Visual meteorological conditions prevailed and no flight plan had been filed. The personal flight departed from Arlington, Washington, and was conducted under 14 CFR 91. In a telephone interview with the Safety Board on the day of the accident, the pilot stated that he did not check his fuel level prior to departure because he was in a "rush." Shortly after departure, the airplane "ran out of fuel" and the engine stopped producing power. The pilot force landed the airplane on a road. During the landing, the airplane struck a fence and a stop sign and was substantially damaged. In a written statement provided by the pilot to the Safety Board (attached), the pilot stated: After almost 2 hours of flying around the area, the engine suddenly sputtered and quit. I tried to restart, but it wouldn't.... I had run out of gas. I set up for an emergency landing, picked out what looked like a suitable field, and headed for it. On final approach, the airplane hit an up-draft at the approach end of the field, went up slightly, and then continued down. It remained in ground effect, and wouldn't settle to land. By the time it finally touched down, we had run out of field, and couldn't stop before running through the fence at the end of the field, crossed the road, and ended up in the yard of the house across the street.