Crash of a Swearingen SA227AC Metro III in La Ronge

Date & Time: Sep 21, 2004 at 1410 LT
Type of aircraft:
Operator:
Registration:
C-FIPW
Survivors:
Yes
Schedule:
Stony Rapids - La Ronge
MSN:
AC-524
YOM:
1982
Flight number:
KA1501
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
9
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
A Northern Dene Airways Ltd. Metro III (registration C-FIPW, serial number AC524), operating as Norcanair Flight KA1051, departed Stony Rapids, Saskatchewan, with two crew members and nine passengers on a day, visual flight rules flight to La Ronge, Saskatchewan. On arrival in La Ronge, at approximately 1410 central standard time, the crew completed the approach and landing checklists and confirmed the gear-down indication. The aircraft was landed in a crosswind on Runway 18 and touched down firmly, approximately 1000 feet from the threshold. On touchdown, the left wing dropped and the propeller made contact with the runway. The aircraft veered to the left side of the runway, despite full rudder and aileron deflection. The crew applied maximum right braking and shut down both engines. The aircraft departed the runway and travelled approximately 200 feet through the infield before the nose and right main gear were torn rearwards; the left gear collapsed into the wheel well. The aircraft slid on its belly before coming to rest approximately 300 feet off the side of the runway. Three of the passengers suffered minor injuries from the sudden stop associated with the final collapsing of the landing gear; the other passengers and the pilots were not injured.
Probable cause:
Findings as to Causes and Contributing Factors:
1. An incorrect roller of a smaller diameter and type was installed on the left main landing gear outboard bellcrank assembly, contrary to company and industry practice.
2. The smaller diameter roller reduced the required rigging tolerances for the bellcrank-to-cam assembly in the down-and-locked position and allowed the roller to eventually move beyond the cam cutout position, resulting in the collapse of the left landing gear.
3. A rigging check was not carried out after the replacement of the bellcrank roller. Such a check should have revealed that neither the inboard nor outboard bellcrank assembly met the minimum rigging requirements for proper engagement with the positioning cam.
Final Report:

Crash of a Swearingen SA227AC Metro III in George

Date & Time: Sep 10, 2004 at 0545 LT
Type of aircraft:
Registration:
ZS-OLS
Flight Type:
Survivors:
Yes
Schedule:
Bloemfontein – George
MSN:
AC-748B
YOM:
1989
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2465
Captain / Total hours on type:
657.00
Aircraft flight hours:
8760
Circumstances:
The aircraft was on a Domestic Charter flight (IFR) from Bloemfontein Aerodrome to George Aerodrome when the crew elected to execute an ILS approach for landing onto Runway 11. At 1,000 feet from the threshold of Runway 11 with the undercarriage selected down and at full flaps for landing at an IAS of 120kt when he advised the copilot that was the flying pilot at the time, to continue visually with the approach for Runway 11. Shortly thereafter they heard a loud impact sound and the right hand engine failed. The aircraft suddenly yawed and banked severely to the right and the flying pilot commented that they had experienced a bird strike on the right hand engine. The pilot-in-command immediately took over the controls and attempted to arrest the yaw to the right but the aircraft kept yawing to the right. He then made a blind transmission on frequency 118.9 MHz and called for a go-around. The co-pilot then selected full power on both engines retracted the undercarriage, whilst the pilot-in-command feathered the right-hand propeller. According to the pilot-in-command, the aircraft continued to yaw to the right and with the stall aural warning sounding with a loss of altitude, he pulled the left-hand engine stop and feather control and was committed to execute a forced landing on a cattle farm The pilot-in-command stated that aircraft was approximately just outside the boundary fence. Both wings collided with the gum poles of a telephone and wire fence causing extensive damage to the wings and fuselage under-surface. Both occupants sustained no injuries.
Probable cause:
The aircraft encountered a bird strike on the right-hand engine prior to landing at George Aerodrome. It appears that the cockpit crew did not apply the correct procedures for a go-around when the aircraft yawed Severely to the right. The aircraft failed to climb and a forced landing was executed on a cattle farm.
Final Report:

