FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA23FA067 · Piper PA-30

19 Nov 2022 · Winston-Salem, NC, United States

Piper PA-30 · Accident: loss of control in flight while maneuvering

From London-Corbin Airport/Magee Field (LOZ) to Smith Reynolds Airport (INT)

Report a problem

Event

NTSB case
ERA23FA067
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
2 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Piper PA-30

Aircraft type
Piper PA-30
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N7295Y
Operator
Unknown
Onboard fatalities
Unknown
Route
From London-Corbin Airport/Magee Field (LOZ), London, KYTo Smith Reynolds Airport (INT), Winston-Salem, NC
Aircraft age
About 58 years (built 1964)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Maneuvering
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

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.

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA23FA067
Event ID
20221119106324
Case number
ERA23FA067
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, cause areas. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: d74dd9baa96d184e24661426dd02f21a4edac97709356e49fdf830885a293fe5; retrieved 2026-09-15T07:54:20.542Z.