ERA15LA285

NTSB accident investigation · Piper PA-28-151 · Perkasie, PA · July 25, 2015

Accident · No injuriesLimited investigationFinal report
Date
July 25, 2015, 12:30 local (16:30 UTC)
Place
Perkasie, PA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N777EXPiper PA-28-151
Defining event
Landing: Landing area overshoot
Weather
Visual (VMC) · Day
Status
Completed · report November 19, 2015
Report
Approved by Office Director
NTSB office
Eastern Region Aviation
Parties
FAA/FSDO
FAA report
20150725015479A
Case key
91651

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 use the mixture control to override a throttle anomaly and reduce engine power, which resulted in excessive airspeed upon landing and a subsequent runway overrun. Contributing to the accident was the pilot’s inability to reduce the engine power via the throttle control for reasons that could not be determined because a postaccident examination and test run of the engine revealed no anomalies.

Findings · 3

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.

Action: lack of actionPersonnel issues › Action/decision · PilotPiper PA-28-151: 3 casesAll aircraft: 792 casesProbable cause
Performance/control parameters: airspeedAircraft › Aircraft oper/perf/capability · Not attained/maintainedPiper PA-28-151: 4 casesAll aircraft: 1,681 casesProbable cause
Engine fuel and controlAircraft › Aircraft power plant · Not specifiedPiper PA-28-151: 1 caseAll aircraft: 49 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 pilot reported that, while on approach to land after a short cross-country flight, he was unable to adequately slow the airplane because he could not reduce the engine power below 2,000 rpm by manipulating the throttle control. The pilot unsuccessfully attempted to land the airplane five times and conducted a go-around after each attempt. During the sixth attempted landing, the airplane touched down, but the pilot was unable to stop the airplane, and it overran the runway. When asked why he did not reduce the mixture control to slow the airplane, the pilot reported that he was concerned that the engine would lose all power. Examination of the wreckage revealed that the throttle linkage and carburetor were intact, and no anomalies were noted. During a subsequent engine test run, the engine started on the first attempt and ran continuously. The engine was run to 2,000 rpm, and a successful magneto check was performed. The engine was then run to full power (2,300 rpm), followed by a power reduction to idle without any anomalies noted.

Factual narrative

On July 25, 2015, about 1230 eastern daylight time, a Piper PA-28-151, N777EX, operated by a private individual, was substantially damaged during a runway overrun, while landing at Pennridge Airport (CKZ), Perkasie, Pennsylvania. The private pilot was not injured. The personal flight was conducted under the provisions of 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed and no flight plan was filed for the planned flight to Doylestown Airport (DYL), Doylestown, Pennsylvania. The flight originated from South Jersey Regional Airport (VAY), Mount Holly, New Jersey, about 1145.The pilot reported that earlier during the day, he flew from DYL to VAY uneventfully. During his return trip, on approach to DYL, he was unable to slow the airplane below 100 mph as he could not reduce the engine power below 2,000 rpm by manipulating the throttle control. The throttle lever was not jammed, but the engine did not respond when the throttle lever was moved toward a reduced power setting. After five unsuccessful attempts to land at DYL, the pilot diverted to CKZ due to its longer runway. He was still unable to reduce engine rpm below 2,000 by utilizing the throttle control. The pilot was eventually able to slow the airplane below 100 mph during his sixth approach, which was about 30 mph above the desired final approach speed, and he believed that he could stop on the runway with aggressive braking. The airplane touched down on runway 26, a 4,211-foot long asphalt runway, but the pilot was unable to stop before the end of the runway. The airplane subsequently traveled beyond the end of the runway and came to rest upright in a ditch. When asked why he did not reduce the mixture control to slow the airplane, the pilot reported that he was concerned the engine would lose all power. Examination of the wreckage by a Federal Aviation Administration inspector revealed that during the overrun, the nosegear collapsed and the left wing sustained substantial damage. The inspector did not observe any anomalies with the throttle control linkage. The wreckage was reexamined at a recovery facility on September 17, 2015. The throttle linkage was examined and no anomalies were noted. The carburetor was then removed for examination and no anomalies were observed with the butterfly valve. The carburetor was reinstalled for an engine test run. The wings had been removed from the airplane for transport to the recovery facility. The remaining fuselage was secured to a flatbed trailer and fuel was supplied via a 5-gallon container to the right wing side of the fuel selector valve. Once the battery was charged, the engine started on the first attempt and ran continuously. The engine was run to 2,000 rpm and a successful magneto check was performed. The engine was then run to a full power of 2,300 rpm, followed by a power reduction to idle without any anomalies noted. The airplane had been operated for about 11 hours since its most recent annual inspectionwas completed on May 11, 2015. The pilot reported a total flight experience of 817.3 hours; of which, 717.3 hours were in the same make and model as the accident airplane and 8.3 of those hours were flown during the 90-day period preceding the accident.

Aircraft

Registration
N777EX
Reported as
Piper PA-28-151
Category
Airplane
Serial number
28-7515039
Built
1974
Airframe hours
5,868
Engine
Lycoming O-320 SERIES, 150 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Operator
Verespy Stephen J Jr
Registered owner
Verespy Stephen J Jr
Airworthiness certificate
Standard, Normal
Last inspection
Annual · May 21, 2015 · 11 hours before
Departed
VAY · Mount Holly, NJ
Destination
DYL · Doylestown, PA
Airport
CKZ · Pennridge Airport, runway 26, 4,211 × 100 ft, asphalt
Equipment
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
71
Injuries
None
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, Without waivers/limitations
Last flight review
January 20, 2014
Seat
Left
Restraint
3-point
Flight hours
817 total · 717 in this make and model · 817 as pilot in command · 8 in the last 90 days · 3 in the last 30 days · 1 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
Calm
Visibility
10 statute miles
Temperature
82 °F, dew point 55 °F
Altimeter
30.00 inHg
Observed at
DYL, 10 nm away

Docket · 6

The files NTSB released with the investigation on October 23, 2015, on NTSB’s docket system: statements, records, photos and specialists’ reports. 1.3 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.