Crash of a Swearingen SA227AC Metro III in Carepa: 5 killed

Date & Time: May 5, 2004 at 1300 LT
Type of aircraft:
Registration:
HK-4275X
Survivors:
Yes
Schedule:
Bogotá – Carepa
MSN:
AC-676
YOM:
1987
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
5
Aircraft flight hours:
19335
Circumstances:
Following an uneventful flight from Bogotá-El Dorado Airport, the crew started the approach to Carepa-Los Cedros Airport, the copilot was the pilot-in-command. On final approach, the captain took over controls and continued the descent when the GPWS alarm sounded seven times. For unknown reasons, the captain failed to respond to this situation and did not proceed with any corrective actions. On short final, at a height of about 200 feet, one of the engine failed. The crew failed to follow the published procedures, causing the aircraft to stall and to crash about 100 metres short of runway 33. Two passengers were seriously injured while five other occupants were killed.
Probable cause:
The following findings were identified:
- Poor judgement of distance, speed, altitude and the obstacle clearance during the final approach,
- Attempting the operation beyond the experience and the high level of competence required by the crew,
- Encountering unforeseen circumstances exceeded the capacity of the crew,
- Diverting attention on the operation of the aircraft,
- Lack of approved procedures, directives and instructions,
- The absence of CRM procedures and low situational awareness,
- The lack of evasive action when the ground proximity warning system's alarm sounded,
- The sudden loss of power in one of the engines,
- The wrong use of the world's major flight to maintain directional control,
- The activation of the Stall Avoidance System (SAS) on the control column, moving it forward when the plane was at low altitude.

Crash of a Swearingen SA227AC Metro III in Aberdeen

Date & Time: Dec 24, 2002 at 0745 LT
Type of aircraft:
Operator:
Registration:
OY-BPH
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Aberdeen - Aalborg
MSN:
AC-580B
YOM:
1984
Flight number:
NFA924
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4600
Captain / Total hours on type:
2800.00
Circumstances:
At approximately 0630 hrs on 24 December 2002, the pilots arrived by car at Aberdeen Airport. With no requirement for their aircraft to transport mail on this occasion, it was decided to fly directly to their home airport in Denmark. The aircraft had been refuelled the previous day and the total fuel on board of 2,200 lb was sufficient for the flight; with no cargo on board, take-off weight was calculated as 12,000 lb (maximum take-off weight: 16,000 lb). The commander carried out an external inspection on OY-BPH while the co-pilot, who was the designated handling pilot for the flight to Denmark, submitted a flight plan. The weather at 0720 hrs was reported as follows: Surface wind 150°M/ 12 kt; visibility 2,500 metres in mist; cloud scattered 100 feet agl, overcast at 200 feet agl; air temperature +9°C; QNH 994 hPa. The runway was reported as wet and Low Visibility Procedures (LVP) had been in force at Aberdeen since 0633 hrs. OY-BPH, callsign 'Birdie Nine Two Four', was parked on Taxiway Bravo and the crew called for, and were given, start clearance at 0736 hrs by 'Ground Movement Control' on frequency 121.7 MHz. Then, following their after-start checks, the crew were cleared to taxi to 'Whiskey Five' for Runway 16 at 0740 hrs. During taxi, the crew were passed and correctly acknowledged the following clearance: "LEAVE CONTROLLED AIRSPACE CLIMBING FLIGHT LEVEL ONE FIVE FIVE SQUAWK SIX TWO FOUR ZERO". Then, at 0742 hrs as the aircraft approached 'Whiskey Five', the crew were transferred to 'Aberdeen Tower' on frequency 118.1 MHz. On the 'Tower' frequency, they were given line-up clearance for Runway 16. At 0743 hrs, the controller transmitted: "BIRDIE NINE TWO FOUR WITH A LEFT TURN DIRECT KARLI CLEAR TAKE OFF ONE SIX SURFACE WIND ONE SIX ZERO ONE TWO KNOTS". The crew correctly acknowledged this clearance. The controller watched the initial movement of the aircraft along the runway before transferring her attention to another aircraft, which was lining up. Shortly after, at 0746 hrs, she transmitted: "OY-BPH REPORT TURNING LEFT" but received no reply. About this time, a telephone message was received in the 'Tower' from a witness in front of the Terminal Building to the effect that an aircraft appeared to have crashed just south of the airfield. This witness had heard a "change in pitch" from the aircraft but had seen no flames prior to it disappearing from his sight: ATC personnel immediately activated their emergency procedures. For the reduced power take-off roll, with the flaps at ¼, the power was set by the commander. The crew considered that the performance of the aircraft was normal, with no unusual instrument indications. The calculated V1 and VR speeds (co-incident at 100 kt) were achieved and called by the commander and, at VR, the co-pilot rotated the aircraft to a pitch attitude of about 12° to 15° nose-up. As the aircraft left the ground, the co-pilot detected the aircraft 'yawing' to the right; almost immediately, he was also aware of a distinct smell of smoke. He called to the commander that he had an engine failure, called for maximum power and tried to maintain control by corrective aileron and rudder inputs. The commander felt the aircraft roll about 15° to the right and realised that there was a problem with the right (No 2) engine. He reached for both power levers and moved them forward. There were no audio or visual warnings associated with the apparent problem. The commander looked at the EGT gauges with the power levers fully forward and noted that the No 2 engine indicated about 600°C EGT, whereas the left (No 1) engine indicated greater than 650°C EGT (the normal maximum) and that its fuel 'Bypass' light was on. He retarded the No 1 power lever until the 'Bypass' light extinguished and noted the resultant EGT at about 630°C. He did not recall any other abnormal indications on the engine instruments but, later in the investigation, the commander recalled hearing a sound "like a compressor stall from the right engine". About this time, the co-pilot heard the automatic "Bank Angle" voice activate. As the aircraft continued to turn to the right, the co-pilot called that he "couldn't control the aircraft". The commander reached for and pulled No 2 engine 'Stop and Feather Control' but, almost immediately, OY-BPH struck the ground initially with the right wing. The aircraft slid along the surface of a field, through a fence and onto a road, before coming to rest. As it did so, the co-pilot was aware that the aircraft had struck a car, which was now at rest outside the right forward side of the cockpit. The co-pilot saw that the whole of the right wing was on fire and called this to the commander before evacuating out of the left door of the aircraft. As the copilot left, the commander pulled No 1 engine 'Stop and Feather Control' and activated both engine fire extinguishers before leaving the aircraft. Outside OY-BPH, the co-pilot went to the car to check if anyone was still inside; as he did so, he saw someone running away. With the intense fire and the car apparently empty, both pilots moved well away from the aircraft. At 0748 hrs, the co-pilot used his mobile phone to advise ATC of the accident and to request assistance. The local emergency services had been alerted at 0745 hrs by a member of the public, who reported a road accident; by 0753 hrs, the local fire service was on the scene. By 0754 hrs, the first AFS vehicle was on the scene and three further AFS vehicles arrived one minute later. A fifth vehicle arrived at 0800 hrs. The fire was quickly extinguished and the Fire Officer confirmed that all the aircraft and vehicle occupants had been located and that there had been no serious injuries. Following runway and taxiway inspections, the airport was re-opened at 0954 hrs.
Probable cause:
Although the investigation was hampered by the lack of FDR data, which might have provided information on engine handling and behaviour, the available evidence from the crew and the initial examination of the aircraft at the accident site, pointed to a major loss of power in the right engine. As a result of the discovery of dead birds close to the point of lift-off on the runway, and a section of braided wire found near the start of the take-off roll, consideration was given as to whether the these had been factors in the accident. The braided wire was not identified as having originated from OY-BPH. There was conclusive evidence that the left engine, which had continued to run, had ingested parts of birds, but no such evidence was found with the right engine. Nevertheless, the crew were adamant that there was a power loss from the right engine and were not conscious of any power reduction from the left engine. The technical examination of the left engine and its propeller assembly revealed evidence of damage consistent with this unit delivering a high level of power at impact. The examination of the right engine and propeller revealed all damage to be consistent with a low, or no, power condition at impact, consistent with either a genuine loss of power or as a consequence of the commander pulling the 'Stop and Feather' control immediately before impact. However, an exhaustive examination of the right engine revealed no evidence of anything that could have caused a failure. Therefore, the items found on the runway were not considered to have been causal or contributory factors in the accident. The crew's recollection of the event included a low EGT indication, at 600°C. This suggested that either the engine might have flamed out, should they have only momentarily looked at the indication as the engine was cooling down, or that the engine was operating at reduced power for an undetermined reason. Flame out could have occurred due to a number of reasons, including, for example, water contamination of the fuel. However, analysis of the bulk supply samples proved negative and, moreover, there were no reports of contaminated fuel from other operators at Aberdeen Airport. Ingestion of ice or water could also have resulted in a flame-out, although this is considered unlikely due to the conditions not being conducive to the formation of engine icing, the lack of significant standing water on the runway, and the absence of heavy precipitation. However, it could not be completely discounted and, if flame-out had occurred, the non-incorporation of the FAA mandated auto-relight system would have reduced the possibility of an immediate relight. Approximately six months before the accident, the left engine had failed during a landing roll-out whilst the aircraft was being operated in Spain. This failure was never satisfactorily explained although, at one stage, the fuel cut-off valve came under suspicion. The valves were interchanged, according to the records, so that the unit that had been fitted to the left engine was installed on the right engine, at the time of the accident. Whilst a stray electrical signal causing the valve to close would certainly result in the engine flaming out, rumours that such events had occurred were not substantiated by the engine manufacturer. In summary, the left engine experienced a bird strike, but with no apparent power loss, and the extensive technical examination could not identify any reason for a loss of power on the right engine. Although an engine failure during takeoff after V1 is a serious emergency, the aircraft was at a relatively light weight and, even with an such a failure, the crew should have been able to fly OYBPH safely away. However, if other factors had been involved, the margins for safe flight would have become more critical. These other factors could have included incorrect operation of the NTS system and/or a failure of the feathering system on the right engine, a concurrent power loss from the left engine, or the crew not handling the emergency effectively. There is no doubt that the left engine had been producing power at impact, but a definite conclusion could not be made as to the blade pitch angles of the right propeller. From the evidence of the commander and the propeller examination by the manufacturer, it is probable that the right propeller was close to the feather position at ground impact. The functionality of the NTS and feathering system could not be determined but, as noted earlier, the pre-flight NTS check actually only ensured that oil pressure was available for this system, and did not check the operation of the whole system. With the evidence that only the left engine had ingested birds, there was a possibility that the left engine was not producing maximum power, although the crew considered it was operating normally. The commander could remember that he compared the engine EGT indications, once he had pushed both power levers forward, and recalled that the left EGT was indicating greater than 650°C with the 'Bypass' light on. He then retarded the left power lever until the 'Bypass' light went out, following which the EGT indicated about 630°C. This retardation of the power lever was not required, as the function of the 'Bypass' system is to reduce the fuel flow in order to keep the engine parameters within limits. This reported retardation could, however, have resulted in a lower engine power than was possible within the available limits, possibly with an associated reduction in EGT. While it remains a possibility that the left engine may have experienced a transient power reduction as a result of the bird ingestion, it is likely that the commander's action in retarding the left power lever resulted in a more significant reduction of power. To maintain straight flight, following an engine failure, it is vital to apply sufficient corrective rudder input to maintain the wings essentially level and minimise the drag due to sideslip. In the case of OYBPH, there was a constant turn to the right before ground impact. The commander's recollection was that left rudder had been applied by the co-pilot, but not to full deflection. The amount of rudder deflection required depends mainly on the airspeed and the difference in engine power but, with the wings not level, more deflection was obviously required, and was available. Greater use of rudder would have reduced the overall drag of the aircraft, with consequent improvement in the aircraft's performance. Furthermore, following an engine failure, the second segment climb requirement is to climb from 35 feet to 400 feet at V2 with the landing gear selected to up. The commander did not raise the gear because he did not observe a positive rate of climb. However, evidence from the FDR was that a maximum airspeed of 128 kt was achieved and, as this was some 19 kt higher than the V2 speed, it indicated that the aircraft had a capability to climb which was not being used. These last three factors may have combined to reduce the climb capability of the aircraft to zero and, in that situation, the decision to not raise the gear was correct. However, all these factors were influenced by inappropriate crew actions. Although both pilots had flown together before, the lack of adherence to JAR-OPS conversion requirements may have been partly responsible for their actions during the emergency.
Final Report:

Crash of a Swearingen SA227AC Metro III in Hawthorne

Date & Time: Sep 29, 2002 at 0913 LT
Type of aircraft:
Registration:
N343AE
Flight Phase:
Survivors:
Yes
Schedule:
Hawthorne – Grand Canyon
MSN:
AC554
YOM:
1983
Crew on board:
2
Crew fatalities:
Pax on board:
19
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2858
Captain / Total hours on type:
2212.00
Copilot / Total flying hours:
4462
Copilot / Total hours on type:
612
Aircraft flight hours:
30660
Aircraft flight cycles:
44949
Circumstances:
The airplane veered off the runway during a rejected takeoff, overran an airport sign, and impacted a hangar. The captain stated that during the after start checklist he moved the power levers to disengage the start locks on the propellers. Post accident examination found that the left propeller was still in the start lock position, while the right propeller was in the normal operating range. The captain was the pilot flying (PF) and the second-in-command (SIC) was the non flying pilot (NFP). After receiving their clearance, the PF taxied onto the runway and initiated the takeoff sequence. The SIC did not set and monitor the engine power during takeoff, as required by the company procedures. During the takeoff acceleration when the speed was between 40 and 60 knots, the captain released the nose gear steering control switch as the rudder became aerodynamically effective. When the switch was released, the airplane began immediately veering left due to the asymmetrical thrust between the left and right engine propellers. The PIC did not advise the SIC that he had lost directional control and was aborting the takeoff, as required by company procedures. The distance between where the PIC reported that he began the takeoff roll and where the first tire marks became apparent was about 630 feet, and the distance between where the marks first became apparent and where the airplane's left main landing gear tire marks exited the left side of the runway was about 220 feet. Thereafter, marks (depressions in the dirt) were noted for a 108-foot-long distance in the field located adjacent to the runway. Medium intensity tire tread marks were apparent on the parallel taxiway and the adjacent vehicle service road. These tread marks, over a 332-foot-long distance, led directly to progressively more pronounced marks and rubber transfer, and to the accident airplane's landing gear tires. Based on an examination of tire tracks and skid marks, the PIC did not reject the takeoff until the airplane approached the runway's edge, and was continuing its divergent track away from the runway's centerline. The airplane rolled on the runway through the dirt median and across a taxiway for 850 feet prior to the PIC applying moderate brakes, and evidence of heavier brake application was apparent only a few hundred feet from the impacted hangar. No evidence of preimpact mechanical failures or malfunctions was found with the propeller assemblies, nose wheel steering mechanism, or brakes.
Probable cause:
The pilot-in-command's failure to maintain directional control during the rejected takeoff. The loss of directional control was caused by the crew's failure to follow prescribed pre takeoff and takeoff checklist procedures to ensure the both propellers were out of the start locks. Contributing factors were the failure of the crew to follow normal company procedures during takeoff, the failure of the flightcrew to recognize an abnormal propeller condition during takeoff, and a lack of crew coordination in performing a rejected takeoff.
Final Report: