NYC91LA233 · Piper PA-34-200
Piper PA-34-200 · Accident: overrun during landing
From Lehigh Valley International Airport (ABE) to an unrecorded destination
Event
- NTSB case
- NYC91LA233
- 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-34-200
- Aircraft type
- Piper PA-34
- 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
- N55145
- Operator
- Jeff Van Arsdale
- Onboard fatalities
- Unknown
- Route
- From Lehigh Valley International Airport (ABE), Allentown, 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(cfi) › In-flight planning/decision, improper
- Pilot in command(cfi) › Proper touchdown point, not attained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
A SINGLE ENGINE CFI WAS RECEIVING DUAL INSTRUCTION TO BE UPGRADED TO A MULTI ENGINE CFI. THE PILOT RECEIVING INSTRUCTION WAS HAVING DIFFICULTY WITH RUNWAY ALIGNMENT AND HANDLING THE CROSSWIND AND TURNED CONTROL OF THE AIRPLANE OVER TO THE PIC. THE PIC CONTINUED THE APPROACH AND LANDING. THE RUNWAY SURFACE WAS WET FROM RAIN AND THE AIRPLANE OVERRAN THE RUNWAY AND WENT INTO A PLOWED FIELD. THE PIC SAID HE LANDED IN THE FIRST 1/3. A WITNESS SAID THE LANDING WAS 2/3 TO 3/4 DOWN THE RUNWAY WHICH IS 1953 FEET LONG. THE AIRPLANE WAS NOT EQUIPPED WITH BRAKE PEDALS ON THE RIGHT SIDE AND THE FAA SAID THEY DID NOT NOTICE ANY SKID MARKS IN THE GRASS. THE PIC SAID HE BRAKED THE AIRPLANE USING THE PARKING BRAKE LEVER LOCATED ON THE LOWER INSTRUMENT PANEL BETWEEN THE TWO PILOT SEATS.
Probable cause
AN OVERRUN AFTER THE PILOT-IN-COMMAND LANDED LONG ON A SHORT, WET RUNWAY. A FACTOR RELATED TO THE ACCIDENT WAS THE FAILURE OF THE PILOT TO MAKE A GO-AROUND.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC91LA233
- Event ID
- 20001212X18167
- Case number
- NYC91LA233
- 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: 613f416e07b3db9ee29a666be672004a0f45aba27782da96b65edf7a4cdf8832; retrieved 2026-09-21T23:26:53.362Z.