NYC96LA065 · Piper PA-46-350P
Piper PA-46-350P · Accident: overrun during landing
From Vero Beach Regional Airport (VRB) to N52
Event
- NTSB case
- NYC96LA065
- 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
- Instrument Meteorological Cond
Piper PA-46-350P
- Aircraft type
- Piper PA-46
- 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
- N9254X
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Vero Beach Regional Airport (VRB), Vero Beach, FLTo N52
- 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 · aborted
- 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 › Distance, misjudged
- Pilot in command › Go-around, not performed
Approximate · Estimated position: the centre of Bedminster, NJ, the place the record names. Not the accident site.
NTSB narrative
The pilot had received radar vectors for a straight in approach to runway 08. About 700 feet above mean sea level, he broke out of the clouds, saw the airport, and then circled to land on runway 30, which was 2,733 feet long and 65 feet wide. The pilot reported that he landed long, and about 200 feet from the runway end, he realized he would not stop on the remaining runway, so he aborted the landing. He was unable to get airborne, the airplane overran the runway, and impacted trees. The pilot reported no mechanical malfunctions. He stated that the accident could have been prevented if he had turned base farther out from the runway.
Probable cause
the pilot's failure to perform a go-around, and his misjudged distance during the landing resulting in the overrun and the subsequent collision with the trees during the aborted landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC96LA065
- Event ID
- 20001208X05314
- Case number
- NYC96LA065
- 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: 3724ce90056910957b7689268cf0e34d514f786151cee429d5ccd21f9eb7ea1b; retrieved 2026-09-21T21:57:39.813Z.