FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Aeronational Piper PA-31-325 accident

9 Sept 2012 · Washington, PA, United States

Piper PA-31-325 · Accident: abrupt maneuver during initial climb

From Washington County Airport (AFJ) to Bangor International Airport (BGR)

Report a problem

Event

NTSB case
ERA12LA557
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
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
Charter & commuter
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-31-325

Aircraft type
Piper PA-31
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
N3591P
Operator
Aeronational
Onboard fatalities
Unknown
Route
From Washington County Airport (AFJ), Washington, PATo Bangor International Airport (BGR), Bangor, ME
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 135: Air Taxi & Commuter
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
Initial climb
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
Abrupt maneuver
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

Shortly after the airplane lifted off the runway, the pilots observed a flock of geese approaching from the right. The pilot-in-command believed that the birds would impact the cockpit windows, so he pushed forward on the control yoke to descend and avoid such a collision. The airplane struck the runway hard and bounced back into the air. The pilots continued the takeoff and returned to the airport for an uneventful landing. Postaccident examination revealed structural damage to the airframe. Also, bird remains were found on the fuselage.

Probable cause

The airplane’s encounter with a flock of geese during takeoff, which resulted in the airplane’s hard impact with the runway while the pilot maneuvered in an attempt to avoid the geese.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA12LA557
Event ID
20120911X01505
Case number
ERA12LA557
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: f3eb210e300ca4e9252237d17648aa3e5a032caeaf8726f71438798cd3b4d068; retrieved 2026-09-15T19:49:30.735Z.