28 Feb 2016: CESSNA 182 K

28 Feb 2016: CESSNA 182 K (N2816R) — Unknown operator

No fatalities • Gainesville, FL, United States

Probable cause

The failure of the engine crankshaft near the Nos. 4 and 5 crankshaft journals due to oil starvation. The reason for the oil starvation could not be determined during postaccident examination.

— NTSB Determination

Accident narrative

On February 28, 2016, about 1200 eastern standard time, a Cessna 182K, N2816R, experienced a total loss of engine power and performed a forced landing to a road near Gainesville, Florida. The commercial pilot and passenger incurred minor injuries. Visual meteorological conditions prevailed, and an instrument flight rules flight plan was filed for the flight, which originated at Fort Lauderdale Executive Airport (FXE), Fort Lauderdale, Florida, around 1000. The airplane was owned and operated by the pilot. The personal cross-country flight was conducted under the provisions of 14 Code of Federal Regulations Part 91 and had an intended destination of Gainesville Regional Airport (GNV), Gainesville, Florida.

According to the pilot, he performed a preflight inspection, added 1 quart of oil to the engine, which totaled 8 quarts of oil, and then performed an engine run up with no anomalies noted. The takeoff, climb, and beginning of the descent phase of flight were "uneventful." The pilot was cleared to land on runway 7 when the engine began to run "rough." He unsuccessfully attempted to alleviate the rough engine noise by enriching the mixture and then reducing the power. The engine began shaking, oil sprayed onto the windscreen of the airplane, and then the engine experienced a total loss of power. The pilot declared an emergency, and elected to land on a road. After touching down on the paved surface, the left wing of the airplane impacted a palm tree and the airplane stopped on the road.

A postaccident examination of the airplane revealed that the wings and fuselage were substantially damaged. In addition, the engine cowling was removed to facilitate an engine examination, and a hole was noted in the top of the crankcase in the vicinity of the No. 4 cylinder. In addition, the No. 4 cylinder connecting rod was located on the top of the engine. The engine was retained for further examination.

According to Federal Aviation Administration (FAA) records, the airplane was manufactured in 1967, and registered to the pilot/owner in 2014. It was equipped with a Continental Motors IO-550 D series, 300-hp engine, which was installed in February 2000 in accordance with a supplemental type certificate. According to the pilot, the engine had accumulated 2,135 total hours of time in service since the time of rebuild in 1999, and had approximately 130 flight hours since the most recent annual inspection, which was completed on November 3, 2015. The most recent oil change occurred approximately 32 flight hours prior to the accident. Engine manufacturer guidance recommended that the time-based overhaul of the engine occur at 1,700 flight hours or every 12 years.

The engine was examined at the manufacturer's facility under NTSB oversight. Examination of the cylinders revealed normal operating signatures and combustion deposits. The intake and exhaust valve faces and seats exhibited full seat contact signatures, and the intake and exhaust valve guides exhibited normal wear and operating signatures. The intake and exhaust rocker arms and shafts also exhibited normal operating signatures. All piston heads exhibited normal combustion deposits. The Nos. 4 and 5 pistons exhibited impact damage and the No. 4 piston was fractured.

Disassembly of the engine revealed the Nos. 4 and 5 connecting rods had separated from the crankshaft at their respective journals. The Nos. 4 and 5 journals exhibited discoloration and heat damage, consistent with oil starvation. The oil galleys and passages in the crankshaft were clear and unrestricted.

The engine oil sump was removed from the engine and the forward section exhibited impact damage. In addition, an unmeasured amount of oil and metal particles were noted inside the oil sump. The oil filter remained attached to the engine and was removed. It was disassembled and metal particles were noted in the filter.

The crankcase exhibited exterior damage concentrated at the No. 4 cylinder. Cylinder bays Nos. 4 and 5 were mechanically damaged, with portions of the crankcase missing above the No. 4 cylinder. The main bearing support mating surfaces were intact, exhibited no signs of fretting, and exhibited no signs of bearing movement or rotation. The oil galleys and passages in the left and right crankcase halves were intact, clear, and unrestricted.

The airplane was equipped with a JPI engine data monitor that was capable of recording engine performance data. The engine data monitor was removed and successfully downloaded at the NTSB's Vehicle Recorder Division in Washington, D.C. The data parameters that were recorded for the accident flight included, fuel flow, exhaust gas temperature, cylinder head temperature, oil temperature, fuel used, battery voltage, and outside air temperature.

According to the data, the flight was uneventful until about 1156, when the oil temperature began a steady increase. In the 4 minutes that followed, oil temperature continued to rise and peaked at 202 degrees F prior to the end of the data. According to the engine instruments in the cockpit, the DO NOT EXCEED oil temperature was 225 degrees F. Below 225 degrees F was the normal oil temperature operating range.

Contributing factors

  • cause Recip engine power section — Failure
  • cause Fluid level
  • Contributed to outcome

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.