Crash of a Beechcraft 350 Super King Air in Thunder Bay

Date & Time: Jan 31, 2022 at 1222 LT
Operator:
Registration:
C-GEAS
Survivors:
Yes
Schedule:
Trenton - Thunder Bay
MSN:
FL-17
YOM:
1990
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from RCAF Trenton on behalf of the RCAF, the twin engine aircraft apparently landed hard at Thunder Bay Airport. After touchdown on runway 25, it went out of control and veered off runway into a snow covered area. All three crew members evacuated safely while the aircraft suffered severe damages to wings and tail. The fuselage also broke in two.

Crash of a Socata TBM-910 in Westlock

Date & Time: Oct 10, 2021 at 1102 LT
Type of aircraft:
Registration:
C-FFYM
Flight Type:
Survivors:
Yes
Schedule:
Vernon – Calgary – Westlock
MSN:
1190
YOM:
2017
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total hours on type:
235.00
Aircraft flight hours:
449
Circumstances:
The airplane was conducting an instrument flight rules flight from Vernon Airport, British Columbia, to Westlock Aerodrome, Alberta, with a stop at Calgary/Springbank Airport, Alberta, to pick up passengers, after which 1 pilot and 3 passengers were on board. At 1102:26 Mountain Daylight Time, while the aircraft was landing on Runway 28 at Westlock Aerodrome, the aircraft bounced and the pilot initiated a go-around. During the application of engine power for the go-around, the aircraft rolled to the left, struck the runway inverted, and came to rest on the runway’s south side. The 3 passengers exited the aircraft through the main cabin door with the assistance of persons nearby. One passenger received serious injuries, and the other 2 had minor injuries. The pilot, who was seriously injured, was trapped in the cockpit for approximately 2 hours before first responders could safely rescue him from the wreckage. An emergency locator transmitter signal was received by the search and rescue satellite system. The aircraft was significantly damaged and there was no post-impact fire.
Probable cause:
Findings as to causes and contributing factors:
1. The aircraft joined the final approach well above the optimal 3° descent path and, during the steep approach that followed, the aircraft’s airspeed continually decelerated and resulted in an unstabilized approach.
2. On short final, the pilot reduced the rate of descent by increasing pitch rather than by adding power. As a result, the airspeed continued to decrease and the aircraft entered a stall, resulting in a hard landing and a subsequent bounce.
3. During the attempted rejected landing, the aircraft entered a 25° nose-high attitude and approached a stall condition. This low-speed condition combined with the high power setting resulted in the aircraft entering a rapid roll to the left and striking the runway in an inverted attitude.
4. The passengers did not receive a safety briefing before departure or before landing, and multiple items in the cabin were not secured. As a result, 1 passenger sustained serious injuries due to the deceleration forces and the loose items that were thrown around in the cabin during the accident.
5. The pilot was not wearing the available shoulder harness, and his torso was unrestrained during the impact. As a result, he sustained serious injuries.

Findings as to risk:
1. If pilots do not declare all health issues to Transport Canada Civil Aviation Medical Examiners and pilots’ family physicians do not declare issues assessed to be a risk to aviation safety to Transport Canada, there is an increased risk that pilots will operate with diagnosed medical conditions or medical side effects that could affect flight safety.
2. If an aircraft propeller is rotating and passengers are not supervised during boarding operations, there is a risk that passengers may inadvertently contact the propeller, potentially causing fatal injuries.

Other findings:
1. Following a review of the pilot’s medical history and prescription medication use, the investigation determined that the medication did not contribute to the accident.
Final Report:

Crash of a Rockwell Grand Commander 690B in Thunder Bay: 1 killed

Date & Time: Aug 16, 2021 at 2109 LT
Operator:
Registration:
C-GYLD
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Thunder Bay – Dryden
MSN:
690-11426
YOM:
1977
Flight number:
BD160
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
2662
Captain / Total hours on type:
230.00
Aircraft flight hours:
7620
Circumstances:
The airplane, operated by MAG Aerospace Canada Corp. as flight BD160, was conducting a visual flight rules flight from Thunder Bay Airport, Ontario, to Dryden Regional Airport, Ontario, with only the pilot on board. At 2109 Eastern Daylight Time, the aircraft began a takeoff on Runway 12. Shortly after rotation, the aircraft entered a left bank, continued to roll, and then struck the surface of Runway 07 in an inverted attitude. The pilot was fatally injured. The aircraft was destroyed by the impact and postimpact fire. The emergency locator transmitter activated on impact.
Probable cause:
Findings as to causes and contributing factors:
1. After takeoff from Runway 12 at Thunder Bay Airport, Ontario, as the pilot conducted a rapid, low-level, climbing steep turn, the aircraft entered an accelerated stall that resulted in a loss of control and subsequent collision with the surface of Runway 07 in an inverted attitude.
2. The decision to conduct the rapid, low-level, climbing steep turn was likely influenced by an altered perception of risk from previous similar takeoffs that did not result in any adverse consequences.

Findings as to risk:
1. If air traffic controllers engage in communications that may be perceived by pilots to encourage unusual flight manoeuvres, pilots may perceive this encouragement as a confirmation that the manoeuvres are acceptable to perform, increasing the risk of an accident.
2. If NAV CANADA’s reporting procedures do not contain specific criteria for situations where air traffic services personnel perceive aircraft to be conducting unsafe flight manoeuvres, there is a risk that these manoeuvres will continue and result in an accident.

Other findings
1. Most of the wires that comprised the elevator trim cable failed before the impact as a result of excessive wear; however, this did not contribute to the occurrence because the trim tab remained in the normal take-off position.
Final Report:

Crash of a Piper PA-60-602P Super 700 Aerostar on Gabriola Island: 3 killed

Date & Time: Dec 10, 2019 at 1805 LT
Operator:
Registration:
C-FQYW
Flight Type:
Survivors:
No
Schedule:
Cabo San Lucas – Chino – Bishop – Nanaimo
MSN:
60-8265-020
YOM:
1982
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
320
Aircraft flight hours:
5752
Circumstances:
On 09 December 2019, a private Piper Aerostar PA-60-602P aircraft (registration C-FQYW, serial number 60-8265020), departed Cabo San Lucas International Airport (MMSL), Baja California Sur, Mexico, with 3 people on board, for a 2-day trip to Nanaimo Airport (CYCD), British Columbia (BC). As planned the aircraft stopped for an overnight rest at Chino Airport (KCNO), California, U.S. At 1142, on 10 December 2019, the aircraft departed KCNO on a visual flight rules (VFR) flight plan to Bishop Airport (KBIH), California, U.S., for a planned fuel stop. The aircraft departed KBIH at approximately 1425 on an instrument flight rules (IFR) flight plan to CYCD. On 10 December 2019, night started at 1654. At 1741, the Vancouver area control centre air traffic controller advised the pilot that an aerodrome special meteorological report (SPECI) had been issued for CYCD at 1731. The SPECI reported visibility as 2 ½ statute miles (SM) in light drizzle and mist, with an overcast ceiling of 400 feet above ground level (AGL). The pilot informed the controller that he would be conducting an instrument landing system (ILS) approach for Runway 16. At 1749, when the aircraft was approximately 32 nautical miles (NM) south of CYCD, the pilot contacted the controller to inquire about the weather conditions at Victoria International Airport (CYYJ), BC. The controller informed the pilot that a SPECI was issued for CYYJ at 1709 and it reported the visibility as 5 SM in mist, a broken ceiling at 600 feet AGL, and an overcast layer at 1200 feet AGL. The controller provided the occurrence flight with pilot observations from another aircraft that had landed at CYCD approximately 15 minutes before. That crew had reported being able to see the Runway 16 approach lights at minimums, i.e., at 373 feet AGL. Between 1753 and 1802, the controller provided vectors to the pilot in order to intercept the ILS localizer. At 1803, the controller observed that the aircraft had not intercepted the localizer for Runway 16. The aircraft had continued to the southwest, past the localizer, at an altitude of 2100 feet above sea level (ASL) and a ground speed of 140 knots. The controller queried the pilot to confirm that he was still planning to intercept the ILS for Runway 16. The pilot confirmed that he would be intercepting the ILS as planned. The aircraft made a heading correction and momentarily lined up with the localizer before beginning a turn to the west. At 1804:03, the pilot requested vectors from the controller and informed him that he “just had a fail.” The controller responded with instructions to “turn left heading zero nine zero, tight left turn.” The pilot asked the controller to repeat the heading. The controller responded with instructions to “…turn right heading three six zero.” The pilot acknowledged the heading; however, the aircraft continued turning right beyond the assigned heading while climbing to 2500 feet ASL and slowing to a ground speed of 80 knots. The aircraft then began to descend, picking up speed as it was losing altitude. At 1804:33, the aircraft descended to 1800 feet ASL and reached a ground speed of 160 knots. At 1804:40, the pilot informed the air traffic controller that the aircraft had lost its attitude indicator.Footnote6 At the same time, the aircraft was climbing into a 2nd right turn. At 1804:44, the air traffic controller asked the pilot what he needed from him; the pilot replied he needed a heading. The controller provided the pilot with a heading of three six zero. At 1804:47, the aircraft reached an altitude of 2700 feet ASL and a ground speed of 60 knots. The aircraft continued its right turn and began to lose altitude. The controller instructed the pilot to gain altitude if he was able to; however, the pilot did not acknowledge the instruction. The last encoded radar return for the aircraft was at 1805:26, when the aircraft was at 300 feet ASL and travelling at a ground speed of 120 knotsControl of the aircraft was lost. The aircraft collided with a power pole and trees in a wooded park area on Gabriola Island, BC, and then impacted the ground. The aircraft broke into pieces and caught fire. The 3 occupants on board received fatal injuries. As a result of being damaged in the accident, the emergency locator transmitter (Artex ME406, serial number 188-00293) did not activate.
Probable cause:
The occurrence aircraft was equipped with a BendixKing KI 825 electronic horizontal situation indicator (HSI) that was interfaced to the flight control system and GPS (global positioning system) Garmin GNS530W/430W. The HSI also supplies the autopilot system with heading information. The investigation determined that the HSI had failed briefly during operation on 22 November 2019 and a 2nd time, 3 days later, on 26 November 2019. The KI 825 HSI is electrically driven and therefore is either on and working, or off and dark with no display. The aircraft owner was in contact with an aircraft maintenance organization located at Boundary Bay Airport (CZBB), BC, and an appointment to bring the occurrence aircraft in for troubleshooting of the 2 brief HSI malfunctions had been made for 11 December 2019, i.e., the day after the accident. In total, 13 flights had been conducted after the 1st failure of the HSI. There were no journey log entries for defects with the HSI or evidence of maintenance completed. RegulationsFootnote9 require that defects that become apparent during flight operations be entered in the aircraft journey logbook, and advisory guidance in the regulatory standardsFootnote10 states that all equipment required for a particular flight or type of operation, such as the HSI in this case, be functioning correctly before flight. The HSI was destroyed in the accident and the investigation was unable to determine if it was operational on impact. Similarly, it could not be determined if the HSI was supplying the autopilot with heading information, or if the autopilot was engaged during the approach.
Final Report:

Crash of a De Havilland DHC-3 Otter off Little Grand Rapids: 3 killed

Date & Time: Oct 26, 2019 at 0845 LT
Type of aircraft:
Operator:
Registration:
C-GBTU
Survivors:
No
Schedule:
Bissett - Little Grand Rapids
MSN:
209
YOM:
1957
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
9500
Captain / Total hours on type:
5800.00
Aircraft flight hours:
16474
Circumstances:
At approximately 0745 Central Daylight Time on 26 October 2019, the Blue Water Aviation float-equipped deHavillandDHC-3 Otteraircraft (registration C-GBTU, serial number 209) departed Bissett Water Aerodrome, Manitoba, with the pilot, 2 passengers, and approximately 800 pounds of freight on board. The destination was Little Grand Rapids, Manitoba, on the eastern shore of Family Lake. At approximately 0845, while on approach to Family Lake, the aircraft’s right wing separated from the fuselage. The aircraft then entered a nose-down attitudeand struck the water surface of the lake. The pilot and the 2 passengers were fatally injured. The aircraft was destroyed by impact forces. The emergency locator transmitter activated momentarily.
Probable cause:
Findings as to causes and contributing factors:
These are conditions, acts or safety deficiencies that were found to have caused or contributed to this occurrence.
1. A fatigue fracture originated in the bolt hole bore of the right-hand wing lift strut’s upper outboard lug plate, and eventually led to an overstress fracture of the right-hand wing lift strut’s upper outboard and inboard lug plates during the left turn prior to the final approach.
2. The failure of the outboard and inboard lug plates led to the separation of the righthand wing lift strut from the wing and, subsequently, the separation of the right wing from the aircraft.

Findings as to risk:
These are conditions, unsafe acts or safety deficiencies that were found not to be a factor in this occurrence but could have adverse consequences in future occurrences.
1. If operational flight plans data and load calculations are not available, there is a risk that, in the event of a missing aircraft or accident, aircraft information, including its number of occupants, route, cargo, and weight and balance information, will not be available for search and rescue operations or accident investigation.

Other findings:
These items could enhance safety, resolve an issue of controversy, or provide a data point for future safety studies.
1. The detailed visual inspection prescribed in the Viking Air Ltd. Supplementary Inspection and Corrosion Control Manual, and required by Airworthiness DirectiveCF2018-4, did not identify cracks that could form in the right-hand wing strut’s upper outboard lug plate.
Final Report:

Crash of a Cessna 208B Grand Caravan near Mayo: 2 killed

Date & Time: Aug 6, 2019 at 1113 LT
Type of aircraft:
Operator:
Registration:
C-FSKF
Flight Phase:
Survivors:
No
Site:
Schedule:
Rackla - Mayo
MSN:
208B-0673
YOM:
1998
Location:
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
1694
Captain / Total hours on type:
212.00
Aircraft flight hours:
19060
Circumstances:
At 1101 Pacific Daylight Time on 06 August 2019, the Alkan Air Ltd. Cessna 208B Grand Caravan aircraft (registration C‐FSKF, serial number 208B0673) departed Rau Strip, Yukon, on a visual flight rules company flight itinerary to Mayo Airport, Yukon. The aircraft had 1 pilot, 1 passenger, and cargo on board. At 1113, the aircraft entered instrument meteorological conditions and struck rising terrain in a box canyon shortly after. The crash occurred approximately 25 nautical miles east‐northeast of Mayo Airport, at an elevation of 5500 feet above sea level. The Canadian Mission Control Centre did not receive a signal from the aircraft’s 406 MHz emergency locator transmitter. Eyewitnesses from a nearby exploration camp arrived at the site after approximately 1 hour. Royal Canadian Mounted Police and emergency medical services arrived on site approximately 90 minutes after the accident. The pilot and passenger received fatal injuries. The aircraft was destroyed; there was a brief post‐impact fire.
Probable cause:
Findings as to causes and contributing factors:
These are conditions, acts or safety deficiencies that were found to have caused or contributed to this occurrence.
1. The pilot’s decision making was influenced by several biases and, as a result, the flight departed and subsequently continued into poor weather conditions in mountainous terrain.
2. The high speed at low altitude and low forward visibility reduced the opportunities for the pilot to take alternative action to avoid terrain.
3. Within the box canyon, the canyon floor elevation increased abruptly within less than 1 NM and the low visibility prevented the pilot from detecting this and taking sufficient actions to prevent collision with terrain.
4. When the pilot turned into the box canyon, the terrain awareness and warning system aural alerts were ineffective in warning the pilot about the rising terrain either because he had already heard multiple similar alerts in the preceding minutes, or because he had silenced the alerts.

Findings as to risk:
These are conditions, unsafe acts, or safety deficiencies that were found not to be a factor in this occurrence but could have adverse consequences in future occurrences.
1. If administrative safety defences are not used as intended, it increases the risk that the hazards associated with the flight will not be identified and mitigated.

Other findings:
These items could enhance safety, resolve an issue of controversy, or provide a data point for future safety studies.
1. The pilot held a valid instrument rating and the aircraft was equipped to fly in instrument meteorological conditions. However, there were no scenarios in the pilot’s flying history on the Cessna 208B Grand Caravan or in his training where a transition from visual flight rules to a flight under instrument flight rules in an emergency was performed.
Final Report:

Crash of a De Havilland DHC-2 Beaver off Sechelt

Date & Time: Jul 30, 2019 at 1248 LT
Type of aircraft:
Registration:
C-GPZP
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Vancouver - Pender Harbour
MSN:
722
YOM:
1954
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
En route from Vancouver to Pender Harbour, the pilot encountered engine problems and elected to ditch the aircraft about three miles off Sechelt. All three occupants were able to evacuate the cabin before the aircraft sank and was lost. All three occupants were rescued.

Crash of a Cessna 208 Caravan 675 on Addenbroke Island: 4 killed

Date & Time: Jul 26, 2019 at 1104 LT
Type of aircraft:
Operator:
Registration:
C-GURL
Flight Phase:
Survivors:
Yes
Site:
MSN:
208-0501
YOM:
2008
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
8500
Captain / Total hours on type:
504.00
Aircraft flight hours:
4576
Circumstances:
Seair Seaplanes (Seair) was contracted by a remote fishing lodge on the central coast of British Columbia (BC) (Figure 1) to provide seasonal transport of guests and supplies between Vancouver International Water Aerodrome (CAM9), BC, and the lodge, which is located about 66 nautical miles (NM) north-northwest of Port Hardy Airport (CYZT), BC, and about 29 NM southeast of Bella Bella (Campbell Island) Airport (CBBC), BC. On 26 July 2019, the occurrence pilot arrived at Seair’s CAM9 base at approximately 0630. Over the next hour, the pilot completed a daily inspection of the Cessna 208 Caravan aircraft (registration C-GURL, serial number 20800501), added 300 L of fuel to the aircraft, and began flight planning activities, which included gathering and interpreting weather information. On the morning of the occurrence, 4 Seair visual flight rules (VFR) flights were scheduled to fly to the central coast of BC, all on Caravan aircraft: C-GURL (the occurrence aircraft) was to depart CAM9 at 0730, C-GSAS at 0745, C-FLAC at 0800, and C-GUUS at 0900. The first 3 flights were direct flights to the fishing lodge, while the 4th flight had an intermediate stop at the Campbell River Water Aerodrome (CAE3), BC, to pick up passengers before heading to a research institute located approximately 4 NM southwest of the fishing lodge. Because of poor weather conditions in the central coast region, however, all of the flights were delayed. After the crews referred to weather cameras along the central coast region, the flights began to depart, but in a different order than originally scheduled. It is not uncommon for the order of departure to change when groups of aircraft are going to the same general location. One of Seair’s senior operational staff (operations manager) departed CAM9 at 0850 aboard C-FLAC. C-GUUS, bound for the research institute, departed CAM9 next at 0906, and then the occurrence aircraft departed at 0932 (Table 1). The pilot originally scheduled to fly C-GSAS declined the flight. This pilot had recently upgraded to the Caravan, had never flown to this destination before, and was concerned about the weather at the destination. When Seair’s chief pilot returned to CAM9 at 0953 after a series of scheduled flights on a different type of aircraft, he assumed the last remaining flight to the lodge and C-GSAS departed CAM9 at 1024.After departing the Vancouver terminal control area, the occurrence aircraft climbed to 4500 feet above sea level (ASL) and remained at this altitude until 1023, when a slow descent was initiated. The aircraft levelled off at approximately 1300 feet ASL at 1044, when it was approximately 18 NM northeast of Port Hardy Airport (CYZT), BC, and 57 NM southeast of the destination. At 1050, the occurrence aircraft slowly descended again as the flight continued northbound. During this descent, the aircraft’s flaps were extended to the 10° position. At this point, the occurrence aircraft was 37 NM south-southeast of the fishing lodge. The aircraft continued to descend until it reached an altitude of approximately 330 feet ASL, at 1056. By this point, the occurrence aircraft was being operated along the coastline, but over the ocean. C-FLAC departed from the fishing lodge at 1056 on the return flight to CAM9. C-FLAC flew into the Fitz Hugh Sound and proceeded southbound along the western shoreline. At approximately 1100, it flew through an area of heavy rain where visibility was reduced to about 1 statute mile (SM). C-FLAC descended to about 170 feet ASL and maintained this altitude for the next 5 minutes before climbing to about 300 feet ASL. As the southbound C-FLAC entered Fitz Hugh Sound from the north at Hecate Island, the occurrence aircraft entered Fitz Hugh Sound from the south, near the southern tip of Calvert Island. The occurrence aircraft then changed course from the western to the eastern shoreline, and descended again to about 230 feet ASL (Figure 2), while maintaining an airspeed of approximately 125 knots. The 2 aircraft established 2-way radio contact. The pilot of C-FLAC indicated that Addenbroke Island was visible when he flew past it, and described the weather conditions in the Fitz Hugh Sound to the occurrence pilot as heavy rain showers and visibility of approximately 1 SM around Kelpie Point. The occurrence pilot then indicated that he would maintain a course along the eastern shoreline of the sound. At 1103, the 2 aircraft were separated by 2 NM and passed each other on reciprocal tracks, approximately 4 NM south of the accident site. The occurrence aircraft maintained a consistent track and altitude for the next 54 seconds, then slowly began a 25° change in track to the west (0.35 NM from the Addenbroke Island shoreline). Seven seconds after the turn started (0.12 NM from the island’s shoreline), the aircraft entered a shallow climb averaging 665 fpm. At 1104:55, the occurrence aircraft struck trees on Addenbroke Island at an altitude of approximately 490 feet ASL, at an airspeed of 114 knots, and in a relatively straight and level attitude. The aircraft then continued through the heavily forested hillside for approximately 450 feet, coming to rest at an elevation of 425 feet ASL, 9.7 NM east-southeast of the destination fishing lodge. The pilot and three passengers were killed and five other occupants were injured, four seriously.
Probable cause:
Findings as to causes and contributing factors:
These are conditions, acts or safety deficiencies that were found to have caused or contributed to this occurrence.
1. The flight departed Vancouver International Water Aerodrome even though the reported and forecast weather conditions in the vicinity of the destination were below visual flight rules minima; the decision to depart may have been influenced by the group dynamics of Seair pilots and senior staff at the flight planning stage.
2. The pilot continued flight in reduced visibility, without recognizing the proximity to terrain, and subsequently impacted the rising terrain of Addenbroke Island.
3. The configuration of the visual and aural alerting systems and the colouration ambiguity in the primary flight display of the Garmin G1000 was ineffective at alerting the occurrence pilot to the rising terrain ahead.
4. The occurrence pilot’s attention, vigilance, and general cognitive function were most likely influenced to some degree by fatigue.

Findings as to risk:
These are conditions, unsafe acts or safety deficiencies that were found not to be a factor in this occurrence but could have adverse consequences in future occurrences.
1. If pilots do not receive specialized training that addresses the hazards of their flying environment, there is a risk that they will not be proficient in the specific skills necessary to maintain safety margins.
2. If aircraft are operated in excess of the maximum allowable take-off weight, there is a risk of performance degradation and adverse flight characteristics, which could jeopardize the safety of the flight.
3. If cargo is stowed in front of emergency exits, there is a risk that egress may be impeded in an emergency situation, potentially increasing evacuation time and risk of injuries.
4. If air operators do not employ a methodology to accurately assess threats inherent to daily operations, then there is a risk that unsafe practices will become routine and operators will be unaware of the increased risk.
5. If air operators that have flight data monitoring capabilities do not actively monitor their flight operations, they may not be able to identify drift toward unsafe practices that increase the risk to flight crew and passengers.
6. If Transport Canada’s oversight of operators is insufficient, there is a risk that air operators will be non-compliant with regulations or drift toward unsafe practices, thereby reducing safety margins.
7. If Transport Canada does not make safety management systems mandatory, and does not assess and monitor these systems, there is an increased risk that companies will be unable to effectively identify and mitigate the hazards associated within their operations.

Other findings:
These items could enhance safety, resolve an issue of controversy, or provide a data point for future safety studies.
1. The pilot was actively using a cellphone throughout the flight; the operator provided no guidance or limitations on approved cellphone use in flight.
Final Report: