23 Jan 2010: CESSNA 182C — Kiley Chandler

23 Jan 2010: CESSNA 182C (N8948T) — Kiley Chandler

No fatalities • Reno, NV, United States

Probable cause

A total loss of engine power during cruise due to oil starvation as a result of foreign material blockage of the oil pickup tube.

— NTSB Determination

Accident narrative

On January 23, 2010, about 1500 Pacific standard time, a Cessna 182C airplane, N8948T, was substantially damaged during a forced landing near Reno, Nevada. The airplane was registered to Alpine Aviation Partners LLC of Reno, and operated by the pilot under the provisions of Title 14 Code of Federal Regulations Part 91. The private pilot and passenger sustained minor injuries. Visual meteorological conditions prevailed and no flight plan was filed for the personal flight. The local flight originated from the Reno-Stead Airport (4SD), about 1415.

In a written statement, the pilot reported that during cruise flight, the airplane experienced a “significant shake” similar to a “small strike.” The pilot verified his instruments, noticed the “manifold pressure jumping,” and noted that it felt like the engine was losing power. The pilot applied carburetor heat, checked the fuel selector handle, and reduced the engine power and initiated a precautionary landing to a road. The pilot stated that during the descent and on a base leg to his selected landing area, the “engine failed completely.” Despite his attempts, the engine would not restart and the propeller would not move. Subsequently, the pilot landed on an unoccupied road. During the landing roll, the airplane struck a ditch and nosed over.

Examination of the airplane by the pilot revealed that oil was visible on both sides of the fuselage and wing flaps. The top portion of the vertical stabilizer and rudder were bent and buckled. Buckling in the fuselage was observed just forward of the empennage.

The Continental O-470-L engine, serial number 82178-4-L, was examined at the facilities of Teledyne Continental Motors under the supervision of the Safety Board investigator-in-charge (IIC). Examination of the engine revealed that the number one connecting rod exhibited extreme thermal and mechanical damage and was fractured through at the base of the I-beam. Fragments of the number one connecting rod cap exhibited thermal and mechanical damage. The number two connecting rod exhibited extreme thermal and mechanical damage and the bearing supports were distorted. The number two connecting rod cap exhibited thermal and mechanical damage and was deformed.

The oil sump exhibited impact damage. About five quarts of oil was drained from the oil sump. The oil was dark in color and contained portions of what appeared to be a paper towel and fragments of damaged internal engine components. The oil pickup tube was intact and undamaged. The oil pickup tube was restricted with a paper-towel-like material.

The crankcase exhibited exterior damage concentrated above the number two cylinder bay. The number one and two cylinder bays exhibited mechanical damage at the centerline of the cylinder bore that displaced the intake lifter bore material from the crankcase casting. The remaining cylinder bays were intact and undamaged. The main bearing support mating surfaces were intact and exhibited no signs of fretting or bearing tang lock-slot elongation. The main bearing support diameters were intact 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 rear crankshaft main bearing exhibited lubrication distress and thermal smearing of the surface babbit. The number two intermediate crankshaft main bearings exhibited lubrication distress and thermal smearing of the surface babbit, exposing the copper layer. The number three intermediate crankshaft main bearings exhibited contamination imbedded in the surface layer. The front crankshaft main bearings exhibited contamination imbedded in the surface layer.

The pilot reported that the engine had accumulated a total time in service of 3,039 hours, with 993 since last overhaul.

Contributing factors

  • cause Engine (reciprocating) — Failure
  • cause Oil

Conditions

Weather
VMC, wind 260/10kt, 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.