PIPER PA30 - NO SERIES near Bullhead City, AZ — 2014-04-21
- Date
- 2014-04-21
- Location
- Bullhead City, AZ, USA
- Airport
- A20
- Aircraft
- PIPER PA30 - NO SERIES
- Registration
- N7880Y
- Category
- Airplane
- Highest injury
- Minor
- Fatalities
- 0
- Phase of flight
- Approach
Probable cause
The pilot's mismanagement of the throttle and propeller controls during the attempted go-around after encountering turbulence, which resulted in his failure to maintain adequate airspeed and climb rate and a subsequent forced landing and impact with terrain. Contributing to the accident was the pilot’s lack of knowledge about the airplane’s equipment.
NTSB narrative
The pilot reported that, upon arrival at the airport, he overflew the runway, checked the wind direction, and then entered the downwind leg for a landing to the north. While turning onto final approach, the airplane encountered severe turbulence, at which time the pilot initiated a go-around by adding full power to both engines. However, he noted that "it seemed like the airplane would not fly" and that it was "like it was being pushed down." He added that he was not sure if the engines completely failed or not but that "I just know I didn't have any power." The airplane subsequently impacted terrain about 1/4 mile from the departure end of the runway and then came to rest upright. The airplane sustained substantial damage to the wings and empennage. Postaccident examination of the airplane and engine revealed no mechanical malfunctions or failures that would have precluded normal operation. Fuel was drained from both the left and right fuel tanks, and no water or sediment was observed. The left propeller blades were found in the feathered position, and the right propeller blades were found in low pitch. The feathered propellers indicated that, despite the pilot's statement that the engine did not have power, the engine likely did have power but no thrust. Followup discussions with the pilot revealed that he had been improperly using the propeller controls as the throttles, with the throttle controls in the full-forward position, during the flight. Additionally, the pilot had pulled both propeller controls to the full-feather position upon touching down on the runway and then abruptly advanced them when he initiated a go-around rather than using the throttle as required. The pilot reported that he had an extensive amount of flight time in another airplane make and model that was configured with the propeller and throttle controls oriented in a position directly opposite their position in the accident airplane. The pilot's mismanagement of the throttle and propeller controls during the attempted go-around after encountering turbulence resulted in insufficient airspeed and degraded climb performance and a subsequent forced landing and impact with terrain.
Analysis
- Primary failure mode
- Automation / mode confusion
- First missed decision gate
- Pilot could have clarified control usage before flight to prevent confusion.
NTSB coding
Evidence available
- Photos
- 10 docket documents
Docket documents10
- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1form
- Release of Aircraft Wreckage, NTSB Form 6120.15form
- Statement From A&P Mechanic - Mark Naumerinterview
- Excerpts From Maintenance Recordsother
- Record of Conversation - FAA Inspectorother
- Weather Dataother
- Photo 1 - Propellers (Photo Courtesy of FAA)photos
- Photo 2 - Power Control Quadrant (Photo Courtesy of FAA)photos
- Photo 3 - Earlier Beechcraft Baron Model Power Control Quadrant (Photo Courtesy of Textron Aviation)photos
- FAA Inspector's Reportreport
Related mishaps
- Mooney M20C
2020-08-19 · Hillsboro, OR
- MUSTANG II
2018-11-02 · Broomfield, CO · 2 fatalities
- CESSNA 172N
2016-11-18 · Moss Beach, CA · 1 fatality
- CESSNA 172N
2014-01-25 · Boulder, CO
- CESSNA 182P
2012-09-02 · Newberry, MI
- Beech C23
2008-08-06 · Augusta, KS