ASN logo
ASN Wikibase Occurrence # 204970
Last updated: 12 April 2021
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Time:10:02 LT
Type:Silhouette image of generic DH8D model; specific model in this crash may look slightly different
de Havilland Canada DHC-8-402Q Dash 8
Owner/operator:Porter Airlines
Registration: C-GKQA
C/n / msn: 4357
Fatalities:Fatalities: 0 / Occupants: 15
Other fatalities:0
Aircraft damage: None
Location:9.5 nm SW of Sudbury Airport, ON (YSB/CYSB) -   Canada
Phase: Approach
Nature:Passenger - Scheduled
Departure airport:Toronto City-Billy Bishop Airport, ON (YTZ/CYTZ)
Destination airport:Sudbury Airport, ON (YSB/CYSB)
Investigating agency: TSB Canada
On 14 October 2016, Porter Airlines Flight 533 (DHC-8-402Q, C-GKQA) was on an instrument flight rules (IFR) flight to the Sudbury Airport (CYSB), Canada. It was to arrive from the south with an estimated time of arrival at 10:05 LT. Soon after the North Bay controller cleared Flight 533 for a visual approach to runway 04, Jazz Aviation Flight 604 (DHC-8-402Q, C-GXJZ) took off under visual flight rules (VFR) on runway 22, heading south towards its destination. Runway 22 was the active runway at Sudbury and reciprocal to runway 04. Approximately three minutes later, when both aircraft were 9.5 nautical miles southwest of the Sudbury Airport, the traffic alert and collision avoidance systems (TCAS) in the flight crews' respective aircraft issued a resolution advisory to take specific action to avoid a collision. Both flight crews took evasive action. Radar data indicated that the two aircraft came within 0.4 nautical miles of each other at the same altitude.

The investigation found that the North Bay controllers' practice of clearing incoming IFR aircraft for an approach without regard for the active runway at the Sudbury Airport created a situation wherein IFR traffic was counter to the flow of, and therefore more likely to come into conflict with, VFR traffic operating at the airport. Further, air traffic control approved the VFR departure of Flight 604 without a coordinated plan to prevent conflict between the aircraft and incoming IFR traffic. Flight 604 was not fully aware of the traffic situation at the airport when it taxied to runway 22, as the Sudbury flight service station's taxi departure advisory did not include information about inbound opposite direction traffic.

The risk of collision occurred after Flight 604 made its left turn to fly away from the airport towards its destination. This turn was not apparent to North Bay air traffic control, as the display was set at a scale that was too large to detect heading changes right after they occur. Unaware of Flight 604's exact position, the controller suggested that it turn right, essentially bringing it back toward the approach path of runway 04 and in conflict with Flight 533.

Following the TCAS resolution advisory, the flight crew from both Flight 604 and 533 initially maneuvered their respective aircraft contrary to the TCAS commands. As result, the vertical separation between the two aircraft was reduced.


Accident investigation:
Investigating agency: TSB Canada
Status: Investigation completed
Duration: 1 year and 3 months
Download report: Final report


Photo of C-GKQA courtesy

Montréal - Pierre Elliott Trudeau International (CYUL / YUL)
31 March 2018; (c) Pierre Langlois

Flight tracks of JZA604 and POE533 (Source: Google Earth, with TSB annotations)

Revision history:

24-Jan-2018 08:33 harro Added

Corrections or additions? ... Edit this accident description