# NTSB ERA20LA062: Piper PA32RT, N27GB, Fletcher, NC, December 28, 2019

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Class 3 · Limited · Final report
- Date: December 28, 2019, 17:35 local (22:35 UTC)
- Place: Fletcher, NC · Western North Carolina Agricultural Center
- Coordinates: 35.424999, -82.531944 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=35.4250&lon=-82.5319&mi=10
- Phase of flight: [Initial climb](https://openairdocs.org/ntsb-phases/350) (OpenAirDocs' grouping)
- Defining event: [Initial climb: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341)
- Highest injury: No injuries
- Injuries: 6 uninjured
- Status: Completed
- Report: Approved by Office Director
- Investigation class: Class 3
- NTSB office: Eastern Region Aviation
- Parties: Lycoming Aircraft Engines, FAA FSDO, Piper Aircraft
- NTSB case key (mKey): 100753
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA20LA062
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/100753/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=100753
- Page: https://openairdocs.org/ntsb/ERA20LA062

## Probable cause

A failure of two of the oil pump drive gear’s teeth, which resulted in a loss of engine oil lubrication, and a total loss of engine power.

## Findings

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

- [Engine (reciprocating): recip eng oil sys](https://openairdocs.org/ntsb-findings/01058550): Aircraft › Aircraft power plant · Failure (probable cause); cases with it: [Piper PA-32RT-300, 1 case](https://openairdocs.org/ntsb-findings/01058550/cases.md?model=7103215), [All aircraft, 130 cases](https://openairdocs.org/ntsb-findings/01058550/cases.md)

## Sequence of events

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

- [Initial climb: Loss of engine power (partial)](https://openairdocs.org/ntsb-events/342); cases with it: [Piper PA-32RT-300, 3 cases](https://openairdocs.org/ntsb-events/342/sequence.md?model=7103215), [All aircraft, 1,858 cases](https://openairdocs.org/ntsb-events/342/sequence.md)
- [Initial climb: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341) (defining event); cases with it: [Piper PA-32RT-300, 4 cases](https://openairdocs.org/ntsb-events/341/sequence.md?model=7103215), [All aircraft, 3,820 cases](https://openairdocs.org/ntsb-events/341/sequence.md)
- [Emergency descent: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Piper PA-32RT-300, 11 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7103215), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md)
- [Landing: Off-field or emergency landing](https://openairdocs.org/ntsb-events/440); cases with it: [Piper PA-32RT-300, 5 cases](https://openairdocs.org/ntsb-events/440/sequence.md?model=7103215), [All aircraft, 3,365 cases](https://openairdocs.org/ntsb-events/440/sequence.md)
- [Post-impact: Fire/smoke (post-impact)](https://openairdocs.org/ntsb-events/170); cases with it: [Piper PA-32RT-300, 2 cases](https://openairdocs.org/ntsb-events/170/sequence.md?model=7103215), [All aircraft, 354 cases](https://openairdocs.org/ntsb-events/170/sequence.md)

## Analysis

The pilot reported that shortly after taking off, the airplane experienced a loss of engine power so he subsequently performed a forced landing to a parking lot. During the approach to land, he thought the oil pressure gauge was in the “yellow,” and the engine felt like it was “rolling back.” During the impact sequence, the airplane struck a chain link fence, and an electrical distribution box before coming to rest. Much of the airplane was consumed by a postcrash fire. Examination of the engine revealed that the drivetrain could not be rotated during an attempted rotation by hand of the propeller. Removal of the six cylinders revealed discoloration consistent with lack of lubrication of the connecting rod journals; furthermore, the number four connecting rod was separated from the crankshaft. Removal of the accessories, accessory case, and oil sump revealed that two of the oil pump’s drive gear teeth were fractured. No visible damage was observed to the idler gear which drove the oil pump. Examination revealed the idler gear would not rotate the oil pump drive gear with two separated teeth. Examination of the oil pump drive gear indicated that the two teeth fractured in overstress under rotation. The direction of bending and shear in the teeth fracture was consistent with the direction of rotation of the gear. Given this information, it is likely that the lack of rotation of the oil pump due to the broken teeth resulted in a lack of lubrication to the engine and the subsequent total loss of engine power. The reason for the failure of the oil pump drive gear teeth could not be determined.

## Factual narrative

On December 28, 2019, about 1732 eastern standard time, a Piper PA-32RT-300 Airplane, N27GB, was destroyed when it was involved in an accident near Fletcher, North Carolina. The pilot and four passengers were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. According to the pilot, they had departed from Cobb County International Airport-McCollum Field (RYY), Atlanta, Georgia earlier in the day and flew to Asheville Regional Airport (AVL), Asheville, North Carolina. When he went to depart AVL for the return flight, he did a runup and everything was normal. During taxi he was following a Canadair Regional Jet (CRJ), and tower advised him of wake turbulence. During the takeoff he rotated a little early at 75 knots to avoid the wake turbulence from the CRJ. He was climbing at Vx (best angle of climb) when the airplane started to feel “sluggish.” He checked that the mixture, propeller, and throttle controls were all full forward and nosed the airplane forward. He felt there was a and initiated a turn back to the airport. The airplane felt like it was mushing though, so he elected to perform a forced landing to a parking lot. He glanced over and thought that the oil pressure gauge was in the “yellow,” and the engine felt like it was “rolling back.” He kept the landing gear in the up position and extended the wing flaps and aimed between light poles. The right wing hit something, and the airplane stopped. During the impact sequence the airplane struck a chain link fence and an electrical distribution box before coming to rest. Much of the cabin and aft fuselage was consumed by a post-crash fire. The engine had remained attached to its mount with no evidence of pre-impact fire or fire damage observed. During a postaccident examination, the drivetrain could not be rotated during an attempted rotation by hand of the propeller. Removal of the six cylinders revealed discoloration consistent with lack of lubrication of the connecting rod journals; furthermore, the number four connecting rod was separated from the crankshaft. All six cylinders oil spray nozzles remained attached to their respective attach points. Removal of the accessories, accessory case, and oil sump revealed that two of the oil pump’s drive gear teeth were fractured. They were later located in the oil sump. No visible damage was observed to the idler gear which drove the oil pump. Examination revealed the idler gear would not rotate the oil pump drive gear with two separated teeth. The oil pump, idler gear, and additional associated components were examined by the National Transportation Safety Board (NTSB) Materials Laboratory. Examination of the oil pump drive gear indicated that the two teeth fractured in overstress under rotation. The direction of bending and shear in the teeth fracture was consistent with the direction of rotation of the gear. The examination did not determine why the gear teeth fractured and separated from theoil pump drive gear. According to FAA and airplane maintenance records, the engine had accrued about 365 hours since major overhaul, which had occurred on November 5, 2013.

## Aircraft

- Registration: [N27GB](https://openairdocs.org/deregistered/N27GB-2022-09-03), registration cancelled 2022-09-03, S/N 32R-7885203 (OpenAirDocs)
- Reported make and model: Piper PA32RT (300)
- Registry model: [Piper PA-32RT-300](https://openairdocs.org/model/piper-pa-32rt-300) (registry code 7103215) (OpenAirDocs)
- Registry engine: [Lycoming TI0-540 series](https://openairdocs.org/engine/lycoming-ti0-540-series) (registry code 41533, turbo-prop) (OpenAirDocs)
- Category: Airplane
- Serial number: 32R-7885203
- Year built: 1978
- Airframe hours: 4081.6
- Engines: Lycoming IO-540-K1GD5 300 horsepower reciprocating
- Damage: Destroyed
- Fire: On-Ground
- Flight: Personal, Part 91
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, May 6, 2019, 24 hours before
- Departed: AVL, Asheville, NC
- Destination: RYY, Atlanta, GA
- Flight plan: IFR
- Airport: AVL, Asheville Regional Airport, runway 17, 7,001 × 100 ft, asphalt
- Equipment: Stall warning system, ADS-B, Auto-pilot, Electronic flight bag or handheld device

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 41; injuries: none; private; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 3, without waivers/limitations; last flight review June 28, 2019; seat: left; restraint: 3-point; flight hours: 327 total, 224 in this make and model, 295 as pilot in command, 4 in the last 90 days, 2 in the last 30 days, 2 in the last 24 hours

## Weather

- Conditions: Visual (VMC), Dusk
- Wind: 150° at 5 knots
- Visibility: 9 statute miles
- Lowest ceiling: 10,000 ft overcast
- Temperature: 61 °F, dew point 48 °F
- Altimeter: 30.20 inHg
- Observed at: AVL, 1 nm away

## 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 20191228021909A](https://openairdocs.org/incident/20191228021909A), Dec 28, 2019: Piper PA-32RT-300, Fletcher, NC, Destroyed. The pilot and his family(wife and 3 children) had flown from kryy to kavl for a day trip. Trip from kryy to kavl was uneventful. Pilot conducted a preflight…

## Docket (12 files)

The files NTSB released with the investigation on March 22, 2022, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=100753. 53.1 MB in all.

- Pilot/operator aircraft accident report, NTSB form 6120.1 (item 1, PDF, 13 pages, 4.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13156924&FileExtension=pdf&FileName=NTSB%20Form%206120%20(Signed)_Redacted-Rel.pdf
- Witness statements and interview summaries (item 2, PDF, 9 pages, 3.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13155879&FileExtension=pdf&FileName=Witness%20Statements%20and%20Interview%20Summaries_Redacted-Rel.pdf
- Kavl - ATC audio recording (2200Z) (item 3, MP3, 3.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13156696&FileExtension=mp3&FileName=KAVL-Gnd-Twr-App-Dec-28-2019-2200Z-Rel.mp3
- Kavl - ATC audio recording (2230Z) (item 4, MP3, 3.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13156663&FileExtension=mp3&FileName=KAVL-Gnd-Twr-App-Dec-28-2019-2230Z-Rel.mp3
- Kavl - airport diagram (item 5, PDF, 1 page, 118 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13155624&FileExtension=pdf&FileName=Airport%20Diagram-Rel.pdf
- Satellite image of accident area (item 6, PDF, 1 page, 339 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13156541&FileExtension=pdf&FileName=Satellite%20View%20of%20Accident%20Area-Rel.pdf
- Photo array (item 7, PDF, 20 pages, 9.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13158019&FileExtension=pdf&FileName=Photo%20Array-Rel.pdf
- Memorandum for record - wreckage examination (item 8, PDF, 3 pages, 133 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13156934&FileExtension=pdf&FileName=Memorandum%20For%20Record%20-%20Wreckage%20Examination-Rel.pdf
- Materials laboratory factual report (item 9, PDF, 28 pages, 37 photos, 15.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=11820774&FileExtension=pdf&FileName=20-047%20-%20Materials%20Lab%20Factual%20Report%20(ERA20LA062)-Rel.pdf
- Materials laboratory errata report (item 10, PDF, 1 page, 94 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=11907553&FileExtension=pdf&FileName=20-047B%20-%20Materials%20Lab%20Errata%20Report%20(ERA20LA062)-Rel.pdf
- Statement of party representatives to NTSB investigation (item 11, PDF, 2 pages, 1.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13155889&FileExtension=pdf&FileName=Party%20Forms_Redacted-Rel.pdf
- Wreckage release and evidence control (item 12, PDF, 7 pages, 11.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13156823&FileExtension=pdf&FileName=Wreckage%20Release%20and%20Evidence%20Control_Redacted-Rel.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.