Crash of a Casa 212 Aviocar in Saskatoon: 1 killed

Date & Time: Apr 1, 2011 at 1830 LT
Type of aircraft:
Operator:
Registration:
C-FDKM
Survivors:
Yes
Site:
Schedule:
Saskatoon - Saskatoon
MSN:
196
YOM:
1981
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
7400
Captain / Total hours on type:
75.00
Copilot / Total flying hours:
7800
Copilot / Total hours on type:
1800
Aircraft flight hours:
21292
Circumstances:
At 1503 Central Standard Time, the Construcciones Aeronauticas SA (CASA) C-212-CC40 (registration C-FDKM, serial number 196) operated by Fugro Aviation Canada Ltd., departed from Saskatoon/Diefenbaker International Airport, Saskatchewan, under visual flight rules for a geophysical survey flight to the east of Saskatoon. On board were 2 pilots and a survey equipment operator. At about 1814, the right engine lost power. The crew shut it down, carried out checklist procedures, and commenced an approach for Runway 27. When the flight was 3.5 nautical miles from the runway on final approach, the left engine lost power. The crew carried out a forced landing adjacent to Wanuskewin Road in Saskatoon. The aircraft impacted a concrete roadway noise abatement wall and was destroyed. The survey equipment operator sustained fatal injuries, the first officer sustained serious injuries, and the captain sustained minor injuries. No ELT signal was received.
Probable cause:
Conclusions
Findings as to Causes and Contributing Factors:
1. The right engine lost power when the intermediate spur gear on the torque sensor shaft failed. This resulted in loss of drive to the high-pressure engine-driven pump, fuel starvation, and immediate engine stoppage.
2. The ability of the left-hand No. 2 ejector pump to deliver fuel to the collector tank was compromised by foreign object debris (FOD) in the ejector pump nozzle.
3. When the fuel level in the left collector tank decreased, the left fuel level warning light likely illuminated but was not noticed by the crew.
4. The pilots did not execute the fuel level warning checklist because they did not perceive the illumination of the fuel level left tank warning light. Consequently, the fuel crossfeed valve remained closed and fuel from only the left wing was being supplied to the left engine.
5. The left engine flamed out as a result of depletion of the collector tank and fuel starvation, and the crew had to make a forced landing resulting in an impact with a concrete noise abatement wall.
Findings as to Risk:
1. Depending on the combination of fuel level and bank angle in single-engine uncoordinated flight, the ejector pump system may not have the delivery capacity, when the No. 1 ejector inlet is exposed, to prevent eventual depletion of the collector tank when the engine is operated at full power. Depletion of the collector tank will result in engine power loss.
2. The master caution annunciator does not flash; this leads to a risk that the the crew may not notice the illumination of an annunciator panel segment, in turn increasing the risk of them not taking action to correct the condition which activated the master caution.
3. When cockpit voice and flight data recordings are not available to an investigation, this may preclude the identification and communication of safety deficiencies to advance transportation safety.
4. Because the inlets of the ejector pumps are unscreened, there is a risk that FOD in the fuel tank may become lodged in an ejector nozzle and result in a decrease in the fuel delivery rate to the collector tank.
Other Findings:
1. The crew’s decision not to recover or jettison the birds immediately resulted in operation for an extended period with minimal climb performance.
2. The composition and origin of the FOD, as well as how or when it had been introduced into the fuel tank, could not be determined.
3. The SkyTrac system provided timely position information that would have assisted search and rescue personnel if position data had been required.
4. Saskatoon police, firefighters, and paramedics responded rapidly to the accident and provided effective assistance to the survivors.
Final Report:

Crash of a Piper PA-46-350P Malibu Mirage in Monroe: 3 killed

