ERA14CA265
2014-05-25 · Harpswell, Maine, United States · None · 1 aircraft · Status: Completed
Airport ME33
Current FAA registration · N403WD
- Make / Model
- VAN'S AIRCRAFT RV-4
- Year of manufacture
- 2003 · 11 years old at event
- Engine
- LYCOMING O-360 SERIES (180 hp)
- Seats / Engines
- 2 seats · 1 engine
- Last airworthiness date
- 20040102
- ADS-B equipped
- Yes — Mode-S A4B9BE
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot's inadequate preflight and in-flight planning which resulted in total loss of engine power due to fuel exhaustion.
Factual narrative
The pilot stated that the flight planning indicated the time en-route to be 3.0 hours, which allowed for a 45 minute fuel reserve. After takeoff the flight remained at 1,500 feet until clear of Special Flight Rules Area (SFRA) at PALEO exit Gate, then climbed on course to 7,500 feet mean sea level (msl). Course deviations en-route due to weather occurred, and when the flight was 15 nautical miles south of Portland, Maine, he descended to 5,500 feet msl and continued at that altitude towards the destination airport until, "…indications of pending engine failure at approximately 10 NM northeast of Portland." He established best glide airspeed, declared an emergency with air traffic control and confirmed the distance to Portland and his destination airports. He proceeded towards another airport (Farr Field Airport) and flew over it at "High Key" position, or over the runway, and turned east for "Base Key." While on final approach he maneuvered between trees and touched down on runway 32. After touchdown he intentionally applied left rudder and brake to avoid runway overrun into water past the departure end of the runway. After coming to rest, both occupants exited the airplane; the total flight duration was reported to be 2 hours 45 minutes. The pilot reported there was no preimpact failure or malfunction that would have precluded normal operation. During the accident sequence, the airplane sustained damage to the firewall and left side of the aft fuselage near the tailwheel assembly.Postaccident inspection of the airplane by a Federal Aviation Administration airworthiness inspector revealed the fuel tanks were empty and were not breached. A copy of the FAA Inspector Statement and photographs depicting the damage are contained in the NTSB public docket. The pilot further stated that factors that resulted in increased fuel consumption for which he did not take into account included a recent propeller change which increased engine rpm, fuel consumption planning for the accident flight based on a previous flight flown at a higher altitude and less weight, and finally course deviations. The pilot stated that the flight planning indicated the time en-route to be 3.0 hours, which allowed for a 45 minute fuel reserve. After takeoff the flight remained at 1,500 feet until clear of Special Flight Rules Area (SFRA) at PALEO exit Gate, then climbed on course to 7,500 feet mean sea level (msl). Course deviations en-route due to weather occurred, and when the flight was 15 nautical miles south of Portland, Maine, he descended to 5,500 feet msl and continued at that altitude towards the destination airport until, "…indications of pending engine failure at approximately 10 NM northeast of Portland." He established best glide airspeed, declared an emergency with air traffic control and confirmed the distance to Portland and his destination airports. He proceeded towards another airport (Farr Field Airport) and flew over it at "High Key" position, or over the runway, and turned east for "Base Key." While on final approach he maneuvered between trees and touched down on runway 32. After touchdown he intentionally applied left rudder and brake to avoid runway overrun into water past the departure end of the runway. After coming to rest, both occupants exited the airplane; the total flight duration was reported to be 2 hours 45 minutes. The pilot reported there was no preimpact failure or malfunction that would have precluded normal operation. During the accident sequence, the airplane sustained damage to the firewall and left side of the aft fuselage near the tailwheel assembly. Postaccident inspection of the airplane by a Federal Aviation Administration airworthiness inspector revealed the fuel tanks were empty and were not breached. A copy of the FAA Inspector Statement and photographs depicting the damage are contained in the NTSB public docket. The pilot further stated that factors that resulted in increased fuel consumption for which he did not take into account included a recent propeller change which increased engine rpm, fuel consumption planning for the accident flight based on a previous flight flown at a higher altitude and less weight, and finally course deviations. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
FAA avdata. C = Cause, F = Factor.
- C Personnel issues-Task performance-Planning/preparation-Fuel planning-Pilot - C
- C Aircraft-Fluids/misc hardware-Fluids-Fuel-Fluid management - C
- C Aircraft-Fluids/misc hardware-Fluids-Fuel-Fluid level - C
Verbatim from NTSB's published report. Source file
NTSB_2014_ERA14CA265.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, engine failure). All research papers
- arXiv 2022 · arXiv preprint Multi-level Adaptation for Automatic Landing with Engine Failure under Turbulent Weather
This paper addresses efficient feasibility evaluation of possible emergency landing sites, online navigation, and path following for automatic landing under engine-out failure subject to turbulent wea…
- NASA NTRS 2019 · Conference Paper Simulation of Liquid Rocket Engine Failure Propagation Using Self-Evolving Scenarios
Traditional probabilistic risk assessment approaches often require failure scenarios to be explicitly defined through event sequences that are then quantified as part of the integrated analysis.
- NASA NTRS 2019 · Conference Paper Rocket engine failure detection using system identification techiques
The theoretical foundation and application of two univariate failure detection algorithms to Space Shuttle Main Engine (SSME) test firing data is presented.
- NASA NTRS 2019 · Conference Paper Rocket engine failure detection using system identification techniques
The theoretical foundation and application of two univariate failure detection algorithms to Space Shuttle Main Engine (SSME) test firing data is presented.
- NASA NTRS 2019 · Technical Memorandum (TM) A simulator investigation of engine failure compensation for powered-lift STOL aircraft
A piloted simulator investigation of various engine failure compensation concepts for powered-lift STOL aircraft was carried out at the Ames Research Center.
- Semantic Scholar 2019 · Article (AIAA Scitech 2019 Forum) Impact of Engine Failure Constraints on the Initial Sizing of Hybrid-Electric GA Aircraft
Potential advantages of hybrid-electric aircraft are fuel savings, lower emissions, and reduced noise. Since these aircraft generally apply multiple power sources, they can also be designed to sustain…