Crash of a De Havilland DHC-3 Otter in Lagopede Lake

Date & Time: Apr 19, 2006 at 1115 LT
Type of aircraft:
Operator:
Registration:
C-FKLC
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
255
YOM:
1958
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The Otter registered C-FKLC was on the frozen Lagopede Lake, ready for takeoff, when another Otter operated by Air Saguenay and registered C-FODT landed on the same lake. Upon touchdown, the pilot lost control of the aircraft that collided with the Otter waiting for departure. While the Otter registered C-FODT was slightly damaged, the Otter registered C-FKLC was damaged beyond repair after its right wing was torn off. The pilot, sole on board, was uninjured.

Crash of a Piper PA-31-350 Navajo Chieftain in Powell River: 1 killed

Date & Time: Mar 8, 2006 at 1639 LT
Operator:
Registration:
C-GNAY
Flight Type:
Survivors:
Yes
Schedule:
Vancouver – Powell River
MSN:
31-8052095
YOM:
1980
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
1200
Copilot / Total flying hours:
500
Circumstances:
The aircraft departed from its home base at Vancouver, British Columbia, with two crew members on board. The aircraft was being repositioned to Powell River (a 30-minute flight) to commence a freight collection route. On arriving at Powell River, the crew joined the circuit straight-in to a right downwind for a visual approach to Runway 09. A weather system was passing through the area at the same time and the actual local winds were shifting from light southwesterly to gusty conditions (11 to 37 knots) from the northwest. The aircraft was lower and faster than normal during final approach, and it was not aligned with the runway. The crew completed an overshoot and set up for a second approach to the same runway. On the second approach, at about 1639 Pacific standard time, the aircraft touched down at least halfway down the wet runway and began to hydroplane. At some point after the touchdown, engine power was added in an unsuccessful attempt to abort the landing and carry out an overshoot. The aircraft overran the end of the runway and crashed into an unprepared area within the airport property. The pilot-in-command suffered serious injuries and the first officer was fatally injured. A local resident called 911 and reported the accident shortly after it occurred. The pilot-in-command was attended by paramedics and eventually removed from the wreckage with the assistance of local firefighters. The aircraft was destroyed, but there was no fire. The ELT (emergency locator transmitter) was automatically activated, but the signal was weak and was not detected by the search and rescue satellite.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The downwind condition on approach contributed to the aircraft landing long and with a high ground speed. This, in combination with hydroplaning, prevented the crew from stopping the aircraft in the runway length remaining.
2. When the decision to abort the landing was made, there was insufficient distance remaining for the aircraft to accelerate to a sufficient airspeed to lift off.
3. The overrun area for Runway 09 complied with regulatory standards, but the obstacles and terrain contour beyond the overrun area contributed to the fatality, the severity of injuries, and damage to the aircraft.
Finding as to Risk:
1. Alert Service Bulletin A25-1124A (dated 01 June 2000), which recommended replacing the inertia reel aluminum shaft with a steel shaft, was not completed, thus resulting in the risk of failure increasing over time.
Other Findings:
1. The weather station at the Powell River Airport does not have any air–ground communication capability with which to pass the flight crew timely wind updates.
2. The decision to make a second approach was consistent with normal industry practice, in that the crew could continue with the intent to land while maintaining the option to break off the approach if they assessed that the conditions were becoming unsafe.
Final Report:

Crash of a Cessna 208B Grand Caravan near Port Alberni: 3 killed

