ATL97LA142
1997-09-27 · WINSTON-SALEM, North Carolina, United States · None · 1 aircraft · Status: Completed
Airport INT
Current FAA registration · N331DP
- Make / Model
- BEECH 35-C33
- Year of manufacture
- 1965 · 32 years old at event
- Engine
- CONT MOTOR I0-470 SERIES (260 hp)
- Seats / Engines
- 4 seats · 1 engine
- Last airworthiness date
- 19650824
- ADS-B equipped
- Yes — Mode-S A399DF
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
the pilot's improper planning/decision, which resulted in fuel exhaustion, loss of engine power, and a forced landing.
Factual narrative
On September 27, 1997, at 1710 eastern daylight time, a Beech 33, N331DP, collided with a utility pole while attempting an emergency landing to a field eight miles southwest of Winston-Salem, North Carolina. The pilot operated the personal flight under the provisions of Title 14 CFR Part 91 with no flight plan filed. Visual weather conditions prevailed at the time of the accident. The airplane sustained substantial damage, and the private pilot and the three passengers were not injured. The flight departed Jasper, Georgia, at 1455. The pilot stated that before departing Jasper he checked the aircraft fuel supply and elected not to refuel. During the examination of the fuel supply, he reported that the fuel supply in the left wing tank was two inches below the filler cap. The right fuel gauge showed 1/4 tank. The pilot thought he had ample fuel for the 269 mile fight back to Winston Salem. At 1640, the pilot advised Greensboro Tower that he was experiencing engine problems and requested assistance to the nearest airport. Moments later, the pilot told the tower controller that the engine was running again, and he wanted to continue the flight to Winston-Salem. At approximately 1647, the pilot reported that the engine had quit again; the airplane collided with the utility pole and lines during the forced landing. Examination of the airplane failed to disclose a mechanical problem or system malfunction. There was no fuel recovered from the aircraft fuel system during the field examination of the airframe. The pilot stated that more fuel should have been put into the right tank before he departed. The pilot stated that before takeoff, he checked the aircraft fuel supply and elected not to refuel. He reported that during examination of the fuel supply, the fuel supply in the left wing tank was two inches below the filler cap, and the right fuel gauge showed 1/4 tank. The pilot thought he had ample fuel for the 269 mile flight to the destination airport. Before reaching his distination, the pilot advised an air traffic controller that he was experiencing engine problems and requested assistance to the nearest airport. Moments later, he reported that the engine was running again, and he wanted to continue the flight to the destination airport. About five miles from the airport, the pilot reported that the engine had quit again. Subsequently, during a forced landing, the airplane collided with a utility pole and lines. Examination of the airplane failed to disclose a mechanical problem or system malfunction. There was no fuel recovered from the aircraft fuel system during field examination of the airframe. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1997_ATL97LA142.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗
Related research
Matched on aircraft type or causal vocabulary (fuel exhaustion). All research papers
- arXiv 2020 · arXiv preprint A Lean and Highly-automated Model-Based Software Development Process Based on DO-178C/DO-331
The emergence of a global market for urban air mobility and unmanned aerial systems has attracted many startups across the world.
- NASA NTRS 1995 · Conference Paper Human Factor Implications of the Eurocopter AS332L-1 Super Puma cockpit
The purpose of this paper is to identify and describe some of the human factor problems which can occur in the cockpit of a modern civilian helicopter.
- AOPA Air Safety Institute 2024 · Annual report (Nall Report) 33rd Joseph T. Nall Report — General Aviation Accidents in 2022
The annual Joseph T. Nall Report from the AOPA Air Safety Institute summarizes general aviation accidents and causal factors for calendar year 2022.
- arXiv 2026 · arXiv preprint nBMS, a Neuromorphic Battery Management System with a Silicon-Validated Spiking State-of-Charge Core for eVTOL Aircraft
State-of-charge (SoC) estimation for electric vertical take-off and landing (eVTOL) aircraft must run on the vehicle under hard energy and certification budgets, on a duty cycle unlike anything in the…
- arXiv 2026 · arXiv preprint Multi-Domain Physics-Based MDO of Multirotor UAVs: A Deterministic Framework for Discrete COTS Sizing
Multirotor Unmanned Aerial Vehicle (UAV) design is governed by a tightly coupled system of non-linear equations spanning structural mechanics, electrochemistry, aerodynamics, and kinematics.
- arXiv 2026 · arXiv preprint Conflict Resolution under Degraded Surveillance in Air Corridors Using Multi-Agent Reinforcement Learning
Safe Advanced Air Mobility operations require aircraft to maintain separation when surveillance information is noisy, delayed, incomplete, or temporarily unavailable.