10 Jun 2018: CESSNA 182 A

10 Jun 2018: CESSNA 182 A (N3889D) — Unknown operator

No fatalities • ARECIBO, PR, United States

Probable cause

Maintenance personnel's failure to properly apply torque to the engine through bolts, which ultimately resulted in the crankshaft failure and the total loss of engine power.

— NTSB Determination

Accident narrative

On June 10, 2018, about 1234 Atlantic Standard time, a Cessna 182, N3889D, was substantially damaged during a forced landing after it experienced a total loss of engine power shortly after takeoff from the Antonio (Nery) Juarbe Pol Airport (ABO), Arecibo, Puerto Rico. The pilot was seriously injured, and the four passengers sustained minor injuries. The airplane was privately owned and operated by Skydive Puerto Rico as a Title 14 Code of Federal Regulations Part 91 skydiving flight. Visual meteorological conditions prevailed, and no flight plan was filed for the local flight that had just departed ABO.The pilot stated that shortly after takeoff from runway 8, about 275 ft above the ground, he made a left turn to avoid descending jumpers. While in the turn, the airplane started to vibrate, and the engine made a "clicking" sound while losing power. The pilot was unable to maintain altitude and made a forced landing to a field. The airplane flipped over, which resulted in substantial damage to the firewall, fuselage, right wing strut, and vertical stabilizer/rudder. The propeller was also damaged.

A postaccident examination of the engine by a Federal Aviation Administration (FAA) inspector revealed the crankshaft was fractured. Preparation was made to have the engine removed from the airframe and shipped to the manufacturer. Due to the limited availability of resources in Puerto Rico after Hurricane Maria, there was a delay in having the engine shipped. During this time, and unbeknownst to the National Transportation Safety Board (NTSB), the engine was sold while the investigation was still on-going. The FAA was able to locate the engine in Puerto Rico and the new owner assisted in having the engine shipped to the manufacture in Mobile, Alabama, where the engine was disassembled and examined under the supervision of the NTSB.

The examination revealed the crankshaft was fractured at the No. 3 cheek just forward of the No. 2 connecting rod and aft of the No. 2 main crankshaft journal. The No. 2 main bearing was displaced from its saddle and was severely worn. The head of the No. 2 cylinder's connecting rod bolt was fractured and not recovered. The crankcase web mating surfaces at the Nos. 2, 3, and No. 4 bearing saddles exhibited pitting consistent with fretting. The fractured ends of the crankshaft were examined at the NTSB Materials Laboratory. The examination revealed the fracture surfaces were consistent with fatigue cracking.

A review of the engine logbook revealed the engine was last overhauled on October 2, 1997, about 21 years prior to the accident. According to the Continental Standard Practice Maintenance Manual, the recommended time between overhauls for this model engine was 1,500 hours or 12 years. At the time of the accident, the engine had accrued a total of 2,821.2 hours and 1,111.2 hours since major overhaul.

Further review of the engine logbook revealed the engine was removed from the airplane on September 15, 2017, "due to excessive camshaft and lifter wear." A work order associated with this repair stated that the engine's camshaft and lifters were replaced at a tachometer time of 2,541 hours and 831 hours since overhaul (280 hours prior to the accident.). On January 5, 2018, at 965 hours since overhaul (146.2 hours prior to the accident), the No. 4 cylinder was removed and reinstalled after the piston rings were staggered. The engine underwent two additional 100-hour inspections, with the last being completed on June 5, 2018, at an engine time of 1,087 hours since overhaul.

The pilot held a commercial pilot certificate with ratings for airplane single and multiengine land, and instrument airplane. His last FAA first-class medical certificate was issued on December 12, 2017. The pilot reported a total of 2,285 flight hours, of which, 1,187 hours were in the same make/model as the accident airplane.

Contributing factors

  • cause Maintenance personnel
  • cause Recip engine power section — Failure

Conditions

Weather
VMC, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.