Skip to content

Atlas / NTSB / FTW04LA027

NTSB CAROL · Event

Event FTW04LA027

2003-11-21 Sweetwater, Texas, United States Airport · SWW None 1 aircraft Status: Completed

Aircraft involved

Probable cause & findings

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.

Factual narrative

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. 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. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12

Verbatim from NTSB's published report. Source file NTSB_2003_FTW04LA027.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.

Related research

What the literature says.

Academic papers and agency reports matching this event's aircraft type or causal vocabulary (maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.

Browse the full corpus — academia portal ↗