Airport (less than 10 km from airport)

The twin engine aircraft departed Alta Airport at 1522LT on a regular schedule service to Båtsfjord, carrying 24 passengers and a crew of three. Following an uneventful flight, the crew started a LOC/DME approach to runway 21. Shortly after passing the missed approach point, the pilot-in-command lost visual contact with the runway so the captain took over controls and continued the approach. The airplane became unstable and the crew encountered control problems due to difficulties to disengage the autopilot system. This caused the aircraft to lose height during the last segment and it landed hard, causing the right main gear to collapse upon impact. The aircraft slid for few dozen metres then veered off runway to the right and came to rest in a grassy area 23 metres to the right of the runway. All 27 occupants evacuated safely while the aircraft was damaged beyond repair.

During a forced landing the left wing struck a light standard pole, and the airplane came to rest inverted after colliding with a fence. The purpose of the flight was to conduct recurrent training to include emergency procedures. On the accident flight the certified flight instructor (CFI) initiated a simulated engine failure after takeoff during the initial climb out. The student advised the tower, and turned crosswind at 700 feet agl. The student set up for landing, which included lowering the landing gear and adding 10 degrees of flaps. On short final, descending through 400 feet agl, both the CFI and student realized they would not make the runway. Both pilot's advanced the throttle, to arrest the descent and perform a go-around. There was no corresponding response from the engine. During the final stages of the emergency descent, the pilot maneuvered the airplane to avoid a work crew at the airport boundary fence and the airplane collided with the light standard pole and a fence. An airframe and engine examination discovered no discrepancies with any system. Following documentation of the engine and related systems it was removed and installed in an instrumented engine test cell for a functional test. The engine started without hesitation and was operated for 44 minutes at various factory new engine acceptance test points. During acceleration response tests, technicians rapidly advanced the throttle to the full open position, and the engine accelerated with no hesitation. A second acceleration response test produced the same results. According to Textron Lycoming, there were no discrepancies that would have precluded the engine from being capable of producing power.

The Venezuelan registered Beech King Air C90 departed Caracas, Venezuela's Óscar Machado Zuloaga International Airport at 1516 eastern daylight time with a pilot and two passengers aboard, and flew to Fort Lauderdale-Hollywood International Airport, Florida. The route of flight filed with air traffic control was: after departure, direct to Maiquetia, thence Amber Route-315 to Bimini, thence Bahama Route 57V to Fort Lauderdale. The {planned} flight level was 220, and the pilot stated that 7 hours 15 minutes of fuel was aboard. Immigration/customs general declaration papers found aboard the wreckage stated the flight's intended destination was Nassau, and the pilot's daughter stated he always stopped at Nassau for fuel on many previous trips. After 6 hours 6 minutes, the aircraft crashed into a highway abutment about 1,700 feet short of his intended landing runway at Fort Lauderdale with total accountable onboard fuel of 3 to 4 gallons. One passenger received fatal injuries, one passenger received serious injuries, and the pilot received serious injuries. Engine factory service center disassembly examination revealed that the engines and their components exhibited no evidence of any condition that would have precluded normal operation, precrash. No precrash abnormalities with the propellers, their respective components, or any other aircraft system component were noted. Type certification data sheets for the C90 state that the unusable fuel aboard is 24 lbs., (3.6 gallons of Jet-A fuel).

During a test flight, the airplane encountered an elevator system oscillation while in a high speed dive outside the normal operating envelope. The 17 second oscillation was recorded on the cockpit voice recorder and had an average frequency of 28 Hz. The aft elevator sector clevis (p/n 2331510-32) fractured due to reverse bending fatigue caused by vibration, resulting in a complete loss of elevator control. The flight crew reported that pitch control was established by using horizontal stabilizer pitch trim. The flightcrew stated that during final approach to runway 17 (13,337 feet by 200 feet, dry/asphalt) the aircraft's nose began to drop and that the flying pilot was unable to raise the nose using a combination of horizontal stabilizer trim and engine power. The aircraft landed short of the runway, striking an airport perimeter fence and a berm. The surface winds were from the south at 23 knots, gusting to 32 knots.

The copilot inadvertently induced a lateral oscillation and lost control of the airplane while practicing touch-and-go landings. The pilot made the first touch-and-go. The copilot successfully made the second touch-and-go. The copilot attempted the third touch-and-go. At 50 feet, he disengaged the yaw damper and entered a pilot induced lateral oscillation. The airplane rapidly decelerated and developed a high sink rate. The airplane dragged the right tip fuel tank, which separated from the airplane, and the airplane bounced back into the air. The airplane landed hard, the main landing gear collapsed, and the airplane skidded to a stop off the right side of the runway. Both pilots and the passenger deplaned through the main entry door. The pilot-in-command had not demonstrated the handling characteristics of the airplane with the yaw damper off, and he felt he did not react quickly enough to prevent the accident.

