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.
Sweetwater, TX
During cruise flight, the engine lost power and the airplane impacted the terrain short of the alternate airport. The 123-hour private pilot stated the engine "suddenly stopped producing power." He attempted to restart the engine; however, he was not successful. During the forced landing, "strong surface winds came up," and the airplane impacted the terrain approximately 450 feet short of the runway. The airplane then struck trees, a fence, two poles and came to rest on the runway surface. Examination of the engine revealed the crankshaft bolt and crankshaft dowel pin had fractured and failed. The bolt fracture surfaces displayed signatures consistent with fatigue. At the time of the accident, the engine had accumulated approximately 576 hours since major overhaul.
the loss of engine power due to a failure of the crankshaft bolt. A contributing factor was the lack of suitable terrain for the forced landing.
On November 21, 2003, approximately 0800 central standard time, a Piper PA-28-235 single-engine airplane, N56318, sustained substantial damage during a forced landing following a loss of engine power while in cruise flight near Sweetwater, Texas. The private pilot and his passenger were not injured. The airplane was registered to Master Plumbers LLC, Hobbs, New Mexico, and operated by the pilot. Visual meteorological conditions prevailed, and a flight plan was not filed for the 14 Code of Federal Regulations Part 91 personal flight. The flight departed the Lea County Regional Airport, near Hobbs, New Mexico, at 0610, and was destined for Abilene, Texas. The 123-hour pilot stated that during the flight, approximately 7 to 9 nautical miles west of Avenger Field Airport (SWW), near Sweetwater, the engine "suddenly stopped producing power." The pilot attempted to restart the engine; however, was not successful. During the forced landing to SWW, "strong surface winds came up," and the airplane impacted the terrain approximately 450 feet short of the runway. According to a Federal Aviation Administration (FAA) Inspector who responded to the accident site, after impacting the terrain, the airplane struck trees, a fence, two poles and came to rest on the runway surface. The inspector stated the fuselage was twisted, and the horizontal stabilizer sustained structural damage. At the accident site, the inspector rotated the engine crankshaft by hand and continuity to the accessories and valve train was not established. The airframe and engine were recovered for further examination. On December 10, 2003, under the supervision of an FAA Inspector, the Lycoming O-540-B4B5 engine, serial number L-15593-40, was disassembled for examination. Examination of the engine revealed the crankshaft bolt and crankshaft dowel pin had fractured and failed. The bolt fracture surfaces displayed signatures consistent with fatigue. A review of the engine maintenance records revealed the engine underwent a major overhaul, dated October 21, 1988, at 1,762.15 hours total time. The most recent annual inspection on the engine was completed on May 20, 2003, at a total time of 494.8 hours since major overhaul. At the time of the accident, the engine had accumulated approximately 576 hours since major overhaul. Review of the maintenance records revealed no evidence of any uncorrected maintenance discrepancies.