# NTSB ERA13LA337: Piper PA-28-181, N371JB, Columbus, GA, July 27, 2013

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Limited investigation · Final report
- Date: July 27, 2013, 10:22 local (14:22 UTC)
- Place: Columbus, GA
- Coordinates: 32.52, -84.949996 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=32.5200&lon=-84.9500&mi=10
- Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping)
- Defining event: [Takeoff-rejected takeoff: Runway excursion](https://openairdocs.org/ntsb-events/300)
- Highest injury: No injuries
- Injuries: 2 uninjured
- Status: Completed, report June 22, 2015
- Report: Approved by Office Director
- NTSB office: Eastern Region Aviation
- Parties: FAA/FSDO
- NTSB case key (mKey): 87596
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA13LA337
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/87596/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=87596
- Page: https://openairdocs.org/ntsb/ERA13LA337

## Probable cause

The pilot's delayed decision to abort the takeoff. Contributing to the accident was the airplane's perceived lack of performance for reasons that could not be determined due to insufficient information.

## Findings

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

- [Action: delayed action](https://openairdocs.org/ntsb-findings/02041025): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Piper PA-28-181, 11 cases](https://openairdocs.org/ntsb-findings/02041025/cases.md?model=7102807), [All aircraft, 894 cases](https://openairdocs.org/ntsb-findings/02041025/cases.md)
- [Performance/control parameters](https://openairdocs.org/ntsb-findings/01062000): Aircraft › Aircraft oper/perf/capability · Not specified (probable cause); cases with it: [Piper PA-28-181, 4 cases](https://openairdocs.org/ntsb-findings/01062000/cases.md?model=7102807), [All aircraft, 1,269 cases](https://openairdocs.org/ntsb-findings/01062000/cases.md)

## Sequence of events

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

- [Takeoff: Miscellaneous/other](https://openairdocs.org/ntsb-events/900); cases with it: [Piper PA-28-181, 6 cases](https://openairdocs.org/ntsb-events/900/sequence.md?model=7102807), [All aircraft, 1,556 cases](https://openairdocs.org/ntsb-events/900/sequence.md)
- [Takeoff-rejected takeoff: Runway excursion](https://openairdocs.org/ntsb-events/300) (defining event); cases with it: [Piper PA-28-181, 35 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=7102807), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md)

## Analysis

Another pilot reported that she had aborted a takeoff on a previous flight in the accident airplane when she felt that the engine was not developing sufficient power. The accident pilot subsequently arrived at the airport, they "checked everything again," and he attempted to take off. However, both pilots again "felt the same thing," and the accident pilot aborted that takeoff attempt. The accident pilot subsequently attempted to take off again, but, after feeling that the engine was not developing enough power, he decided to land straight ahead. During the landing, the airplane bounced once and overran the runway end; it then pivoted 180 degrees before coming to a stop. The accident pilot also indicated that he and the other pilot originally thought that there was an airspeed indication problem. The accident pilot looked at the pitot head after his first aborted takeoff and noticed debris, which he removed. He then performed a high-speed taxi test to ensure that the airspeed indicator was functioning properly before the final takeoff attempt. The airplane was sold for parts before it could be further examined for possible performance-related anomalies.

## Factual narrative

On July 27, 2013, at 1022 eastern daylight time, a Piper PA-28-181, N371JB, was substantially damaged during a runway overrun at Columbus Airport (CSG), Columbus, Georgia. The private pilot and pilot-rated passenger were not injured. Visual meteorological conditions prevailed, and no flight plan had been filed for the local personal flight, which was conducted under the provisions of 14 Code of Federal Regulations Part 91.According to a written statement by the pilot-rated passenger, she had earlier attempted a takeoff from runway 31. However, she felt that the engine was not developing enough power and aborted the takeoff. The accident pilot subsequently arrived at the airport, they "checked everything again," and he decided to "go one more time." However, they "felt the same thing" and he aborted the takeoff. The accident pilot subsequently took off on a third attempt, and after feeling once again that the engine was not developing enough power, decided to land straight ahead. In a written statement by the accident pilot, he confirmed the first pilot's recollection of the events, but added that during the third attempt, the airplane took off about 70 knots and climbed to about 60 feet above the ground when he felt there wasn't enough power to continue the flight. He then decided to abort the takeoff and landed the airplane in the grass just past the end of the runway. A witness stated that he saw the airplane bounce once on the runway before overrunning the end, then "pivot" 180 degrees before coming to a stop, which resulted in the nose landing gear collapse and damage to the right wing. The witness also noted that earlier, the pilot of the first attempt had stated to him that the airspeed indicator was "not performing." Wind, recorded about the time of the accident, was calm. The responding Federal Aviation Administration (FAA) inspector stated that the accident pilot subsequently confirmed that he and the other pilot originally thought there was an airspeed indication problem. The accident pilot looked at the pitot head after the first aborted takeoff and noticed debris, which he removed. He then performed a high speed taxi test to ensure that the airspeed indicator was functioning properly before attempting another takeoff. The pilot was originally going to have the airplane repaired, but instead sold it to an aircraft parts company; further investigation into possible performance-related anomalies was not pursued.

## Aircraft

- Registration: [N371JB](https://openairdocs.org/deregistered/N371JB-2020-09-04), registration cancelled 2020-09-04, S/N 28-8490106, built 1984 (OpenAirDocs)
- Reported make and model: PIPER PA-28-181
- Registry model: [Piper PA-28-181](https://openairdocs.org/model/piper-pa-28-181) (registry code 7102807) (OpenAirDocs)
- Registry engine: [Lycoming O&VO-360 series](https://openairdocs.org/engine/lycoming-o-vo-360-series) (registry code 41514, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 28-8490106
- Airframe hours: 6900
- Engines: LYCOMING O&VO-360 SER 180 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Airworthiness certificate: Standard, Normal
- Departed: CSG, Columbus, GA
- Destination: CSG, Columbus, GA
- Airport: CSG, Columbus Airport, runway 31, 3,997 × 150 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 47; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; last flight review March 13, 2012; seat: left; flight hours: 255 total, 215 in this make and model, 8 in the last 90 days, 8 in the last 30 days

## Weather

- Conditions: Visual (VMC), Day
- Wind: calm
- Visibility: 6 statute miles
- Lowest ceiling: none
- Temperature: 81 °F, dew point 70 °F
- Altimeter: 29.98 inHg
- Observed at: CSG

## 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 20130727016739A](https://openairdocs.org/incident/20130727016739A), Jul 27, 2013: Piper PA-28-181, Columbus, GA, Substantial damage. Aircraft lost power during takeoff from runway 31. Pilot aborted the takeoff at approximately 60 feet altitude forcing aircraft back down to runway. Aircraft…

## Docket (5 files)

The files NTSB released with the investigation on May 21, 2015, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=87596. 2.2 MB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 1.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40426693&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF
- Pilots’ Statements (item 2, .PDF, 540 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40426694&FileExtension=.PDF&FileName=Pilots%E2%80%99%20%20Statements-Redacted.PDF
- Witness Statement (item 3, .PDF, 236 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40426695&FileExtension=.PDF&FileName=Witness%20Statement%20-Redacted.PDF
- FAA Inspector Emails (item 4, .PDF, 180 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40426696&FileExtension=.PDF&FileName=FAA%20Inspector%20Emails-Master.PDF
- Memorandum of Record (item 5, .PDF, 51 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40426697&FileExtension=.PDF&FileName=Memorandum%20of%20Record-Master.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.