Date & Time: Mar 29, 2011 at 1604 LT
Registration:
N619VH
Flight Type:
Survivors:
No
Schedule:
Bedford – Monroe
MSN:
46-36402
YOM:
2006
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
1600
Aircraft flight hours:
851
Circumstances:
A witness reported and radar data showed the airplane approaching the runway at a higher‐than‐normal speed. As the airplane leveled low over the runway, the propeller began striking the runway surface. The damage from repetitive propeller strikes resulted in a loss of the thrust and airspeed necessary for flight. The airplane impacted the ground and subsequently caught fire. The postaccident examination of the wreckage confirmed that the airplane was configured with the landing gear and flaps retracted. No mechanical anomalies were observed that would have precluded normal operation of the airplane. Weight and balance estimates of the airplane indicated that the pilot was operating the airplane outside of its certified weight and center of gravity limits. Forensic toxicology performed on the pilot showed the presence of Hydrocodone and Dihydrocodeine, indicative of the pilot using disqualifying sedating cough or pain medications. These medications can impair performance in high workload environments. The level of medication found in the pilot’s blood at the time of the accident could not be determined. Additionally, Nortriptyline was detected in the pilot’s tissues. While the medications could have had degrading effects on the pilot’s performance, the investigation was not able to determine what role they may have played in the accident sequence.
Probable cause:
The pilot's demonstration of poor judgment by attempting a high‐speed pass several feet above the runway and his subsequent failure to maintain clearance from the runway.
Final Report:

Crash of a Cessna 425 Conquest I in Canadian

Date & Time: Mar 28, 2011 at 0825 LT
Type of aircraft:
Operator:
Registration:
N410VE
Flight Type:
Survivors:
Yes
Schedule:
Grand Junction - Canadian
MSN:
425-0097
YOM:
1981
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
22500
Captain / Total hours on type:
1000.00
Aircraft flight hours:
7412
Circumstances:
While on a straight-in global-positioning-system approach, the airplane broke out of the clouds directly over the end of the runway. The pilot then remained clear of the clouds and executed a no-flap circling approach to the opposite direction runway. The pilot said that his airspeed was high when he touched down. The landing was hard, and the right main landing gear tire blew out, the airplane departed the runway to the left, and the left main landing gear collapsed. No preaccident mechanical malfunctions or failures were found that would have precluded normal operation.
Probable cause:
The pilot’s continuation of the approach with excessive airspeed, which resulted in a hard landing and a loss of directional control.
Final Report:

Crash of an Antonov AN-12BP in Pointe-Noire: 23 killed

Date & Time: Mar 21, 2011 at 1530 LT
Type of aircraft:
Operator:
Registration:
TN-AGK
Flight Type:
Survivors:
No
Site:
Schedule:
Brazzaville - Pointe-Noire
MSN:
40 20 06
YOM:
1963
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
23
Circumstances:
The four engine airplane departed Brazzaville-Maya Maya Airport on a cargo service to Pointe-Noire, carrying five passengers, four crew members and a load of 750 kilos of meat. On final approach to Pointe-Noire Airport runway 17, the aircraft rolled to the right, got inverted and crashed in the residential area of Mvoumvou located 4 kilometers short of runway. The aircraft was totally destroyed as well as several houses. All nine occupants and 14 people on the ground were killed.
Probable cause:
It is believed that the loss of control on final approach was the consequence of the failure of both right engines n°3 and 4.

Crash of a De Havilland DHC-6 Twin Otter 100 in Clayton: 2 killed

Date & Time: Mar 8, 2011 at 1140 LT
Operator:
Registration:
N157KM
Flight Type:
Survivors:
No
Schedule:
Clayton - Clayton
MSN:
57
YOM:
1967
Location:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
1255
Captain / Total hours on type:
492.00
Aircraft flight hours:
16541
Aircraft flight cycles:
20927
Circumstances:
The airplane had not been flown for about 5 months and the purpose of the accident flight was a maintenance test flight after both engines had been replaced with higher horsepower models. Witnesses observed the airplane depart and complete two uneventful touch-and-go landings. The airplane was then observed to be struggling to gain altitude and airspeed while maneuvering in the traffic pattern. One witness, who was an aircraft mechanic, reported that he observed the airplane yawing to the left and heard noises associated with propeller pitch changes, which he believed were consistent with the "Beta" range. The airplane stalled and impacted trees in a wooded marsh area, about 1 mile from the airport. It came to rest about 80-degrees vertically. Examination of the wreckage did not reveal any preimpact malfunctions; however, the lack of flight recorders and the condition of the wreckage precluded the gathering of additional relevant information. Damage observed to both engines and both propellers revealed they were likely operating at symmetrical power settings and blade angles at the time of the impact, with any differences in scoring signatures likely the result of impact damage. The reason for the yawing and the noise associated with propeller pitch changes that were reported prior to the stall could not be determined.
Probable cause:
The pilot did not maintain airspeed while maneuvering, which resulted in an aerodynamic stall.
Final Report:

