Crash of a Beechcraft A100 King Air in Grande Prairie

Date & Time: Apr 7, 2001 at 0512 LT
Type of aircraft:
Operator:
Registration:
C-FWPN
Survivors:
Yes
Schedule:
Fort Saint John – Grande Prairie
MSN:
B-51
YOM:
1970
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Fort Saint John, the crew started a night approach to Grande Prairie Airport. The aircraft landed slightly to the left of the runway centerline. After touchdown on a snow covered runway (about two inches of snow), the left wing struck a windrow of snow. Out of control, the aircraft veered off runway and came to rest in snow. All five occupants escaped uninjured while the aircraft was damaged beyond repair.

Crash of a Boeing 737-2E1F in Saint John's

Date & Time: Apr 4, 2001 at 0615 LT
Type of aircraft:
Operator:
Registration:
C-GDCC
Flight Type:
Survivors:
Yes
Schedule:
Hamilton – Montréal – Halifax – Saint John’s
MSN:
20681
YOM:
1973
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
At 2320, Newfoundland daylight time, on 03 April 2001, the Royal Cargo flight, a Boeing 737-200, left Mirabel, Quebec, for a scheduled instrument flight rules cargo flight with two pilots on board. The flight was headed for Hamilton, Ontario; Mirabel; Halifax, Nova Scotia; St. John's, Newfoundland; and Mirabel. The flights from Mirabel to Halifax were uneventful. Before departure from Halifax, the pilot flying (PF) received the latest weather information for the flight to St. John's from the company dispatch; he did not ask for, or receive, the latest notices to airmen (NOTAMs). At 0545, the aircraft departed Halifax for St. John's. The PF was completing his line indoctrination training after having recently upgraded to captain. The training captain, who was the pilot not flying (PNF), occupied the right seat. After departure from Halifax, he contacted Halifax Flight Service Station (FSS) and received the latest weather report for St. John's, the 0530 aviation routine weather report (METAR). The weather was as follows: wind 050° magnetic (M) at 35, gusting to 40, knots; visibility 1 statute mile in light snow and blowing snow; ceiling 400 feet overcast; temperature -1°C; dew point -2°C; and altimeter 29.41 inches of mercury. The FSS passed runway surface condition (RSC) reports for both runways (11/29 and 16/34), including Canadian runway friction index (CRFI) readings of 0.25 for Runway 11/29 and 0.24 for Runway 16/34. The FSS specialist also provided the NOTAMs for St. John's, which included a NOTAM released more than five hours earlier advising of the unserviceability of the instrument landing system (ILS) for Runway 11. The flight crew had initially planned an ILS approach, landing on Runway 11 at St. John's. Because of the marginal weather, the loss of Runway 11/29, and his greater experience, the training captain decided to switch seats and assume the duties and full responsibilities as captain and PF. Returning to Halifax was not considered because the aircraft would be overweight for landing there. The option of diverting the flight to the alternate airport was also discussed by the crew; however, in the end, they felt that a safe landing was achievable in St. John's. At 0638:27, the PF contacted St. John's tower to ask if the approach to Runway 34 was still an option. The response indicated that Runway 34 was probably the only option because of the wind: 050°M (estimated) at 35, gusting to 40, knots. The ILS on Runway 11 was unserviceable, and the glidepath for Runway 29 was unserviceable. The only instrument approaches available were the localizer back course Runway 34 and the ILS Runway 16. Also, at about 0638, the Gander Area Control Centre (ACC) controller suggested to the crew that they obtain the 0630 automatic terminal information service (ATIS) for St. John's. The ATIS was reporting surface winds of 055°M at 20, gusting to 35, knots. The PNF attempted to obtain the ATIS information; however, because of a simultaneous radio transmission on the second VHF radio between the PF and St. John's tower, the ATIS information was not obtained. At 0641, the PNF contacted Gander ACC, which reported the winds at St. John's as 040°M at 13, gusting to 18, knots. The PNF pointed out the discrepancy in the two wind reports to the PF; however, there was no acknowledgement of the significance of the discrepancy. It was later determined that the discrepancy was an unserviceable anemometer at the St. John's airport due to ice accretion on the anemometer. The anemometer was providing a direct reading of the incorrect wind information to Gander ACC. Gander ACC was unaware of the unserviceability and unknowingly passed the incorrect wind information on to the flight crew. At 0644, Gander ACC transmitted a significant meteorological report (SIGMET), issued at 0412 and valid from 0415 to 0815, that included St. John's. The SIGMET forecast severe mechanical turbulence below 3000 feet due to surface wind gusts in excess of 50 knots. However, the crew may not have been listening to the SIGMET broadcast: while the ACC transmitted the SIGMET, the crew were discussing the application of an 18-knot quartering tailwind for the approach to Runway 16. This tailwind was well under the 50 knots described by the SIGMET. The crew did not acknowledge receipt of the SIGMET until prompted by the controller. Before the descent into St. John's, the crew discussed approach options. The approach to Runway 11 was discounted because of the unserviceability of the ILS, and Runway 34 was eliminated as an option because the weather was below its published approach minimums. The crew discussed the ILS approach to Runway 16. Although the PNF expressed concern about the tailwind, it was decided to attempt the approach because the wind reported by Gander ACC was within the aircraft's landing limits. In calculating the approach speed in preparation for the approach, there was confusion during the application of the tailwind and gust corrections to the landing reference speed (Vref ). The crew had correctly established a flap-30 Vref of 132 knots indicated airspeed (KIAS) and ultimately an approach speed of 142 KIAS. The approach speed calculations were derived using the incorrect wind information from Gander ACC; further, the crew added five knots for the gust increment to the nominal approach speed (Vref + 5 knots), that is, Vref + 10 knots. This incorrect calculation (adding the gust factor) was consistent with company practice at the time of the accident. During the descent, the crew also had difficulty completing the descent and approach checklists; there were several missteps and repeated attempts at completion of checks. Clearance for an ILS approach to Runway 16 was obtained from Gander ACC , and the crew was advised to contact St. John's tower. Just over two minutes before landing, the tower advised that the wind was 050°M (estimated) at 20, gusting to 35, knots and provided the following RSC report for Runway 16: Full length 170 feet wide, surface 30% very light dusting of snow and 70% compact snow and ice; remainder is 20% light snow, 80% compact snow and ice, windrow along the east side of the runway; friction index 0.20; and temperature -1°C at 0925. The aircraft crossed the final approach fix on the ILS glideslope at 150 KIAS. During the final approach, the airspeed steadily increased to 180 KIAS (ground speed 190 knots); the glidepath was maintained with a descent rate of 1000 feet per minute. From 1000 feet above sea level, no airspeed calls were made; altitude calls were made and responses were made. The Royal Boeing 737 operations manual states that the PNF shall call out significant deviations from programmed airspeed. In the descent, through 900 feet above sea level, the aircraft encountered turbulence resulting in uncommanded roll and pitch deviations and airspeed fluctuations of +/- 11 knots. At about 300 feet above decision height, the crew acquired visual references for landing. Approximately one minute before landing, St. John's tower transmitted the runway visual range, repeated the estimated surface wind (050°M [estimated] at 20, gusting to 35, knots), and issued a landing clearance to the aircraft; the PNF acknowledged this information. The aircraft touched down at 164 KIAS (27 KIAS above the desired touchdown speed of Vref), 2300 to 2500 feet beyond the threshold. Radar ground speed at touchdown was 180 knots. The wind at this point was determined to be about 050°M at 30 knots. Shortly after touchdown, the speed brakes and thrust reversers were deployed, and an engine pressure ratio (EPR) of 1.7 was reached 10 seconds after touchdown. Longitudinal deceleration was -0.37g within 1.3 seconds of touchdown, suggesting that a significant degree of effective wheel braking was achieved. With approximately 1100 feet of runway remaining, through a speed of 64 KIAS, reverse thrust increased to about 1.97 EPR on engine 1 and 2.15 EPR on engine 2. As the aircraft approached the end of the runway, the captain attempted to steer the aircraft to the right, toward the Delta taxiway intersection. Twenty-two seconds after touchdown, the aircraft exited the departure end of the runway into deep snow. The aircraft came to rest approximately 75 feet beyond and 53 feet to the right of the runway centreline on a heading of 235°M.
Probable cause:
Findings as to Causes and Contributing Factors:
1. A combination of excessive landing speed, extended touchdown point, and low runway friction coefficient resulted in the aircraft overrunning the runway.
Findings as to Risk:
1. Before departure from Halifax, the flight crew did not request nor did dispatch personnel inform the crew of the notice to airmen (NOTAM) advising of the instrument landing system's failure for Runway 11 at St. John's International Airport.
2. The St. John's dynamic wind information provided to the Gander Area Control Centre controller was inaccurate. The controller was not aware of this inaccuracy.
3. The crew applied tailwind corrections in accordance with company practices; however, these practices were not in accordance with those stated in the operations manual.
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain in Val d'Or

