NYC00LA212 · Piper PA-46
Piper PA-46 · Accident: overrun during landing
From Teterboro Airport (TEB) to CQX
Event
- NTSB case
- NYC00LA212
- 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-46
- 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
- N555JV
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Teterboro Airport (TEB), TETERBORO, NJTo CQX
- 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 › Brakes(normal), delayed
Approximate · Estimated position: the centre of Chatham, MA, the place the record names. Not the accident site.
NTSB narrative
Once in the terminal area, the pilot was vectored to the final approach course for the GPS-A approach. The airplane entered visual meteorological conditions between 800 and 1,000 feet agl. Once clear of the clouds, the pilot executed a circle-to-land to the 3,000-foot long runway. The airplane touched down with a 6 to 8 knot right quartering tailwind, approximately 300 to 400 feet past the landing threshold with full flaps. During rollout, the pilot used the brakes, and the airplane decelerated to approximately 10 knots, noticing nothing unusual. The pilot planned to use the taxiway located at the end of the runway. He applied the right brake to exit onto the taxiway, but did not feel the airplane respond. He then applied both brakes. The airplane decelerated, but there was insufficient runway remaining to stop. The airplane departed the end runway, the right wing struck the ground, and the airplane came to a stop. No preimpact failures or malfunctions were identified with the airplane or any of its systems.
Probable cause
The pilot's delayed use of the brakes, which resulted in a runway overrun. Factors in the accident were the pilot's improper decision to land with a right quartering tailwind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC00LA212
- Event ID
- 20001212X21594
- Case number
- NYC00LA212
- 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: 83adff26faea732b02b65dba00a4f88a6e5c44ad33f41571302ddd05e76ed80b; retrieved 2026-09-21T20:08:34.832Z.