Cessna 421C Golden Eagle III

After takeoff from runway 34 at Lyon-Bron Airport, while in initial climb at a height of 200 feet, the twin engine airplane deviated to the left, rolled to the left and then veered to the left with a low rate of climb. Shortly after passing the end of the runway, the airplane lost height then struck the ground and caught fire. The airplane was destroyed by a post crash fire and all four occupants were killed. For unknown reasons, the pilot-in-command was seating in the right seat.

Company personnel reported that, in the weeks before the accident, the airplane's left engine had been experiencing a problem that prevented it from initially producing 100 percent power. The accident pilot and maintenance personnel attempted to correct the discrepancy; however, the discrepancy was not corrected before the accident flight, and company personnel had previously flown flights in the airplane with the known discrepancy. Witnesses reported observing a portion of the takeoff roll, which they described as slower than normal. However, the airplane was subsequently blocked from their view. Examination of the runway environment showed that, during the takeoff roll, the airplane traveled the entire length of the 4,501-ft runway, continued to travel through a 300-ft-long grassy area and a 300- ft-long soybean field, and then impacted the top of 10-ft-tall corn stalks for about 50 ft before it began to climb. About 1/2 mile from the airport, the airplane impacted several trees in a leftwing, nose-low attitude, consistent with the airplane being operated below the minimum controllable airspeed. The main wreckage was consumed by postimpact fire. Postaccident examinations revealed no evidence of mechanical anomalies with the airframe, right engine, or propellers that would have precluded normal operation. Given the left engine's preexisting condition, it is likely that its performance was degraded; however, postimpact damage and fire preluded a determination of the cause of the problem.

During a cross-country instrument flight rules (IFR) flight, the air traffic controller cleared the pilot to begin his initial descent for landing and issued a heading change to begin the approach. The pilot acknowledged the altitude and heading change. One minute later, the controller noticed that the airplane's radar track was not tracking the assigned heading. The controller queried the pilot as to his intentions, and the pilot replied that he was in a spin. There were no further communications with the pilot. The wreckage was subsequently located in steep mountainous terrain. A study of the weather indicated widespread cloud cover in the area around the time of the accident. A witness near the accident site reported that he heard an airplane in a dive but could not see it due to the very dark clouds in the area. He heard the engine noise increase and decrease multiple times. It is likely that the pilot entered into the clouds and failed to maintain airplane control. The changes in the engine noise were most likely the result of the pilot's attempt to recover from the spin. About 8 months before the accident, the pilot completed the initial pilot training course in the accident airplane and was signed off for IFR currency; however, recent or current IFR experience could not be determined. Examination of the fragmented airplane and engines revealed no abnormalities that would have precluded normal operation.

On December 8, 2012, at 1334 eastern standard time, a Cessna 421C, N297DB, operated by a private individual, was destroyed when it collided with trees and terrain following a loss of control after takeoff from North Palm Beach County Airpark (LNA), Lantana, Florida. The commercial pilot was fatally injured. Visual meteorological conditions prevailed, and no flight plan was filed for the personal flight, which was conducted under the provisions of Title 14 Code of Federal Regulations Part 91. The pilot took delivery of the airplane from a maintenance facility that had just completed an annual inspection and repainting of the airplane. According to the owner of the facility, who was a certificated pilot and an airframe and powerplant mechanic, the pilot completed the preflight inspection and the airplane was towed outside. The pilot started the airplane, but then shutdown to resolve an alternator charging light. Afterwards, the pilot stated that he planned to fly to Okeechobee, Florida, complete a few landings, and then continue to Miami. According to the mechanic, the pilot performed a ground run of the airplane for several minutes before taxiing to the approach end of Runway 3 for takeoff. The airplane lifted off about halfway down the runway and climbed at a "normal" rate. The mechanic then observed the airplane suddenly yaw to the left "for a second or two" and the airplane's nose continued to pitch up before rolling left and descending vertically, nose-down, until it disappeared from view. Several witnesses provided similar accounts to a Federal Aviation Administration (FAA) inspector and the local sheriff's department. One witness, a certificated flight instructor said, "The airplane just kept pitching up, and then it looked like a VMC roll."

