# NTSB ERA17CA039: Piper PA 24-250, N7682P, Houlton, ME, November 8, 2016

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: November 8, 2016, 16:10 local (21:10 UTC)
- Place: Houlton, ME
- Coordinates: 46.115276, -67.800834 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=46.1153&lon=-67.8008&mi=10
- Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping)
- Defining event: [Approach-VFR pattern downwind: Fuel starvation](https://openairdocs.org/ntsb-events/191)
- Highest injury: No injuries
- Injuries: 2 uninjured
- Status: Completed, report December 15, 2017
- Report: Approved by Office Director
- NTSB office: Eastern Region Aviation
- Parties: FAA FSDO
- NTSB case key (mKey): 94353
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA17CA039
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/94353/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=94353
- Page: https://openairdocs.org/ntsb/ERA17CA039

## Probable cause

A total loss of engine power due to fuel starvation, which resulted from the pilot’s mismanagement of the available fuel.

## Findings

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

- [Fuel system: fuel selector/shutoff valve](https://openairdocs.org/ntsb-findings/01022823): Aircraft › Aircraft systems · Not used/operated (probable cause); cases with it: [Piper PA-24-250, 4 cases](https://openairdocs.org/ntsb-findings/01022823/cases.md?model=7102404), [All aircraft, 177 cases](https://openairdocs.org/ntsb-findings/01022823/cases.md)
- [Use of equip/info: use of equip/system](https://openairdocs.org/ntsb-findings/02063015): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Piper PA-24-250, 16 cases](https://openairdocs.org/ntsb-findings/02063015/cases.md?model=7102404), [All aircraft, 1,397 cases](https://openairdocs.org/ntsb-findings/02063015/cases.md)
- [Fluids: fuel](https://openairdocs.org/ntsb-findings/01071010): Aircraft › Fluids/misc hardware · Fluid level (probable cause); cases with it: [Piper PA-24-250, 24 cases](https://openairdocs.org/ntsb-findings/01071010/cases.md?model=7102404), [All aircraft, 1,696 cases](https://openairdocs.org/ntsb-findings/01071010/cases.md)
- [Fluids: fuel](https://openairdocs.org/ntsb-findings/01071010): Aircraft › Fluids/misc hardware · Fluid management (probable cause); cases with it: [Piper PA-24-250, 24 cases](https://openairdocs.org/ntsb-findings/01071010/cases.md?model=7102404), [All aircraft, 1,696 cases](https://openairdocs.org/ntsb-findings/01071010/cases.md)
- [Terrain](https://openairdocs.org/ntsb-findings/03021000): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Piper PA-24-250, 2 cases](https://openairdocs.org/ntsb-findings/03021000/cases.md?model=7102404), [All aircraft, 267 cases](https://openairdocs.org/ntsb-findings/03021000/cases.md)

## Sequence of events

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

- [Approach-VFR pattern downwind: Fuel starvation](https://openairdocs.org/ntsb-events/191) (defining event); cases with it: [Piper PA-24-250, 13 cases](https://openairdocs.org/ntsb-events/191/sequence.md?model=7102404), [All aircraft, 733 cases](https://openairdocs.org/ntsb-events/191/sequence.md)
- [Approach-VFR pattern downwind: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341); cases with it: [Piper PA-24-250, 23 cases](https://openairdocs.org/ntsb-events/341/sequence.md?model=7102404), [All aircraft, 3,824 cases](https://openairdocs.org/ntsb-events/341/sequence.md)

## Analysis

The private pilot had recently purchased the airplane; he and a flight instructor were conducting a local familiarization flight. After about 1 hour of flying with the left inboard fuel tank selected, he returned to the airport traffic pattern and performed two additional takeoffs. While on the left downwind leg of the traffic pattern, the engine experienced a total loss of power. The pilot checked that the fuel pump was on while the flight instructor attempted to determine why the engine lost power. The flight instructor then took control of the airplane and turned toward the runway. The airplane contacted the tops of some trees and landed on uneven terrain covered with tall grass and brush about 500 ft short of the runway, which resulted in substantial damage to the firewall, fuselage, and wings. Before exiting the airplane, the pilot moved the fuel selector to the "off" position. A Federal Aviation Administration inspector examined the wreckage and found that the left inboard fuel tank was absent of fuel, while the right inboard fuel tank was full. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. When asked how the accident could have been prevented, the pilot stated, "switched to the other fuel tank."

## Factual narrative

The private pilot had recently purchased the airplane; he and a flight instructor were conducting a local familiarization flight. After about one hour of flying with the left inboard fuel tank selected, he returned to the airport traffic pattern and performed two additional takeoffs. While on the left downwind leg of the traffic pattern, the engine experienced a total loss of power. The pilot checked that the fuel pump was on while the flight instructor attempted to determine why the engine lost power. The flight instructor then took control of the airplane and turned towards the runway. The airplane contacted the tops of some trees and landed on uneven terrain covered with tall grass and brush about 500 feet short of the runway, resulting in substantial damage to the firewall, fuselage, and wings. Before exiting the airplane, the pilot moved the fuel selector to the off position. A Federal Aviation Administration inspector examined the wreckage and found that the left inboard fuel tank was absent of fuel, while the right inboard fuel tank was full. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. When asked how the accident could have been prevented, the pilot stated, "switched to the other fuel tank."

## Aircraft

- Registration: [N7682P](https://openairdocs.org/deregistered/N7682P-2020-05-02), registration cancelled 2020-05-02, S/N 24-2891, built 1961 (OpenAirDocs)
- Reported make and model: PIPER PA 24-250 (250)
- Registry model: [Piper PA-24-250](https://openairdocs.org/model/piper-pa-24-250) (registry code 7102404) (OpenAirDocs)
- Registry engine: [Lycoming 0-540 series](https://openairdocs.org/engine/lycoming-0-540-series) (registry code 41532, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 24-2891
- Year built: 1961
- Airframe hours: 5617.4
- Engines: LYCOMING O-540 SERIES 250 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, June 17, 2016
- Departed: HUL, Houlton, ME
- Destination: HUL, Houlton, ME
- Airport: HUL, Houlton Intl, runway 05, 5,015 × 100 ft, asphalt
- Equipment: None

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 57; injuries: none; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; seat: left; restraint: 3-point; flight hours: 312 total, 1 in this make and model, 265 as pilot in command, 9.8 in the last 90 days, 4.3 in the last 30 days
- Flight instructor; age 89; injuries: none; flight instructor; airplane ratings: multi-engine land, single-engine sea, single-engine land; medical: class 2; seat: right; restraint: lap only

## Weather

- Conditions: Visual (VMC), Day
- Wind: 200° at 3 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 54 °F, dew point 43 °F
- Altimeter: 29.90 inHg
- Observed at: HUL, 1 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 20161108022769A](https://openairdocs.org/incident/20161108022769A), Nov 8, 2016: Piper PA-24-250, Houlton, ME, Substantial damage. The pilot stated the aircraft was fueled at the FBO prior to the flight with 30 gallons in each inboard fuel tank and approximately 8 gallons in each outboard…

## Other investigations on N7682P (1)

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.

- [NTSB DEN67D0206](https://openairdocs.org/ntsb/DEN67D0206), Jan 14, 1967: Piper PA-24 (N7682P), Carrizozo, NM, substantial damage

## Docket (3 files)

The files NTSB released with the investigation on November 24, 2017, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=94353. 2.0 MB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 335 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40458367&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF
- FAA Inspector's Statement (item 2, .PDF, 28 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40458368&FileExtension=.PDF&FileName=FAA%20Inspector%27s%20Statement-Master.PDF
- Accident Site and Damage Photographs (item 3, .PDF, 1.6 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40458369&FileExtension=.PDF&FileName=Accident%20Site%20and%20Damage%20Photographs-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.
