Crash of a Piper PA-46-350P Malibu Mirage on Mt Lakit: 1 killed

Date & Time: Oct 17, 1999 at 2025 LT
Registration:
N90D
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Lynn Lake – Cranbrook – Spokane
MSN:
46-22086
YOM:
1989
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
On October 17, 1999, about 20:25 Mountain Daylight Time, a Piper PA-46-350P, N90D, was substantially damaged while descending to the Cranbrook Airport (CYXC), Cranbrook, British Columbia. The certificated airline transport pilot was fatally injured. Night visual meteorological conditions prevailed, and an instrument flight rules (IFR) flight plan was filed for the flight that originated near Lynn Lake (CYYL), Manitoba. The ferry flight was conducted under Canadian flight rules. According to a Transportation Safety Board of Canada Investigator, the airplane was being ferried from England to Spokane, Washington. At the last departure point, CYYL, the airplane was refueled and the pilot filed an IFR flight plan. During the flight, the pilot was in contact with Vancouver Area Control Center. While approaching CYXC, the pilot contacted Cranbrook Flight Service Station (FSS) and was provided the latest airport information. The pilot did not report any difficulties with the airplane or flight at that time. The pilot's last transmission with the FSS was about 10 miles from the airport. After attempting to contact the airplane, FSS contacted the Rescue Coordination Center, and notified them that the airplane was overdue. An emergency locator transmitter signal was received about 21:55, but the airplane was not found until the following morning. The airplane was located on the eastern side of Lakit Mountain at the 6,500-foot level, 9 miles northeast of CYXC. The weather reported by CYXC, at 20:00 was, wind from 300 degrees at 4 knots, scattered clouds at 10,000 feet, and a broken cloud layer at 24,000 feet. The pilot (sole person on board) was killed.
Probable cause:
Controlled flight into terrain.

Crash of a Cessna 208B Super Cargomaster in Ranger Lake

Date & Time: Oct 15, 1999 at 1225 LT
Type of aircraft:
Operator:
Registration:
C-FKSL
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Deer Lake - Red Lake
MSN:
208B-0129
YOM:
1988
Flight number:
WSG126
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
While holding outside the control zone at Red Lake (YRL) pending a special VFR clearance, the pilot made a descending turn to avoid a flock of large birds. The right wing struck the water of Ranger Lake and the Cessna overturned. A military DHC-8 diverted to Red Lake and located the Cessna on the west side of Ranger Lake. The airplane was partially submerged and the pilot was on the wing. A floatplane (C-FVTU) subsequently picked up the pilot and returned him to Red Lake. The pilot suffered shoulder injuries, arm injuries, facial injuries and hypothermia.

Crash of a De Havilland DHC-2 Beaver near Pickle Lake

Date & Time: Oct 2, 1999 at 1430 LT
Type of aircraft:
Operator:
Registration:
C-GZBQ
Flight Phase:
Survivors:
Yes
Schedule:
Big Trout Lake - Geraldton
MSN:
919
YOM:
1956
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
1420
Captain / Total hours on type:
725.00
Aircraft flight hours:
13372
Circumstances:
The de Havilland DHC-2 Beaver seaplane departed from Big Trout Lake, Ontario, on a visual flight rules flight for Geraldton, Ontario, with a pilot and an aircraft maintenance engineer on board. After encountering adverse weather conditions en route to Geraldton, the pilot decided to divert to Pickle Lake, Ontario. At about 1430 central daylight time, the engine lost power at an altitude of about 300 feet above ground level while in the descent for Pickle Lake. The pilot turned the aircraft toward a nearby narrow river. In an attempt to restart the engine, the pilot confirmed that the fuel pressure was normal, the fuel selector was on the fullest tank (front), the throttle was at idle, the mixture was rich, and the ignition switch was on both, then he operated the wobble pump. When the engine did not restart, he switched to the centre fuel tank and operated the wobble pump again, but the engine still did not restart. He then switched back to the front tank and tried another restart, without success. He then landed the aircraft on the river at an estimated landing speed of about 40 to 45 mph. After the forced landing, the left wingtip collided with trees on the river bank, and the aircraft yawed to the left about 180 degrees and struck the river bank, breaking off the floats and the float struts. Impact with more trees on the river bank damaged the right wing and elevator. Both occupants were wearing lap belts with shoulder harnesses and were uninjured. The aircraft was substantially damaged. The pilot advised Thunder Bay flight service station by radio of the engine failure and crash and the crew were rescued two hours later.
Probable cause:
Findings as to Causes and Contributing Factors:
- The engine quit operating because the aircraft fuel system was contaminated with a large amount of water.
- The most likely source of the water contamination was the drums from which the aircraft was refuelled.
- A proper filter to prevent water contamination was not used when the aircraft was refuelled.
- The nose-level aircraft attitude when beached and the freezing of water probably prevented the water contamination from being drained from the front tank during the pilot's pre-flight checks.
Other Findings:
- The aircraft's maintenance records indicate that the aircraft was certified, equipped, and maintained in accordance with existing regulations and approved procedures.
- The use of the available shoulder harnesses probably prevented serious injury to the pilot and engineer.
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain in Princess Harbor

Date & Time: Aug 29, 1999 at 1532 LT
Operator:
Registration:
C-GHMK
Flight Phase:
Survivors:
Yes
Schedule:
Saint Andrews - Berens River
MSN:
31-7952120
YOM:
1979
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The Piper PA-31-350 Navajo, C-GHMK, departed from St. Andrews, Manitoba, on a visual flight rules charter flight to Berens River. One pilot and ten passengers, including one infant, were on board, and a dog was stowed in the baggage compartment behind the right, rear seat. At approximately 1530 central daylight saving time (CDT), while the aircraft was at an altitude of about 2 500 feet and about 30 nautical miles south of Berens River, the pilot heard a loud sound from the left engine. He saw deformation of the left engine cowling and smoke coming from the engine, and the aircraft yawed to the left. Part of the engine cowling departed in flight. The pilot could not pull the left propeller lever beyond half of its normal travel, nor could he move it into the feather position. He set maximum power on the right engine, but the aircraft did not maintain altitude. The pilot advised company dispatch over the radio that he would attempt a forced landing, then force landed in a mossy marsh area. Everyone on board, including the dog, deplaned. Five of the passengers sustained minor injuries during the evacuation. A fire ensued, completely destroying the aircraft except for the empennage aft of the horizontal stabilizers.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The number three cylinder lower forward through stud was missing its base nut, which allowed the lower rear base nut of the number two cylinder to loosen.
2. The missing base nut of the through stud indicates that the base nut did not have sufficient clamping force; however, it could not be determined if the base nut did not receive the required torque during installation or if the base nut lost its clamping force during engine operation.
3. The d-inch studs and the 2-inch through studs of the number two cylinder failed in fatigue, and the number two cylinder of the left engine separated from the crankcase.
4. The left propeller could not be feathered because of interference between the propeller governor control and the separated number two cylinder.
5. The drag from the unfeathered left propeller and the deformed left engine cowling resulted in the aircraft being incapable of maintaining its altitude.
Other Findings:
1. The pilot was certified and qualified for the accident flight.
2. The aircraft's weight and balance were within the specified limits at the time of the accident.
3. The ELT was not readily accessible without tools.
Final Report:

Crash of a Beechcraft 1900D in Seven Islands: 1 killed

