# NTSB ERA10CA230: Piper PA-32R-301T, N541VB, Augusta, GA, April 5, 2010

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: April 5, 2010, 17:09 local (21:09 UTC)
- Place: Augusta, GA
- Coordinates: 33.466388, -82.039169 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=33.4664&lon=-82.0392&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining event: [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300)
- Highest injury: No injuries
- Injuries: 2 uninjured
- Status: Completed, report April 12, 2011
- Report: Approved by Office Director
- NTSB office: Eastern Region Aviation
- Parties: FAA/FSDO
- NTSB case key (mKey): 75763
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA10CA230
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/75763/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=75763
- Page: https://openairdocs.org/ntsb/ERA10CA230

## Probable cause

The pilot’s inadequate braking after touchdown, which resulted in a runway excursion.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Performance/control parameters: surface speed/braking](https://openairdocs.org/ntsb-findings/01062045): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Piper PA-32R-301T, 1 case](https://openairdocs.org/ntsb-findings/01062045/cases.md?model=7103220), [All aircraft, 238 cases](https://openairdocs.org/ntsb-findings/01062045/cases.md)
- [Action: delayed action](https://openairdocs.org/ntsb-findings/02041025): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Piper PA-32R-301T, 1 case](https://openairdocs.org/ntsb-findings/02041025/cases.md?model=7103220), [All aircraft, 894 cases](https://openairdocs.org/ntsb-findings/02041025/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300) (defining event); cases with it: [Piper PA-32R-301T, 6 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=7103220), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md)
- [Landing-landing roll: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Piper PA-32R-301T, 19 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7103220), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md)

## Analysis

The pilot stated that after touchdown he did not apply maximum braking and attempted to let the airplane slow down on its own. As the airplane approached the end of the runway, the pilot realized that the airplane would not stop in time and aggressively applied the brakes, sending the airplane into a skid off the end of the runway. The right wing and propeller collided with a fence, resulting in substantial damage to both. The pilot reported no preimpact mechanical malfunctions with the airplane.

## Factual narrative

The pilot stated that he was performing a landing on runway 29. After touchdown, the pilot did not apply maximum braking and attempted "to let the plane slow down on by itself." As the airplane approached the end of the runway, the pilot realized that the airplane would not stop in time and aggressively applied the brakes, sending the airplane into a skid off the end of the runway. The right wing and propeller hit a fence, incurring substantial damage to both. The pilot did not report any mechanical malfunctions with the airplane prior to the accident.

## Aircraft

- Registration: [N541VB](https://openairdocs.org/aircraft/N541VB), registered now, S/N 3257334, built 2003 (OpenAirDocs)
- Reported make and model: PIPER PA-32R-301T
- Registry model: [Piper PA-32R-301T](https://openairdocs.org/model/piper-pa-32r-301t) (registry code 7103220) (OpenAirDocs)
- Registry engine: [Lycoming TIO-540 series](https://openairdocs.org/engine/lycoming-tio-540-series) (registry code 41569, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 3257334
- Airframe hours: 1203
- Engines: LYCOMING TIO 540 SER 300 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, May 13, 2009
- Departed: FTY, Atlanta, GA
- Destination: DNL, Augusta, GA
- Flight plan: IFR
- Airport: DNL, Daniel Field, runway 29, 3,738 × 100 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 38; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, without waivers/limitations; last flight review March 31, 2010; seat: left; flight hours: 360 total, 200 in this make and model, 280 as pilot in command, 50 in the last 90 days, 20 in the last 30 days, 3 in the last 24 hours

## Weather

- Conditions: Visual (VMC), Day
- Wind: 220° at 4 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 90 °F, dew point 52 °F
- Altimeter: 30.12 inHg
- Observed at: DNL

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20100405035539A](https://openairdocs.org/incident/20100405035539A), Apr 5, 2010: Piper PA-32R-301T, Augusta, GA, Substantial damage. Aircraft landed midway on runway 29. While approaching the end of the runway, pilot applied brakes aggressively inducing a skid to the right, and off the…

## Docket (1 files)

The files NTSB released with the investigation on November 17, 2010, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=75763. 723 KB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 723 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40330273&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.