12 Oct 2016: ROCKWELL INTERNATIONAL 112A A — SHO CO KIDS LLC

12 Oct 2016: ROCKWELL INTERNATIONAL 112A A (N509CA) — SHO CO KIDS LLC

No fatalities • Phoenix, AZ, United States

Probable cause

A catastrophic engine failure due to lack of lubrication due to the absence of 2 piston cooling nozzles that backed out of their respective threaded bores, which resulted in a forced landing on unsuitable terrain.

— NTSB Determination

Accident narrative

On October 12, 2016, about 1011 mountain standard time, a Rockwell International 112A airplane, N509CA, was substantially damaged when it was involved in an accident near Deer Valley Airport (DVT), Phoenix, Arizona. The pilot and passenger were seriously injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

According to air traffic control transcripts provided by the Federal Aviation Administration, the airplane departed from Falcon Field Airport (FFZ), Mesa, Arizona, about 0942 destined for Lake Havasu City Airport (HII), Lake Havasu City, Arizona. About 0955, a Phoenix Terminal Radar Approach Control Facility controller cleared the pilot to climb to his requested altitude of 10,500 ft mean sea level (msl). About 0959, the pilot advised the controller that the engine oil temperature was “running a little hot” and that he needed to level off at 7,500 ft msl to “cool off.” About 3 minutes later, the controller told the pilot his altitude was showing 7,200 ft msl and then asked him if he was going to be “okay,” and the pilot replied that he would be but that the oil temperature was still high and that he was going to monitor it a little longer.

About 1006, the pilot repeated that he was having trouble with the oil temperature and stated that he wanted to land at FFZ. The controller advised the pilot that he was about 8 miles from Phoenix Deer Valley Airport (DVT), Phoenix, Arizona, and the pilot stated that he would fly close to DVT in case he had to land there and repeated that he was not declaring an emergency. About 1007, the controller switched the flight to the DVT air traffic control tower and advised a controller of the flight’s issues. About 1008, the DVT tower controller issued the pilot a straight-in approach for runway 7R, but the pilot responded that his engine had lost power and that he was going to have to land because the airplane would not be able to reach DVT. The controller then gave the pilot his location and told him that there was a freeway to his right. The pilot replied that he would not be able to reach the freeway and was going to attempt to land on a nearby road. The airplane subsequently impacted terrain in a train yard about 3 miles west of DVT.

The airplane came to rest between a tree and a wood-frame structure. The wings and airframe were substantially damaged.

The engine remained attached to the engine mount, which had separated from the firewall during the impact sequence. During examination of the engine, a hole was found at the top of the engine crankcase at the No. 4 cylinder. No evidence of preimpact fire was found. The No. 4 connecting rod bearing had extruded and exhibited signatures consistent with a lack of oil lubrication. The connecting rod had separated from its respective crankshaft journal and exhibited localized heat distress signatures. Connecting rod bearing material was found in the engine crankcase and in the oil suction screen.

The combustion chambers were undamaged, and no evidence of foreign object ingestion was found. The valves were intact and undamaged, and no valve-to-piston contact was observed. No oil residue was observed in the exhaust system gas path.

The magnetos remained secured to their respective mounting pads, and the ignition harness remained secured at each magneto. Both magnetos produced spark at the end of their respective spark plug leads during hand rotation.

The fuel flow divider remained secured at its mounting bracket at the top of the engine. No evidence of internal mechanical malfunction or obstruction to the fuel flow was found. The fuel nozzles remained secured at each cylinder. The fuel injection servo remained secured at its mounting pad, and the throttle and mixture controls remained secured at their respective control arm at the servo.

The spark plugs remained secured at each position with their respective leads attached. The spark plug electrodes remained undamaged. The top spark plugs were removed, and they exhibited coloration consistent with normal operation. The starter, alternator, and vacuum pump remained secured at their respective mounting pads. The accessory gears remained undamaged; however, flecks of metal were embedded in the case. The normalizing turbocharger and associated system components remained secured at their respective mountings. The turbocharger was not damaged, and the turbine was free to rotate.

The numbers 2 and 4 piston cooling nozzles were absent from their respective threaded bore at the crankcase. Both nozzles were in the oil sump and had sustained damage due to their meshing with the engines internal rotating components. The threaded bores for the Nos 2 and 4 nozzles were not damaged. The No 1 piston cooling nozzle remained secure in its position, and the No 3 piston cooling nozzle was in its position; however, it was loose and could be rotated a quarter of a turn before it became tight. Lycoming SSSP 1776-1, Table of Limits, Section V, page 1-35 required each piston cooling nozzle be torqued to 100 in/lb during assembly.

The three-bladed propeller assembly remained attached to the engine crankshaft. One of the propeller blades was bent rearward. The propeller governor drive was intact and free to rotate. The propeller governor gasket screen contained metal debris.

An engine logbook entry dated September 7, 2016, indicated that the manifold pressure (MAP) indicator was inaccurate and that a mechanic had to troubleshoot it. A logbook entry dated September 30, 2016, indicated that the engine vernatherm, which is a thermostatic bypass valve that controls the flow of oil to the oil cooler, was replaced with a serviceable unit. The oil filter was replaced, and the left and right magneto ignition timing was verified. A run-up and leak check were performed, and the pilot was to conduct a test flight to observe the engine oil operating temperature.

Contributing factors

  • Power plant — Failure
  • Fluid level

Conditions

Weather
VMC, wind 130/08kt, 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.