FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA25LA095 · Piper PA-28-161

10 Jan 2025 · Newburyport, MA, United States Narrative disagrees

Piper PA-28-161 · Accident: collision with terrain/object (non-CFIT) during landing

From Beverly Regional Airport (BVY) to an unrecorded destination

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
ERA25LA095
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-161

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
N9184Y
Operator
Unknown
Onboard fatalities
Unknown
Route
From Beverly Regional Airport (BVY), Beverly, MATo not recorded
Aircraft age
About 40 years (built 1985)
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
Collision with terrain/object (non-CFIT)
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

  • Personnel issues › Action/decision

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

NTSB narrative

The flight instructor reported that the flight began normally, with the student pilot departing the airport for maneuvering practice. During the flight, the instructor initiated a simulated loss of engine power, and the student pilot selected a runway for an emergency landing based on wind conditions and location. As they approached the runway, they determined they were too high to land directly and initiated a 270-degree turn to intercept the final approach. During the approach, the student extended the flaps earlier than anticipated, which resulted in greater than expected deceleration. They then observed that an obstacle, a trailer located near the end of the runway, was higher than anticipated. As the airplane neared the obstacle, the flight instructor assumed control of the airplane and applied full power to execute a go-around; however, the airplane struck the top of the trailer, pitched downward, and subsequently impacted a fence before coming to rest. Both of the airplane’s wings were substantially damaged during the accident sequence. The flight instructor and student pilot reported that there were no preimpact mechanical failures or malfunctions of the airplane that would have precluded normal operation.

Probable cause

The flight instructor’s delayed decision to initiate a go-around, which resulted in the airplane colliding with an obstacle during approach.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA25LA095
Event ID
20250114199537
Case number
ERA25LA095
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: 7560df1f4dfb2846bff6f223c9bafc7c494f12f289896ce1a7292f3f1c621c56; retrieved 2026-09-16T19:35:44.553Z.