# NTSB ERA14CA265: Divis S L/Waltrip A J RV 4, N403WD, Harpswell, ME, May 25, 2014

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: May 25, 2014, 19:30 local (23:30 UTC)
- Place: Harpswell, ME
- Coordinates: 43.779724, -70.015556 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=43.7797&lon=-70.0156&mi=10
- Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping)
- Defining event: [Enroute-cruise: Fuel exhaustion](https://openairdocs.org/ntsb-events/192)
- Highest injury: No injuries
- Injuries: 2 uninjured
- Status: Completed, report October 9, 2014
- Report: Approved by Office Director
- NTSB office: Eastern Region Aviation
- Parties: FAA/FSDO
- NTSB case key (mKey): 89303
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA14CA265
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/89303/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=89303
- Page: https://openairdocs.org/ntsb/ERA14CA265

## Probable cause

The pilot's inadequate preflight and in-flight planning which resulted in total loss of engine power due to fuel exhaustion.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Planning/preparation: fuel planning](https://openairdocs.org/ntsb-findings/02061030): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Divis S L/Waltrip A J VANS RV-4, 1 case](https://openairdocs.org/ntsb-findings/02061030/cases.md?model=05615QT), [All aircraft, 719 cases](https://openairdocs.org/ntsb-findings/02061030/cases.md)
- [Fluids: fuel](https://openairdocs.org/ntsb-findings/01071010): Aircraft › Fluids/misc hardware · Fluid management (probable cause); cases with it: [Divis S L/Waltrip A J VANS RV-4, 1 case](https://openairdocs.org/ntsb-findings/01071010/cases.md?model=05615QT), [All aircraft, 1,695 cases](https://openairdocs.org/ntsb-findings/01071010/cases.md)
- [Fluids: fuel](https://openairdocs.org/ntsb-findings/01071010): Aircraft › Fluids/misc hardware · Fluid level (probable cause); cases with it: [Divis S L/Waltrip A J VANS RV-4, 1 case](https://openairdocs.org/ntsb-findings/01071010/cases.md?model=05615QT), [All aircraft, 1,695 cases](https://openairdocs.org/ntsb-findings/01071010/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Enroute-cruise: Fuel exhaustion](https://openairdocs.org/ntsb-events/192) (defining event); cases with it: [Divis S L/Waltrip A J VANS RV-4, 1 case](https://openairdocs.org/ntsb-events/192/sequence.md?model=05615QT), [All aircraft, 804 cases](https://openairdocs.org/ntsb-events/192/sequence.md)
- [Enroute-cruise: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341); cases with it: [Divis S L/Waltrip A J VANS RV-4, 1 case](https://openairdocs.org/ntsb-events/341/sequence.md?model=05615QT), [All aircraft, 3,820 cases](https://openairdocs.org/ntsb-events/341/sequence.md)
- [Landing-landing roll: Miscellaneous/other](https://openairdocs.org/ntsb-events/900); cases with it: [Divis S L/Waltrip A J VANS RV-4, 1 case](https://openairdocs.org/ntsb-events/900/sequence.md?model=05615QT), [All aircraft, 1,556 cases](https://openairdocs.org/ntsb-events/900/sequence.md)

## Analysis

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.

## 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.

## Aircraft

- Registration: [N403WD](https://openairdocs.org/aircraft/N403WD), registered now, S/N 641, built 2003 (OpenAirDocs)
- Reported make and model: DIVIS S L/WALTRIP A J RV 4
- Registry model: [Divis S L/Waltrip A J VANS RV-4](https://openairdocs.org/model/divis-s-l-waltrip-a-j-vans-rv-4) (registry code 05615QT) (OpenAirDocs)
- Registry engine: [Lycoming O-360 series](https://openairdocs.org/engine/lycoming-o-360-series) (registry code 41575, reciprocating) (OpenAirDocs)
- Category: Airplane, amateur-built
- Serial number: 641
- Year built: 2003
- Airframe hours: 260
- Engines: LYCOMING O-360-A4M 180 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Operator: Thomas Spencer S
- Registered owner: Thomas Spencer S
- Airworthiness certificate: Special, Experimental (Special)
- Last inspection: Condition, November 10, 2013
- Departed: 2W5, Indian Head, MD
- Destination: BXM, Brunswick, ME
- Flight plan: VFR
- Airport: ME33, Farr Field Airport, runway 32, 1,900 × 100 ft, grass/turf

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 46; injuries: none; commercial; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: unknown, without waivers/limitations; last flight review November 2, 2013; seat: front; flight hours: 4,300 total, 280 in this make and model, 4,100 as pilot in command, 5 in the last 90 days, 3 in the last 30 days, 3 in the last 24 hours

## Weather

- Conditions: Visual (VMC), Day
- Wind: 190° at 7 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 55 °F, dew point 48 °F
- Altimeter: 30.01 inHg
- Observed at: PWM, 15 nm away

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20140525013519A](https://openairdocs.org/incident/20140525013519A), May 25, 2014: Divis S L/Waltrip A J VANS RV-4, Harpswell, ME, Minor damage. Pilot reported that he departed 2W5, Maryland airport, indian head Maryland, to bxm, brunswick executive airport, brunswick Maine. Time enroute was planned and…

## Docket (5 files)

The files NTSB released with the investigation on October 1, 2014, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=89303. 8.3 MB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 2.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40417069&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF
- Weather Report and Record (item 2, .PDF, 111 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40417070&FileExtension=.PDF&FileName=Weather%20Report%20and%20Record-Master.PDF
- FAA Inspector Statement (item 3, .PDF, 13 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40417071&FileExtension=.PDF&FileName=FAA%20Inspector%20Statement-Redacted.PDF
- Photo 1 - Right Side of Firewall (Photo Courtesy of FAA) (item 4, .PDF, 3.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40417072&FileExtension=.PDF&FileName=Photo%201%20-%20Right%20Side%20of%20Firewall%20(Photo%20Courtesy%20of%20FAA)-Master.PDF
- Photo 2 - Left Side of the Aft Fuselage (Photo Courtesy of FAA) (item 5, .PDF, 2.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40417073&FileExtension=.PDF&FileName=Photo%202%20-%20Left%20Side%20of%20the%20Aft%20Fuselage%20(Photo%20Courtesy%20of%20FAA)-Master.PDF

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.