ERA26LA163 · Piper PA31T 1
Piper PA31T 1 · Accident: runway excursion during landing
From Montgomery County Airpark (GAI) to an unrecorded destination
Event
- NTSB case
- ERA26LA163
- 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
- Ongoing
- 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 PA31T 1
- Aircraft type
- Piper PA31
- 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
- N96MA
- Operator
- Avione
- Onboard fatalities
- Unknown
- Route
- From Montgomery County Airpark (GAI), Gaithersburg, MDTo not recorded
- Aircraft age
- About 48 years (built 1978)
- 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
- 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
- Runway excursion
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
On April 1, 2026, about 1635 eastern daylight time, a Piper PA-31T1, N96MA, was substantially damaged when it was involved in an accident near Ocean City, New Jersey. The pilot and passenger were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 positioning flight.
The pilot reported that the instrument flight rules (IFR) flight was uneventful from Gaithersburg, Maryland. The flight was cleared for a visual approach to runway 6 at Ocean City Municipal Airport (26N), Ocean City, New Jersey. The automated weather observation system (AWOS) reported the wind as calm and the pilot flew the GPS approach to runway 6, utilizing the lateral and vertical guidance. The airplane was configured for landing at the final approach fix, and the pilot flew a stable approach on the “blue” line (112 knots indicated airspeed, best one-engine inoperative climb speed), then slowed to final approach speed, once landing on the runway was assured.
About 300 ft above ground level, the pilot slowed the airplane further. The airplane landed on the appropriate touchdown point, and initial deceleration seemed normal. However, about 30 knots, the pilot was unable to slow the airplane further despite applying maximum brake pressure. The brakes appeared ineffective. He continued applying maximum pressure on the brake pedals. As the airplane departed the end of the 2,972-ft-long runway, both main landing gear tires “grabbed” and the airplane veered to the left.
The right main landing gear contacted soft ground and collapsed. The airplane then spun 180° and came to rest upright about 30 ft beyond the end of the runway. After securing and exiting the airplane, the pilot noticed that the windsock was indicating a direct tailwind from 240° at 15 knots. The pilot added that the windsock was not visually discernible during the approach and he was relying on the AWOS report, which indicated calm wind.
After the accident, the pilot captured a screenshot on his mobile device, showing the AWOS information indicating a calm wind. He also took a photograph of the windsock and supplied the two to the NTSB. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
The pilot of another airplane, N96GD, was on an IFR flight from Frederick, Maryland, and landed about 20 minutes before the accident airplane. He also reported that the AWOS was reporting calm wind but noted after touchdown on runway 6 that he had a direct tailwind in excess of 8 knots.
During a telephone conversation, the airport manager at 26N stated that the AWOS was an “AV” AWOS, indicating that the altimeter setting and visibility information were certified, but that the wind information was advisory only. He added that he had not received any other reports of a discrepancy between actual wind information and that which the AWOS was broadcasting. He further stated that a weather front passed through the area about the time of the accident.
Atlantic City International Airport (ACY), Atlantic City, New Jersey, was located about 13 miles north of the accident site. The recorded wind at ACY, at 1554, was from 240° at 8 knots. The recorded wind at ACY, at 1654, was from 130° at 8 knots.
Cape May County Airport (WWD), Wildwood, New Jersey, was located about 23 miles southwest of the accident site. The recorded wind at WWD, at 1556, was from 150° at 7 knots. The recorded wind at WWD, at 1656, was from 120° at 5 knots.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record ERA26LA163
- Event ID
- 20260407202770
- Case number
- ERA26LA163
- 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, coordinates. 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: 465bd2ec62c76c647a35c6dbf9775eff2f0fca500e285615dfc13b2b79cda11d; retrieved 2026-09-16T21:10:47.015Z.