FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA23LA218 · Piper PA-28-180

5 May 2023 · Greenville, NC, United States

Piper PA-28-180 · Accident: loss of engine power (total) on approach

From Piedmont Triad International Airport (GSO) to Pitt-Greenville Airport (PGV)

Report a problem

Event

NTSB case
ERA23LA218
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
Event fatalities
Unknown
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Piper PA-28-180

Aircraft type
Piper PA-28
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N180LR
Operator
Unknown
Onboard fatalities
Unknown
Route
From Piedmont Triad International Airport (GSO), Greensboro, NCTo Pitt-Greenville Airport (PGV), Greenville, NC
Aircraft age
About 61 years (built 1962)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach · VFR pattern final
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of engine power (total)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft handling/service
  • Aircraft › Aircraft power plant
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot made a forced landing in a swamp after the engine lost complete power. The landing resulted in substantial damage to the airplane and serious injuries to both occupants. Postaccident examination of the engine found large amounts of metallic flakes and debris in the oil filter and oil sump screen. When the engine was disassembled, wear was noted on the camshaft lobes and associated lifters, and the No. 2 aft piston pin plug. The No. 2 forward piston plug was missing and metal shavings consistent with the plug were found in the oil suction sump screen. Metallurgical examination of engine 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. Therefore, the wear noted in the engine most likely became excessive, and over time produced metal shavings and debris that collected in the oil screen, which led to oil starvation. The bearings and connecting rods overheated, which resulted in the release of the No. 3 connecting rod from its crankshaft journal during engine operation. A review of the engine maintenance records revealed the oil had been changed and the filter replaced but had not been checked for about 8 months before the accident. Per a Mandatory Service Bulletin released by the engine manufacturer, titled “Oil Servicing, Metallic Solids Identification After Oil Servicing, and Associated Corrective Action,” the oil filter and oil sump suction screen were to be checked after each oil change. This check was to see if the engine was being contaminated with metallic particles due to excessive wear and to help prevent a future engine failure. In addition, the engine manufacturer recommended the engine be overhauled every 12 years or 2,000 hours to “mitigate engine deterioration that occurs with age, including corrosion of metallic components…” Engine maintenance records indicated the engine was last overhauled about 21 years before the accident, and had accrued 2,118.5 hours of operation at the time of the accident. As such, the engine was 9 years past its recommended overhaul interval and 118 hours over the recommended time in service. Had the airplane operator overhauled the engine as recommended by the engine manufacturer, and if maintenance personnel checked the oil filter/and oil sump suction screen in the months leading up to the accident, it is likely they would have observed metallic debris being produced by the engine due to excessive wear. Both actions would likely have prevented the engine failure due to oil starvation.

Probable cause

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

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA23LA218
Event ID
20230505109776
Case number
ERA23LA218
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (5)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, cause areas. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: ed31d94b3b9fdf4b36602e5c51e3b79bb0574e083e970bc3b9ba174cc2120ca9; retrieved 2026-09-16T17:34:32.328Z.
  • Corrected after a review of the NTSB narrative, which states these values explicitly: departure. Typo in city name; airport code GSO is Piedmont Triad International Airport, Greensboro, NC.