# NTSB ERA10CA002: Piper PA-24-260, N9237P, Highgate, VT, October 3, 2009

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: October 3, 2009, 11:45 local (15:45 UTC)
- Place: Highgate, VT
- Coordinates: 44.940277, -73.097221 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=44.9403&lon=-73.0972&mi=10
- Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping)
- Defining event: [Takeoff: Fuel starvation](https://openairdocs.org/ntsb-events/191)
- Highest injury: No injuries
- Injuries: 4 uninjured
- Status: Completed, report April 19, 2010
- Report: Approved by Office Director
- NTSB office: Eastern Region Aviation
- NTSB case key (mKey): 74842
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA10CA002
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/74842/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=74842
- Page: https://openairdocs.org/ntsb/ERA10CA002

## Probable cause

The pilot’s improper fuel management which resulted in loss of engine power due to fuel starvation.

## Findings

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

- [Fluids: fuel](https://openairdocs.org/ntsb-findings/01071010): Aircraft › Fluids/misc hardware · Fluid management (probable cause); cases with it: [Piper PA-24-260, 7 cases](https://openairdocs.org/ntsb-findings/01071010/cases.md?model=7102406), [All aircraft, 1,695 cases](https://openairdocs.org/ntsb-findings/01071010/cases.md)
- [Knowledge: knowledge of equipment](https://openairdocs.org/ntsb-findings/02032015): Personnel issues › Experience/knowledge · Pilot (probable cause); cases with it: [Piper PA-24-260, 1 case](https://openairdocs.org/ntsb-findings/02032015/cases.md?model=7102406), [All aircraft, 69 cases](https://openairdocs.org/ntsb-findings/02032015/cases.md)

## Sequence of events

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

- [Takeoff: Fuel starvation](https://openairdocs.org/ntsb-events/191) (defining event); cases with it: [Piper PA-24-260, 3 cases](https://openairdocs.org/ntsb-events/191/sequence.md?model=7102406), [All aircraft, 733 cases](https://openairdocs.org/ntsb-events/191/sequence.md)
- [Takeoff: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341); cases with it: [Piper PA-24-260, 7 cases](https://openairdocs.org/ntsb-events/341/sequence.md?model=7102406), [All aircraft, 3,820 cases](https://openairdocs.org/ntsb-events/341/sequence.md)
- [Emergency descent: Off-field or emergency landing](https://openairdocs.org/ntsb-events/440); cases with it: [Piper PA-24-260, 7 cases](https://openairdocs.org/ntsb-events/440/sequence.md?model=7102406), [All aircraft, 3,365 cases](https://openairdocs.org/ntsb-events/440/sequence.md)
- [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Piper PA-24-260, 9 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=7102406), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md)
- [Landing-landing roll: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Piper PA-24-260, 24 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7102406), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md)

## Analysis

According to the pilot, he was conducting multiple 10- to 15-minute "Young Eagle" flights. After taking off on the fifth flight, and as the airplane reached 300 feet, the engine lost power. The pilot switched fuel tanks and verified that the fuel pump was on, but to no avail. He then force-landed the airplane on the departure end of the runway. However, the airplane continued off the end of the runway and through a grassy overrun for about 100 yards, until it impacted a fence, substantially damaging both wings. The pilot noted that there were two main fuel tanks and two auxiliary fuel tanks on the airplane, and that during the first four flights, he only utilized fuel from the left main tank. Prior to the fifth flight, both auxiliary tanks and the right main tank were full, and the left main tank indicated 1/4 full. The pilot initially switched fuel feed to the right main tank, but then decided to utilize the remaining fuel in the left main tank, and switched back to that tank before takeoff. Postflight examination of the left fuel tank revealed no fuel in the tank. The pilot also stated that there were no preexisting mechanical anomalies with the airplane.

## Factual narrative

According to the pilot, he was conducting multiple "Young Eagle" flights of 10 to 15 minutes' duration each. After taking off on the fifth flight, and as the airplane reached 300 feet, the engine lost power. The pilot switched fuel tanks and verified that the fuel pump was on, but to no avail. He then force-landed the airplane on the departure end of the runway. However, the airplane continued off the end of the runway and through a grassy overrun for about 100 yards, until it impacted a fence, substantially damaging both wings. The pilot noted that there were two main fuel tanks and two auxiliary fuel tanks on the airplane, and that during the first four flights, he only utilized fuel from the left main tank. Prior to the fifth flight, both auxiliary tanks and the right main tank were full, and the left main tank indicated 1/4 full. The pilot initially switched fuel feed to the right main tank, but then decided to utilize the remaining fuel in the left main tank, and switched back to that tank before takeoff. Postflight examination of the left fuel tank revealed no fuel in the tank. The pilot also stated that there were no preexisting mechanical anomalies with the airplane.

## Aircraft

- Registration: [N9237P](https://openairdocs.org/aircraft/N9237P), registered now, S/N 24-4736, built 1967 (OpenAirDocs)
- Reported make and model: PIPER PA-24-260
- Registry model: [Piper PA-24-260](https://openairdocs.org/model/piper-pa-24-260) (registry code 7102406) (OpenAirDocs)
- Registry engine: [Lycoming TI0-540 series](https://openairdocs.org/engine/lycoming-ti0-540-series) (registry code 41533, turbo-prop) (OpenAirDocs)
- Category: Airplane
- Serial number: 24-4736
- Airframe hours: 4977
- Engines: LYCOMING TIO-540 SER 310 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Operator: Robert Desmarais
- Registered owner: Robert Desmarais
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, October 3, 2009
- Departed: KFSO, Highgate, VT
- Destination: KFSO, Highgate, VT
- Airport: KFSO, Franklin County State Airport, runway 19, 3,000 × 60 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 57; injuries: none; commercial; airplane ratings: multi-engine land, single-engine land, single-engine sea; instrument ratings: airplane; medical: class 3, with waivers/limitations; last flight review August 22, 2009; seat: left; flight hours: 845 total, 48 in this make and model, 780 as pilot in command, 27 in the last 90 days, 4 in the last 30 days, 1 in the last 24 hours

## Weather

- Conditions: Visual (VMC), Day
- Wind: 160° at 3 knots
- Visibility: 10 statute miles
- Lowest ceiling: 2,900 ft overcast
- Temperature: 57 °F, dew point 54 °F
- Altimeter: 29.89 inHg
- Observed at: KFSO

## 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 20091003050079A](https://openairdocs.org/incident/20091003050079A), Oct 3, 2009: Piper PA-24-260, Highgate, VT, Substantial damage. Pilot miscalculated amount of remaining fuel in left main tank and assumed sufficient fuel remained for a 10 minute flight. During takeoff aircraft climbed to…

## Docket (4 files)

The files NTSB released with the investigation on December 10, 2009, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=74842. 764 KB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 648 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40321453&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF
- Memorandum for Record (1) (item 2, .PDF, 50 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40320790&FileExtension=.PDF&FileName=Memorandum%20for%20Record%20(1)-Redacted.PDF
- Memorandum for Record (2) (item 3, .PDF, 39 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40321454&FileExtension=.PDF&FileName=Memorandum%20for%20Record%20(2)-Redacted.PDF
- Memorandum for Record (3) (item 4, .PDF, 26 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40321538&FileExtension=.PDF&FileName=Memorandum%20for%20Record%20(3)-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.
