ASN Wikibase Occurrence # 269125
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Friday 22 October 2021 |
| Time: | 15:57 |
| Type: |  Piper PA-32R-300 Cherokee Lance |
| Owner/operator: | Demelva Aviation LLC |
| Registration: | N1652H |
| MSN: | 32R-7780168 |
| Year of manufacture: | 1977 |
| Total airframe hrs: | 6049 hours |
| Engine model: | Lycoming IO-540-K1G5D |
| Fatalities: | Fatalities: 1 / Occupants: 2 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | near Walterboro, SC -
 United States of America
|
| Phase: | En route |
| Nature: | Private |
| Departure airport: | Fredericksburg-Shannon Airport, VA (KEZF) |
| Miami Executive Airport, FL (TMB/KTMB) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
On 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 from its home airport for an airport about 802 nautical miles away with the airplane's fuel tanks filled to their total fuel capacity of 98 gallons. The pilot planned for the flight to only be a single leg, but about 1.5 hours into the flight he decided to land for fuel due to the 20-knot headwind, which he had not accounted for during his flight planning. About 2 hours and 53 minutes into the flight, the pilot advised air traffic control (ATC) that he wanted to divert for fuel and then resume his instrument flight rules (IFR) flight plan to his destination. The air traffic controller cleared the pilot to fly direct to a diversion airport. When the airplane was approximately nine miles north of the diversion airport, at an assigned altitude of 1,600 feet msl, the pilot declared “Mayday' and reported a “lagging engine.' The pilot described that, when he reached 1,600 feet, he pushed the throttle forward to level off from the preceding descent, but the engine did not respond. The engine then surged (went up and back down), but it would not respond to his throttle inputs. The airplane subsequently impacted trees short of the diversion airport. During the impact sequence, the pilot was seriously injured and the passenger was fatally injured.
The pilot had flown for about 3 hours, and 351 miles of the 802-mile flight, at the time of the accident. Fuel consumption calculations indicated that, depending on the power setting, more than half of the fuel load of 94 gallons of usable fuel would have been consumed before the accident (about 47.7 to 56.7 gallons, depending on power setting). This was greater than the usable fuel amount in each wing (47 gallons per side). While the pilot stated that he checked the fuel gauges every 15 minutes and would continue flying on the fuel tank that had the higher fuel indication, the Pilot's Operating Handbook (POH) for the airplane, advised that 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. 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.'
Postaccident examination of the airplane at the accident site revealed the postimpact fire had a burn pattern that appeared to initiate from the area of the right wing. Residual fuel was found in the right outboard fuel tank, and fuel staining was also present around the fuel filler port for the right wing. However, minimal thermal damage was present on the inboard leading edge of the left wing, and residual fuel and fuel staining were not evident. This physical evidence suggests that little or no fuel was present in the left wing fuel tanks, and that the majority of the fuel onboard the airplane at the time of the accident was in the right wing tanks. The postaccident examination of the engine did not reveal evidence of any preimpact failures or malfunctions that would have precluded normal operation.
Based on this information, it is likely that the loss of power was due to the left wing having little or no usable fuel available, which subsequently introduced air into the fuel lines. Thus, after the loss of power, the fuel in the right wing would not have been a reliable source of fuel to quickly restore engine power. Based on the available evidence, the circumstances of the accident are consistent with fuel starvation resulting from the pilot's mismanagement of the fuel system during the flight.
Probable Cause: The pilot's inadequate fuel planning and fuel management, which resulted in a loss of engine power due to fuel starvation.
Accident investigation:
 |
|
Sources:
NTSB ERA22FA026
https://data.ntsb.gov/Docket?ProjectID=104150
https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=1652H
https://flightaware.com/live/flight/N1652H/history/20211022/1645Z/KEZF/KTMB
Location
Images:
Photo: NTSB
Media:
NTSB is investigating the Oct. 22, 2021, crash of a Piper PA-32R-300 airplane near Walterboro, South Carolina.
— NTSB_Newsroom (@NTSB_Newsroom) October 22, 2021
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 22-Oct-2021 22:13 | Captain Adam | Added |
| 22-Oct-2021 22:41 | Captain Adam | Updated [Aircraft type, Location, Embed code, Narrative] |
| 23-Oct-2021 00:47 | Geno | Updated [Source, Embed code] |
| 23-Oct-2021 04:02 | RobertMB | Updated [Time, Operator, Nature, Source] |
| 23-Oct-2021 13:54 | johnwg | Updated [Phase, Narrative, Category] |
| 24-Oct-2021 04:44 | RobertMB | Updated [Registration, Cn, Operator, Total fatalities, Departure airport, Destination airport, Source, Narrative] |
| 28-Oct-2021 22:39 | Captain Adam | Updated [Narrative] |
| 12-Nov-2021 20:13 | aaronwk | Updated [Time, Narrative, Category] |
| 18-Nov-2021 16:56 | Captain Adam | Updated [Source, Narrative] |
| 22-Dec-2023 11:22 | ASN Update Bot | Updated [Time, Other fatalities, Source, Narrative, Accident report] |
| 22-Dec-2023 12:29 | Captain Adam | Updated [Time, Source, Narrative, Photo] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation