# NTSB ERA11CA425: Piper PA-24-250, N7365P, Sidney, NY, July 27, 2011 - Type: NTSB accident investigation - Classification: Accident · Serious injuries · Data collection · Final report - Date: July 27, 2011, 14:30 local (18:30 UTC) - Place: Sidney, NY - Coordinates: 42.302501, -75.416114 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=42.3025&lon=-75.4161&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach-VFR pattern final: Fuel starvation](https://openairdocs.org/ntsb-events/191) - Highest injury: Serious injuries - Injuries: 1 serious - Status: Completed, report October 17, 2011 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 81266 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA11CA425 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/81266/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=81266 - Page: https://openairdocs.org/ntsb/ERA11CA425 ## Probable cause The pilot's inadequate fuel planning and management, which resulted in fuel starvation and a total loss of engine power during final approach. ## 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: [Piper PA-24-250, 12 cases](https://openairdocs.org/ntsb-findings/02061030/cases.md?model=7102404), [All aircraft, 719 cases](https://openairdocs.org/ntsb-findings/02061030/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Prior to flight: Preflight or dispatch event](https://openairdocs.org/ntsb-events/030); cases with it: [Piper PA-24-250, 4 cases](https://openairdocs.org/ntsb-events/030/sequence.md?model=7102404), [All aircraft, 355 cases](https://openairdocs.org/ntsb-events/030/sequence.md) - [Approach-VFR pattern final: 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 final: 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,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-250, 23 cases](https://openairdocs.org/ntsb-events/440/sequence.md?model=7102404), [All aircraft, 3,365 cases](https://openairdocs.org/ntsb-events/440/sequence.md) - [Landing: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Piper PA-24-250, 55 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7102404), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot stated that he last checked the fuel quantity before a flight that he conducted 2 weeks prior to the accident flight. During that flight, he noticed that the right auxiliary fuel gauge was inoperative. The airplane landed uneventfully and remained in a hangar until the accident flight. The purpose of the accident flight was to drain fuel from the right auxiliary fuel tank, in order for maintenance work to be performed on the fuel tank sending unit. The pilot did not check the fuel quantity prior to the accident flight as he estimated that sufficient fuel remained from the previous flight. The pilot completed a 20-minute local flight and was on final approach to land, with the fuel selector positioned to the right auxiliary fuel tank, when a low fuel pressure indicator light illuminated in the cockpit. At that time, the airplane was about 800 feet above ground level, over a populated town. The pilot activated the fuel boost pump, but did not reposition the fuel selector to a different fuel tank. The engine subsequently experienced a total loss of power and the pilot performed a forced landing into trees and a river. During the landing, the airplane sustained substantial damage to both wings and the fuselage. The pilot further stated that the accident was "pilot error" as he ran the right auxiliary fuel tank dry. ## Factual narrative The pilot stated that he last checked the fuel quantity before a flight that he conducted 2 weeks prior to the accident flight. During that flight, he noticed that the right auxiliary fuel gauge was inoperative. The airplane landed uneventfully and remained in a hangar until the accident flight. The purpose of the accident flight was to drain fuel from the right auxiliary fuel tank, in order for maintenance work to be performed on the fuel tank sending unit. The pilot did not check the fuel quantity prior to the accident flight as he estimated that sufficient fuel remained from the previous flight. The pilot completed a 20-minute local flight and was on final approach to land, with the fuel selector positioned to the right auxiliary fuel tank, when a low fuel pressure indicator light illuminated in the cockpit. At that time, the airplane was about 800 feet above ground level, over a populated town. The pilot activated the fuel boost pump, but did not reposition the fuel selector to a different fuel tank. The engine subsequently experienced a total loss of power and the pilot performed a forced landing into trees and a river. During the landing, the airplane sustained substantial damage to both wings and the fuselage. The pilot further stated that the accident was "pilot error" as he ran the right auxiliary fuel tank dry. ## Aircraft - Registration: [N7365P](https://openairdocs.org/deregistered/N7365P-2017-10-30), registration cancelled 2017-10-30, S/N 24-2543, built 1961 (OpenAirDocs) - Reported make and model: PIPER PA-24-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-2543 - Airframe hours: 5087 - Engines: LYCOMING O-540 250 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Petzold Milton H - Registered owner: Petzold Milton H - Airworthiness certificate: Standard, Normal - Last inspection: Annual, September 2, 2010, 20 hours before - Departed: N23, Sidney, NY - Destination: N23, Sidney, NY - Airport: N23, Sidney Municipal Airport, runway 25 ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 69; injuries: serious; commercial; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; last flight review June 23, 2011; seat: left; flight hours: 1,941 total, 800 in this make and model, 4 in the last 90 days, 2 in the last 30 days, 0 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: variable at 5 knots - Visibility: 10 statute miles - Lowest ceiling: 5,000 ft broken - Temperature: 75 °F, dew point 55 °F - Altimeter: 29.98 inHg - Observed at: BGM, 20 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 20110727015539A](https://openairdocs.org/incident/20110727015539A), Jul 27, 2011: Piper PA-24-250, Sidney, NY, Substantial damage. On July 28, 2011, the albany flight standards district office, investigated an accident of N7365P, a Piper PA-24-250 (comanche). The aircraft impacted a large… ## Other investigations on N7365P (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 OAK69D0148](https://openairdocs.org/ntsb/OAK69D0148), Sep 13, 1968: Piper PA-24 (N7365P), Garberville, CA, substantial damage ## Docket (3 files) The files NTSB released with the investigation on September 7, 2011, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=81266. 6.7 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 6.6 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40353505&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Interview Summaries (item 2, .PDF, 66 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40353508&FileExtension=.PDF&FileName=Interview%20Summaries-Master.PDF - Weather Report (item 3, .PDF, 11 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40353507&FileExtension=.PDF&FileName=Weather%20Report-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.