FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA24LA350 · Piper PA-24-250

17 Aug 2024 · Shirley, NY, United States

Piper PA-24-250 · Accident: abnormal runway contact during landing

From Martha's Vineyard Airport (MVY) to an unrecorded destination

Report a problem

Event

NTSB case
ERA24LA350
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
Event fatalities
Unknown
Ground fatalities
Unknown
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-24-250

Aircraft type
Piper PA-24
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
N7531P
Operator
Unknown
Onboard fatalities
Unknown
Route
From Martha's Vineyard Airport (MVY), Martha's Vineyard, MATo not recorded
Aircraft age
About 63 years (built 1961)
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
Defining eventThe 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
Abnormal runway contact
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot reported that the enroute portion of the cross-country flight was uneventful. He set up for an approach the 4,200-ft-long runway. He stated that he landed at the normal touchdown point, about 1,000 feet down the runway. When he applied wheel brakes, they did not respond enough to sufficiently slow the airplane. He then elected to abort the landing, but the airplane did not obtain enough lift and settled back toward the ground. The airplane contacted a perimeter fence and came to a stop in a grassy area. The pilot and the three passengers exited the airplane without injury and were met by first responders. An inspector with the Federal Aviation Administration (FAA) reported that there was substantial damage to the airplane’s wings, fuselage, and empennage. When asked to provide additional information about the wheel brakes, the pilot reported that he did not have an opinion either way whether the brakes malfunctioned. The FAA reported that damage to the airframe precluded a functional check of the brake system. A review of Automatic Dependent Surveillance-Broadcast track data revealed that the airplane’s ground speed on final approach (about 625 feet from the runway) reached about 132 mph. The pilot’s operating handbook for the airplane specified an approach airspeed of 82 mph. Additionally, the weather conditions at the airport at the time of landing included 3-knot tailwind for the landing runway.

Probable cause

The pilot’s excessive speed during the final approach, which resulted in a collision with a fence during the subsequent aborted landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA24LA350
Event ID
20240818194944
Case number
ERA24LA350
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, cause areas. 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: 19606e31c07ed00960be9d01444fe05eec83453c67690cbc2b5c8acab5747d2c; retrieved 2026-09-16T19:10:40.807Z.