Skip to content

Atlas / NTSB / ERA14CA265

NTSB CAROL · Event

Event ERA14CA265

2014-05-25 Harpswell, Maine, United States Airport · ME33 None 1 aircraft Status: Completed

Registry · N403WD

FAA Aircraft Registry record.

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

Registrant of record

THOMAS SPENCER S

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

Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or 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 ↗.

Related research

What the literature says.

Academic papers and agency reports matching this event's aircraft type or causal vocabulary (fuel exhaustion, engine failure). 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 ↗