Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

July 25, 2015 · Piper PA-28-151 · N777EX

Perkasie, PA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
July 25, 2015
Injury Outcomes
No injuries (1 uninjured)
Location
Perkasie, PA
Aircraft
Piper PA-28-151 (1974)
Tail Number
N777EX
Operator
Verespy Stephen J Jr
Injuries
None
Aircraft Damage
Substantial
NTSB Number
ERA15LA285

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.

NTSB 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.

Full 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.

Flight

Event TypeAccident
Event Time12:30 EDT
Nearest AirportPennridge Airport (0nm N)
Runway26
Runway Length4211 ft
Runway Width100 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-28-151
Tail NumberN777EX
Aircraft CategoryAir
DamageSubstantial
OperatorVerespy Stephen J Jr
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320 SERIES · Reciprocating · 150
Seats4

People & Injuries

Injury SummaryNo injuries (1 uninjured)
Fatal0
Serious0
Minor0
Uninjured1
Total1
Crew 1Age 71 · Third Class · None

Conditions

ConditionsVMC
LightDaylight
WindCalm
Visibility10 sm
CeilingNone
Temperature / Dew Point55
Altimeter30.00 inHg
Observation Time16:54
Weather SourceWFAC

Appendix: Source Data