27 Sep 2016: RYAN NAVION B

27 Sep 2016: RYAN NAVION B (N5327K) — Unknown operator

No fatalities • Hurt, VA, United States

Probable cause

Incorrect installation of the oil temperature probe and an inadequate annual inspection that failed to detect leaking oil around the loose probe, which resulted in a catastrophic engine failure due to oil starvation.

— NTSB Determination

Accident narrative

On September 27, 2016, about 1745 eastern daylight time, a Ryan Navion B, N5327K, was substantially damaged during a forced landing, following a total loss of engine power while in cruise flight near Hurt, Virginia. The private pilot was not injured. Visual meteorological conditions prevailed, and no flight plan was filed for the personal flight, which was conducted under the provisions of 14 Code of Federal Regulations Part 91. The flight departed Culpeper Regional Airport (CJR), Culpeper, Virginia, about 1700, destined for Long Island Airport (NC26), Long Island, North Carolina.According to the pilot, about 45 minutes into the flight, at an altitude of 3,000 feet mean sea level, the engine suddenly began to vibrate. He informed Roanoke Approach air traffic control (ATC) of his intent to try to land at the nearest airport, which was New London Airport (W90), Forest, Virginia. A few seconds later he heard a loud bang, the vibration worsened, smoke and oil emanated from the engine compartment, and the engine lost power as the propeller continued to windmill. The pilot then advised ATC that he would not be able to make the airport, and he then performed an emergency landing to a mowed hay field. During the landing rollout, the airplane struck and rolled through a post-and-wire fence resulting in substantial damage to the right wing.

Examination of the airplane by a Federal Aviation Administration inspector revealed that the right wing leading edge sustained substantial damage, and fence wire was wrapped around the propeller flange. The top left side of the engine crankcase was damaged, and there were holes in the crankcase near cylinder Nos. 6, 4 and 2. A connecting rod protruded through the hole near cylinder No. 4. No oil was present in the crankcase. A teardown examination of the engine was subsequently performed at the manufacturer's facility, under the supervision of a National Transportation Safety Board investigator. The examination revealed that the internal engine components exhibited heat distress consistent with a lack of lubrication. Further examination revealed that the oil temperature probe was safety wired, however it could be moved by hand. An air pressure hose was attached to the oil cooler and when 30 psi was applied, bubbles were noted around the crush washer seal of the oil temperature probe. Oil residue was also noted all over the oil cooler and surrounding area of the engine. See Figure 1. The oil temperature probe was removed, and the crush washer was found installed backwards.

Figure 1. Oil Temperature Probe The temperature probe was considered an airframe item and was not installed by the engine manufacturer. The engine was delivered with a plug in the oil temperature probe port, and the installer could remove the plug and replace it with an oil temperature probe. A review of the 1951 Navion B Service Manual revealed no specific torque values for tightening the oil temperature probe. The maintenance manual for the accident engine provided a torque range for the oil temperature port plug (with crush washer), as 190 in/lbs to 210 in/lbs. The version of the manual in effect at the time of the accident did not specify the orientation of crush washers.

Maintenance records revealed that the airplane's most recent annual inspection occurred on September 16, 2016. At that time, the airplane had accrued a total of 4,488 flight hours, and the engine had accrued a total of 832 hours since overhaul.

Contributing factors

  • cause Maintenance personnel
  • cause Maintenance personnel
  • cause Power plant — Failure
  • cause Fluid level
  • Contributed to outcome

Conditions

Weather
VMC, wind 160/06kt, 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.