- Date
- July 27, 2013, 10:22 local (14:22 UTC)
- Place
- Columbus, GA
- Injuries
- 2 uninjured
- Damage
- Substantial damage
- Phase of flight
- Takeoff
- Aircraft
- N371JBPiper PA-28-181
- Defining event
- Takeoff-rejected takeoff: Runway excursion
- Weather
- Visual (VMC) · Day
- Status
- Completed · report June 22, 2015
- Report
- Approved by Office Director
- NTSB office
- Eastern Region Aviation
- Parties
- FAA/FSDO
- FAA report
- 20130727016739A
- Case key
- 87596
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
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 · 2
NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.
Sequence of events
The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.
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
- Reported as
- Piper PA-28-181
- Category
- Airplane
- Serial number
- 28-8490106
- Airframe hours
- 6,900
- Engine
- 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
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Age
- 47
- Injuries
- None
- Certificate
- 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
Docket · 5
The files NTSB released with the investigation on May 21, 2015, on NTSB’s docket system: statements, records, photos and specialists’ reports. 2.2 MB in all.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.