ERA20LA212 · Piper PA32RT 300T
Piper PA32RT 300T · Accident: loss of engine power (total) en route
From Walker County Airport Bevill Field (JFX) to Craig Field (SEM)
Event
- NTSB case
- ERA20LA212
- 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
- API-reported fatalities
- 2 · all aircraft and ground
- Ground fatalities
- 0
- 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 PA32RT 300T
- Aircraft type
- Piper PA32
- 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
- N543GS
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Walker County Airport Bevill Field (JFX), Jasper, ALTo Craig Field (SEM), Selma, AL
- Aircraft age
- About 42 years (built 1978)
- 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
- En route · cruise
- 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
- Destroyed
Cause areas
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
After departure, the pilot leveled the airplane at a cruise altitude of 15,000 ft mean sea level (msl). About 40 minutes into the flight, the pilot reported an engine "fluctuation" to the controller and requested to divert to a nearby airport. The controller cleared the airplane for the diversion, and the pilot indicated that the propeller was turning; however, the airplane had experienced a total loss of engine power and then an in-flight fire. When the airplane was about 3 miles from the diversion airport and about 3,100 ft msl, radar and voice communications were lost. The airplane impacted a field, and all components of the airplane were within the vicinity of the main wreckage. Examination of the engine revealed a hole in the top of the crankcase, thermal discoloration on the aft section of the crankshaft, and detachment of the No. 6 connecting rod from the crankshaft journal. The No. 6 rod journal exhibited severe thermal discoloration. Examination of the connecting rod journal bearings revealed extensive damage to all the submitted bearings. Circumferential score marks and heavy wear were visible on the inner diameter of the bearing halves. The camshaft was fractured in torsional overstress. The oil sump was removed from the engine and contained oil, metallic particles, small carbon chips, and organic debris. The oil filter was removed, disassembled, and a small amount of carbon chips and metallic debris was noted on the filter. The oil pump was removed from the accessory section of the engine and the pump body exhibited scoring. In addition, the oil suction screen was completely occluded by debris that filled the screen over 60% and likely starved the engine of oil. Examination of the debris in the oil suction screen revealed that approximately 75% of the debris was metallic and the remaining 25% of the debris was not metallic. Given the significant amount of nonmetallic debris, it likely accumulated over time and resulted in the engine being starved of oil. When the engine subsequently lost total power, the crankcase was penetrated, which is likely the origin of the in-flight fire. There was no record that the oil suction screen was cleaned during the airplane’s most recent oil change about 3 months before the accident. The last documented cleaning of the oil suction screen was about 11 years before the accident and the engine had accumulated an additional 550 hours until the time of the accident. The engine's operating manual stated that "at each fifty hours inspection,” the oil suction and oil pressure screens should be removed and inspected for metal particles, cleaned and reinstalled. It also noted that, “on installations employing external oil filters,” inspection of the oil suction screen “should be observed at the 100-hour inspection.” Furthermore, the airframe service manual stated that the oil suction screen should be cleaned at every 50-hour interval. When asked if the oil suction screen was cleaned during the oil change associated with the most recent annual inspection, the mechanic who performed the work stated that the oil cooler was cleaned, which likely indicates that the oil suction screen was not cleaned. A discrepancy for low oil pressure that was recorded in the engine maintenance log the day before the accident was likely due to the obstructed oil suction screen. Subsequently, the obstructed oil suction screen led to the engine being starved of oil and a total loss of engine power.
Probable cause
The mechanic’s failure to clean the oil suction screen during the most recent maintenance, which resulted in oil starvation and subsequent total loss of engine power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA20LA212
- Event ID
- 20200610X83452
- Case number
- ERA20LA212
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- 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. 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: 51d283bdb0ff7069badafb9a0c27e7578d1ed6df42e10fda664e7ceccdedd934; retrieved 2026-09-15T07:16:08.874Z.