Crash of a De Havilland DHC-8-106 in Nuuk

Date & Time: Mar 4, 2011 at 1609 LT
Operator:
Registration:
TF-JMB
Survivors:
Yes
Schedule:
Reykjavik - Kulusuk - Nuuk
MSN:
337
YOM:
1992
Flight number:
FXI223
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
31
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
8163
Captain / Total hours on type:
44.00
Copilot / Total flying hours:
4567
Copilot / Total hours on type:
1130
Aircraft flight hours:
32336
Aircraft flight cycles:
35300
Circumstances:
The flight crew got visual contact with the runway at BGGH and decided to deviate to the right (west) of the offset localizer (LLZ) to runway 23. The flight continued towards the runway from a position right of the extended runway centerline. As the aircraft approached runway 23, it was still in the final right turn over the landing threshold. The aircraft touched down on runway 23 between the runway threshold and the touchdown zone and to the left of the runway centerline. The right main landing gear (MLG) shock strut fuse pin sheared leading to a right MLG collapse. The aircraft skidded down the runway and departed the runway to the right. Neither passengers nor crew suffered any injuries. The aircraft was substantially damaged. The accident occurred in daylight under visual meteorological conditions (VMC).
Probable cause:
Findings:
- The licenses and qualifications held by the flight crew, flight and duty times, the documented technical status of the aircraft and the aircraft mass and balance had no influence on the sequence of events
- The flight crew planned the flight from BGKK to BGGH with the destination alternate BGSF
- The latest BGGH TAF before departure from BGKK indicated marginal weather conditions (strong winds, low visibility and low cloud base) for a successful approach and landing at BGGH
- The forecasted weather conditions at the expected approach time at BGGH were below preplanning minima (use of two destination alternate aerodromes)
- The actual weather conditions at BGGH and enroute weather briefings were equivalent to the forecasted weather conditions
- With reference to the operator’s aerodrome and procedure briefing and the latest reported wind conditions from Nuuk AFIS before landing, a landing was prohibited
- Strong winds and moderate to severe orographic turbulence from the surrounding mountainous terrain increased the flight crew load
- On approach, the flight crew had difficulties of maintaining stabilized approach parameters
- The flight crew most likely suffered from task saturation and information overload
- No flight crew call outs on divergence from the operator’s stabilized approach policy were made
- An optimum crew resource management was not present
- Important low altitude stabilized approach parameters like airspeed, bank angle and runway alignment were not sufficiently corrected
- The flight crew was solely focused on landing and task saturation mentally blocked a decision of going around
- A divergence from the operator’s stabilized approach policy caused an unstabilized approach and a hard landing leading to an excess load of the right MLG at touchdown
- The right MLG fuse pin sheared as a result of overload
Factors:
- A divergence from the operator’s stabilized approach policy caused an unstabilized approach and a hard landing leading to an excess load of the right MLG at touchdown
- The right MLG fuse pin sheared as a result of stress
Summary:
Adverse wind and turbulence conditions at BGGH led to flight crew task saturation on final approach and a breakdown of optimum cockpit resource management (CRM) resulting in a divergence from the operator’s stabilized approach policy.
The divergence from the operator’s stabilized approach policy caused an unstabilized approach and a hard landing leading to an excess load of the right MLG at touchdown. According to its design, the right MLG fuse pin sheared as a result of stress.
Final Report:

Crash of a Swearingen SA227AC Metro III in Oslo

