# NTSB GAA18CA574: Piper PA24, N6148P, Crewe, VA, September 29, 2018 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: September 29, 2018, 15:30 local (19:30 UTC) - Place: Crewe, VA - Coordinates: 37.183612, -78.101943 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=37.1836&lon=-78.1019&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing: Aerodynamic stall/spin](https://openairdocs.org/ntsb-events/241) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report April 8, 2019 - Report: Approved by Office Director - NTSB office: General Aviation Accidents - Parties: FAA - NTSB case key (mKey): 98393 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA18CA574 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/98393/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=98393 - Page: https://openairdocs.org/ntsb/GAA18CA574 ## Probable cause The pilot’s failure to maintain adequate airspeed and his exceedance of the airplane’s critical angle of attack, which resulted in an aerodynamic stall. Contributing to the accident was the pilot’s improper fuel management, which resulted in fuel starvation and the subsequent total loss of engine power. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Piper PA-24-250, 34 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=7102404), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Performance/control parameters: airspeed](https://openairdocs.org/ntsb-findings/01062010): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Piper PA-24-250, 12 cases](https://openairdocs.org/ntsb-findings/01062010/cases.md?model=7102404), [All aircraft, 1,681 cases](https://openairdocs.org/ntsb-findings/01062010/cases.md) - [Performance/control parameters: angle of attack](https://openairdocs.org/ntsb-findings/01062042): Aircraft › Aircraft oper/perf/capability · Capability exceeded (probable cause); cases with it: [Piper PA-24-250, 9 cases](https://openairdocs.org/ntsb-findings/01062042/cases.md?model=7102404), [All aircraft, 990 cases](https://openairdocs.org/ntsb-findings/01062042/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,695 cases](https://openairdocs.org/ntsb-findings/01071010/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,391 cases](https://openairdocs.org/ntsb-findings/02063015/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach: Fuel starvation](https://openairdocs.org/ntsb-events/191); 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: 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) - [Approach: Attempted remediation/recovery](https://openairdocs.org/ntsb-events/060); cases with it: [Piper PA-24-250, 6 cases](https://openairdocs.org/ntsb-events/060/sequence.md?model=7102404), [All aircraft, 1,422 cases](https://openairdocs.org/ntsb-events/060/sequence.md) - [Landing: Aerodynamic stall/spin](https://openairdocs.org/ntsb-events/241) (defining event); cases with it: [Piper PA-24-250, 12 cases](https://openairdocs.org/ntsb-events/241/sequence.md?model=7102404), [All aircraft, 1,529 cases](https://openairdocs.org/ntsb-events/241/sequence.md) - [Landing: Hard landing](https://openairdocs.org/ntsb-events/092); cases with it: [Piper PA-24-250, 6 cases](https://openairdocs.org/ntsb-events/092/sequence.md?model=7102404), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md) - [Landing: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Piper PA-24-250, 11 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=7102404), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) ## Analysis The pilot reported that, after a cross-country flight, he wanted to fuel the airplane at the airport, but the fuel tanks were locked. He then flew to a nearby airport to fuel the airplane, but once over the airport, he was told via the UNICOM frequency that the airport was closed for construction and that he would not be able to land. He returned to the departure airport, and as he reduced power and performed his "gump" check, the engine lost total power. He switched from the left fuel tank to the right fuel tank, turned the fuel pump on, and pumped the throttle to no avail. He continued downwind and abeam the runway numbers and added flaps. On base, he felt the airplane was low and decided to head straight for the runway. Near the beginning of the runway, the airplane aerodynamically stalled and landed hard. The airplane slid about 300 ft and came to rest in the grass adjacent the runway. The airplane sustained substantial damage to the left wing. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The Federal Aviation Administration inspector reported that he verified that the left fuel tank was completely empty. He also removed the drain plug from the carburetor, which was also empty. Additionally, the insurance adjuster reported that he looked into the fuel tanks with a scope and saw that the left fuel tank was "bone dry" and that the right tank had about 12 gallons of fuel. ## Factual narrative The pilot reported that, after a cross country flight, he wanted to fuel the airplane at the airport, but the fuel tanks were locked. He then flew to a nearby airport to fuel the airplane, but once over the airport he was told via the universal communication frequency (UNICOM) that the airport was closed for construction and he would not be able to land. He returned to the departure airport and as he reduced power and performed his "gump" check, the engine had a total power loss. He switched from the left fuel tank to the right fuel tank, turned the fuel pump on, and pumped the throttle, but "still no power". He continued downwind and abeam the runway numbers, he added flaps. On base, he felt the airplane was low and decided to head straight for the runway. Near the beginning of the runway, the airplane aerodynamically stalled and landed hard. The airplane slid about 300 ft and came to rest in the grass adjacent the runway. The airplane sustained substantial damage to the left wing. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The Federal Aviation Administration inspector reported that he verified that the left fuel tank was completely empty. He also removed the drain plug from the carburetor, which was empty as well. Additionally, the insurance adjuster reported that he looked into the fuel tanks with a scope and observed that the left fuel tank was "bone dry" and the right tank had about 12 gallons of fuel. ## Aircraft - Registration: [N6148P](https://openairdocs.org/deregistered/N6148P-2019-06-29), registration cancelled 2019-06-29, S/N 24-1249, built 1959 (OpenAirDocs) - Reported make and model: Piper PA24 (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-1249 - Year built: 1959 - Engines: Lycoming O-540 SERIES 250 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, May 21, 2018 - Departed: W81, Crewe, VA - Destination: W81, Crewe, VA - Airport: W81, Crewe Muni, runway 33, 3,300 × 60 ft, asphalt - Equipment: Handheld GPS ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 51; injuries: none; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; last flight review November 2, 2017; seat: left; flight hours: 448 total, 157 in this make and model ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 79 °F, dew point 66 °F - Altimeter: 30.25 inHg - Observed at: KBKT, 9 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 20180929016509A](https://openairdocs.org/incident/20180929016509A), Sep 29, 2018: Piper PA-24-250, Crewe, VA, Substantial damage. Pilot states that he landed at Crewe airport, W-81 and attempted to get fuel. Since the fuel pumps were locked, he attempted to fly to farmville airport… ## Other investigations on N6148P (2) 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 MIA68D0114](https://openairdocs.org/ntsb/MIA68D0114), Apr 29, 1967: Piper PA-24 (N6148P), Omega, GA, substantial damage - [NTSB MIA67F0201](https://openairdocs.org/ntsb/MIA67F0201), Jul 8, 1966: Piper PA-24 (N6148P), Jacksonville, FL, substantial damage ## Docket (6 files) The files NTSB released with the investigation on December 17, 2018, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=98393. 2.8 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 2.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40469568&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Pilot's Statement (item 2, .PDF, 319 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40469569&FileExtension=.PDF&FileName=Pilot%27s%20Statement-Master.PDF - Record of Conversation - Pilot (item 3, .PDF, 68 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40469570&FileExtension=.PDF&FileName=Record%20of%20Conversation%20-%20Pilot-Master.PDF - Record of Conversation - FAA (item 4, .PDF, 67 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40469571&FileExtension=.PDF&FileName=Record%20of%20Conversation%20-%20FAA-Master.PDF - Record of Conversation - Insurance Adjuster (item 5, .PDF, 67 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40469572&FileExtension=.PDF&FileName=Record%20of%20Conversation%20-%20Insurance%20Adjuster-Master.PDF - Accident Photo (item 6, .PDF, 1 photo, 158 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40469573&FileExtension=.PDF&FileName=Accident%20Photo-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.