The airplane was substantially damaged during an in-flight encounter with weather, in-flight separation of airframe components, and subsequent impact with the ground near Wells, Texas. The private pilot, who was the sole occupant, was fatally injured. The airplane sustained impact and fire damage to all major airframe components. The aircraft was registered to H-S Air LP and operated by the pilot under the provisions of 14 Code of Federal Regulations Part 91 as a business flight. Instrument meteorological conditions prevailed for the flight, which operated on an instrument flight rules (IFR) flight plan. The flight originated from the West Houston Airport (IWS), Houston, Texas, about 2040 and was bound for the Richard Lloyd Jones Jr. Airport (RVS), Tulsa, Oklahoma. Witnesses near the accident site reported hearing an explosion and then seeing a fireball descending through the clouds to the ground. Radar track data for the last portion of the flight depicted the airplane on a 7720 transponder code. The track showed the airplane initially on a heading of about 20 degrees at 23,000 feet. The track continued in this direction until 2120:03.73 when the airplane began a right turn. The right turn continued for about 30 seconds during which time the altitude remained constant and the heading changed to about 90 degrees. After 2120:45.86, the track showed an erratic steep descent that continued to the end of the data. The final data location was received at 2122:15.53 at an altitude of 2,800 feet. The accident location was 0.86 miles and 94 degrees from the last recorded radar position.

The aircraft impacted terrain following an in-flight breakup near Shaver Lake, California. The private pilot/registered owner was operating the airplane under the provisions of 14 Code of Federal Regulations Part 91. The pilot and passenger sustained fatal injuries. The airplane sustained substantial damage during the accident sequence, and was partially consumed by postimpact fire. The cross-country flight departed Salinas Municipal Airport, Salinas, California, at 1837, with a planned destination of Eppley Airfield, Omaha, Nebraska. Visual meteorological conditions prevailed, and an instrument flight rules (IFR) flight plan had been filed. The pilot was the son of the passenger. Both had spent the weekend attending a driving academy at the Laguna Seca Raceway, having arrived in the accident airplane earlier in the week. According to the pilot's wife, they had encountered strong headwinds during the outbound flight from Omaha, and had decided to take advantage of tailwinds for the return flight that night, rather than stay in a hotel. The pilot planned to return his father to Omaha, and then fly to his residence in Missouri the following day. Radar and voice communication data provided by the Federal Aviation Administration (FAA) revealed that prior to departure, the pilot was given an IFR clearance to Omaha, and that during his interaction with clearance delivery personnel he read back the clearance correctly. A few minutes after departing Salinas the airplane was cleared to fly direct to the Panoche VORTAC (co-located very high frequency omnidirectional range (VOR) beacon and tactical air navigation system). The airplane followed a direct course of 60 degrees; reaching Panoche at a mode C reported altitude of 17,200 feet, about 14 minutes later. The airplane continued on that course, reaching the Clovis VOR at 1912, coincident to attaining the pilots stated cruise altitude of 27,000 feet. The pilot reported leveling for cruise, and flying direct to Omaha. The sector controller reported that the pilot should fly direct to the Coaldale VOR and then to Omaha, and the pilot responded, acknowledging the correction. For the next 5 minutes, the airplane continued at the same altitude and heading, with no further transmissions from the pilot. The airplane then began a descending turn to the right, with a final mode C reported radar target recorded 60 seconds later. During that period, it descended to 22,600 feet, with an accompanying increase in ground speed from about 190 to 375 knots. For the remaining 6 minutes, a 6.5-mile-long cluster of primary targets (no altitude information) was observed emanating from the airplane's last location, on a heading of about 150 degrees. Following the initial route deviation, the air traffic controller made five attempts to make contact with the pilot with no success. Throughout the climb and cruise portion of the flight, the airplane flew directly to the assigned waypoints with minimal course variation, in a manner consistent with the pilot utilizing the autopilot.

According to a statement provided by the Jacksonville Center air traffic control (ATC) facility, the pilot contacted ATC while at flight level 270. About 25 minutes later, the airplane began to deviate from the ATC-assigned altitude and route. The controller’s attempts to contact the pilot were unsuccessful. The North American Aerospace Defense Command launched military fighter aircraft to intercept the airplane. The military pilots reported that the airplane was circling in a left turn at a high altitude and low airspeed and that its windows were partially frosted over. They also reported that the pilot was slumped over in the cockpit and not moving. They fired flares, and the pilot continued to be unresponsive. The airplane circled for about 3 hours before it descended into the Gulf of Mexico and sank. The pilot and airplane were not recovered. Review of the pilot’s Federal Aviation Administration medical records did not reveal any recent medical conditions that would have deemed him unfit to fly.

Shortly after the airplane lifted off, the tower controller informed the pilot that a plume of smoke was visible behind the airplane. No communications were received from the pilot after he acknowledged the takeoff clearance. Witnesses reported that white smoke appeared to be trailing from the area of the left engine during takeoff. The witnesses subsequently observed flames at the inboard side of the left engine. The airplane began a left turn. As the airplane continued the turn, the flames and trail of white smoke were no longer visible. When the airplane reached a southerly heading, the nose dropped abruptly, and the airplane descended to the ground. Witnesses stated that they heard an increase in engine sound before impact. A postimpact fire ensued. The accident site was located about 3/4 mile from the airport. A postaccident examination determined that the left engine fuel selector and fuel valve were in the OFF position, consistent with the pilot shutting down that engine after takeoff. However, the left engine propeller was not feathered. Extensive damage to the right engine propeller assembly was consistent with that engine producing power at the time of impact. The landing gear and wing flaps were extended at the time of impact. Teardown examinations of both engines did not reveal any anomalies consistent with a loss of engine power. The left engine oil cap was observed to be unsecured at the accident site; however, postaccident comparison of the left and right engine oil caps revealed disproportionate distortion of the left oil cap, likely due to the postimpact fire. As a result, no determination was made regarding the security of left engine oil cap before the accident. Emergency procedures outlined in the pilot’s operating handbook (POH) noted that when securing an engine, the propeller should be feathered. Performance data provided in the POH for single-engine operations were predicated on the propeller of the inoperative engine being feathered, and the wing flaps and landing gear retracted. Thus, the pilot did not follow the emergency procedures outlined in the POH for single-engine operation.

The multi-engine airplane was in cruise flight at flight level 210 when the pilot declared an emergency due to a rough-running right engine and diverted to a non-towered airport about 10 miles from the airplane’s position. About 4 minutes later, the pilot reported that he had shut down the right engine. The pilot orbited around the diversion airport during the descent and reported to an air traffic controller that he did not believe he would require any assistance after landing. The airplane initially approached the airport while descending through about 17,000 feet mean sea level (msl) and circled above the airport before entering a left traffic pattern approach for runway 22. About 7,000 feet msl, the airplane was about 2.5 miles northeast of the airport. The airplane descended through 2,300 feet msl when it was abeam the runway threshold on the downwind leg of the traffic pattern. According to the airplane information manual, procedures for landing with an inoperative engine call for “excessive altitude;” however, the airplane's last radar return showed the airplane at an altitude of 700 feet msl (about 600 feet above ground level) and about 3 miles from the approach end of the runway. The airplane was configured for a single-engine landing and was likely on or turning to the final approach course when it rolled and impacted trees. The airplane came to rest in a wooded area about 0.8 miles north of the runway threshold, inverted, in a flat attitude with no longitudinal deformation. A majority of the airplane, including the cockpit, main cabin, and left wing, were consumed by a postcrash fire. Search operations located the airplane about 6 hours after its expected arrival time. Due to the severity of the postcrash fire, occupant survivability after the impact could not be determined. Examination of the airframe, the left engine, and both propellers did not reveal any preaccident mechanical malfunctions or failures that would have precluded normal operation. The investigation revealed that the right engine failed when the camshaft stopped rotating after the camshaft gear experienced a fatigue fracture on one of its gear teeth. The remaining gear teeth were fractured in overstress and/or were crushed due to interference contact with the crankshaft gear. Spalling observed on an intact gear tooth suggested abnormal loading of the camshaft gear; however, the origin of the abnormal loading could not be determined.

A witness reported that, despite the darkness, he was able to see the navigation lights on the airplane as it flew over the south end of the airport at an altitude of 150 to 200 feet above the ground. The airplane made a left turn to the downwind leg of the traffic pattern and continued a descending turn until the airplane impacted the ground in a near-vertical attitude. Due to the airplane’s turn, the 10- to 20-knot quartering headwind became a quartering tailwind. The airplane was also turned toward a rural area with very little ground lighting. A postaccident examination of the airplane and engines did not reveal any preimpact anomalies that would have precluded normal operation of the airplane.