WPR24LA076 · Piper PA-28-181
Piper PA-28-181 · Accident: powerplant system/component malfunction/failure en route
From Colorado City Municipal Airport (AZC) to Kanab Municipal Airport (KNB)
Event
- NTSB case
- WPR24LA076
- 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-181
- 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
- N2886X
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Colorado City Municipal Airport (AZC), Colorado City, AZTo Kanab Municipal Airport (KNB), Kanab, UT
- Aircraft age
- About 45 years (built 1979)
- 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
- Powerplant system/component malfunction/failure
- 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 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 reported that, while the airplane ascended through about 8,000 ft to 8,200 ft mean sea level (msl), the engine started vibrating and producing a loud “clunking” noise. He assumed that the engine had been subjected to carburetor icing and applied carburetor heat, but the condition worsened. He performed an emergency engine shutdown, configured the airplane to maintain the best glide airspeed, and selected the nearest suitable landing area. During the landing roll, the nose landing gear sheared off, and the left wing struck the ground resulting in damage to the aileron. Postaccident examination of the engine revealed heat tinting and scoring damage on three of four connecting rod journals, which is consistent with insufficient lubrication. Pitting was observed on the tappet body faces and corrosion observed on two of the tappet body faces had corresponding wear on the camshaft lobes. Additionally, material deformation was observed on the No. 2 cylinder piston skirt. The No. 2 piston pin bushing was worn into a small aluminum ball within the bore where it was normally situated. The wear signatures appeared consistent with long-term abnormal wear. The piston pin bore was elongated to the point of material deformation observed to the oil control ring, the second compression ring, and their respective lands. The oil suction screen contained an excessive quantity of metallic material that likely restricted oil flow throughout the engine. The engine was last overhauled about 28 years before the accident and had accumulated about 1,683 hours since. The manufacturer’s recommended overhaul time is 12 years or 2,000 hours, whichever occurs first. While closely monitored and frequently operated engines may be able to safely operate beyond the manufacturer’s recommended schedule, the damage observed on the No. 2 piston, the tappets and the camshaft suggest a likelihood that either the engine was not adequately monitored for signs of deterioration, or signs of deterioration were observed but ignored. For example, the wear on the No. 2 piston skirt, piston rings and their lands, camshaft lobe and pitted tappet body faces would have produced excessive metal for some time and was detected by oil trend analysis. An unspecified amount of ferrous metal flakes in the oil filter was recorded in the engine logbook about 15 months (about 65.5 engine hours) before the accident, no metal was observed during subsequent oil filter and oil screen inspections performed 12 months and 2 months before the accident. The engine’s logbook indicated that oil analysis was performed at intervals four times in the 19 months before the accident. Since the inception of the oil analysis, an increase in iron content quantity to the “reportable” range was documented; however, a subsequent oil analysis performed 7 days (about 5 engine hours) before the accident showed a decrease in the iron content, back into the “normal” range. Additionally, a consistent increase in aluminum and chromium along with increased reported oil consumption was observed in each of the reported oil samples. Components in this engine with a material composition comprised of aluminum, iron, or chromium include pistons, piston pin plugs, piston rings, valve stems, bearings, and rotating shafts within the valve train. It’s likely that more in depth analysis of the oil analysis coupled with additional engine inspections by maintenance personnel may have resulted in the detection of the failed No. 2 piston plug and associated damage to the No. 2 piston. The excessive quantity of metallic debris captured by the oil suction screen would have restricted oil flow throughout the engine. It is likely that the loss of engine power was ultimately due to insufficient lubrication to the connecting rod bearings that resulted in the No. 3 connecting rod bearing failure and subsequent fracture of the No. 3 connecting rod bolts.
Probable cause
The loss of engine power due to the failure of the No. 2 piston pin plug, which resulted in oil starvation and subsequent failure of the No. 3 connecting rod. Contributing to the accident was the inadequate engine inspections by maintenance personnel.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR24LA076
- Event ID
- 20240117193674
- Case number
- WPR24LA076
- 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: 5f530ffc7c2d879c2f16cab07ed50addbc1d2c10e0a9752b5e0f8a89ed929252; retrieved 2026-09-16T18:26:39.613Z.
- Corrected after a review of the NTSB narrative, which states these values explicitly: destination. City slot holds the airport name; KNB is Kanab Municipal Airport at Kanab, UT.