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.
Sherrill, AR
While on the final leg of a solo cross-country flight, approximately 1 mile from the airport, the airplane's engine lost power. The student pilot initiated a forced landing to a cornfield. During the forced landing, the airplane impacted cornstalks, the terrain, and came to rest upright in a field. The pilot stated "[visual] examination [revealed] that fuel exhaustion [caused the accident]." The engine was test run on the airframe and ran at various power settings for approximately 2 minutes with no anomalies noted.
the pilot's inadequate in-flight planning/decision which resulted in the loss of engine power due to fuel exhaustion.
On July 9, 2004, approximately 1420 central daylight time, a Cessna 150M, single engine airplane, N8959U, sustained substantial damage when it impacted terrain during a forced landing following a loss of engine power during cruise flight near Sherrill, Arkansas. The student pilot, who was the sole occupant, was not injured. The airplane was registered to and operated by a private individual. Visual meteorological conditions prevailed, and a flight plan was not filed for the Title 14 Code of Federal Regulations Part 91 instructional flight. The cross-country flight departed Stuttgart Municipal Airport, Stuttgart, Arkansas, approximately 1345, and was destined for Sherrill. According to the pilot, he had departed Smith's International Airport (99A), Sherrill, Arkansas, to complete a solo cross-country flight. During the cross-county flight, the pilot landed the airplane at two other airports and had flown for approximately 2 hours and 15 minutes. While on the final leg of a solo cross-country, approximately 1 mile from the airport, the engine began to "sputter and cut out." Shortly thereafter, the airplane's engine lost total power. The student pilot initiated a forced landing to a cornfield. During the forced landing, the airplane impacted cornstalks and terrain, and came to rest upright in a field. The pilot stated "[visual] examination [revealed] that fuel exhaustion [caused the accident]." The pilot did not refuel the airplane prior to departure from 99A or during the cross-country flight, and it was not determined how much fuel was on-board at the time of the departure from 99A. A Federal Aviation Administration (FAA) inspector, who responded to the accident site, reported the aft fuselage was buckled, the nose landing gear was separated, and the firewall was bent. The inspector observed "minimal" fuel in both main fuel tanks, and no damage was noted on the propeller. The airplane was recovered for further examination. On July 27, 2004, under the supervision of an FAA inspector, at the facilities of Dawson Aircraft, Clinton, Arkansas, the engine was test run on the airframe. According to the inspector, some oil was added prior to the engine test run. The engine started on the first attempt, and a magneto check was performed. The engine ran at various power settings for approximately 2 minutes with no anomalies noted.