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.
Rayville, LA
The airplane was flying level at 6,000 feet in dark night light conditions when the engine lost power. The pilot declared an emergency and received radar vectors to a nearby airport. During the ensuing forced landing, the pilot observed oil cover the front windscreen and sparks coming from beneath the engine cowling. He moved the mixture control to the idle/cut-off position and secured the engine. The airplane landed short of the airport, struck a fence, and came to rest upright. A review of airframe and engine maintenance records did not reveal any evidence of uncorrected maintenance discrepancies. The reason for the loss of engine power was not determined.
The loss of engine power for an undetermined reason, which resulted in a forced landing. A factor was the dark night light condition.
On March 13, 2000, at 2330 central standard time, a Siai-Marchetti S.205/22R airplane, was substantially damaged during a forced landing following a loss of engine power near Rayville, Louisiana. The airplane was registered to and operated by the instrument rated private pilot, sole occupant, who was not injured. Dark night visual meteorological conditions prevailed for the 14 Code of Federal Regulations Part 91 personal flight, for which an IFR flight plan was filed. The cross-country flight originated from the Montgomery Regional Airport, Montgomery, Alabama, and was destined for the Shreveport Regional Airport, Shreveport, Louisiana. According to the pilot, the airplane was flying level at 6,000 feet agl. when he felt an "extreme vibration," followed by a partial loss of engine power, and subsequently, oil appeared on the front windscreen. The pilot declared an emergency to the Fort Worth Air Route Traffic Control Center and was provided radar vectors to the John H. Hooks Jr. Memorial Airport, Rayville, Louisiana. The airplane was descending through 4,000 feet when the pilot observed "sparks" coming from beneath the engine cowling. At 1,300 feet the pilot moved the mixture control to the idle/cut-off position and secured the engine. The airplane touched down short of the runway, struck a fence, and came to a stop upright. The pilot added that during the preflight examination, prior to the accident flight, he confirmed that the engine oil level was normal. An FAA inspector examined the airplane and stated that the right wing spar was structurally damaged. A review of the airplane's airframe and engine maintenance records revealed that the airframe had accumulated a total of 1,940.0 hours at the time of the accident and underwent its most recent annual inspection on March 8, 2000. The airplane was equipped with a 220-horsepower Franklin 6A-350-CIR engine. The engine had accumulated a total of 240.6 hours since major overhaul at the time of the accident, and underwent its most recent 100-hour inspection on March 8, 2000, 15.8 hours prior to the accident. A review of the maintenance records did not reveal evidence of any uncorrected maintenance discrerpancies. The reason for the loss of engine power was not determined.