ERA21LA019

NTSB accident investigation · Piper PA32 · Atlanta, GA · October 11, 2020

Accident · No injuriesClass 3 · LimitedFinal report
Date
October 11, 2020, 08:10 local (12:10 UTC)
Place
Atlanta, GA
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Initial climb
Aircraft
N3595WPiper PA32
Defining event
Initial climb: Loss of engine power (partial)
Weather
Visual (VMC) · Day
Status
Completed
Report
Approved by Office Director
Investigation class
Class 3
NTSB office
Eastern Region Aviation
Parties
FAA FSDO
FAA report
20201011018349A
Case key
102138

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

A partial loss of engine power during takeoff due to a right magneto anomaly, which resulted in the pilot’s decision to abort the takeoff and the subsequent runway excursion.

Findings · 1

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.

Ignition system: magneto/distributorAircraft › Aircraft power plant · MalfunctionPiper PA-32-260: 1 caseAll aircraft: 101 casesProbable cause

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

The commercial pilot reported that, after takeoff, the engine lost partial power. With limited runway remaining, the pilot decided to make a forced landing during which the airplane departed the runway and traveled about 200 ft into the grass. During the runway excursion the airplane sustained substantial damage to the empennage. A postaccident engine test run revealed that the right magneto exhibited a drop off of 245 rpm, which exceeded the airplane manufacturer’s ground check guidance. Furthermore, the timing of the right magneto could not be determined because the contact points would not open far enough. The left magneto operated normally and had proper timing. It is likely that the anomaly observed with the right magneto resulted in a partial loss of engine power, the pilot’s decision to abort the takeoff, and the subsequent runway excursion.

Factual narrative

On October 11, 2020, about 0810 eastern daylight time, a Piper PA-32-260, N3595W, was substantially damaged when it was involved in an accident at Dekalb-Peachtree Airport (PDK), Atlanta, Georgia. The pilot and two passengers were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. According to the pilot, he landed at PDK on the day before the accident and requested that the airplane fuel tanks be topped off. On the day of the accident, the pilot performed a preflight inspection with no anomalies noted. He taxied the airplane to runway 21R, advanced the throttle to full power for takeoff, and noted that “the RPMs were producing full power, temps [temperatures] and pressures where in range and that airspeed was alive and increasing as normal.” The pilot stated that, after takeoff, the airplane continued to accelerate normally until it was about 150 to 200 ft above ground level. At that time, the pilot noted an “abrupt reduction in engine noise.” The pilot decided to make a forced landing, and the airplane touched down on the runway. The airplane then departed the end of the runway and traveled about 200 ft into the grass. The airplane sustained substantial damage to the empennage. A postaccident engine run was performed. When the magnetos were checked, the right magneto drop off was 245 rpm. The oil filter was examined, and small ferrous and nonferrous particles were noted. A cylinder compression check was performed, and low compression was noted in cylinders Nos. 2 and 4. The magneto timing was checked, and the left magneto was timed to 25° from top dead center. The right magneto contact points would not open far enough to check the timing. The engine controls were examined, and no anomalies were noted. Furthermore, the mechanic performing the engine rebuilding work after the accident noted that four cylinders “showed signs of extreme heat.” The cylinder bores had grooves, and the interior marks “appeared fresh” with “no signs of smoothing” from operation. In addition, multiple “substantial” intake system leaks were noted. According to the Sky Ranch Engineering Manual, high cylinder temperature could be a result of an improperly timed engine. According to the Piper PA-32-260 owner’s handbook, during a ground check, a “drop off on either magneto should not exceed 125 RPM.”

Aircraft

Registration
N3595W
Reported as
Piper PA32 (260)
Category
Airplane
Serial number
32-491
Built
1966
Airframe hours
6,011
Engine
Lycoming O-540-E4B5, 260 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Airworthiness certificate
Standard, Normal
Last inspection
Annual · October 2, 2020
Destination
HEF · Manassas, VA
Flight plan
IFR
Airport
PDK · Dekalb-Peachtree Airport, runway 21R, 3,746 × 150 ft, asphalt
Equipment
Electronic flight bag or handheld device, Auto-pilot, ADS-B, Onboard weather, Electronic primary flight display

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
45
Injuries
None
Certificates
Private, Commercial
Airplane ratings
Multi-engine land, Single-engine land
Instrument ratings
Helicopter, Airplane
Medical
BasicMed, Without waivers/limitations
Last flight review
November 23, 2019
Seat
Left
Restraint
Lap only
Flight hours
2,175 total · 670 in this make and model · 1,363 as pilot in command · 64 in the last 90 days · 19 in the last 30 days · 5 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
150° at 6 knots
Visibility
10 statute miles
Lowest ceiling
1,000 ft broken
Temperature
70 °F, dew point 68 °F
Altimeter
29.80 inHg
Observed at
KPDK
METAR
KPDK 111153Z 15006KT 10SM OVC012 21/20 A2980 RMK AO2 SLP078 60001 70340 T02060200 10222 20206 53003

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.

Other investigations on N3595W · 1

Matched to the same aircraft by N-number and date.