Crash of a Beechcraft A100 King Air in Québec: 7 killed

Date & Time: Jun 23, 2010 at 0559 LT
Type of aircraft:
Operator:
Registration:
C-FGIN
Flight Phase:
Survivors:
No
Schedule:
Québec - Seven Islands - Natashquan
MSN:
B-164
YOM:
1973
Flight number:
APO201
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
7
Captain / Total flying hours:
3046
Captain / Total hours on type:
372.00
Copilot / Total flying hours:
2335
Copilot / Total hours on type:
455
Aircraft flight hours:
19665
Aircraft flight cycles:
16800
Circumstances:
Aircraft was making an instrument flight rules flight from Québec to Sept-Îles, Quebec. At 0557 Eastern Daylight Time, the crew started its take-off run on Runway 30 at the Québec/Jean Lesage International Airport; 68 seconds later, the co-pilot informed the airport controller that there was a problem with the right engine and that they would be returning to land on Runway 30. Shortly thereafter, the co-pilot requested aircraft rescue and fire-fighting (ARFF) services and informed the tower that the aircraft could no longer climb. A few seconds later, the aircraft struck the ground 1.5 nautical miles from the end of Runway 30. The aircraft continued its travel for 115 feet before striking a berm. The aircraft broke up and caught fire, coming to rest on its back 58 feet further on. The 2 crew members and 5 passengers died in the accident. No signal was received from the emergency locator transmitter (ELT).
Probable cause:
Findings as to Causes and Contributing Factors:
1. After the take-off at reduced power, the aircraft performance during the initial climb was lower than that established at certification.
2. The right engine experienced a problem in flight that led to a substantial loss of thrust.
3. The right propeller was not feathered; therefore, the rate of climb was compromised by excessive drag.
4. The absence of written directives specifying which pilot was to perform which tasks may have led to errors in execution, omissions, and confusion in the cockpit.
5. Although the crew had the training required by regulation, they were not prepared to manage the emergency in a coordinated, effective manner.
6. The priority given to ATC communications indicates that the crew did not fully understand the situation and were not coordinating their tasks effectively.
7. The impact with the berm caused worse damage to the aircraft.
8. The aircraft’s upside-down position and the damage it sustained prevented the occupants from evacuating, causing them to succumb to the smoke and the rapid, intense fire.
9. The poor safety culture at Aéropro contributed to the acceptance of unsafe practices.
10. The significant measures taken by TC did not have the expected results to ensure compliance with the regulations, and consequently unsafe practices persisted.
Findings as to Risk:
1. Deactivating the flight low pitch stop system warning light or any other warning system contravenes the regulations and poses significant risks to flight safety.
2. The maintenance procedures and operating practices did not permit the determination of whether the engines could produce the maximum power of 1628 ft-lb required at take-off and during emergency procedures, posing major risks to flight safety.
3. Besides being a breach of regulations, a lack of rigour in documenting maintenance work makes it impossible to determine the exact condition of the aircraft and poses major risks to flight safety.
4. The non-compliant practice of not recording all defects in the aircraft journey log poses a safety risk because crews are unable to determine the actual condition of the aircraft at all times, and as a result could be deprived of information that may be critical in an emergency.
5. The lack of an in-depth review by TC of SOPs and checklists of 703 operators poses a safety risk because deviations from aircraft manuals are not detected.
6. Conditions of employment, such as flight hours–based remuneration, can influence pilots’ decisions, creating a safety risk.
7. The absence of an effective non-punitive and confidential voluntary reporting system means that hazards in the transportation system may not be identified.
8. The lack of recorded information significantly impedes the TSB’s ability to investigate accidents in a timely manner, which may prevent or delay the identification and communication of safety deficiencies intended to advance transportation safety.
Final Report:

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

Date & Time: Dec 9, 2009 at 2250 LT
Type of aircraft:
Operator:
Registration:
C-GPBA
Survivors:
Yes
Schedule:
Val d'Or - Chicoutimi
MSN:
B-215
YOM:
1975
Flight number:
ET822
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
3500
Captain / Total hours on type:
1000.00
Copilot / Total flying hours:
1000
Copilot / Total hours on type:
150
Circumstances:
The Beechcraft was on an instrument flight rules flight between Val-d’Or and Chicoutimi/Saint-Honoré, Quebec, with 2 pilots and 2 passengers on board. At 2240 Eastern Standard Time, the aircraft was cleared for an RNAV (GNSS) Runway 12 approach and switched to the aerodrome traffic frequency. At 2250, the International satellite system for search and rescue detected the aircraft’s emergency locator transmitter signal. The aircraft was located at 0224 in a wooded area approximately 3 nautical miles from the threshold of Runway 12, on the approach centreline. Rescuers arrived on the scene at 0415. The 2 pilots were fatally injured, and the 2 passengers were seriously injured. The aircraft was destroyed on impact; there was no post-crash fire.
Probable cause:
Findings as to Causes and Contributing Factors:
For undetermined reasons, the crew continued its descent prematurely below the published approach minima, leading to a controlled flight into terrain (CFIT).
Findings as to Risk:
1. The use of the step-down descent technique rather than the stabilized constant descent angle (SCDA) technique for non-precision instrument approaches increases the risk of an approach and landing accident (ALA).
2. The depiction of the RNAV (GNSS) Runway 12 approach published in the Canada Air Pilot (CAP) does not incorporate recognized visual elements for reducing ALAs, as recommended in Annex 4 to the Convention, thereby reducing awareness of the terrain.
3. The installation of a terrain awareness warning system (TAWS) is not yet a requirement under the Canadian Aviation Regulations (CARs) for air taxi operators. Until the changes to regulations are put into effect, an important defense against ALAs is not available.
4. Most air taxi operators are unaware of and have not implemented the FSF ALAR task force recommendations, which increases the risk of a CFIT accident.
5. Approach design based primarily on obstacle clearance instead of the 3° optimum angle increases the risk of ALAs.
6. The lack of information on the SCDA technique in Transport Canada reference manuals means that crews are unfamiliar with this technique, thereby increasing the risk of ALAs.
7. Use of the step-down descent technique prolongs the time spent at minimum altitude, thereby increasing the risk of ALAs.
8. Pilots are not sufficiently educated on instrument approach procedure design criteria. Consequently, they tend to use the CAP published altitudes as targets, and place the aircraft at low altitude prematurely, thereby increasing the risk of an ALA.
9. Where pilots do not have up-to-date information on runway conditions needed to check runway contamination and landing distance performance, there is an increased risk of landing accidents.
10. Non-compliance with instrument flight rules (IFR) reporting procedures at uncontrolled airports increases the risk of collision with other aircraft or vehicles.
11. If altimeter corrections for low temperature and remote altimeter settings are not accurately applied, obstacle clearance will be reduced, thereby increasing the CFIT risk.
12. When cockpit recordings are not available to an investigation, this may preclude the identification and communication of safety deficiencies to advance transportation safety.
13. Task-induced fatigue has a negative effect on visual and cognitive performance which can diminish the ability to concentrate, operational memory, perception and visual acuity.
14. Where an emergency locator transmitter (ELT) is not registered with the Canadian Beacon Registry, the time needed to contact the owner or operator is increased which could affect occupant rescue and survival.
15. If the tracking of a call to 911 emergency services from a cell phone is not accurate, search and rescue efforts may be misdirected or delayed which could affect occupant rescue and survival.
Other Findings:
1. Weather conditions at the alternate airport did not meet CARs requirements, thereby reducing the probability of a successful approach and landing at the alternate airport if a diversion became necessary.
2. Following the accident, none of the aircraft exits were usable.
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 Piper PA-31-350 Navajo Chieftain in Grand Lac Germain: 1 killed

Date & Time: Apr 1, 2007 at 0700 LT
Operator:
Registration:
C-FTIW
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Seven Islands - Wabush
MSN:
31-7752123
YOM:
1977
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
5475
Captain / Total hours on type:
790.00
Circumstances:
The aircraft, operated by Aéropro, was on a visual flight rules (VFR) flight from Sept-Îles, Quebec, to Wabush, Newfoundland and Labrador. The pilot, who was the sole occupant, took off around 0630 eastern daylight time. Shortly before 0700, the aircraft turned off its route and proceeded to Grand lac Germain to fly over the cottage of friends. Around 0700, the aircraft overflew the southeast bay of Grand lac Germain. The pilot then overflew a second time. The aircraft proceeded northeast and disappeared behind the trees. A few seconds later, the twin-engine aircraft crashed on the frozen surface of the lake. The pilot was fatally injured; the aircraft was destroyed by impact forces.
Probable cause:
Finding as to Causes and Contributing Factors:
1. The aircraft stalled at an altitude that was too low for the pilot to recover.
Findings as to Risk:
1. The aircraft was flying at an altitude that could lead to a collision with an obstacle and that did not allow time for recovery.
2. The steep right bank of the aircraft considerably increased the aircraft’s stall speed.
3. The form used to record the pilot’s flight time, flight duty time, and rest periods had not been updated for over a month; this did not allow the company manager to monitor the pilot’s hours.
4. At the time of the occurrence, the Aéropro company operations manual did not make provision for the restrictions on daytime VFR flights prescribed in Section 703.27 of the Canadian Aviation Regulations.
Other Findings:
1. The fact that the aircraft was not equipped with a flight data recorder (FDR) or a cockpit voice recorder (CVR) limited the information available for the investigation and limited the scope of the investigation.
2. Since the aircraft was on a medical evacuation (MEDEVAC) flight, the company mistakenly advised the search and rescue centre that there were two pilots on board the aircraft when it was reported missing.
Final Report:

Crash of a De Havilland DHC-2 Beaver I near La Grande-4

Date & Time: Jan 21, 2007 at 1212 LT
Type of aircraft:
Operator:
Registration:
C-GUGQ
Flight Phase:
Survivors:
Yes
MSN:
400
YOM:
1952
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
1200
Captain / Total hours on type:
400.00
Circumstances:
The ski-equipped aircraft took off around 1130 eastern standard time from Mirage Outfitter, located 60 miles east of La Grande-4 Airport, Quebec, with a pilot and four passengers on board, to locate caribou herds. About 40 minutes after departure, the engine stopped as a result of fuel starvation. The pilot was not able to regain power and made a forced landing on rugged ground. The aircraft was heavily damaged and two passengers were seriously injured. The pilot used a satellite telephone to request assistance. First-aid assistance arrived by helicopter about 1 hour 30 minutes after the occurrence. The aircraft fuel system had been modified after the installation of wings made by Advanced Wing Technologies Corporation.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The engine stopped as a result of fuel starvation; the amount of fuel in the wings was less than the amount estimated by the pilot, the fuel senders gave an incorrect reading, and the low fuel pressure warning light could illuminate randomly.
2. The engine stopped at low altitude, which reduced the time needed to complete the emergency procedure. The pilot was unable to glide to the lake and made a forced landing on an unsuitable terrain, causing significant damage to the aircraft and injuries to the occupants.
Findings as to Risk:
1. The wing tank selection system was subject to icing in cold weather, and the pilots adopted the practice to place the wing tank selector in the middle position, which is contrary to the aircraft flight manual supplement instructions and a placard posted on the instrument panel.
2. When the change to the type design was approved through issuance of the Supplementary Type Certificate (STC), Transport Canada did not notice the fact that the fuel senders and triple fuel level gauge did not meet airworthiness standards; Transport Canada issued an STC that contained several deficiencies. 3. Storage of the shoulder harnesses underneath the aircraft interior covering made them inaccessible; since the pilot and the front seat passenger did not wear their shoulder harness, their protection was reduced.
Final Report:

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 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:

Crash of a BAe 125-600B in Bromont

Date & Time: Feb 21, 2005 at 1818 LT
Type of aircraft:
Operator:
Registration:
N21SA
Survivors:
Yes
Schedule:
Montreal - Bromont
MSN:
256006
YOM:
1973
Location:
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5000
Captain / Total hours on type:
550.00
Copilot / Total flying hours:
1700
Copilot / Total hours on type:
100
Circumstances:
The aircraft, operated by Scott Aviation, with two crew members and four passengers on board, took off from Montréal, Quebec, at 1756 eastern standard time, for a night instrument flight rules flight to Bromont, Quebec. Upon approaching Bromont, the co-pilot activated the lighting system and contacted the approach UNICOM (private advisory service). The flight crew was advised that the runway edge lights were out of order. However, the approach lights and the visual approach slope indicator did turn on. The flight crew executed the approach, and the aircraft touched down at 1818 eastern standard time, 300 feet to the left of Runway 05L and 1800 feet beyond the threshold. It continued on its course for a distance of approximately 1800 feet before coming to a stop in a ditch. The crew tried to stop the engines, but the left engine did not stop. The co-pilot entered the cabin to direct the evacuation. One of the passengers tried to open the emergency exit door, but was unsuccessful. All of the aircraft’s occupants exited through the main entrance door. Both pilots and one passenger sustained serious injuries, and the three remaining passengers received minor injuries. The aircraft suffered major damage.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The flight crew attempted a night landing in the absence of runway edge lights. The aircraft touched down 300 feet to the left of Runway 05L and 1800 feet beyond the threshold.
2. The runway was not closed for night use despite the absence of runway edge lights. Nothing required it to be closed.
3. Poor flight planning, non-compliance with regulations and standard operating procedures (SOPs), and the lack of communications between the two pilots reveal a lack of airmanship on the part of the crew, which contributed to the accident.
Findings as to Risk:
1. Because they had not been given a safety briefing, the passengers were not familiar with the use of the main door or the emergency exit, which could have delayed the evacuation, with serious consequences.
2. The armrest of the side seat had not been removed as required and was blocking access to the emergency exit, which could have delayed the evacuation, with serious consequences.
3. Because they had not been given a safety briefing, the passengers seated in the side seats did not know that they should have worn shoulder straps and did not wear them, so they were not properly protected.
4. The possibility of flying to an airport that does not meet the standards for night use gives pilots the opportunity to attempt to land there, which in itself increases the risk of an accident.
5. The landing performance diagrams and the chart used to determine the landing distance did not enable the flight crew to ensure that the runway was long enough for a safe landing on a snow-covered surface.
Final Report:

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

Date & Time: Jun 14, 2004 at 1340 LT
Type of aircraft:
Registration:
C-GJST
Flight Type:
Survivors:
No
Schedule:
Gatineau - Gatineau
MSN:
1368
YOM:
1959
Location:
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
1709
Captain / Total hours on type:
700.00
Circumstances:
The pilot and sole occupant of the DHC-2 seaplane, registration C-GJST, serial number 1368, was on his first flight of the season on the Ottawa River at Gatineau, Quebec. This training flight, conducted according to visual flight rules, was to consist of about 12 touch-and-go landings. The aircraft took off at approximately 1300 eastern daylight time, and made several upwind touch-and-go landings in a westerly direction. At approximately 1340 eastern daylight time, the aircraft was seen about 50 feet above the surface of the water proceeding downwind in an easterly
direction, in a nose-down attitude of over 20 degrees. The right float then struck the water and the aircraft tumbled several times, breaking up on impact. Despite the waves and gusting wind on the river, some riverside residents who witnessed the accident attempted a rescue, but the aircraft sank before they could reach it. Even though the pilot was wearing a seat-belt, he sustained head injuries at impact and drowned.
Probable cause:
Finding as to Causes and Contributing Factors:
1. The aircraft struck the water for undetermined reasons.
Findings as to Risk:
1. The certificate of airworthiness was not in effect at the time of the accident because of the airworthiness directives that had not been completed.
2. The distress signal emitted by the fixed, automatic emergency locator transmitter (ELT) was not received because of the reduced range of the signal once the ELT was submerged, which could have increased the response time of search and rescue units if there had been no witnesses to the accident.
3. The pilot had not made a training flight with an instructor for more than 19 months, which could have resulted in a degradation of his skills and decision-making process.
Final Report:

Crash of a Beechcraft A100 King Air in Chibougamau

Date & Time: Apr 19, 2004 at 1018 LT
Type of aircraft:
Operator:
Registration:
C-FMAI
Survivors:
Yes
Schedule:
Quebec - Chibougamau
MSN:
B-145
YOM:
1973
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
11338
Captain / Total hours on type:
2600.00
Copilot / Total flying hours:
1176
Copilot / Total hours on type:
400
Circumstances:
The Beechcraft A100, registration C-FMAI, operated by Myrand Aviation Inc., was on a chartered instrument flight rules flight from QuÈbec/Jean Lesage International Airport, Quebec, to Chibougamau/Chapais Airport, Quebec, with two pilots and three passengers on board. The copilot was at the controls and was flying a non-precision approach for Runway 05. The pilot-in-command took the controls less than one mile from the runway threshold and saw the runway when they were over the threshold. At approximately 1018 eastern daylight time, the wheels touched down approximately 1500 feet from the end of Runway 05. The pilot-in-command realized that the remaining landing distance was insufficient. He told the co-pilot to retract the flaps and applied full power, but did not reveal his intentions. The co-pilot cut power, selected reverse pitch and applied full braking. The aircraft continued rolling through the runway end, sank into the gravel and snow, and stopped abruptly about 500 feet past the runway end. The aircraft was severely damaged. None of the occupants were injured.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The aircraft was positioned over the runway threshold at an altitude that did not allow a landing at the beginning of the runway, and this, combined with a tailwind component and the wet runway surface, resulted in a runway excursion.
2. Failure to follow standard operating procedures and a lack of crew coordination contributed to confusion on landing, which prevented the crew from aborting the landing and executing a missed approach.
3. The pilot-in-command held several management positions within the company and controlled the pilot hiring and dismissal policies. This situation, combined with the level of experience of the co-pilot compared with that of the pilot-in-command, had an impact on crew cohesiveness.
Findings as to Risk:
1. The pilot-in-command of C-FMAI decided to execute an approach for Runway 05 without first ensuring that there would be no possible risk of collision with the other aircraft.
2. The regulatory requirement to conform to or avoid the traffic pattern formed by other aircraft is not explicit as to how the traffic pattern should be avoided, in terms of either altitude or distance, which can result in risks of collision.
3. The regulations do not indicate whether the missed approach segment should be considered part of the traffic pattern; this situation can lead pilots operating in uncontrolled airspace to believe that they are avoiding another aircraft executing an instrument approach when in reality a risk of collision exists.
Final Report: