Dallas-Fort Worth

Shortly after takeoff the pilot reported to the air traffic controller that he was losing engine power. The pilot then said he was going to divert to a nearby airport and accepted headings to the airport. The pilot then reported the loss of engine power had stabilized, so he wanted to return to his departure airfield. A few moments later the pilot reported that he was losing engine power again and he needed to go back to his diversion airport. The controller reported that another airport was at the pilot’s 11 o’clock position and about 3 miles. The pilot elected to divert to that airport. The airplane was at 4,500 ft and too close to the airport, so the pilot flew a 360° turn to set up for a left base. During the turn outbound, the engine lost all power, and the pilot was not able to reach the runway. The airplane impacted a field, short of the airport. The airplane’s wings separated in the accident and a small postcrash fire developed. A review of the airplane’s maintenance records revealed maintenance was performed on the day of the accident flight to correct reported difficulty moving the Power Control Lever (PCL) into reverse position. The control cables were inspected from the pilot’s control quadrant to the engine, engine controls, and propeller governor. A static rigging check of the PCL was performed with no anomalies noted. Severe binding was observed on the beta control cable (propeller reversing cable). The cable assembly was removed from the engine, cleaned, reinstalled, and rigged in accordance with manufacturer guidance. During a post-accident examination of the engine and propeller assembly, the beta control cable was found mis-rigged and the propeller blades were found in the feathered position. The beta valve plunger was extended beyond the chamfer face of the propeller governor, consistent with a position that would shut off oil flow from the governor oil pump to the constant speed unit (CSU). A wire could be inserted through both the forward and aft beta control cable clevis inspection holes that function as check points for proper thread engagement. The forward beta control cable clevis adjustment nut was rotated full aft. The swaging ball end on the forward end of the beta control cable was not properly secured between the clevis rod end and the push-pull control terminal and was free to rotate within the assembly. Before takeoff, the beta valve was in an operational position that allowed oil flow to the CSU, resulting in normal propeller control. Vibration due to engine operation and beta valve return spring force most likely caused the improperly secured swaging ball to rotate (i.e. “unthread”) forward on the beta control cable. The resulting lengthening of the reversing cable assembly allowed the beta valve to stroke forward and shut off oil flow to the propeller CSU. Without propeller servo oil flow to maintain propeller control, the propeller faded to the high pitch/feather position due to normal leakage in the transfer bearing. The reported loss of power is consistent with a loss of thrust due to the beta control cable being mis-rigged during the most recent maintenance work.

The 7,660-hour airline transport rated pilot lost control of the twin-engine airplane while attempting to abort the landing. Dark night conditions prevailed for the attempted landing on runway 18. Runway 18 was reported to be 5,280-feet long, by 50 feet wide. The asphalt runway was reported to be dry and in good condition at the time of the accident. The pilot stated in the accident report (NTSB form 6120.1/2) that "I saw the one row of lights on short final and my mind played a trick on me. I had the thought that I was off-course and that those lights were houses." The pilot delayed making the decision to execute a go-around and by the time he added power the airplane had touched down in the "turnaround" area to the right of the approach end of runway 18. During the inadvertent touchdown the airplane rolled to the left and the left propeller struck the ground, resulting in damage to the left engine. The pilot added that he elected to retard the right engine to avoid losing control of the airplane and the airplane impacted the ground to the left of the runway. The airplane came to rest in an area of small bushes and mesquite trees. The pilot was able to egress the airplane unassisted through the main cabin door, and was not injured. A post-impact fire developed and consumed the airplane. The pilot reported that he was familiar with the airport and had operated several airplanes in and out of that location. Weather reported at Del Rio International Airport, located approximately 11 miles north of the accident site, was clear skies, 3 miles visibility, with winds from 150 degrees at 5 knots, temperature of 70 degrees Fahrenheit, and an altimeter setting of 29.95 inches of Mercury. The pilot added that he was not aware that the first 5 or 6 runway lights on the left side of the runway (at the approach end) were out of service when he initiated the night landing approach.

During landing touchdown, following a stabilized approach, the right main landing gear failed. The airplane remained controllable by the pilots and came to a stop on the runway, resting on its right wing. The DFW Fire Department arrived at the accident site in 35 seconds and, following communication between the airplane's Captain and Fire Department's Incident Commander, it was decided that an emergency evacuation of the airplane was not necessary. Examination revealed that the right main gear's outer cylinder had fractured allowing the lower portion of the gear (including the wheel assembly) to separate from the airplane. Research, examination & testing of the cylinder revealed that a forging fold was introduced into the material during the first stage of its forging process. The first stage is a hand operation, therefore the quality is highly dependent on the person performing the hand operation. Following the first landing, the forging fold became a surface breaking crack, due to the normal loads imposed during landing. Although growth of the fatigue crack was suppressed by crack blunting, high load landings resulted in growth of the fatigue crack. Subsequently, the landing gear failed when the crack had reached a critical length. Additionally, the airplane's maintenance records were reviewed and no anomalies were found.

The captain was the flying pilot for the night landing on runway 01 in instrument meteorological conditions (IMC), with a right cross wind from 110 degrees at 14 gusting 18 knots, drizzle, and a wet runway. Prior to starting the approach, the flightcrew determined that the landing approach speed (Vref) and the approach speed (Vapp) were 122 and 128 knots, respectively. DFDR data showed the airplane flying on autopilot as it passed the middle marker at 200 feet AGL at 130 knots on the ILS approach. Approximately 3 seconds after the first officer called "runway in sight twelve o'clock," the captain disconnected the autopilot, while at a radio altitude of 132 feet and on a heading of approximately 18 degrees. Within approximately 11 seconds after the autopilot disconnect, the glideslope and localizer deviation increased. The first officer called "runway over there." Approximately 5 seconds before touchdown, the airplane rolled right, then left, then right. DFDR data-based performance calculations showed the airplane crossed the threshold at an altitude of 35 feet and 130 knots. The airplane touched down 2,802 feet from the approach end of the 5,495-foot runway (844- foot displaced threshold) at 125 knots on a heading of 10 degrees. The airplane overran the runway and struck a ditch 175 feet beyond the departure end of the runway. Landing roll calculations showed a ground roll of 2,693 feet after touchdown, consisting of 1,016 feet ground roll before braking was initiated and 1,677 feet ground roll after braking was initiated until the airplane exited the pavement. According to Saab, for a wet runway, the aircraft would have needed 1,989 feet from the time of braking initiation to come to a complete stop. The American Eagle Airlines, Inc., FAA approved aircraft operating manual (AOM), states in part: Stabilized approaches are essential when landing on contaminated runways. Landing under adverse weather conditions, the desired touch-down point is still 1,000 feet from the approach end of the runway. Touchdown at the planned point. Cross the threshold at Vapp, then bleed off speed to land approximately Vref -5. Use reverse, if needed. To achieve maximum braking effect on wet runway, apply maximum and steady brake pressure. In 1992, the City of Killeen submitted a proposal that included extending the north end of runway 01 by 194 feet. The FAA originally disapproved the proposal, in part, because the runway extension decreased the length of the runway safety area (RSA) which was already shorter than the recommended 1,000 feet for a 14 CFR Part 139 certificated airport. The proposal was subsequently approved and a drainage ditch was installed in the north RSA, perpendicular to the runway and approximately 175 feet north of the departure end of runway 01. In 1993, the airport received FAA Part 139 certification. The 1998 and 1999, FAA airport certification inspection reports noted the inadequate RSA; however, neither letter of correction, sent from the FAA to the City of Killeen following the inspections, mentioned the RSA. Following this accident, the ILS runway 01 was flight checked by the FAA and all components were found to be operating within prescribed tolerances. Examination of the airplane found no anomalies that would have prevented it from operating per design prior to departing the runway and encountering the ditch.

The Cessna 551, collided with trees and subsequently the ground following a missed approach to runway 10, at the Crisp County Airport in Cordele, Georgia. According to the Jacksonville Air Traffic Control Center, the pilot was given radar vectors to the outer marker and cleared him for the non-precision localizer approach to runway 10. Recorded radar data showed the airplane initiating the approach at 1900 feet mean sea level (MSL) as published. The airplane descended to 600 feet MSL as published and over-flew the airport. The controller stated that he was waiting for the missed approach call, as he observed the airplane climb to 700 feet MSL. The airplane then descended back to 600 feet MSL and disappeared from radar. The controller never received a missed approach call. A witness near the airport stated that he heard the airplane fly over but did not see it due to haze and fog.