Date & Time: Aug 12, 1999 at 2357 LT
Type of aircraft:
Operator:
Registration:
C-FLIH
Survivors:
Yes
Schedule:
Port-Menier - Seven Islands
MSN:
UE-347
YOM:
1999
Flight number:
RH347
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
7065
Captain / Total hours on type:
606.00
Copilot / Total flying hours:
2600
Copilot / Total hours on type:
179
Aircraft flight hours:
373
Circumstances:
The RégionnAir flight took off from Port-Menier at 23:34 for an IFR flight to Seven Islands. The crew decided to carry out a straight-in GPS approach to runway 31. However, there is no published GPS approach for that runway. The descent from cruise flight into the airport was started late, and the aircraft was high and fast during the approach phase to the NDB. From an altitude of 10 000 feet at 9 nm from the NDB, the rate of descent generally exceeded 3000 fpm. The aircraft crossed the beacon at 600 feet asl. For the last 30 seconds of flight and from approximately 3 nm from the threshold, the aircraft descended steadily at approximately 850 fpm, at 140 to 150 knots indicated airspeed, with full flaps extended. The captain coached the first officer throughout the descent and called out altitudes and distances. The GPWS "Minimums" activation sounded, consistent with the decision height selection of 100 feet, to which the captain responded with directions to continue a slow descent. The last call was at 30 feet, 1.2 seconds before impact. Eight seconds before impact, the GPWS voice message "Minimums, Minimums" activated. The aircraft continued to descend and struck trees in a near-level attitude, in an area of rising terrain. A post-crash fire destroyed the wings, the right engine, and the right midside of the fuselage. The cabin area remained relatively intact, but the cockpit area separated and was crushed during the impact sequence. The Beechcraft in question was a brand new aircraft, registered just 2 months earlier. This accident was RégionnAir's second Beech 1900 loss in 1999; on January 4 an accident happened on approach to St. Augustin River. No one received fatal injuries in that accident however.
Probable cause:
Findings as to causes and contributing factors:
1. The pilot flying did not establish a maximum performance climb profile, although required by the company's standard operating procedures (SOPs), when the ground proximity warning system (GPWS) "Terrain, Terrain" warning sounded during the descent, in cloud, to the non-directional beacon (NDB).
2. The pilot flying did not fly a stabilized approach, although required by the company's SOPs. The crew did not carry out a go-around when it was clear that the approach was not stabilized.
3. The crew descended the aircraft well below safe minimum altitude while in instrument meteorological conditions.
4. Throughout the approach, even at 100 feet above ground level (agl), the captain asked the pilot flying to continue the descent without having established any visual contact with the runway environment.
5. After the GPWS "Minimums, Minimums" voice activation at 100 feet agl, the aircraft's rate of descent continued at 850 feet per minute until impact.
6. The crew planned and conducted, in cloud and low visibility, a user-defined global positioning system approach to Runway 31, contrary to regulations and safe practices.
Findings as to risk:
1. At the time of the approach, the reported ceiling and visibility were well below the minima published on the approach chart.
2. Because the runway was not equipped with a reporting runway visual range system, flying the NDB approach was allowable under the existing regulations.
3. The crew did not follow company SOPs for the approach and missed-approach briefings.
4. Both crew members had surpassed their maximum monthly and quarterly flight times and maximum daily flight duty times. They were thus at increased risk of fatigue, which leads to judgement and performance errors.
5. The first officer likely suffered from chronic fatigue, having worked an average of 14 hours a day for the last 30 days, with only 1 day of rest.
6. Transport Canada was not aware that the company's pilots were exceeding the flight and duty times.
7. The company operations manager did not effectively supervise the flight and duty times of company pilots.
8. The captain had not received the mandatory training in pilot decision making or crew resource management.
Other findings:
1. The emergency locator transmitter activated on initial impact but ceased to transmit shortly thereafter when its antenna cable was severed.
Final Report:

Crash of a De Havilland DHC-3 Otter in Long Haul Lake: 1 killed

Date & Time: Jun 25, 1999 at 1320 LT
Type of aircraft:
Operator:
Registration:
C-FIFP
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
73
YOM:
1955
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
1
Aircraft flight hours:
23960
Circumstances:
The Blue Water Aviation Services seaplane departed from Long Haul Lake, Manitoba, with a pilot and an aviation maintenance engineer on board. Shortly after take-off, at 1320 central daylight savings time, the aircraft's engine abruptly lost power. The pilot's attempts to restart the engine were unsuccessful, and the aircraft descended into a stand of trees and struck the ground. The engineer suffered fatal injuries, and the pilot was seriously injured. The aircraft was destroyed by impact forces.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The most likely accident scenario during the second take-off is that water contamination migrated from the centre fuel tank to the engine, resulting in a loss of engine power.
2. The engine stopped at a point from which there was insufficient time for the engine to restart, nor from which a safe landing could be made.
3. Indications of water contamination were found in the fuel system after the occurrence; however, the source(s) of the water contamination could not be identified.
Other Findings:
1. Examination of the aircraft and testing of the engine and components did not identify any pre-occurrence structural, mechanical, or electrical defects or malfunctions that would have
contributed to this occurrence.
2. The post-crash fire in the carburettor most likely resulted from uncontaminated fuel brought forward by the windmilling engine and the pilot's efforts to clear contamination from the fuel
system.
3. The pilot's use of his shoulder harness likely prevented more serious injuries during the impact sequence.
4. The engineer's injuries likely would have been less severe had he been using both his seat belt and shoulder harness.
5. The pilot was certified and qualified for the flight.
6. The aircraft's weight and centre of gravity were within approved limits.
7. The aircraft's records indicated that the aircraft had been certified and maintained in accordance with existing regulations.
8. The aircraft's engine power loss during the first attempted take-off was likely due to water contamination in the fuel.
Final Report:

Crash of a Beechcraft A100 King Air in Thunder Bay

Date & Time: Jun 14, 1999 at 1038 LT
Type of aircraft:
Operator:
Registration:
C-GASW
Flight Phase:
Survivors:
Yes
Schedule:
Thunder Bay – Red Lake
MSN:
B-108
YOM:
1972
Flight number:
THU103
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The Thunder Airlines Limited Beech A100 King Air aircraft, serial number B108, took off at 1034 eastern daylight saving time (EDT) on a charter flight from Thunder Bay, Ontario, for Red Lake, Ontario, with two pilots and three passengers on board. After getting airborne, the aircraft pitched up to approximately 70 degrees, reaching a height estimated to be between 500 and 700 feet above ground level. It then rolled to the left, pitched steeply nose-down, and descended to the ground within the confines of the airport. The aircraft contacted the soft, level ground in a relatively level attitude and covered a distance of about 500 feet before coming to rest in a wooded area immediately beyond an elevated railroad bed and track. The cabin remained intact during the crash sequence, and all occupants escaped without any injuries. The aircraft was damaged beyond repair. An ensuing fuel-fed fire was rapidly extinguished by airport emergency response services (ERS)
personnel.
Probable cause:
The flight crew lost pitch control of the aircraft on take-off when the stabilizer trim actuators became disconnected because they had not been properly reinstalled by the AME during maintenance work conducted before the flight. The crew chief responsible for the inspection did not ensure correct assembly of the stabilizer trim actuators, which contributed to the accident.
Final Report:

Crash of a Mitsubishi MU-2B-40 Solitaire in Parry Sound: 2 killed

Date & Time: May 24, 1999 at 2130 LT
Type of aircraft:
Registration:
N701K
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Parry Sound – Toronto
MSN:
410
YOM:
1979
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
5500
Captain / Total hours on type:
400.00
Circumstances:
With one pilot and one passenger, the Mitsubishi MU-2B-40 Solitaire aircraft, serial number 410 S.A., departed on a night instrument flight rules flight from Parry Sound / Georgian Bay Airport, Ontario, destined for Toronto / Lester B. Pearson International Airport. Prior to departure, the pilot received his instrument flight rules clearance via telephone from the Sault Ste. Marie flight service station with a clearance valid time of 2118 eastern daylight time from Toronto Area Control Centre and a clearance cancel time of 2135. When the pilot did not establish communications with Toronto Area Control Centre within the clearance valid time, the Area Control Centre supervisor commenced a communication search. At 2151, he confirmed with Parry Sound / Georgian Bay Airport personnel that the aircraft had departed 10 to 15 minutes earlier. The aircraft was assumed missing and the Rescue Coordination Centre in Trenton, Ontario, was notified. Search and rescue was dispatched and three days later the aircraft wreckage was located one nautical mile west of the airport. Both of the aircraft occupants were fatally injured. The aircraft disintegrated as it cut a 306-foot swath through the poplar forest. The accident occurred at night in instrument meteorological conditions.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The accident flight was conducted at night in IMC, and the pilot, whose private pilot licence was not endorsed with an instrument rating, was not certified for the IFR flight.
2. The pilot may have been subjected to somatogravic illusion and allowed the aircraft to descend into terrain after a night take-off in IMC.
3. The pilot did not completely report his medical conditions to the civil aviation medical examiner.
Other Findings
1. The pilot was not certified to fly this model of aircraft as his private pilot licence was not endorsed with the appropriate high-performance aircraft rating.
2. The pilot conducted a downwind take-off.
3. While the aircraft was turning left for the on-course track, the aircraft flaps were retracting.
4. The aircraft struck trees while in a shallow descent. The integrity of the aircraft was compromised as it rolled inverted and entered the impact zone at high speed.
5. The aircraft engine teardown examination revealed no pre-impact failures of any component parts or accessories in either the left or right engine that would have precluded normal engine operation.
6. The propeller teardown examination revealed that both propellers were in a normal operating range and were rotating with power at the time of impact.
7. The ELT did not function due to the impact damage sustained by its various components.
Final Report:

Crash of a De Havilland DHC-3 Otter near Points North Landing

Date & Time: May 1, 1999
Type of aircraft:
Operator:
Registration:
C-FASV
Flight Phase:
Survivors:
Yes
MSN:
23
YOM:
1953
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
20000
Captain / Total hours on type:
6400.00
Circumstances:
The wheel-ski equipped de Havilland DHC-3 Otter, C-FASV, serial number 23, was engaged in flying road construction crews from base camps to work sites in northern Saskatchewan. A five-man crew was moved from a base camp to a small lake, about 22 nautical miles (nm) from Points North Landing, Saskatchewan, the company's main base. The drop-off was made in the morning with a pick-up planned for late afternoon. The pilot then flew back to Points North Landing and filled the aircraft's fuel tanks from the company's main fuel supply. When the pilot returned for the pick-up, the ambient temperature was about seven degrees Celsius, and there were between five and six inches of slush on the ice surface. The pilot loaded the passengers and attempted a take-off. The aircraft accelerated slowly in the slush, and the pilot rejected the take-off. He selected a different take-off run, moved a passenger to a forward seat, and attempted a second take-off. The pilot continued beyond his previously selected rejection distance. The engine revolutions per minute (rpm) then reportedly decreased by about 150 rpm. The aircraft did not become airborne, and it ran into the low shoreline and crashed, skidding to a stop about 300 feet from the shore. An intense fire broke out immediately. The passengers and pilot evacuated the aircraft. Only one passenger suffered minor burns during the evacuation. Flames engulfed the main fuselage and engine, destroying the aircraft.
Probable cause:
The pilot continued the take-off run with the left ski firmly adhering to the slushy surface beyond a point at which a reject could have been made safely. Contributing to the occurrence was the decrease in engine rpm during take-off.
Final Report:

Crash of a De Havilland DHC-6 Twin Otter in Davis Inlet: 1 killed

Date & Time: Mar 19, 1999 at 0945 LT
Operator:
Registration:
C-FWLQ
Flight Type:
Survivors:
Yes
Schedule:
Goose Bay - Davis Inlet
MSN:
724
YOM:
1980
Flight number:
PB960
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
1600
Captain / Total hours on type:
2500.00
Copilot / Total flying hours:
500
Copilot / Total hours on type:
70
Aircraft flight hours:
30490
Circumstances:
The flight was a pilot self-dispatched, non-scheduled cargo flight from Goose Bay to Davis Inlet, Newfoundland, and was operating as Speed Air 960 under a defence visual flight rules flight plan. Before the flight, the captain received weather information from the St. John's, Newfoundland, flight service station (FSS) via telephone and fax. The aircraft departed for Davis Inlet at 0815 Atlantic standard time (AST). The captain was the pilot flying (PF). During the first approach, the first officer (FO) had occasional visual glimpses of the snow on the surface. The captain descended the aircraft to the minimum descent altitude (MDA) of 1340 feet above sea level (asl). When the crew did not acquire the required visual references at the missed approach point, they executed a missed approach. On the second approach, the captain flew outbound from the beacon at 3000 feet asl until turning on the inbound track. It was decided that if visual contact of the surface was made at any time during the approach procedure, they would continue below the MDA in anticipation of the required visual references. The captain initiated a constant descent at approximately 1500 feet per minute with 10 degrees flap selected. The FO occasionally caught glimpses of the surface. At MDA, in whiteout conditions, the captain continued the descent. In the final stages of the descent, the FO acquired visual ground contact; 16 seconds before impact, the captain also acquired visual ground contact. At 8 seconds before impact, the crew selected maximum propeller revolutions per minute. The aircraft struck the ice in controlled flight two nautical miles (nm) from the airport (see Appendix B). During both approaches, the aircraft encountered airframe icing. The crew selected wing de-ice, which functioned normally by removing the ice.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The captain decided to descend below the minimum descent altitude (MDA) without the required visual references.
2. After descending below MDA, both pilots were preoccupied with acquiring and maintaining visual contact with the ground and did not adequately monitor the flight instruments; thus, the aircraft flew into the ice.
Findings as to Risk:
1. The flight crew did not follow company standard operating procedures.
2. Portions of the flight were conducted in areas where the minimum visual meteorological conditions required for visual flight rules flight were not present.
3. Although both pilots recently attended crew resource management (CRM) training, important CRM concepts were not applied during the flight.
4. The cargo was not adequately secured before departure, which increased the risk of injury to the crew.
5. The company manager and the pilot-in-command did not ensure that safe aircraft loading procedures were followed for the occurrence flight.
6. There were lapses in the company's management of the Goose Bay operation; these lapses were not detected by Transport Canada's safety oversight activities.
7. The aircraft was not equipped with a ground proximity warning system, nor was one required by regulation.
8. Records establish that the aircraft departed approximately 500 pounds overweight.
Other Findings:
1. The flight crew were certified, trained, and qualified to operate the flight in accordance with existing regulations and had recently attended CRM training.
2. During both instrument approaches, the aircraft was operating in instrument meteorological conditions and icing conditions.
3. There was no airframe failure or system malfunction prior to or during the flight. In particular, the airframe de-icing system was serviceable and in operation during both approaches.
4. It was determined that an ice-contaminated tailplane stall did not occur.
5. The fuel weight was not properly recorded in the journey logbook.
6. The wreckage pattern was consistent with a controlled, shallow descent.
7. The emergency locator transmitter was damaged due to impact forces during the accident, rendering it inoperable.
Final Report: