FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA15LA266 · Grumman American AVN. CORP. AA 5 UNDESIGNAT

13 Jul 2015 · Southbridge, MA, United States

Grumman American AVN. CORP. AA 5 UNDESIGNAT · Accident during takeoff

From Southbridge Municipal Airport (3B0) to Southbridge Municipal Airport (3B0)

Report a problem

Event

NTSB case
ERA15LA266
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

Grumman American AVN. CORP. AA 5 UNDESIGNAT

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
N1356R
Operator
Unknown
Onboard fatalities
Unknown
Route
From Southbridge Municipal Airport (3B0), Southbridge, MATo Southbridge Municipal Airport (3B0), Southbridge, MA
Aircraft age
About 40 years (built 1975)
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
Takeoff
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
Miscellaneous/other
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

  • Environmental issues › Physical environment
  • Personnel issues › Action/decision

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airline transport pilot reported that, during takeoff from a 3,501-ft-long asphalt runway, a gust of wind yawed the airplane left at rotation and it became airborne. The pilot corrected for the yaw and was able to maintain runway heading; however, he chose to reject the takeoff rather than trying to continue. The airplane touched down and the pilot applied heavy braking, but was unable to stop the airplane before it continued off the runway and impacted trees and brush at the perimeter of the airport. Examination of the wreckage did not reveal any preimpact mechanical malfunctions. The reported wind at a nearby airport about the time of the accident was variable at 4 knots.

Probable cause

The pilot’s decision to abort the takeoff with insufficient runway remaining, which resulted in a runway excursion.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA15LA266
Event ID
20150714X13011
Case number
ERA15LA266
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: 16ff488fa1e14a2f2e4cedb0cfc25af9cfaa37da857dbafb8d7392aa99c0770a; retrieved 2026-09-16T02:31:41.318Z.