N1652H

Destroyed
Fatal

PIPER PA-32R-300S/N: 32R-7780168

Accident Details

Date
Friday, October 22, 2021
NTSB Number
ERA22FA026
Location
Walterboro, SC
Event ID
20211022104150
Coordinates
33.042500, -80.598217
Aircraft Damage
Destroyed
Highest Injury
Fatal
Fatalities
1
Serious Injuries
1
Minor Injuries
0
Uninjured
0
Total Aboard
2

Probable Cause and Findings

The pilot’s inadequate fuel planning and fuel management, which resulted in a loss of engine power due to fuel starvation.

Aircraft Information

Registration
Make
PIPER
Serial Number
32R-7780168
Engine Type
Reciprocating
Model / ICAO
PA-32R-300P32R
Aircraft Type
Fixed Wing Single Engine
No. of Engines
1
Seats
7
FAA Model
PA-32R-300

Registered Owner (Current)

Name
DEMELVA AVIATION LLC
Address
7854 MIDDAY LN
City
ALEXANDRIA
State / Zip Code
VA 22306-2724
Country
United States

Analysis

HISTORY OF FLIGHTOn October 22, 2021, about 1557 eastern daylight time, a Piper PA-32R-300 airplane, N1652H, was destroyed when it was involved in an accident near Walterboro, South Carolina. The pilot was seriously injured, and the passenger was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 personal flight.

The airplane departed on an 802 nautical mile flight from Shannon Airport (EZF), Fredericksburg, Virginia, about 1256 destined for Miami Executive Airport (TMB), Miami, Florida. Before departure, the pilot brought the airplane’s fuel tanks up to their total fuel capacity of 98 gallons by adding 78.81 gallons of 100LL aviation gasoline.

The flight was uneventful until about 2 hours and 53 minutes into the flight, when the airplane was in cruise at 6,000 feet above mean sea level (msl). The pilot advised air traffic control (ATC) that he wanted to divert to Lowcountry Regional Airport (RBW), Walterboro, South Carolina, for fuel, and then resume his IFR flight plan to TMB.

The air traffic controller then cleared the pilot to fly direct to RBW and approved him to leave the frequency to get the current weather and NOTAMS for the airport. When the pilot reported that he was back on frequency, the air traffic controller instructed him to maintain 3,000 feet msl and to state his approach request. The pilot requested the visual approach to runway 23. The air traffic controller then instructed the pilot to maintain 1,600 feet msl, and subsequently instructed him to fly heading 190° to the RBW Airport.

The airplane was approximately nine miles north of RBW when the airplane began to descend without a clearance. The pilot then declared “Mayday” and reported a “lagging engine” to which the air traffic controller advised that RBW was at one o’clock and seven miles, and to maintain present heading and altitude.

The minimum safe altitude warning then activated at the air traffic controller’s station as the airplane descended through 1,000 feet msl. The air traffic controller queried the pilot if they were reporting a rough running engine, to which there was no response. The airplane continued descending while in a left turn to the northeast and was last observed by ATC radar at an altitude of 100 feet msl. There was no further communication with the pilot.

According to a witness, he heard an airplane “sputter and stop.” He looked in the direction of the airplane, and continued to hear sputtering, before the sound of an engine cut out, and then sputtering again. The airplane kept flying and then went out of sight.

According to two other witnesses, about 1556, they began to hear an engine noise. They observed [the accident airplane] almost directly above the tree line behind their neighbor’s house. It appeared to be in a left turn, and then they next heard a loud “pop” from the airplane and the engine noise ceased.

According to the pilot, once he arrived at the airport, he pulled the airplane out of the hangar with his tug, loaded their baggage, boarded the airplane, and then started the engine. He then taxied to the fuel pumps. He filled both wing tanks all the way up (just below the caps). He then took off. The weather was VMC and he had filed an instrument flight rules flight plan. He planned to cruise at 6,000 feet and he could not remember if he changed altitude at any time during the cruise portion of the flight.

He had filed the flight as one leg. About 1.5 hours into the flight, he decided to land for fuel due to the headwinds he encountered. He had also made the decision to get fuel early, as he would be landing at his destination at night.

He received the weather for the diversion airport and, as he was proceeding to the airport, he received a clearance to descend to 1,600 feet. He began the descent and pulled the power back. When he reached 1,600 feet, he pushed the throttle forward, but the engine did not respond. He then pulled it back towards idle to try and match the throttle to where the engine was operating. The engine surged (went up and back down). He pushed the throttle forward, but there was no response.

He then pitched the airplane to get the speed to about 90 knots (towards best glide). He then declared an emergency and when they were about 100 feet above the trees, he lowered the landing gear. He told the passenger to “Brace” as they were going to crash and transmitted: “Mayday, Mayday, Mayday” before the airplane contacted the trees. He could not remember anything after hitting the trees. The next thing he remembered was being in the hospital.

The pilot reported that he had his lap belt on, but the shoulder harness was broken, and had been that way since when he purchased the airplane. The passenger had her lap belt on, but he could not remember if she had her shoulder harness on. He did not try to check the magnetos or switch tanks after the loss of engine power.

He stated that fuel management was not an issue as he would set the timer on his Garmin unit every 15 minutes, and if the fuel tank he was on was higher than the other one he would stay on that tank. He would determine the quantity by looking at the fuel gauges to estimate what fuel he had. He also stated that he was at the halfway point and should have had enough fuel to make it, or close. He could not remember what tank he was on when the accident occurred. He added that he just wanted to configure the airplane for landing and all he saw was trees. PERSONNEL INFORMATIONAt the time of the accident, the pilot was a colonel in the United States Air Force, was rated as a command pilot, and had flown the T-37A, T-38A, C-130E, AT-38B, F-16C, A-10A, and A-10C.

According to Federal Aviation Administration (FAA) records, the pilot held a commercial pilot certificate, with ratings for airplane single-engine land, airplane multi-engine land, and instrument airplane.

His most recent FAA second-class medical certificate was issued on October 20, 2021. At the time of the accident, he had accrued approximately 1,968 total flight hours, of which about 76 hours were in the accident airplane make and model. AIRCRAFT INFORMATIONMaintenance Records

A review of partial copies of the airplane’s maintenance logbook entries had revealed that the engine had accumulated 2083.76 hours at the time of the most recent annual inspection dated August 5, 2021.

According to maintenance records, the airplane's most recent annual inspection was completed on August 5, 2021. At the time of the inspection, the airplane had accrued about 6,050 total hours of operation, and the engine had accrued about 2,084 hours since major overhaul.”

Fuel System

The fuel system consisted of two interconnected tanks in each wing, having a combined capacity of 49 U.S. gallons, for a total capacity of 98 U.S. gallons (94 usable). Fuel flow was indicated on a gauge located in the instrument panel. A fuel quantity gauge for each wing system was also located in the instrument panel, which indicated the amount of fuel remaining as transmitted by the electric fuel quantity sending units located in the wing tanks. An exterior sight gauge was installed in the inboard tank of each wing so fuel quantities could be checked on the ground during the preflight inspection of the airplane.

Fuel was drawn through a finger screen located in the inboard fuel tank and routed to a three-position fuel selector valve and filter unit which was located aft of the main spar. The valve had “OFF,” “LEFT,” and “RIGHT” positions that were remotely selected by means of a torque tube operated by a handle located in the pedestal. The handle had a spring-loaded detent to prevent accidental selection to the “OFF” position. From the selector valve the fuel would go to the electric fuel pump, which also was mounted aft of the main spar and then would go forward to the engine-driven fuel pump, which forced the fuel through the injector unit into the engine.

Guidance for Fuel Tank Selection

According to the Pilot’s Operating Handbook (POH) for the airplane, to keep the airplane in best lateral trim during cruise flight, the fuel should be used alternately from each tank at one-hour intervals.

The POH also stated, “Always remember that the electric fuel pump should be turned ‘ON’ before switching tanks and should be left on for a short period thereafter. To preclude making a hasty selection, and to provide continuity of flow, the selector should be changed to another tank before fuel is exhausted from the tank in use. The electric fuel pump should be normally ‘OFF’ so that any malfunction of the engine driven fuel pump is immediately apparent.

If signs of fuel starvation should occur at any time during flight, fuel exhaustion should be suspected, at which time the fuel selector should be immediately positioned to a full tank and the electric fuel pump switched to the ‘ON’ position.” METEOROLOGICAL INFORMATIONSynoptic conditions

The National Weather Service Surface Analysis Chart for 1700 for the eastern United States depicted a low-pressure system at 1012 hectopascals over the Virginia and North Carolina border, with a cold front extending southwestward into North and South Carolina, Georgia, and into the Florida panhandle. The front then became a warm front and extended westward along the gulf coast. The accident site was located in the vicinity of the cold front. The station models in the vicinity of the accident site indicated westerly winds of 10 knots, clear to scattered clouds over the area with temperatures in the 80's °F, with dew point temperatures in the 60's °F. No significant weather or obstructions to visibility were identified surrounding the accident site.

Observations

The accident airplane was diverting to Lowcountry Regional Airport (RBW), Walterboro, South Carolina, which listed an elevation of 101 ft msl, with a magnetic variation of 7° W based on the sectional chart for the area. The airport had an Automated Weather Observation System (AWOS), which wa...

Data Source

Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# ERA22FA026