NYC93LA179 · Piper PA-28-161
Piper PA-28-161 · Accident: overrun during landing
From Wilkes Barre Wyoming Valley Airport (WBW) to an unrecorded destination
Event
- NTSB case
- NYC93LA179
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Piper PA-28-161
- Aircraft type
- Piper PA-28
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N2572U
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Wilkes Barre Wyoming Valley Airport (WBW), Forty Fort, PATo not recorded
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · landing roll
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Overrun
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Altitude, misjudged
- Pilot in command › Distance, misjudged
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC93LA179
- Event ID
- 20001211X13251
- Case number
- NYC93LA179
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 30abd5a4cf631c26816170a2833e5928b910904efadbd00ee2263bbe97b6f5a9; retrieved 2026-09-23T01:41:40.366Z.