# NTSB ERA11CA423: Piper PA-28-161, N81917, Quinton, VA, July 26, 2011 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Data collection · Final report - Date: July 26, 2011, 04:15 local (08:15 UTC) - Place: Quinton, VA - Coordinates: 37.546112, -77.214721 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=37.5461&lon=-77.2147&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach-IFR missed approach: Fuel exhaustion](https://openairdocs.org/ntsb-events/192) - Highest injury: Minor injuries - Injuries: 1 minor - Status: Completed, report November 3, 2011 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 81229 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA11CA423 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/81229/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=81229 - Page: https://openairdocs.org/ntsb/ERA11CA423 ## Probable cause The pilot's inadequate preflight planning and fuel management, which resulted in a 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: [Piper PA-28-161, 2 cases](https://openairdocs.org/ntsb-findings/02061030/cases.md?model=7102803), [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: [Piper PA-28-161, 11 cases](https://openairdocs.org/ntsb-findings/01071010/cases.md?model=7102803), [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. - [Approach-IFR missed approach: Fuel exhaustion](https://openairdocs.org/ntsb-events/192) (defining event); cases with it: [Piper PA-28-161, 3 cases](https://openairdocs.org/ntsb-events/192/sequence.md?model=7102803), [All aircraft, 804 cases](https://openairdocs.org/ntsb-events/192/sequence.md) - [Approach-IFR missed approach: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341); cases with it: [Piper PA-28-161, 22 cases](https://openairdocs.org/ntsb-events/341/sequence.md?model=7102803), [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-28-161, 19 cases](https://openairdocs.org/ntsb-events/440/sequence.md?model=7102803), [All aircraft, 3,365 cases](https://openairdocs.org/ntsb-events/440/sequence.md) - [Emergency descent: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Piper PA-28-161, 58 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7102803), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis Originally the pilot was going to depart earlier on the day of the accident and had planned to stop enroute to his destination for more fuel. After receiving a weather briefing, he decided to delay his departure until later that evening due to the possibility of thunderstorms being present in the vicinity of his destination airport at his planned time of arrival. Prior to departure that evening, he had the fuel tanks filled to capacity. During the flight, and despite his previous flight planning, he did not stop for more fuel. When he was approximately 64 miles from his destination, the pilot noticed that his fuel gauges were indicating that he had less fuel than he anticipated. Upon arrival at his destination, he flew an instrument approach and advised the air traffic controller that he was low on fuel. Due to the visibility, he was unable to see the runway environment and executed a missed approach. He was then instructed by the air traffic controller to climb to 2,000 feet mean sea level (msl). During the climb, the engine lost power and the airplane began to descend, but the pilot was able to restart the engine. He then began climbing back up to 2,000 feet msl; however, the engine lost power again. The airplane once again began to descend, but this time the pilot was unable to restart the engine. The airplane then struck trees and came to rest after falling approximately 20 feet to the ground. Total duration of the flight was approximately 4 hours and 43 minutes. Postaccident examination of the airplane revealed that the firewall and left wing were substantially damaged and both fuel tanks were absent of fuel. There was no evidence of any preimpact mechanical failure or malfunction of the airplane or engine. Correlation of radar and weather data revealed that the pilot would have encountered a headwind for the majority of the flight. When asked by a state trooper how the accident occurred, the pilot advised him that he had run out of fuel. ## Factual narrative Originally the pilot was going to depart earlier on the day of the accident and had planned to stop enroute to his destination for more fuel. After receiving a weather briefing he decided instead to delay his departure until later that evening due to the possibility of thunderstorms being present at his time of arrival in the vicinity of his destination airport. Prior to departure that evening he had the fuel tanks filled to capacity. During the flight despite his previous flight planning, he did not stop for more fuel. When he was approximately 64 miles from his destination, he noticed that his fuel gauges were indicating that he had less fuel than he anticipated. Upon arrival at his destination he flew an instrument approach and advised air traffic control that he was fuel critical, as he had exceeded his estimated flight time, his fuel gauges were indicating a low fuel state, and other aircraft were also landing. Due to the visibility, he was unable to see the runway environment and executed a missed approach. He was then instructed by Air Traffic Control to climb to 2,000 feet above mean sea level (msl). During the climb the engine lost power and the airplane began to descend. The pilot executed the engine restart procedure and was able to get the engine to restart. He then began climbing back up to 2,000 feet msl however, the engine lost power again. The airplane once again began to descend but this time; the pilot was unable to get the engine to restart. The airplane then struck trees and came to rest after falling approximately 20 feet to the ground. Total duration of flight was approximately 4 hours and 43 minutes. Post-accident examination of the airplane by a Federal Aviation Administration inspector revealed that the firewall and left wing were substantially damaged and both fuel tanks were absent of fuel. There was no evidence of any preimpact mechanical failure or malfunction of the airplane or engine. Correlation of radar and weather data revealed that the pilot for the majority of the flight would have encountered headwinds. The airplane was also not equipped with wheel fairings which according to the manufacturer would have further reduced its range by up to 7 percent. When asked how the accident occurred by a state trooper, the pilot advised him that he had run out of fuel. ## Aircraft - Registration: [N81917](https://openairdocs.org/deregistered/N81917-2012-12-10), registration cancelled 2012-12-10, S/N 28-8216139, built 1982 (OpenAirDocs) - Reported make and model: PIPER PA-28-161 - Registry model: [Piper PA-28-161](https://openairdocs.org/model/piper-pa-28-161) (registry code 7102803) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 28-8216139 - Airframe hours: 13107 - Engines: LYCOMING 0-320-D3G 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Wings of Carolina Flying Club - Registered owner: Fcs Aviation LLC - Airworthiness certificate: Standard, Normal - Last inspection: Annual, July 9, 2011 - Departed: CQX, Chatham, MA - Destination: RIC, Richmond, VA - Flight plan: IFR - Airport: RIC, Richmond International Airport, runway 25, 5,326 × 100 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 29; injuries: minor; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; last flight review July 21, 2011; seat: left; flight hours: 239 total, 29 in this make and model, 169 as pilot in command, 39 in the last 90 days, 22 in the last 30 days ## Weather - Conditions: Instrument (IMC), Night - Wind: 220° at 4 knots - Visibility: 6 statute miles - Lowest ceiling: 600 ft overcast - Temperature: 75 °F, dew point 73 °F - Altimeter: 29.76 inHg - Observed at: RIC, 6 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 20110726015519A](https://openairdocs.org/incident/20110726015519A), Jul 26, 2011: Piper PA-28-161, Quinton, VA, Destroyed. Pilot made a forced landing in a wooded area after reporting low fuel while on an IFR approach to richmond airport (ric). Aircraft departed kcqx on 7/25/11 at… ## Docket (7 files) The files NTSB released with the investigation on September 27, 2011, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=81229. 3.4 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 601 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40353287&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Witness Statements and Interview Summaries (item 2, .PDF, 96 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40353288&FileExtension=.PDF&FileName=Witness%20Statements%20and%20Interview%20Summaries-Redacted.PDF - FlightAware Tracking Information (item 3, .PDF, 359 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40353289&FileExtension=.PDF&FileName=FlightAware%20Tracking%20Information-Master.PDF - Approach Plate (VOR Runway 25) (item 4, .PDF, 38 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40353290&FileExtension=.PDF&FileName=Approach%20Plate%20(VOR%20Runway%2025)-Master.PDF - Excerpts from Piper Cherokee Warrior II Pilot Operating Handbook (Section 5: Performance) (item 5, .PDF, 190 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40353291&FileExtension=.PDF&FileName=Excerpts%20from%20Piper%20Cherokee%20Warrior%20II%20Pilot%20Operating%20Handbook%20(Section%205%3A%20Performance)-Master.PDF - Weather Reports and Records (item 6, .PDF, 882 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40353292&FileExtension=.PDF&FileName=Weather%20Reports%20and%20Records-Master.PDF - Photograph of Main Wreckage (FAA) (item 7, .PDF, 1.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40353295&FileExtension=.PDF&FileName=Photograph%20of%20Main%20Wreckage%20(FAA)-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.