FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA10LA092 · Piper PA-32R 301

6 Dec 2009 · Hatteras, NC, United States

Piper PA-32R 301 · Accident: runway excursion during takeoff

From Billy Mitchell Airport (HSE) to Norfolk International Airport (ORF)

Report a problem

Event

NTSB case
ERA10LA092
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
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-32R 301

Aircraft type
Piper PA-32
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
N5319J
Operator
Unknown
Onboard fatalities
Unknown
Route
From Billy Mitchell Airport (HSE), Hatteras, NCTo Norfolk International Airport (ORF), Norfolk, VA
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 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 · rejected 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
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

  • Personnel issues › Task performance

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

NTSB narrative

The pilot reported that just prior to becoming airborne, a cockpit aural alarm sounded and the manifold pressure was approximately one inch above its maximum limit. He elected to abort the takeoff and applied the brakes. The airplane veered to the left and he concluded that the right brake was not functioning correctly. In response, he attempted to correct the drift using right rudder application. The airplane exited the left side of the runway and collided with sand dunes and vegetation. The reported failure of the right brake was not able to be confirmed and no cause for such a failure was observed.

Probable cause

The pilot's inability to maintain directional control during an aborted takeoff for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA10LA092
Event ID
20091209X11549
Case number
ERA10LA092
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. 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: ddef089d5954be5bd1297d743bdbcb938463eb5cb2f6385c43b73beb5e9f0908; retrieved 2026-09-15T13:33:38.335Z.