Date & Time: Feb 20, 2001 at 1900 LT
Operator:
Registration:
C-GNIE
Flight Type:
Survivors:
Yes
Schedule:
Rouyn – Val d’Or – Saint-Hubert
MSN:
31-7552047
YOM:
1975
Flight number:
APO1023
Location:
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
900
Captain / Total hours on type:
30.00
Circumstances:
A Piper PA-31-350, registration C-GNIE, serial number 31-7552047, was on a scheduled (APO1023) instrument flight rules mail service flight between Rouyn Airport, Quebec, and Val-d'Or Airport, Quebec, at approximately 1845 . After checking for prevailing weather conditions at the destination airport, the pilot decided to make a visual approach on runway 36. The pilot reported by radio at two miles on final approach for runway 36 and then stated that he was going to begin his approach again after momentarily losing visual contact with the runway. This was the last radio contact with the aircraft. No emergency locator transmitter signal was received by the flight service station specialist. Emergency procedures were initiated, and searches were conducted. The aircraft was found by a search and rescue team about three hours after the crash. The aircraft was lying about two miles southeast of the end of runway 36; it was substantially damaged. The pilot suffered serious injuries.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The environmental conditions and loss of visual ground references near Val-d'Or Airport were conducive to spatial disorientation. Because of a lack of instrument flight experience, the pilot probably became disoriented during the overshoot and was unable to regain control of the situation.
2. During the approach, the pilot did not plan to and did not pull up towards the centre of the airport, thereby contributing to spatial disorientation.
3. Although the pilot-in-command received training required by Transport Canada, Aéropro did not ensure that the pilot-in-command completed the required Pilot Proficiency Check (PPC) and was adequately supervised and experienced to conduct a night IFR flight safely as pilot-in-command.
Final Report:

Crash of a Piper PA-60 Aerostar (Ted Smith 602P) on Mt Okanagan: 4 killed

Date & Time: Dec 31, 2000 at 1205 LT
Registration:
N88AT
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Salt Lake City – Penticton
MSN:
62-0862-8165003
YOM:
1981
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
2500
Aircraft flight hours:
3052
Circumstances:
The Piper Aerostar 602P aircraft, registration N88AT, serial number 62P08628165003, with the pilot, who was also the owner, three passengers, and two dogs on board, took off from the Salt Lake City Airport, Utah, on an instrument flight rules flight to Penticton, British Columbia. At 1149 Pacific standard time, the Kamloops/Castlegar sector controller of Vancouver Centre passed N88AT a special weather observation for Penticton: Awinds calm; visibility : mile in snow; sky obscured; vertical visibility 700 feet; remarks snow eight [8/8 of the sky covered]; temperature zero; 1900 [1100 Pacific standard time] altimeter 30.21.@ When approaching Penticton, the pilot requested the localizer distance-measuring equipment B (LOC DME-B) approach to runway 16. When the pilot confirmed that he could complete the procedure turn within 13 miles of the Penticton airport, the controller issued an approach clearance for the LOC DME-B approach, with a restriction to complete the procedure turn within 13 miles of the Penticton airport. This restriction was to prevent possible conflicts between N88AT and aircraft taking off or carrying out missed approaches from runway 15 at Kelowna. The pilot reported to the Penticton Flight Service Station at 1203 Pacific standard time that he was by the Penticton non-directional beacon (NDB) outbound on the localizer, and he was given the latest runway condition report. When the aircraft then failed to respond to numerous radio calls from the Penticton Flight Service Station and Vancouver Centre, search and rescue staff were notified and a search initiated. The wreckage was found two days later, near the summit of Okanagan Mountain, in a wooded area, at an elevation of about 5100 feet above sea level. There were no survivors. The aircraft was destroyed but did not catch fire.
Probable cause:
Findings as to Causes and Contributing Factors:
1. For reasons not determined, the pilot did not adhere to the procedures depicted for the LOC DME-B approach to runway 16 at Penticton. As a result, the aircraft did not remain within the confines of protected airspace, was below the minimum safe altitude for the procedure turn, and struck the tower.
Findings as to Risk:
1. The approach was flown in weather conditions that virtually precluded the pilot from completing a landing.
Other Findings:
1. The pilot's flight medical certificate had expired one month prior to the accident, and no information could be found that he had submitted to an FAA medical during that time.
Final Report:

Crash of a De Havilland DHC-6 Twin Otter 100 off Vancouver

Date & Time: Nov 1, 2000 at 1510 LT
Operator:
Registration:
C-GGAW
Flight Phase:
Survivors:
Yes
Schedule:
Vancouver - Victoria
MSN:
086
YOM:
1967
Flight number:
8O151
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
15
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4000
Captain / Total hours on type:
2500.00
Copilot / Total flying hours:
2000
Copilot / Total hours on type:
1650
Circumstances:
A de Havilland DHC-6-100 float-equipped Twin Otter (serial number 086), operated by West Coast Air Ltd., was on a regularly scheduled flight as Coast 608 from Vancouver Harbour water aerodrome, British Columbia, to Victoria Harbour water aerodrome. The flight departed at about 1510 Pacific standard time with two crew members and 15 passengers on board. Shortly after lift-off, there was a loud bang and a noise similar to gravel hitting the aircraft. Simultaneously, a flame emanated from the forward section of the No. 2 (right-hand) engine, and this engine completely lost propulsion. The aircraft altitude was estimated to be between 50 and 100 feet at the time. The aircraft struck the water about 25 seconds later in a nose-down, right wing-low attitude. The right-hand float and wing both detached from the fuselage at impact. The aircraft remained upright and partially submerged while the occupants evacuated the cabin through the main entrance door and the two pilot doors. They then congregated on top of the left wing and fuselage. Within minutes, several vessels, including a public transit SeaBus, arrived at the scene. The SeaBus deployed an inflatable raft for the occupants, and they were taken ashore by several vessels and transported to hospital for observation. There were no serious injuries. The aircraft subsequently sank. All of the wreckage was recovered within five days.
Probable cause:
Findings as to Causes and Contributing Factors:
1. A planetary gear disintegrated in the propeller reduction gearbox of the No. 2 engine and caused the engine drive shaft to disconnect from the propeller, resulting in a loss of propulsion from this engine.
2. The planetary gear oil strainer screen wires fractured by fatigue as a consequence of the installation at the last overhaul. This created an unsafe condition and it is most probable that the release of wire fragments and debris from this strainer screen subsequently initiated or contributed to distress of the planetary gear bearing sleeve and resulted in the disintegration of the planetary gear.
3. Although airspeed was above Vmc at the time of the power loss, the aircraft became progressively uncontrollable due to power on the remaining engine not being reduced to relieve the asymmetric thrust condition until impact was imminent.
Findings as to Risk:
1. The propeller reduction gearboxes were inspected in accordance with the West Coast Air maintenance control manual. These inspections exceeded requirements of the de Havilland Equalized Maintenance Maximum Availability program. Since the last inspection, 46 hours of flight time before the accident, did not reveal any anomaly, a risk remains of adverse developments with
resulting consequences occurring during the unmonitored period between inspections.
2. Regulations require the installation of engine oil chip detectors, but not the associated annunciator system on the DHC-6. Without an annunciator system, monitoring of engine oil contamination is limited to the frequency and thoroughness of maintenance inspections. An annunciator system would have provided a method of continuous monitoring and may have warned the crew of the impending problem.
3. Although regulations do not require the aircraft to be equipped with an auto-feather system, its presence may have assisted the flight crew in handling the sudden loss of power by reducing the drag created by a windmilling propeller.
4. Since most air taxi and commuter operators use their own aircraft rather than a simulator for pilot proficiency training, higher-risk emergency scenarios can only be practiced at altitude and discussed in the classroom. As a result, pilots do not gain the benefit of a realistic experience during training.
Other Findings:
1. The fact that the aircraft remained upright and floating in daylight conditions contributed to the successful evacuation of the cabin without injury and enabled about half of the passengers to locate and don their life vests.
2. The aircraft was at low altitude and low airspeed at the time of power loss. The selection of full flaps may have contributed to a single-engine, high-drag situation, making a successful landing difficult.
Final Report:

Crash of a Short SC.7 Skyvan 3 Variant 100 in Port Radium: 3 killed

Date & Time: Oct 8, 2000 at 1520 LT
Type of aircraft:
Operator:
Registration:
C-FSDZ
Flight Type:
Survivors:
No
Schedule:
Yellowknife – Kugluktuk – Port Radium – Yellowknife
MSN:
1953
YOM:
1977
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
22000
Captain / Total hours on type:
1000.00
Copilot / Total flying hours:
280
Copilot / Total hours on type:
100
Circumstances:
At 1108 mountain daylight time on 08 October 2000, the Summit Air Charter's Short Brothers SC-7 Skyvan, serial number SH1953, departed on a visual flight rules six-hour flight from Yellowknife, Northwest Territories, to Kugluktuk, Nunavut, to Port Radium, Northwest Territories, and back to Yellowknife. The flight plan indicated a one-hour stop in Kugluktuk, with an estimated time of arrival at Yellowknife of 1710. The pilot-in-command was the chief pilot of Summit Air Charters Ltd. A cargo handler, who was also a pilot, was in the co-pilot's seat, and there was one passenger. When the aircraft failed to arrive at Yellowknife, Search and Rescue (SAR) were alerted and a search was begun. At 2202 SAR personnel confirmed that the SAR satellite was picking up an emergency locator transmitter signal in the vicinity of Port Radium. SAR aircraft were directed to the signal location and found the signal source but were not able to see the wreckage because of fog and freezing rain. The wreckage was found at 1309 the following day. The aircraft had struck the top of steeply rising hills along the east shore of Great Bear Lake, approximately 2.9 nautical miles northeast of the Port Radium airstrip. The crash site is approximately 440 feet above the lake surface and 250 feet above the airstrip elevation (see Appendix A). The aircraft was destroyed, and the three persons on board were fatally injured.
Probable cause:
Findings as to Causes and Contributing Factors:
1. Although the pilot and the aircraft were certified for instrument flight, the pilot apparently continued to fly in accordance with visual flight rules after encountering marginal weather conditions and reduced visibility.
2. For undetermined reasons, the pilot descended below the elevation of the terrain surrounding the airstrip, resulting in a controlled-flight-into-terrain accident.
Finding as to Risk:
1. Given the pilot's flying time during the 30 days before the accident, the pilot=s performance might have been affected by fatigue.
Final Report:

Crash of a Convair CV-580 in La Grande-4

Date & Time: Sep 27, 2000 at 1038 LT
Type of aircraft:
Operator:
Registration:
C-GFHH
Survivors:
Yes
Schedule:
Montreal – Rouyn – La Grande-3 (LG-3) – La Grande-4 (LG-4) – Montreal
MSN:
109
YOM:
1953
Flight number:
APZ180
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
18
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
15500
Captain / Total hours on type:
6000.00
Copilot / Total flying hours:
11000
Copilot / Total hours on type:
4000
Aircraft flight hours:
78438
Circumstances:
The Hydro-Québec Convair 340 (580), registration C-GFHH, serial number 109, with 18 passengers and 4 crew members on board, made an instrument flight rules flight from La Grande 3 to La Grande 4, Quebec. The aircraft touched down on the snow-covered runway at La Grande 4 approximately 800 feet beyond the runway threshold. Shortly after the nose wheel touched down and the pilot set the propellers to reverse pitch, the aircraft drifted to the right. Despite the attempts of the pilot flying (the captain) to correct, the aircraft continued its course and exited the south side of Runway 09 at approximately 50 knots. The aircraft travelled 350 feet over soft, rocky ground and came to rest about 120 feet outside the runway edge, about 2500 feet from the runway threshold. The flight crew followed the procedure to shut down the engines, but the left engine would not stop. On the captain's order, the first officer went into the passenger cabin and ordered an evacuation. All passengers exited the aircraft via the window emergency exits over the right wing. The left engine eventually shut down on its own after about 15 minutes. Five persons sustained minor injuries. The aircraft sustained substantial damage but did not catch fire.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The steering control valve lever was not reassembled in accordance with the specifications and the drawings in the overhaul manual and the maintenance manual: the lever was assembled with two washers instead of one, and the circumference of the bushing was 0.0005 inch greater than the circumference of the hole in the lever. These two deficiencies created additional resistance that
impeded the pivoting of the aircraft steering wheel.
2. The nylon locknuts were reinstalled during the repair of the steering control valve, contrary to the recommendation that they be used only once. The locknuts then came loose in service, creating play in the parts of the valve.
3. Incorrect interpretation of the problem and the influence of previous experience using the nose-gear steering wheel led the crew to make the flight despite their concern about the aircraft's nose-gear steering system.
Findings as to Risk:
1. The maintenance personnel of Precision Aero Components Inc. used the (incomplete) maintenance manual instead of the overhaul manual to overhaul and repair the steering control valve,
contributing to the incorrect reassembly of the valve.
2. The steering control valve lever was not fitted with a grease fitting, and the outside of the bushing was not grooved to allow adequate lubrication, thereby risking corrosion and seizure of the bushing inside the lever.
3. The limited experience and the lack of formal training of the maintenance personnel concerning the repair and the overhaul on the steering control valve might have contributed to the incorrect
reassembly of the steering control valve.
4. The pilot flying cut the electrical power, as required by the hard landing procedure. The left engine could therefore not be shut down, causing a risk of injury when the passengers evacuated.
5. The pilot flying cut the electrical power after the aircraft exited the runway, as required by the hard landing procedure. The electrical power required to operate the public address and alarm systems was thereby lost, and the evacuation could not be ordered promptly.
6. The evacuation slide automatic deployment system was inadvertently deactivated, which could have delayed the evacuation and compromised passenger safety.
7. After separating from the engine, the left propeller blades entered the fuselage and damaged an unoccupied seat.
Other Findings:
1. The numerous changes in ownership of the Convair type certificate and the lack of technical support from the current holder caused maintenance problems for Convair operators and approved
maintenance organizations (AMOs), particularly for recently established AMOs.

Crash of a De Havilland DHC-2 Turbo Beaver near Clearwater

Date & Time: Sep 22, 2000 at 1320 LT
Type of aircraft:
Operator:
Registration:
C-FOES
Flight Phase:
Survivors:
Yes
Schedule:
Clearwater - Clearwater
MSN:
1673
YOM:
1967
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5000
Captain / Total hours on type:
900.00
Circumstances:
The de Havilland DHC-2T Beaver floatplane, serial number 1673TB43, was engaged in aerial application of fish fry to several lakes near Clearwater, British Columbia. The pilot and one other person were on board. The aircraft took off from Clearwater at about 1230 Pacific daylight time (PDT) to begin a planned series of drops to nearby lakes. The aircraft had dropped fish in four lakes before proceeding to Broken Hook Lake.When the aircraft was on approach to the northwestern end of Broken Hook Lake, the pilot reportedly advanced the power lever, but the engine did not respond. At this time, the aircraft was about 100 feet above ground level and struck several treetops. Within seconds, the aircraft descended, struck the terrain, and crashed into trees. The two occupants were seriously injured, and the aircraft was destroyed. There was no fire. The accident occurred at 1320 PDT.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The pilot did not avoid the trees that obstructed his immediate flight path on descent to the lake.
2. The damage to the aircraft from the tree-strike seriously compromised the pilot's ability to control the aircraft, to the point where continued flight was impossible.
3. The pilot and the passenger suffered serious injuries. It is highly likely that proper use of a passenger restraint system would have lessened the injuries to both persons.
Findings as to Risk:
1. Canadian regulations regarding the use of seats and seat restraint systems are not sufficiently clear about high-risk, aerial work operations, such as aerial application.
2. Transport Canada was not advised of the fish-dropping operations and was unaware that the passenger in the cabin was unrestrained during high-risk operations.
3. Canadian regulations do not require specific training in aerial application techniques, such as fish-dropping.
4. The installation of the fish-hopper equipment constituted an aircraft modification, which had not been approved by Transport Canada.
Other Findings:
1. The operator did not maintain a proper logbook.
Final Report: