Aviation Crash Map

Piper PA-30 N7295Y

19 November 2022 · Winston-Salem, North Carolina, United States · Fatal

Summary

On 19 November 2022 at about 16:10 local time, a Piper PA-30 registered N7295Y was involved in an accident near Winston-Salem, North Carolina, United States. 2 people were on board and 2 died. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.

The record

Date
at 16:10
Classification
Accident
Location
Winston-Salem, North Carolina, United States
Nearest airport
Smith Reynolds (INT)
Coordinates
36.1299, -80.2011
Aircraft
Piper PA-30
Registration
N7295Y
Category
Airplane
Year built
1964
Engines
2
Operator
Not recorded
Operating rule
Part 91: General Aviation
Purpose of flight
Personal
Phase of flight
Not recorded
Route
London → Winston-Salem
Aircraft damage
Substantial
Weather
VMC
Light
Day
NTSB number
ERA23FA067

People

2 people died.

On board Died Serious Minor Uninjured
2 2 0 0 0

Probable cause

Contamination and/or misalignment of the regulator section of the right engine’s fuel servo, which resulted in excessive idle fuel flow and a total loss of engine power. Also causal was the pilot's failure to land immediately on the nearest runway at the destination airport, his failure to feather the right propeller following the loss of engine power while approaching the airport, and his failure to maintain airspeed while maneuvering with one engine, which resulted in a loss of control at a low altitude.

Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.

Read the full NTSB narrative

Near the conclusion of the cross-country flight, when the airplane was flying about 2,175 ft pressure altitude and about 4 nautical miles due west of the approach end of runway 4 at the destination airport, the pilot broadcast on the frequency that one engine was not making as much power as the other, but that, “we’re ok.” The controller cleared the pilot to land on runway 4; however, for reasons that were not reported by the pilot, the airplane continued past the extended runway centerline for that runway. The pilot subsequently asked to land on runway 33, which was approved. The airplane continued on an easterly heading past the extended runway 33 centerline, then turned left on northwesterly heading flying parallel to runway 33. While flying east of the airport one witness noted the airplane banking left to about 45° before the wings rolled level and then banked about 10° to the left. The same witness reported that, while flying in a nose-up attitude just above the trees with the landing gear extended, the airplane rolled to an inverted position and descended straight down. The airplane impacted terrain behind a house. Postaccident examination of the flight controls, propellers, right propeller governor, left engine and its systems, and right engine powertrain, lubrication, exhaust, ignition, and air induction systems revealed no evidence of preimpact failure or malfunction. Neither propeller was feathered at impact. The damage to the left propeller was consistent with the engine developing some power at impact while the lack of damage to the right propeller was consistent with windmilling/rotating and not developing power at impact. Additionally, although it was not determined if there were any missing vortex generators (VG’s) on either wing at the time of the accident, the airplane’s performance was not changed by the installation of the VG’s. Thus, if any were missing at the time of the accident, it likely did not contribute to the accident. Postaccident operational testing of the right engine’s fuel servo revealed that it passed all four test points and the regulator hysteresis check, but it failed testing of the idle circuit, which should result in decreased fuel flow with movement of the throttle control from wide open to idle. The fuel flow when reducing the throttle to idle was about 2.6 times higher than what it should have been. Disassembly of the right fuel servo revealed internal contamination in the fuel section of the regulator that was determined to be acrylonitrile-butadiene-styrene (ABS), a thermoplastic, though the exact source of the contamination could not be determined. Following reassembly of the regulator with the internal contamination removed, the idle circuit test was repeated multiple times, and the fuel flow was within limits. Although it could not be determined if the excessive fuel flow during the idle circuit test was caused by the internal contamination or a combination of that and misalignment of the regulator section, the additional 0.011-inch clearance of the throttle valve at idle was likely the result of maintenance personnel attempting to remedy the excessive fuel flow when moving the throttle valve to idle. Thus, it is likely that during the descent approaching the airport with both engines operating at a reduced power setting, the excessive fuel flow to the right engine likely resulted in a total loss of engine power. Although the right engine likely sustained a total loss of engine power due to a malfunction of the fuel servo, it is likely that the pilot either did not, or delayed, feathering the right propeller until the propeller rpm slowed to where the propeller blades engaged on the start locks. In that position, an attempt to feather the propeller would not be possible until the propeller rpm increased above the speed that disengaged the start locks. The increased parasitic drag from the windmilling and unfeathered right propeller likely precluded the possibility of straight and level flight. Towards the end of flight, the airspeed likely reduced below the published Velocity Minimum Control (Vmc) speed, and the airplane rolled to an inverted position. Had the pilot either turned towards runway 4 which was the nearest runway after advising the controller of an engine malfunction, or feathered the right propeller following total loss of right engine power and maintained an airspeed above the published Vmc speed while continuing towards the airport, it is likely that he could have reached the airport and landed uneventfully.

Quoted verbatim from the NTSB record.

Other Piper PA-30 accidents

Date Aircraft Location Operator Outcome Died
14 Mar 2022 Piper PA-30
N8350Y
Sandown, United Kingdom - No injuries -
17 Mar 2022 Piper PA-30
N8357Y
Pond Creek, Oklahoma, United States - Fatal 3
4 Oct 2022 Piper PA-30
N7494Y
Milan, Georgia, United States - No injuries -
23 Aug 2022 Piper PA-30
N4009Y
St Ignatius, Montana, United States - Minor injuries -
15 Oct 2022 Piper PA-30
N7746Y
Tucson, Arizona, United States - No injuries -
28 Feb 2022 Piper PA-30
N7943Y
Farmingdale, New York, United States Century Air No injuries -

All 889 records for this type

Other accidents in this area

Date Aircraft Location Operator Outcome Died
16 Apr 2022 Schweizer SGS 2-33A
N7784S
Zebulon, North Carolina, United States North Carolina Soaring Association Minor injuries -
9 May 2022 Wingren Norman ESCAPADE
N86RD
Brasstown, North Carolina, United States - No injuries -
5 Sep 2022 Cessna 177B
N35243
Ivanhoe, North Carolina, United States - Serious injuries -
16 Jun 2022 Cessna 172
N5064H
Brevard, North Carolina, United States Franklin Air Services LLC Serious injuries -
13 Feb 2022 Pilatus PC-12/47E
N79NX
Beaufort, North Carolina, United States EDP Management Group LLC Fatal 8
20 Jun 2022 Piper PA-28-180
N9676J
Laurinburg, North Carolina, United States - No injuries -

All 170,864 records in United States