While on approach to Santiago de Compostela Airport, around 0000LT, meteorological conditions were reported to be good, and the crew requested a visual approach to runway 17, even though the active runway was 35. Once cleared to land, the aircraft encountered a fog patch and from this moment it began a high rate descent (2,000 to 3,000 feet per minute). A minute after entering an unexpected and unforeseen fog patch, at 00:13:02 of June 7, the aircraft struck some trees, in level flight and with an airspeed of 148 knots. The wings and engines detached from the fuselage, and they dragged along a scrubland area until they came to a stop. The crew suffered minor injuries and the aircraft was completely destroyed.

Following an uneventful cargo flight from Guarapuava, the crew started the descent to Curitiba-Bacacheri Airport by night and adverse weather conditions. After touchdown on a wet runway surface, the twin engine aircraft went out of control, overran and collided with a concrete wall. All three occupants were injured, one of the pilot seriously.

The flight took off on Runway 22 at Gander, Newfoundland and Labrador, at 1428 Newfoundland daylight time with the pilot and four passengers on board. Their destination was Sango Bay, Newfoundland and Labrador, with an intermediate stop in Charlottetown, Newfoundland and Labrador, to drop off one of the passengers. Radar data show that, on departure from Gander, the aircraft climbed at about 500 feet per minute at 125 knots ground speed to 2500 feet, then descended and proceeded en route to Charlottetown at 1900 feet and 150 knots. The aircraft landed at Charlottetown at 1615. After a brief stop, the flight continued to Sango Bay. The pilot broadcast his intention to take off on Runway 10, taxied the aircraft to the threshold of the runway, and commenced the take-off roll. Part-way down the runway, the pilot aborted the take-off. He then broadcast his intention to take off on Runway 28. Both radio broadcasts were acknowledged by a local pilot who was approaching the airport to land. Upon reaching the threshold of Runway 28, the aircraft turned and accelerated, without stopping, on the take-off roll. The aircraft lifted off shortly before the runway end and remained near treetop height until disappearing from view. After lift-off, the stall warning horn sounded intermittently until impact. The aircraft was unable to climb above the hilly terrain and struck the road 1.5 nautical miles from the departure end of the runway. A passing motorist spotted the downed aircraft and notified firefighters and medical personnel who were then dispatched to the scene. The accident occurred at about 1621 during daylight hours, at 58°45' N, 55°66' W, at 440 feet above sea level.

About 20 minutes before the accident, the pilot reported to the air traffic controller that he had a problem with an engine and needed to shut the engine down. The flight had just leveled at 23,000 feet. The controller told the pilot that he was near Jackson, Tennessee, and that he could descend to 7,000 feet. About 10 minutes later, the pilot reported he was at 8,000 feet and requested radar vectors for the instrument landing system approach to runway 2 at the McKellar-Sipes Regional Airport, at Jackson. The pilot told the controller he had the left engine shut down. About 5 minutes later, the pilot reported he had a propeller runaway. About 1 minute later, the pilot reported he was in visual conditions and requested radar vectors direct to the airport. About 2 minutes later, the pilot reported he had a cloud layer under him and that he had the localizer frequency for runway 2 set. About 1 minute later, the pilot was told to contact the McKellar Airport control tower. The pilot acknowledged this instruction. No further transmissions were received from the flight. Examination of the left engine at the accident site showed the left propeller control was found disconnected at the point the propeller control extension bracket attaches to the propeller governor. The propeller control cable had also pulled loose from a swaged point at the control rod and was also separated further aft due to overstress. The housing for the propeller control rod was found securely attached to the engine and the control rod was securely attached to the extension bracket. The propeller governor control arm, which was disconnected from the propeller control cable and rod, was found spring loaded into the high RPM position. Examination of the fractured left propeller bracket assembly was performed by the NTSB Materials Laboratory, Washington, D.C. The bracket assembly was fractured in the area of the outermost eyehole, at the point a bolt passes through the bracket assembly and the propeller governor arm. The fracture surface contained small amounts of dirt, grease, and minor corrosion. The fracture surface features include flat areas that lie on multiple planes separated by ratchet marks, features typically left behind by the propagation of a fatigue crack. The fatigue crack emanated from multiple origins on opposite sides of the bracket. The total area of the fatigue crack occupied approximately 85 percent of the fracture surfaces. The fatigue fractures initiated on the outer edges of the surface and propagated inward toward the center. The remaining 15% of the fracture surface had features consistent with overstress separation. Near the middle of each fatigue region were microfissures suggesting that the crack propagated under high-stress conditions. The NTSB Materials Laboratory also examined the separation point between the left propeller control flexible cable and the rigid rod that connects to the bracket assembly. The cable and the swaged part of the rigid rod were in good condition with no fractures or damage. The Piper PA-31-T2 Pilot Operating Handbook, Section 3, Emergency Procedures, does not contain a procedure for loss of propeller control. Section 3 did contain a procedure for "Over speeding Propeller", which stated that if a propellers speed should exceed 1,976 rpm, to place the power lever of the engine with the over speeding propeller to idle, feather the propeller, place the engine condition lever in the stop position, and complete the engine shutdown procedures. Pilot logbook records show the pilot completed a simulator training course for the accident model airplane about 9 days before the accident and had about 13 flight hours in the Piper PA-31-T2.

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.