Date & Time: Mar 2, 2011 at 0905 LT
Type of aircraft:
Operator:
Registration:
OY-NPB
Survivors:
Yes
Schedule:
Ørland - Oslo
MSN:
AC-420
YOM:
1981
Flight number:
NFA990
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
9
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5187
Captain / Total hours on type:
2537.00
Copilot / Total flying hours:
2398
Copilot / Total hours on type:
1278
Aircraft flight hours:
24833
Aircraft flight cycles:
29491
Circumstances:
After touchdown on runway 19R at Oslo-Gardermoen Airport, while decelerating to a speed of 60 knots, the aircraft deviated to the right. At a speed of 40 knots, it impacted a snow berm then rotated to the right and came to rest in deep snow with its both propellers and the nose damaged. All 11 occupants evacuated safely while the aircraft was considered as damaged beyond repair.
Probable cause:
Comprehensive technical examination of the nose wheel steering on OY-NPB uncovered no single causal factor, but some indications of unsatisfactory maintenance. Irregularities that alone or in combination could have caused a temporary fault with the steering were present. The Accident Investigation Board believes that a temporary fault caused the nose wheel to unintentionally lock itself in a position towards the right. No other defects or irregularities that could explain why the aircraft veered off the runway were found. The AIBN reported that the same fault had occurred 6 days earlier as well, during that encounter the captain managed to disconnect nose wheel steering quickly enough to regain control. Maintenance could not replace the fault and the aircraft was released to service.
Final Report:

Crash of a Swearingen SA227DC Metro III in La Paz

Date & Time: Feb 27, 2011 at 1510 LT
Type of aircraft:
Operator:
Registration:
CP-2473
Survivors:
Yes
Schedule:
San Borja - Rurrenabaque
MSN:
DC-842B
YOM:
1993
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On approach to Rurrenabaque, following an uneventful flight from San Borja, the crew encountered problems with the landing gear which failed to lock down. As all three green lights were not ON on the cockpit panel, the Captain decided to divert to La Paz-El Alto Airport where rescue teams were alerted. After touchdown, the left main gear collapsed. The aircraft veered off runway to the left before coming to rest in a grassy area. All eight occupants escaped uninjured and the aircraft was damaged beyond repair.

Crash of a Rockwell Shrike Commander 500S off Horn Island: 1 killed

Date & Time: Feb 24, 2011 at 0800 LT
Operator:
Registration:
VH-WZU
Flight Type:
Survivors:
No
Schedule:
Cairns - Horn Island
MSN:
3060
YOM:
1970
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
4154
Captain / Total hours on type:
209.00
Aircraft flight hours:
17545
Circumstances:
At 0445 Eastern Standard Time on 24 February 2011, the pilot of an Aero Commander 500S, registered VH-WZU, commenced a freight charter flight from Cairns to Horn Island, Queensland under the instrument flight rules. The aircraft arrived in the Horn Island area at about 0720 and the pilot advised air traffic control that he intended holding east of the island due to low cloud and rain. At about 0750 he advised pilots in the area that he was north of Horn Island and was intending to commence a visual approach. When the aircraft did not arrive a search was commenced but the pilot and aircraft were not found. On about 10 October 2011, the wreckage was located on the seabed about 26 km north-north-west of Horn Island.
Probable cause:
The ATSB found that the aircraft had not broken up in flight and that it impacted the water at a relatively low speed and a near wings-level attitude, consistent with it being under control at impact. It is likely that the pilot encountered rain and reduced visibility when manoeuvring to commence a visual approach. However, there was insufficient evidence available to determine why the aircraft impacted the water.
Several aspects of the flight increased risk. The pilot had less than 4 hours sleep during the night before the flight and the operator did not have any procedures or guidance in place to minimize the fatigue risk associated with early starts. In addition, the pilot, who was also the operator’s chief pilot, had either not met the recency requirements or did not have an endorsement to conduct the types of instrument approaches available at Horn Island and several other locations frequently used by the operator.
Final Report:

Crash of a Cessna 421C Golden III Eagle in Connersville: 1 killed

Date & Time: Feb 23, 2011 at 2002 LT
Operator:
Registration:
N3875C
Flight Type:
Survivors:
No
Schedule:
Indianapolis - Connersville
MSN:
421C-0127
YOM:
1976
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
1360
Captain / Total hours on type:
558.00
Aircraft flight hours:
4158
Circumstances:
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.
Probable cause:
The pilot did not maintain control of the airplane while making a low-altitude turn during dark night conditions.
Final Report: