GAA17LA090

NTSB accident investigation · Piper PA28R · Watertown, WI · November 5, 2016

Accident · No injuriesLimited investigationFinal report
Date
November 5, 2016, 15:00 local (20:00 UTC)
Place
Watertown, WI
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N300KRPiper PA28R
Defining event
Approach-VFR pattern downwind: Miscellaneous/other
Weather
Visual (VMC) · Day
Status
Completed · report May 1, 2017
Report
Approved by Office Director
NTSB office
General Aviation Accidents
Parties
FAA
FAA report
20161105023039A
Case key
94471

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

The pilot’s failure to attain a proper glidepath on approach for landing, which resulted in impact with trees. Contributing to the accident was a partial, temporary loss of engine power for reasons that could not be determined because postaccident examination did not reveal any anomalies that would have precluded normal operation.

Findings · 4

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

AircraftAircraft › Aircraft power plant · MalfunctionPiper PA-28R-200: 1 caseAll aircraft: 151 casesProbable cause
Not determinedNot determined › Not determined · Unknown/Not determinedPiper PA-28R-200: 16 casesAll aircraft: 2,247 casesProbable cause
Performance/control parameters: descent/approach/glide pathAircraft › Aircraft oper/perf/capability · Attain/maintain not possiblePiper PA-28R-200: 5 casesAll aircraft: 809 casesProbable cause

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

The commercial pilot reported that he entered the downwind leg of the airport traffic pattern higher than pattern altitude to avoid a traffic conflict. While on downwind, he switched the fuel selector and turned on the electric fuel pump. As he turned from downwind onto the base leg of the traffic pattern, he reduced engine power to idle and initiated a glide toward the runway. On final approach, the pilot realized that the airplane was too low; he added engine power, but the engine "failed to respond." He cycled the fuel pump, the engine surged, and the airplane impacted treetops and landed short of the runway. The pilot further reported that, after landing, he taxied the airplane to the ramp, thus it is unlikely there was a fuel issue. A postaccident engine examination and test run revealed no anomalies that would have precluded normal operation.

Factual narrative

On November 5, 2016, about 1500 central standard time, a Piper Arrow II airplane, N300KP, had an engine hesitation when the pilot added power during short final approach to Watertown Municipal Airport (RYV), Watertown, Wisconsin. The airplane subsequently landed short of the runway. The airplane was registered to and operated by Wisconsin Aviation, Watertown, under the provisions of 14 Code of Federal Regulations Part 91 as a personal local flight. Visual meteorological conditions prevailed. The commercial pilot was not injured. The airplane departed RYV about 1400 and no flight plan was filed. The pilot reported that upon returning to the airport, after a local flight, he heard another aircraft in the left traffic pattern; he remained high when he entered the downwind leg, because he had lost sight of the other aircraft. He switched the fuel selector to the left fuel tank and turned the electric auxiliary fuel pump on. He reported that to help locate the other aircraft, he "slipped" the airplane for "a while" by applying "left rudder only," but then realized that he was still too high. He reduced the power to idle and glided from the downwind position to final. On final, he saw the airplane was going to be too low so he added power, but the engine "failed to respond." The pilot cycled the fuel pump switch off then back on and the "engine surged". The airplane struck treetops, the engine "sputtered", and the airplane landed short of the runway. The pilot reported that after landing, the propeller continued to rotate and he switched the fuel selector to the right fuel tank. He reported that he taxied the airplane to the tarmac without further incident. The pilot reported that during his preflight inspection, he drained fuel from all the fuel drains and did not observe any contaminants or debris in the fuel samples. He also reported that both fuel tanks were nearly full when he departed. The accident was not reported to the NTSB until 30 days after the accident, and the fuel quantity could not be verified. During a postaccident engine and airframe examination at an aircraft maintenance facility, the engine was run and all systems operated normally. The engine ran on both the right and the left fuel tanks. A visual inspection of the engine and its systems showed no defects. In the Operating Tips section of the Piper Arrow II Pilot's Operating Manual, it states in part: The shape of the wing fuel tanks is such that in certain maneuvers the fuel may move away from the tank outlet. If the outlet is uncovered, the fuel will be interrupted and a temporary loss of power may result. Pilots can prevent inadvertent uncovering of the outlet by avoiding maneuvers which could result in uncovering the outlet. Extreme running turning takeoffs should be avoided as fuel flow interruption may occur. Prolonged slips or skids which result in excess of 2000 feet of altitude loss, or other radical or extreme maneuvers which could cause uncovering of the fuel outletmust be avoided as fuel flow interruption may occur when tank being used is not full. The Federal Aviation Administration published the Advisory Circular (AC) 90-66A. This AC discusses recommended traffic pattern practices at airports without operating control towers and states in part: Arriving aircraft should be at the appropriate traffic pattern altitude before entering the traffic pattern. Entry to the downwind leg should be at a 45-degree angle abeam the midpoint of the runway. It is recommended that airplanes observe a 1000-foot above ground level (agl) traffic pattern altitude.

Aircraft

Registration
N300KR
Reported as
Piper PA28R (200)
Category
Airplane
Serial number
28R-7635210
Built
1976
Airframe hours
8,021.8
Engine
Lycoming IO-360-C1C, 200 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Operator
Wisconsin Aviation, doing business as Wisconsin Aviation
Registered owner
Wisconsin Aviation-Four Lakes Inc
Airworthiness certificate
Standard, Normal
Last inspection
Annual · July 12, 2016
Departed
RYV · Watertown, WI
Destination
RYV · Watertown, WI
Airport
RYV · Watertown Muni, runway 23, 4,429 × 75 ft, asphalt
Equipment
Auto-pilot, Stall warning system

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
80
Injuries
None
Certificate
Commercial
Airplane ratings
Single-engine land
Instrument ratings
Airplane
Medical
Class 3, With waivers/limitations
Last flight review
June 12, 2015
Seat
Left
Restraint
3-point
Flight hours
4,284 total · 100 in this make and model

Weather

Conditions
Visual (VMC) · Day
Wind
Calm
Visibility
10 statute miles
Lowest ceiling
None
Temperature
66 °F, dew point 48 °F
Altimeter
30.23 inHg
Observed at
KRYV

Docket · 5

The files NTSB released with the investigation on March 16, 2017, on NTSB’s docket system: statements, records, photos and specialists’ reports. 1.8 MB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.

Other investigations on N300KR · 2

Matched to the same aircraft by N-number and date.