Crash of a De Havilland DHC-2 Beaver in Crossroads Lake

Date & Time: Jul 14, 2008 at 0816 LT
Type of aircraft:
Operator:
Registration:
C-FPQC
Flight Phase:
Survivors:
Yes
Schedule:
Crossroads Lake - Schefferville
MSN:
873
YOM:
1956
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7885
Captain / Total hours on type:
1000.00
Circumstances:
The Labrador Air Safari (1984) Inc. float-equipped de Havilland DHC-2 (Beaver) aircraft (registration C-FPQC, serial number 873) departed Crossroads Lake, Newfoundland and Labrador, at approximately 0813 Atlantic daylight time with the pilot and six passengers on board. About three minutes after take-off as the aircraft continued in the climb-out, the engine failed abruptly. When the engine failed, the aircraft was about 350 feet above ground with a ground speed of about 85 miles per hour. The pilot initiated a left turn and, shortly after, the aircraft crashed in a bog. The pilot and four of the occupants were seriously injured; two occupants received minor injuries. The aircraft was substantially damaged, but there was no post-impact fire. The impact forces activated the onboard emergency locator transmitter.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The linkpin plugs had not been installed in the recently overhauled engine, causing inadequate lubrication to the linkpin bushings, increased heat, and eventually an abrupt engine failure.
2. Immediately following the engine failure, while the pilot manoeuvred the aircraft for a forced landing, the aircraft entered an aerodynamic stall at a height from which recovery was not possible.
Finding as to Risk:
1. The failure to utilize available shoulder harnesses increases the risk and severity of injury.
Final Report:

Crash of a Piper PA-31T Cheyenne II in Foremost

Date & Time: Apr 25, 2008 at 1430 LT
Type of aircraft:
Operator:
Registration:
C-FRJE
Flight Type:
Survivors:
Yes
MSN:
31-7820002
YOM:
1978
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The twin engine aircraft made a wheels-up landing at Foremost Airport. The pilot, sole on board, was uninjured while the aircraft was damaged beyond repair. For unknown reasons, the landing gear had not been extended on approach.

Crash of a Piper PA-46-350P Malibu Mirage near Wainwright: 5 killed

Date & Time: Mar 28, 2008 at 0811 LT
Operator:
Registration:
C-FKKH
Flight Phase:
Survivors:
No
Schedule:
Edmonton – Winnipeg
MSN:
46-22092
YOM:
1989
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
5
Circumstances:
The privately operated Piper PA-46-350P Jetprop DLX (registration C-FKKH, serial number 4622092) had departed from Edmonton, Alberta, at about 0733 mountain daylight time en route to Winnipeg, Manitoba, on an instrument flight rules flight plan. Shortly after the aircraft levelled off at its cleared altitude of flight level (FL) 270, the aircraft was observed on radar climbing through FL 274. When contacted by the controller, the pilot reported autopilot and gyro/horizon problems and difficulty maintaining altitude. Subsequently, he transmitted that his gyro/horizon had toppled and could no longer be relied upon for controlling the aircraft. The aircraft was observed on radar to make several heading and altitude changes, before commencing a right turn and a steep descent, after which the radar target was lost. An emergency locator transmitter signal was received by the Lloydminster, Alberta, Flight Service Station for about 1 ½ minutes before it stopped. The wreckage was found by the Royal Canadian Mounted Police about 16 nautical miles northeast of Wainwright at about 1205. None of the five people on board survived.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The gyro/horizon failed due to excessive wear on bearings and other components, resulting from a lack of maintenance and due to a vacuum system that was possibly not at minimum operating requirements for the instrument.
2. The gyro/horizon was reinstalled into the aircraft to complete the occurrence flight without the benefit of the recommended overhaul.
3. The autopilot became unusable when the attitude information from the gyro/horizon was disrupted.
4. The pilot had not practised partial panel instrument flying for a number of years, was not able to transition to a partial panel situation, and lost control of the aircraft while flying in instrument meteorological conditions.
5. The aircraft was loaded in excess of its certified gross weight and had a centre of gravity (C of G) that exceeded its aft limit. These two factors made the aircraft more difficult to handle due to an increase of the aircraft’s pitch control sensitivity and a reduction of longitudinal stability.
6. The structural limitations of the aircraft were exceeded during the uncontrolled descent; this resulted in the in-flight breakup.
7. There were a number of deficiencies with the company’s safety management system (SMS), in which the hazards should have been identified and the associated risks mitigated.
8. The company did not conduct an annual risk assessment as required by its SMS; this increased the risk that a hazard could go undetected.
9. The Canadian Business Aviation Association (CBAA) audit did not identify the risks in the company’s operations.
Findings as to Risk:
1. Lack of adequate instrument redundancy increases the risk of loss of control in single-pilot instrument flight rules (IFR) aircraft operations.
2. The pilot did not reduce his airspeed while attempting to maintain control of the aircraft; a lower speed would have allowed a greater margin to maximum operating speed (Vmo) while manoeuvring.
3. There were no quick-donning oxygen masks on board and the pilot was not wearing an oxygen mask at the time of the occurrence, as required by regulation.
4. If effective oversight of private operator certificate (POC) holders is not exercised by the regulator or its delegated organization, there is an increased risk that safety deficiencies will not be identified and properly addressed.
Other Finding:
1. The approved maintenance organization (AMO) that was maintaining the aircraft did not have the approval to maintain PA-46 turbine aircraft.
Final Report:

Crash of a Rockwell Aero Commander 500B near Armstrong

Date & Time: Nov 30, 2007 at 0917 LT
Operator:
Registration:
C-GETK
Flight Phase:
Survivors:
Yes
Schedule:
Dryden – Geraldton
MSN:
500-1093-56
YOM:
1961
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft departed from Dryden, Ontario, en route to Geraldton, Ontario. The flight was conducted under visual flight rules at 5500 feet above sea level with ambient temperatures aloft of -33°C. Approximately 40 minutes into the flight, the crew observed an abnormal right engine fuel flow indication. While troubleshooting the right engine, the engine rpm and fuel flow began to decrease and the crew diverted toward Armstrong, Ontario. A short time later, the left engine rpm and fuel flow began to decrease and the crew could no longer maintain level flight. At 0917 central standard time, the crew made a forced landing 20 nautical miles southwest of Armstrong, into a marshy wooded area. The captain sustained serious injuries and the co-pilot and passenger sustained minor injuries. The aircraft was substantially damaged. The crew and passenger were stabilized and transported to Thunder Bay, Ontario, for medical assistance.
Probable cause:
Findings as to Causes and Contributing Factors:
1. Suspended water in the fuel system precipitated out of solution and froze in the fuel distributor valve. This blocked the fuel supply to the fuel nozzles and led to the loss of engine power.
2. The aircraft was being operated without a fuel additive icing inhibiter. Use of such an additive would have inhibited ice formation in the aircraft’s fuel system and would likely have prevented the fuel system blockage.
Findings as to Risk:
1. The fuel distributor valve on the Aero Commander 500B is exposed directly to the cooling blast of the outside air, which under extremely cold conditions, can lead to the freezing of super-cooled water droplets present in the fuel stream.
2. The operator did not have procedures to describe how fuel additive icing inhibiter should be used during winter operations.
Final Report:

Crash of a Bombardier BD-700-1A11 Global Express 5000 in Fox Harbour

Date & Time: Nov 11, 2007 at 1434 LT
Operator:
Registration:
C-GXPR
Survivors:
Yes
Schedule:
Hamilton – Fox Harbour
MSN:
9211
YOM:
2006
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
9188
Captain / Total hours on type:
64.00
Copilot / Total flying hours:
6426
Copilot / Total hours on type:
9
Aircraft flight hours:
92
Aircraft flight cycles:
26
Circumstances:
The aircraft, operated by Jetport Inc., departed Hamilton, Ontario, for Fox Harbour, Nova Scotia, with two crew members and eight passengers on board. At approximately 1434 Atlantic standard time, the aircraft touched down seven feet short of Runway 33 at the Fox Harbour aerodrome. The main landing gear was damaged when it struck the edge of the runway, and directional control was lost when the right main landing gear collapsed. The aircraft departed the right side of the runway and came to a stop 1000 feet from the initial touchdown point. All occupants evacuated the aircraft. One crew member and one passenger suffered serious injuries; the other eight occupants suffered minor injuries. The aircraft sustained major structural damage.
Probable cause:
Findings as to Risk:
1. Because aircraft EWH information is not readily available to pilots, crews may continue to conduct approaches with an aircraft mismatched to the visual glide slope indicator (VGSI) system, increasing the risk of a reduced TCH safety margin.
2. Due to limited knowledge of the various VGSI systems in operation and their limitations, flight crews will continue to follow visual guidance that might not provide for safe TCH.
3. Jetport did not develop an accurate company risk profile. This precluded identification of systemic safety deficiencies and development of appropriate mitigation strategies.
4. If adequate safety oversight of POC operators is not maintained by the regulator, or the delegated organization, especially during SMS implementation, there is an increased risk that safety deficiencies will not be identified.
5. The fact that the Canadian Business Aviation Association (CBAA) did not insist that milestones for SMS implementation and development be followed may result in some POC operators never reaching full SMS compliance.
6. If Transport Canada does not ensure that the CBAA fulfills its responsibilities for adequate oversight of the Canadian Aviation Regulations (CARs) subpart 604 community, safety deficiencies will not be identified and addressed.
7. The audit of Jetport’s SMS, conducted by the CBAA–accredited auditor, did not identify the deficiencies in the program or make any suggestions for improvement. Without a comprehensive audit of an operator’s SMS, deficiencies could exist resulting in the operator’s inability to implement an effective mitigation strategy.
8. Contrary to the recommendations made in the Transport Canada/CBAA feasibility studies, the CBAA did not have a quality assurance program for its audit process. As a result, there is a risk that the CBAA will fail to identify weaknesses in the POC audit program.
9. At the time of the accident, no one at Fox Harbour (CFH4) had been assigned responsibility for regular maintenance of the APAPI, therefore preventing timely identification of APAPI equipment misalignment.
10. Jetport’s risk analysis before the introduction of the Global 5000 did not identify the incompatibility between the EWH of the aircraft and the APAPI at CFH4.
11. Not wearing shoulder harnesses during landings and take-offs increases the potential risk of passenger injuries.
12. Passengers not wearing footwear could impede evacuation, increase the risk of injury, and reduce post-crash mobility and (potentially) survival.
Other Findings:
1. A SMS integrates sound risk management policies, practices, and procedures into day-to-day operations and, properly implemented, offers great potential to reduce accidents.
2. Contrary to its own assessment protocol, Transport Canada did not document its decision to close off the CBAA assessment even though the CBAA had not submitted an acceptable corrective action plan.
3. Depiction of the different types of VGSIs differs, depending on the publication.
Final Report:

Crash of a Piper PA-46-310P Malibu near Invermere: 3 killed

Date & Time: Oct 26, 2007 at 1912 LT
Registration:
C-GTCS
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Salem – Calgary
MSN:
46-08065
YOM:
1987
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
The privately operated Piper Malibu PA-46-310P was en route from Salem, Oregon, to Springbank, Alberta, on an instrument flight rules flight plan. During the descent through 17 000 feet at approximately 55 nautical miles (nm) southwest of Calgary, the pilot declared an emergency with the Edmonton Area Control Centre, indicating that the engine had failed. The pilot attempted an emergency landing at the Fairmont Hot Springs airport in British Columbia, but crashed at night at about 1912 mountain daylight time 11 nm east of Invermere, British Columbia, in wooded terrain. The pilot and two passengers were fatally injured.
Probable cause:
Findings as to Causes and Contributing Factors:
1. An unapproved part was installed in the alternator coupling. This resulted in debris from the coupling causing a partial blockage of oil flow to the number two connecting rod bearing. This low oil flow caused overheating and failure of the bearings, connecting rod cap bolts and nuts, and the subsequent engine failure.
2. The engine failure occurred after sunset and the low-lighting conditions in the valley would have made selecting a suitable landing area difficult.
3. The engine knocking was not reported to maintenance personnel which prevented an opportunity to discover the deteriorating engine condition.
Finding as to Risk:
1. All flights on the day of the accident were carried out without the oil filler cap in place. The absence of the oil filler cap could have resulted in the loss of engine oil.
Other Findings:
1. There were no current instrument flight rules charts or approach plates on board the aircraft for the intended flight.
2. The Teledyne Continental Motors Service Bulletin M84-5 addressed only the 520 series engines and did not include other gear-driven alternator equipped engines.
Final Report:

Crash of a Beechcraft A100 King Air in Chibougamau: 2 killed

Date & Time: Oct 25, 2007 at 0859 LT
Type of aircraft:
Operator:
Registration:
C-FNIF
Flight Type:
Survivors:
No
Schedule:
Val d’Or – Chibougamau
MSN:
B-178
YOM:
1973
Flight number:
CRQ501
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
1800
Captain / Total hours on type:
122.00
Copilot / Total flying hours:
1022
Copilot / Total hours on type:
71
Circumstances:
The Beechcraft A100 (registration C-FNIF, serial number B-178), operated by Air Creebec Inc. on flight CRQ 501, was on a flight following instrument flight rules between Val-d’Or, Quebec, and Chibougamau/Chapais, Quebec, with two pilots on board. The aircraft flew a non-precision approach on Runway 05 of the Chibougamau/Chapais Airport, followed by a go-around. On the second approach, the aircraft descended below the cloud cover to the left of the runway centreline. A right turn was made to direct the aircraft towards the runway, followed by a steep left turn to line up with the runway centreline. Following this last turn, the aircraft struck the runway at about 500 feet from the threshold. A fire broke out when the impact occurred and the aircraft continued for almost 400 feet before stopping about 50 feet north of the runway. The first responders tried to control the fire using portable fire extinguishers but were not successful. The Chibougamau and Chapais fire departments arrived on the scene at about 0926 eastern daylight time, which was about 26 minutes after the crash. The aircraft was destroyed by the fire. The two pilots suffered fatal injuries.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The aircraft was configured late for the approach, resulting in an unstable approach condition.
2. The pilot flying carried out a steep turn at a low altitude, thereby increasing the load factor. Consequently, the aircraft stalled at an altitude that was too low to allow the pilot to carry out a stall recovery procedure.
Findings as to Risk:
1. The time spent programming the global positioning system reduced the time available to manage the flight. Consequently, the crew did not make the required radio communications on the mandatory frequency, did not activate the aircraft radio control of aerodrome lighting (ARCAL), did not make the verbal calls specified in the standard operating procedures (SOPs), and configured the aircraft for the approach and landing too late.
2. During the second approach, the aircraft did a race-track pattern and descended below the safe obstacle clearance altitude, thereby increasing the risk of a controlled flight into terrain. The crew’s limited instrument flight rules (IFR) experience could have contributed to poor interpretation of the IFR procedures.
3. Non-compliance with communications procedures in a mandatory frequency area created a situation in which the pilots of both aircraft had poor knowledge of their respective positions, thereby increasing the risk of collision.
4. The pilot-in-command monitored approach (PICMA) procedure requires calls by the pilot not flying when the aircraft deviates from pre-established acceptable tolerances. However, no call is required to warn the pilot flying of an approaching steep bank.
5. The transfer of controls was not carried out as required by the PICMA procedure described in the SOPs. The transfer of controls at the co-pilot’s request could have taken the pilot-in-command by surprise, leaving little time to choose the best option.
6. Despite their limited amount of IFR experience in a multiple crew working environment, the two pilots were paired. Nothing prohibited this. Although the crew had received crew resource management (CRM) training, it still had little multiple crew experience and consequently little experience in applying the basic principles of CRM.
Other Findings:
1. The emergency locator transmitter (ELT) had activated after the impact but due to circuit board damage its transmission power was severely limited. This situation could have had serious consequences had there been any survivors.
2. The Chibougamau/Chapais airport does not have an aircraft rescue and firefighting service. Because the fire station is 23 kilometres from the airport, the firefighters arrived at the scene 26 minutes after the accident.
3. Although this accident does not meet the criteria of a controlled flight into terrain (CFIT), it nonetheless remains that a stabilized constant descent angle (SCDA) non-precision approach (NPA) would have provided an added defence tool to supplement the SOPs.
4. After the late call within the mandatory frequency (MF) area, the specialist at the Québec flight information centre asked the crew about its familiarity with the MF area while the aircraft was in a critical phase of the first approach, which was approaching the minimum descent altitude (MDA). This situation could have distracted the flight crew while they completed important tasks.
5. The standard checklist used by the flight crew made no reference to the enhanced ground proximity warning system (EGPWS). Therefore, the crew was not prompted to check it to ensure that it was properly activated before departure.
Final Report:

Crash of a De Havilland DHC-2 Beaver in Dodger Channel

Date & Time: Jul 31, 2007 at 1258 LT
Type of aircraft:
Operator:
Registration:
N340KA
Survivors:
Yes
Schedule:
Patricia Bay - Dodger Channel
MSN:
1127
YOM:
1957
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The Sound Flight DHC-2 float-equipped Beaver aircraft, N340KA, flew from Patricia Bay to Dodger Channel where the pilot planned to land. He set up an approach to land to the south in Dodger Channel, into the wind. On short final, the pilot noticed a shoal so he decided to overshoot, make a circuit, and land beyond the shoal. He applied power, established a climb and began a left turn. As the aircraft turned, it came into the lee of Diana Island. The aircraft encountered subsiding air and began to descend. The pilot was unable to arrest the descent. The aircraft struck the water and sank. All six occupants escaped without any injury but the aircraft was damaged beyond repair.

Crash of a De Havilland DHC-6 Twin Otter 100 in Muncho Lake: 1 killed

Date & Time: Jul 8, 2007 at 1235 LT
Operator:
Registration:
C-FAWC
Flight Phase:
Survivors:
Yes
Schedule:
Muncho Lake – Prince George
MSN:
108
YOM:
1968
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
22000
Captain / Total hours on type:
6000.00
Copilot / Total flying hours:
10800
Copilot / Total hours on type:
105
Circumstances:
At approximately 1235 Pacific daylight time, the Liard Air Limited de Havilland DHC-6-100 Twin Otter (registration C-FAWC, serial number 108) was taking off from a gravel airstrip near the Northern Rockies Lodge at Muncho Lake on a visual flight rules flight to Prince George, British Columbia. After becoming airborne, the aircraft entered a right turn and the right outboard flap hanger contacted the Alaska Highway. The aircraft subsequently struck a telephone pole and a telephone cable, impacted the edge of the highway a second time, and crashed onto a rocky embankment adjacent to a dry creek channel. The aircraft came to rest upright approximately 600 feet from the departure end of the airstrip. An intense post-impact fire ensued and the aircraft was destroyed. One passenger suffered fatal burn injuries, one pilot was seriously burned, the other pilot sustained serious impact injuries, and the other two passengers received minor injuries.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The take-off was attempted at an aircraft weight that did not meet the performance capabilities of the aircraft to clear an obstacle and, as a result, the aircraft struck a telephone pole and a telephone cable during the initial climb.
2. A take-off and climb to 50 feet performance calculation was not completed prior to take-off; therefore, the flight crew was unaware of the distance required to clear the telephone cable.
3. The southeast end of the airstrip was not clearly marked; as a result, the take-off was initiated with approximately 86 feet of usable airstrip behind the aircraft.
4. The take-off was attempted in an upslope direction and in light tailwind, both of which increased the distance necessary to clear the existing obstacles.
Findings as to Risk:
1. Operational control within the company was insufficient to reduce the risks associated with take-offs from the lodge airstrip.
2. The take-off weight limits for lodge airstrip operations were not effectively communicated to the flight crew.
3. Maximum performance short take-off and landing (MPS) techniques may have been necessary in order to accomplish higher weight Twin Otter take-offs from the lodge airstrip; however, neither the aircraft nor the company were approved for MPS operations.
4. The first officer’s shoulder harness assembly had been weakened by age and ultraviolet (UV) light exposure; as a result, it failed within the design limits at impact.
5. The SeeGeeTM calculator operating index (OI) values being used by Liard Air Twin Otter pilots was between 0.5 and 1.0 units greater than the correct SeeGeeTM OI values; therefore, whenever the SeeGeeTM calculator was used for flight planning, the actual centre of gravity (c of g) of the aircraft would have been forward of the calculated CofG.
6. There are no airworthiness standards specifically intended to contain fuel and/or to prevent fuel ignition in crash conditions in fixed-gear United States Civil Aviation Regulation 3 and United States Federal Aviation Regulation 23 aircraft.
Final Report:

Crash of a De Havilland DHC-3 Otter in Mayo: 1 killed

Date & Time: Jun 2, 2007 at 1755 LT
Type of aircraft:
Operator:
Registration:
C-GZCW
Flight Phase:
Flight Type:
Survivors:
No
MSN:
108
YOM:
1956
Location:
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
4000
Captain / Total hours on type:
202.00
Circumstances:
The Black Sheep Aviation and Cattle Company de Havilland DHC-3T Turbo Otter (registration C-GZCW, serial number 447) had been loaded with a cargo of lumber at Mayo, Yukon. The aircraft was taxied to the threshold of Runway 06 and the pilot began the take-off roll at 1755 Pacific daylight time. At lift-off, the aircraft entered an extreme nose-up attitude and began to rotate to the right. Shortly thereafter, the aircraft struck the airport ramp. The pilot, who was the sole occupant of the aircraft, was fatally injured. A small post-impact fire was extinguished by first responders.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The aircraft was loaded in a manner that resulted in the centre of gravity being aft of the rearward limit.
2. Because the cargo was not properly secured, it shifted towards the rear of the aircraft, resulting in the centre of gravity moving further aft, causing the aircraft to pitch up and stall.
Final Report: