25 Jul 2015: PIPER PA-28-151 — VERESPY STEPHEN J JR

25 Jul 2015: PIPER PA-28-151 (N777EX) — VERESPY STEPHEN J JR

No fatalities • Perkasie, PA, United States

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.

— NTSB Determination

Accident 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 inspection was 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.

Contributing factors

  • cause Pilot
  • cause Airspeed — Not attained/maintained
  • factor Engine fuel and control

Conditions

Weather
VMC, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.