NYC04LA151
2004-07-01 · Morgantown, West Virginia, United States · Minor · 1 aircraft · Status: Completed
Airport MGW
Aircraft involved
Probable cause & findings
The pilot's improper fuel management, which resulted in fuel starvation and a subsequent loss of engine power.
Factual narrative
On July 1, 2004, at 1502 eastern daylight time, a Beech 35, N5345E, was substantially damaged when it impacted trees after takeoff from Morgantown Airport (MGW), Morgantown, West Virginia. The certificated private pilot received minor injuries. Visual meteorological conditions prevailed and no flight plan was filed for the personal flight which was destined for the Somerset County Airport (2G9), Somerset, Pennsylvania. According to the pilot, he departed Somerset with the left fuel tank about half full, and the right fuel tank and two auxiliary tanks full (approximately 55 gallons total). He flew approximately 30 minutes to Morgantown, with the fuel selector set to the right tank. The pilot had lunch in Morgantown, and then departed runway 18, with the fuel selector set to the right tank, for the return flight to Somerset. During the takeoff climb, as the airplane reached the end of the runway, at an altitude of about 100 feet, the engine began to sputter and then lost power. The pilot performed a forced landing to a field, during which the airplane impacted trees and was substantially damaged. The pilot additionally stated that the airplane burned more fuel when the right tank was selected, since unused fuel from the engine is returned to the left fuel tank. Thus, the range, when selected to the right tank, was less than the depicted 25 gallons. The pilot stated that the cause of the accident was, "fuel starvation and simple pilot error." Examination of the airplane by a Federal Aviation Administration (FAA) inspector revealed the right fuel tank was ruptured, and the left fuel tank was approximately half full. The fuel lines from the fuel pump to the fuel injector, and the line from the fuel distributor to the cylinders contained no fuel. The fuel line from the fuel selector to the fuel pump contained residual fuel only. According to the Beechcraft BE-35 Pilot's Operating Handbook, the capacity for each of the main tanks was 17 gallons, and each of the two auxiliary tanks held 10 gallons of fuel (54 gallons total). The Systems Description Section of the Handbook stated, "The pressure type carburetor returns about 3 gallons per hour of excess fuel to the left main cell regardless of the cell selected." The fuel burn rate depicted in the Performance section of the Handbook was approximately 9.5 gallons per hour. The pilot departed with the right fuel tank full (approximately 17 gallons) and the left tank about half full. He flew for approximately 30 minutes with the right fuel tank selected, and landed at his destination airport. The pilot departed again with the right tank selected for the return flight. As the airplane reached the end of the runway, the engine began to sputter and then lost power. The pilot performed a forced landing to a field, during which the airplane impacted trees. The pilot reported that the airplane burned more fuel when the right tank was selected, since unused fuel from the engine is returned to the left fuel tank. The pilot stated that the cause of the accident was, "fuel starvation and simple pilot error." Examination of the airplane revealed the right fuel tank was ruptured, and the left fuel tank was approximately half full. The fuel lines from the fuel pump to the fuel injector, and the line from the fuel distributor to the cylinders contained no fuel. The fuel line from the fuel selector to the fuel pump contained residual fuel only. According to the Beechcraft BE-35 Pilot's Operating Handbook, "The pressure type carburetor returns about 3 gallons per hour of excess fuel to the left main cell regardless of the cell selected." The fuel burn rate depicted in the Performance section of the Handbook was approximately 9.5 gallons per hour. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2004_NYC04LA151.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 starvation). All research papers
- Embry-Riddle Scholarly Commons 2025 · Journal article (JAAER) Editor's Note: Celebrating 35 Years of Scholarly Excellence
A letter from the editor, Dr. Dahai Liu, on the JAAER's 35th anniversary.
- NASA NTRS 2024 · Presentation Part 135 and Business Operator Low Altitude Events: An Analysis of ASRS Reports
This presentation provides an aviation SME's human factors analysis of selected Low Altitude and Controlled Flight Towards Terrain (CFTT) events involving Part 135 and business jet operators as report…
- NASA NTRS 2022 · Conference Paper The In-time Aviation Safety Management System Concept for Part 135 Operators
Transformations of the National Airspace System, such as envisioned with Advanced Air Mobility, will enable improvements for managing and assuring safety for Part 135 transportation of passengers and …
- Embry-Riddle Scholarly Commons 2022 · Journal article (JAAER) SMS for Part 135 Commuter and On-Demand Operations - The Practitioner’s Perspective
On May 15th, 2017, N452DA, a Learjet 35A operated by Trans-Pacific Air Charter, LLC, departed from Philadelphia to Teterboro, New Jersey (TEB) on a positioning flight under 14 Code of Federal Regulati…
- NTSB Aircraft Accident Reports 2021 · Accident report Crash of Atlas Air Flight 3591, Boeing 767-300 (N1217A)
Atlas Air 3591 crashed into Trinity Bay, Texas, February 23, 2019. Investigation of the in-flight loss-of-control crash of Atlas Air 3591 into Trinity Bay, Texas.
- Embry-Riddle Scholarly Commons 2020 · Journal article (IJAAA) Analysis of Part 135 Aircraft Accidents to Facilitate Flight Data Monitoring
The scheduled and on-demand air services with Title 14 Code of Federal Regulations (CFR) Part 135 certificate are operating with relatively less stringent safety program criteria compared to Part 121 …