Skip to content

Atlas / NTSB / NYC93LA179

NTSB CAROL · Event

Event NYC93LA179

1993-08-29 WEST MIFFLIN, Pennsylvania, United States Airport · AGC None 1 aircraft Status: Completed

Registry · N2572U

FAA Aircraft Registry record.

Make / Model

PIPER PA-28-161

Engine

LYCOMING 0-320 SERIES (180 hp)

Seats / Engines

4 seats · 1 engine

Last airworthiness date

19790816

ADS-B equipped

Yes — Mode-S A27430

Registrant of record

VAN SCOY BRIDGET ANNE

Source: FAA Aircraft Registry (releasable master file).

Aircraft involved

Probable cause & findings

The pilot's misjudgement of speed and distance, which resulted in a landing overrun of the runway. Factors were an embankment and the pilot not being able to abort the landing.

Factual narrative

On Sunday, August 29, 1993, at about 1600 eastern daylight time, a Piper PA-28-161, N2572U, piloted by Mr. Patrick Flannery, departed the end of the runway during the landing roll at the Allegheny County Airport, West Mifflin, Pennsylvania. The airplane was substantially damaged. The pilot was not injured. Visual meteorological conditions prevailed at the time and no flight plan had been filed. The flight was being conducted under 14 CFR 91. The pilot said he had just touched down on runway 23, and "...decided that my speed was too high and that a go- around would be appropriate." The pilot added power, retracted the flaps and before he could call the tower he noticed, "...what I believed to be a helicopter at low altitude in close proximity to my left...moving in the direction of my planned flight path." The pilot then attempted to stop the airplane, but he said. "...I reached the end of the runway...but could not stop before running off the runway." According to FAA Inspector, Dennis Ferencz's report: ...the aircraft...slid off the end of the runway and came to rest at the bottom of an embankment...it appeared that the aircraft landed at a point approximately 1934 feet past the approach end of the runway which is 2534 feet long. This was apparent by the black skid marks that began at this point and continued for approximately 600 feet to the end of the runway. At the end of the runway is an embankment which drops down approximately 12 feet... According to FAA Inspector, Dennis Ferencz, the pilot told him after the accident that he was high on the approach and had to lower the nose of the airplane to make the runway. In a memo to the Safety Board Mr. Ferencz wrote: ...N2572U landed long on runway 23...control tower personnel state that N2572U touched down at a point between runway 10/28 and taxiway "A"...approximately 650 [feet] from the departure end of runway 23... THE PILOT REPORTED AFTER TOUCHING DOWN ON RUNWAY 23, I DECIDED THAT MY SPEED WAS TOO HIGH AND THAT A GO-AROUND WOULD BE APPROPIATE. I STARTED TO ADD POWER, RETRACTED FLAPS, AND KEYED THE MICROPHONE TO ALERT THE CONTROL TOWER AS TO MY INTENTIONS. HOWEVER, I THEN NOTICED WHAT I BELIEVED TO BE A HELICOPTER AT LOW ALTITUDE IN CLOSE PROXIMITY TO MY LEFT AND MOVING IN THE DIRECTION OF MY PLANNED FLIGHT PATH. I DECIDED TO TRY TO STOP THE AIRCRAFT; I REDUCED POWER AND BEGAN TO APPLY THE BRAKES. I REACHED THE END OF THE RUNWAY AT SLOW SPEED, BUT COULD NOT STOP BEFORE RUNNING OFF THE RUNWAY.' THE AIRPLANE WENT DOWN A 12 FOOT EMBANKMENT AND CAME TO A STOP. A WITNESS REPORTED THE AIRPLANE TOUCHED DOWN ABOUT 2/3 THE LENGTH OF THE RUNWAY. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12

Verbatim from NTSB's published report. Source file NTSB_1993_NYC93LA179.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.

Related research

What the literature says.

Academic papers and agency reports matching this event's aircraft type or causal vocabulary (go-around). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.

Browse the full corpus — academia portal ↗