NYC95LA187 · Piper PA-28-180
Piper PA-28-180 · Accident: overrun during landing
From Martha's Vineyard Airport (MVY) to Fitchburg Municipal Airport (FIT)
Event
- NTSB case
- NYC95LA187
- 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-180
- 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
- N8252W
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Martha's Vineyard Airport (MVY), MARTHAS VINEYAR, MATo Fitchburg Municipal Airport (FIT), Fitchburg, MA
- 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 › Distance/speed, misjudged
Approximate · Estimated position: the centre of Norfolk, MA, the place the record names. Not the accident site.
NTSB narrative
The pilot noticed the weather on his route of flight was deteriorating. He elected to land and wait for the weather to improve. The pilot stated, '...upon reaching the airport bounds I encountered extremely heavy rain and moderate to severe turbulence...my forward visibility was zero.' The pilot reported he landed on the first third of the runway length, but was unable to stop due to hydroplaning, and the aircraft overran the runway. According to an FAA inspector, the pilot landed in heavy rain at higher than recommended speed and about half way down the runway, which had standing water. The aircraft collided with trees and a fence. Before takeoff, the pilot received weather information from a Flight Service Station, and was advised of possible heavy rain and thunderstorms.
Probable cause
The pilot's misjudgement of speed and distance during the landing, which resulted in a runway overrun. Factors relating to the accident were: heavy rain, wet runway, and hydroplaning conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC95LA187
- Event ID
- 20001207X04350
- Case number
- NYC95LA187
- 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: ecb7f8d36f1b01e135563a0495a9e03f4bcfd6e9c5ed4ae18e9fd9dd060fc9f9; retrieved 2026-09-22T23:27:03.324Z.