Date & Time: Jan 21, 2006 at 1420 LT
Type of aircraft:
Operator:
Registration:
C-GRXZ
Flight Phase:
Survivors:
Yes
Schedule:
Tofino – Vancouver
MSN:
208B-0469
YOM:
1995
Flight number:
RXX604
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
7
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
2480
Captain / Total hours on type:
750.00
Circumstances:
The Cessna 208B aircraft (registration C-GRXZ, serial number 208B0469) was en route at 9000 feet above sea level, from Tofino, British Columbia, to Vancouver International Airport, British Columbia, when the engine failed. The pilot began a glide in the direction of the Port Alberni Regional Airport before attempting an emergency landing on a logging road. The aircraft struck trees during a steep right-hand turn and crashed. The accident occurred at about 1420 Pacific standard time, approximately 11 nm south-southeast of the Port Alberni Regional Airport. Five passengers survived with serious injuries; the pilot and the other two passengers were fatally injured.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The engine lost power when a compressor turbine blade failed as a result of the overstress extension of a fatigue-generated crack. The fracture initiated at a metallurgical anomaly in the parent blade material and progressed, eventually resulting in blade failure due to overstress rupture.
2. The combination of aircraft position at the time of the engine failure, the lack of equipment enabling the pilot to locate and identify high terrain, and the resultant manoeuvring required to avoid entering instrument flight conditions likely prevented the pilot from attempting to glide to the nearest airfield.
Findings as to Risk:
1. Single-engine instrument flight rules (SEIFR) operations in designated mountainous regions have unique obstacle risks in the event of an engine failure. Canadian equipment requirements for such operations do not currently include independent terrain mapping, such as terrain awareness and warning systems (TAWS).
2. Airline operators are not currently required to conduct any additional route evaluation or structuring to ensure that the risk of an off-field landing is minimized during SEIFR operations.
3. Pilots involved in commercial SEIFR operations do not receive training in how to conduct a forced landing under instrument flight conditions; such training would likely improve a pilotís ability to respond to an engine failure when operating in instrument meteorological conditions (IMC).
4. Mean time between failure (MTBF) calculations do not take into account In Flight Shut Downs (IFSDs) not directly attributable to the engine itself; it may be more appropriate to monitor all IFSD events.
5. The design of the Cessna 208B Caravan fuel shutoff valves increases the risk that the valves will open on impact, allowing fuel spillage and increasing the potential for fire.
Other Finding:
1. Sonicblue Airways was not providing downloaded engine parameter data for engine condition trend monitoring (ECTM) evaluation at appropriate intervals.
Final Report:

Crash of a Piper PA-31-310 Navajo in Wetaskiwin

Date & Time: Jan 11, 2006 at 2045 LT
Type of aircraft:
Registration:
C-FBBC
Flight Type:
Survivors:
Yes
Schedule:
Fort Vermilion – Wetaskiwin
MSN:
31-48
YOM:
1968
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft was landing on runway 30 at Wetaskiwin Airport following an IFR mail flight from Fort Vermilion. During the landing, the crew lost sight of the runway in a thin layer of dense fog that covered the airport. They aborted the landing, and the aircraft settled into a field about ½ mile northwest of the airport. Both pilots sustained serious injuries and the aircraft was damaged beyond repair. The flight crew used a cell phone to call for help. The emergency locator transmitter (ELT) activated during impact.

Crash of a Douglas C-54G-15-DO Skymaster in Norman Wells

Date & Time: Jan 5, 2006 at 1704 LT
Type of aircraft:
Operator:
Registration:
C-GXKN
Flight Type:
Survivors:
Yes
Schedule:
Norman Wells – Yellowknife
MSN:
36090
YOM:
1946
Flight number:
BFL1405
Country:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The Buffalo Airways Limited Douglas C-54G-DC (DC-4), registration C-GXKN, serial number 36090, departed from Norman Wells, Northwest Territories, at 1749 mountain standard time for a visual flight rules flight to Yellowknife, Northwest Territories, with a crew of four and 2000 pounds of cargo. While climbing through an altitude of approximately 3500 feet above sea level, the crew experienced a failure of the number 2 engine and a nacelle fire. The crew carried out the Engine Fire Checklist, which included discharging the fire bottles and feathering the number 2 propeller. The fire continued unabated. During this period, an uncommanded feathering of the number 1 propeller and an uncommanded extension of the main landing gear occurred. The crew planned for an emergency off-field landing, but during the descent to the landing area, the fuel selector was turned off as part of the Engine Securing Checklist, and the fire self-extinguished. A decision was made to return to the Norman Wells Airport where a successful two-engine landing was completed at 1804 mountain standard time. The aircraft sustained substantial fire damage, but there were no injuries to the four crew members on board.
Probable cause:
Findings as to Causes and Contributing Factors:
1. Airworthiness Directive AD 48-12-01 mandates the replacement of the potentially hazardous fuel line, but the line had not been replaced on this aircraft.
2. A fuel leak from the main fuel inlet line in the engine compartment of this cargo DC-4 caused an in-flight fire that spread into the nacelle and wing.
3. The fuel-fed fire burned for an extended period of time because turning the fuel selector off is not required as part of the primary Engine Fire Checklist.
Final Report:

Crash of a Beechcraft A100 King Air in La Ronge

Date & Time: Dec 30, 2005 at 1500 LT
Type of aircraft:
Operator:
Registration:
C-GAPK
Flight Type:
Survivors:
Yes
Schedule:
Pinehouse Lake – La Ronge
MSN:
B-198
YOM:
1974
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
A Beechcraft A100 King Air, C-GAPK was inbound to La Ronge Airport, SK (YVC), from Pinehouse Lake on a medevac flight. On descent into La Ronge the crew noticed ice building on the wing leading edges. At approximately 6 miles back on final the crew operated the wing de-ice boots, however a substantial amount of residual ice remained after application of the boots. It was reported that in the landing flare at about 100 knots, the aircraft experienced an ice-induced stall from an altitude of about 20 feet followed by a hard landing. The right wing and nacelle buckled forward and downward from the landing impact forces to the extent that the right propeller struck the runway surface while the aircraft was taxiing off the runway.

Crash of a Mitsubishi MU-2B-36 Marquise in Terrace: 2 killed

Date & Time: Dec 20, 2005 at 1834 LT
Type of aircraft:
Operator:
Registration:
C-FTWO
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Terrace – Vancouver
MSN:
672
YOM:
1975
Flight number:
FCV831
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
2111
Captain / Total hours on type:
655.00
Copilot / Total flying hours:
2000
Copilot / Total hours on type:
500
Circumstances:
At 1834 Pacific standard time, the Nav Air Charter Inc. Mitsubishi MU-2B-36 aircraft (registration C-FTWO, serial number 672) took off from Runway 15 at the Terrace Airport for a courier flight to Vancouver, British Columbia. The left engine lost power shortly after take-off. The aircraft descended, with a slight left bank, into trees and crashed about 1600 feet east of the departure end of Runway 15 on a heading of 072° magnetic. The aircraft was destroyed by the impact and a post-crash fire, and the two pilots were fatally injured.
Probable cause:
Findings as to Causes and Contributing Factors:
1. During the take-off, the left engine combustion chamber plenum split open due to a fatigue crack. The rupture was so extensive that the engine flamed out.
2. The crew did not feather the left engine or retract the flaps, and the aircraft entered a moderate left-hand turn after take-off; the resulting drag caused the aircraft to descend until it contacted trees.
3. The first officer’s flying skills may have been challenged during the handling of the engine failure, and the checklist was conducted out of sequence, suggesting that there may have been uncertainty in the cockpit. A contributing factor may have been the captain’s unfamiliarity with handling an emergency from the right seat.
4. The use of flap 20 for take-off, although in accordance with company policy, contributed to the difficulty in handling the aircraft during the emergency.
Findings as to Risk:
1. The TPE331 series engine plenum is prone to developing cracks at bosses, particularly in areas where two bosses are in close proximity and a reinforcing weld has been made. Cracks that develop in this area cannot necessarily be detected by visual inspections or even by fluorescent dye-penetrant inspections (FPIs).
2. Because the wing was wet and the air temperature was at 0°C, it is possible that ice may have formed on top of the wing during the take-off, degrading the wing’s ability to generate lift.
3. Being required to conduct only flap 20 take-offs increases the risk of an accident in the event of an engine problem immediately after take-off.
Other Finding:
1. The plenum manufactured with a single machined casting, incorporating the P3 and bleed air bosses, is an improvement over the non-single casting boss plenum; however, cracks may still develop at bosses elsewhere on the plenum.
Final Report:

Crash of a Cessna 208B Super Cargomaster in Winnipeg: 1 killed

Date & Time: Oct 6, 2005 at 0543 LT
Type of aircraft:
Operator:
Registration:
C-FEXS
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Winnipeg – Thunder Bay
MSN:
208B-0542
YOM:
1996
Flight number:
FDX8060
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
4570
Captain / Total hours on type:
1500.00
Aircraft flight hours:
6724
Circumstances:
On the day before the occurrence, the accident aircraft arrived in Winnipeg, Manitoba, on a flight from Thunder Bay, Ontario. The aircraft was parked in a heated hangar overnight and was pulled outside at about 0410 central daylight time. The pilot reviewed the weather information and completed planning for the flight, which was estimated to take two hours and six minutes. The aircraft was refuelled and taxied to Apron V at the Winnipeg International Airport, where it was loaded with cargo. After loading was complete, the pilot obtained an instrument flight rules (IFR) clearance for the flight to Thunder Bay, taxied to Runway 36, received take-off clearance, and departed. The aircraft climbed on runway heading for about one minute to an altitude of 1300 feet above sea level (asl), 500 feet above ground level (agl). The flight was cleared to 9000 feet asl direct to Thunder Bay, and the pilot turned on course. The aircraft continued to climb, reaching a maximum altitude of 2400 feet asl about 2.5 minutes after take-off. The aircraft then started a gradual descent averaging about 400 feet per minute (fpm) until it descended below radar coverage. The accident occurred during hours of darkness at 0543. The Winnipeg Fire Paramedic Service were notified and responded from a nearby station.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The aircraft departed at a weight exceeding the maximum take-off weight and the maximum weight for operation in icing conditions.
2. After departure from Winnipeg, the aircraft encountered in-flight icing conditions in which the aircraftís performance deteriorated until the aircraft was unable to maintain altitude.
3. During the attempt to return to the Winnipeg International Airport, the pilot lost control of the aircraft, likely with little or no warning, at an altitude from which recovery was not possible.
Findings as to Risk:
1. Aviation weather forecasts incorporate generic icing forecasts that may not accurately predict the effects of icing conditions on particular aircraft. As a result, specific aircraft types may experience more significant detrimental effects from icing than forecasts indicate.
2. Bulk loading prevented determining the cargo weight in each zone, resulting in a risk that the individual zone weight limits could have been exceeded.
3. The aircraftís centre of gravity (CG) could not be accurately determined, and may have been in the extrapolated shaded warning area on the CG limit chart. Although it was determined that the CG was likely forward of the maximum allowable aft CG, bulk loading increased the risk that the CG could have exceeded the maximum allowable aft CG.
4. The incorrect tare weight on the Toronto cargo container presented a risk that other aircraft carrying cargo from that container could have been inadvertently overloaded.
Other Findings:
1. The pilotís weather information package was incomplete and had to be updated by a telephone briefing.
2. The operatorís pilots were not pressured to avoid using aircraft de-icing facilities or to depart with aircraft unserviceabilities.
3. The aircraft departed Winnipeg without significant contamination of its critical surfaces.
4. The biological material on board the aircraft was disposed of after the accident, with no indication that any of the material had been released into the ground or the atmosphere.
5. The fact that the aircraft was not equipped with flight data recorder or cockpit voice recorder equipment limited the information available for the occurrence investigation and the scope of the investigation.
Final Report:

Crash of a De Havilland DHC-2 Beaver near Elross Lake: 1 killed

Date & Time: Sep 1, 2005 at 1630 LT
Type of aircraft:
Operator:
Registration:
C-FODG
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Pons Camp - Squaw Lake
MSN:
205
YOM:
1952
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
2550
Captain / Total hours on type:
1700.00
Aircraft flight hours:
20900
Circumstances:
The float-equipped de Havilland DHC-2 Beaver (registration C-FODG, serial number 205) departed the outfitter base camp at Squaw Lake, Quebec, at 0925 eastern daylight time, with a passenger and a few supplies on board, for a round-trip visual flight rules (VFR) flight to two wilderness camps, Camp 2 and Camp Pons. The weather in Squaw Lake was suitable for visual flight at the time of take-off but was forecast to deteriorate later in the day. The pilot completed the flights to the two camps and on the way back to Squaw Lake, the weather forced the pilot to make a precautionary landing on Elross Lake, 15 nautical miles (nm) northwest of Squaw Lake. At 1630, he reported to the company via high frequency (HF) radio that he intended to take off from Elross Lake, as there seemed to be a break in the weather. Rescue efforts were initiated in the evening when the aircraft did not arrive at the base camp. The aircraft was located at 1230 the following day, 4 nm from Elross Lake. The aircraft was destroyed by a post-impact fire. The pilot sustained fatal injuries.
Probable cause:
Finding as to Causes and Contributing Factors:
1. The pilot attempted to cross the mountain ridge in adverse weather, and the aircraft stalled at an altitude from which recovery was not possible. Loss of visual references, strong updrafts, moderate to severe turbulence and possible wind shear likely contributed to the onset of the aerodynamic stall.
Other Finding:
1. Had this been a survivable accident, rescue efforts may have been compromised by a lack of communication. A satellite phone provides a more effective means of communication when in remote areas.
Final Report: