N180LR

Substantial
Serious

PIPER PA-28-180S/N: 28-872

Accident Details

Date
Friday, May 5, 2023
NTSB Number
ERA23LA218
Location
Greenville, NC
Event ID
20230505109776
Coordinates
35.630829, -77.398041
Aircraft Damage
Substantial
Highest Injury
Serious
Fatalities
0
Serious Injuries
2
Minor Injuries
0
Uninjured
0
Total Aboard
2

Probable Cause and Findings

Inadequate maintenance by the operator and maintenance personnel, which resulted in a loss of engine power due to oil starvation.

Aircraft Information

Registration
N180LR
Make
PIPER
Serial Number
28-872
Engine Type
Reciprocating
Year Built
1962
Model / ICAO
PA-28-180P28A
Aircraft Type
Fixed Wing Single Engine
No. of Engines
1

Registered Owner (Historical)

Name
REGISTRATION PENDING
Address
1060 PTI DR
Status
Deregistered
City
GREENSBORO
State / Zip Code
NC 27409-9469
Country
United States

Analysis

On May 5, 2023, at 0900 eastern daylight time, a Piper PA-28-180 airplane, N180LR, was substantially damaged when it was involved in an accident near Greenville, North Carolina. The private pilot and the passenger were seriously injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

The pilot reported that he had rented the airplane from a flight school located at the Piedmont Triad International Airport (GSO), Greensboro, North Carolina, and planned to fly to the Pitt-Greenville Airport (PGV), Greenville, North Carolina. He conducted a thorough preflight examination of the airplane and found nothing abnormal. Both wing fuel tanks were full, and the engine started and ran normally during all run-up checks. He and his passenger then departed about 0800. The pilot said when he was about 10 miles from PGV, at an altitude of about 4,000 ft mean sea level (msl), he noticed a gradual loss in engine rpm. He tried to add power with the throttle, but there was no response. The pilot also applied carburetor heat, but there was no discernable difference in engine rpm. The engine continued to rapidly lose rpm before it finally stopped producing all power. The pilot trimmed the airplane for best glide speed and landed about a ¼-mile short of PVG in a swamp. The pilot said he observed the oil pressure light flashing on the instrument panel a few seconds before touchdown.

Examination of the engine revealed a large amount of metallic debris in the oil filter and in the oil sump suction screen. When the oil sump was removed, there were numerous pieces of metallic debris sitting in the sump and there was a large hole in the bottom of the crankcase. When the engine was disassembled, the No. 3 connecting rod was found damaged where it connected to the crankshaft journal and its cap was heavily fractured. The No. 2 cylinder forward piston pin plug was missing, and the aft pin plug exhibited preimpact wear up into the oil control ring land. A review of the debris found inside the oil sump suction screen, revealed metal shavings consistent with the missing forward piston pin plug.

The Nos. 3 and 4 camshaft lobes exhibited wear and two of their corresponding lifters were pitted and concave, consistent with preimpact wear. The main journal bearings exhibited wear, scoring, and discoloration. The connecting rod journals and their respective bearings also exhibited scoring and discoloration.

The crankshaft, connecting rods and associated bearings, the main journal bearings, and the oil filter screen with metallic flakes were sent to the National Transportation Safety Board’s Materials Laboratory for further examination. Examination of these components revealed damage consistent with the engine operating at high operating temperatures due to a lack of lubrication and hard contact damage after the No. 3 connecting rod released during operation. No preexisting material failures were identified.

A review of engine maintenance records revealed the engine’s last annual inspection was completed on April 26, 2023. At the time of the accident, the engine had accrued a total of 2,118.5 hours since it was overhauled on September 7, 2002, almost 21 years before the accident.

According to Lycoming Service Instruction No. 1009BE, “TIME BETWEEN OVERHAUL (TBO) SCHEDULES,” the engine should have been overhauled when it had accumulated 2,000 hours in service or within 12 calendar years of the date it first entered service or of its last overhaul, “to mitigate engine deterioration that occurs with age, including corrosion of metallic components…”

On January 5, 2023, a maintenance entry was made in the engine logbook indicating there was a “intermittent variation in power of the engine” during a cross-country flight. A mechanic replaced the Nos. 1 and 2 exhaust gaskets, a missing exhaust nut, and added new washers to the Nos. 1 and 2 cylinder exhaust studs. The engine was test run, and it ran rough with a low exhaust gas temperature indication on the No. 2 cylinder. The No. 2 cylinder valve cover was removed, and a broken valve spring was replaced. The engine was test-run, and the airplane was returned to service. There were no entries indicating that the oil filter or oil sump suction screen were checked for metal debris.

Further examination of the engine maintenance logbook revealed the last time the oil filter was checked was on September 1, 2022, about 8 months before the accident. The airplane then had three 100-hr inspections and an annual inspection before the accident. Each inspection included an entry that said, “Changed oil and filter.” There was no entry that said the oil filter was opened and checked. Per Lycoming Mandatory Service Bulletin 480F, “Oil Servicing, Metallic Solids Identification After Oil Servicing, and Associated Corrective Action,” the oil filter and oil sump suction screen are to be checked after each oil change. The purpose of checking the oil filter is to check for metal debris that would indicate excessive wear in the engine and the potential for a future engine failure. The log entries also did not note a check of the oil sump suction screen at these oil changes.

Data Source

Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# ERA23LA218