Flight 6560 had departed from Yellowknife Airport at 09:40 CDT (14:40 UTC) on 20 August for a flight to Resolute Bay Airport carrying 11 passengers, 4 crew members and freight. Captain Blair Rutherford was designated as pilot flying for the segment, and First Officer David Hare as the pilot monitoring.^[5] The flight was to be conducted in accordance with instrument flight rules. Reports received shortly after take-off indicated deteriorating weather at Resolute, but the crew agreed that the flight should not divert.^[4]

After an uneventful flight and initial descent, at 11:38 the aircraft made its final turn to line up with Resolute Airport's runway 35 (see runway naming), and the crew reported to be 10 nautical miles (19 km; 12 mi) away from it. While descending in cloud, however, instead of following the localizer signal along the runway's track, the aircraft settled on a track roughly parallel and to the east of the runway centreline.^[4]

At 11:41, as the crew initiated a go-around, Flight 6560 collided with terrain abeam the runway approximately 1 NM (1.9 km; 1.2 mi) to the east, breaking up into three main sections. An intense post-crash fire consumed most of the centre section.

Both pilots, two flight attendants and eight passengers were killed in the impact. Three passengers survived with severe injuries. Rescue operations were carried out by Canadian Forces temporarily stationed at Resolute as part of the 2011 Operation Nanook military exercise, which happened to focus on a major air disaster as main training scenario.^[6][7]

The aircraft involved was a combi (or combined passenger-cargo) Boeing 737-210C with registration C-GNWN. It was manufactured in 1975 with serial number 21067/414.^[8]

C-GNWN was fitted with a gravel kit to enable operations from unpaved runways, such as the one at Resolute Bay Airport. No significant problems with the aircraft maintenance records were found during the investigation.^[4]

The accident was investigated by the Transportation Safety Board of Canada (TSB). In January 2012, the TSB issued an investigation update classifying the accident as a controlled flight into terrain (CFIT). It stated that the go-around manoeuvre was initiated two seconds before impact.^[9]

At that time, the crew had completed the landing checklist, the flaps were at 40, the aircraft was travelling at 157 knots (291 km/h; 181 mph) and the landing gear was down and locked. Both engines were in operation and producing power. The aircraft had been following an instrument landing system (ILS) approach due to poor visibility. Post-crash investigation found the airport's ILS system to be operating normally, and was in fact used by another aircraft that successfully landed 20 minutes after the crash of Flight 6560.^[9]

In March 2014, the TSB issued the final accident report. It found that the crew's decision to initiate the descent from cruise altitude was late, and it resulted in a significantly increased workload that affected the crew's subsequent performance and ability to properly track all parameters.^[4]

The approach was entirely flown on autopilot, which was correctly set to capture the localizer signal and track along the runway centreline (VOR/LOC capture mode). However, an inadvertent movement of the control column by the captain during the turn onto the final approach track caused the autopilot to disengage from VOR/LOC mode and revert to maintaining the current heading, resulting in the aircraft rolling out to the right (east) of the runway centreline.^[4]

The deviation was correctly shown on the onboard localizer indicator. However, for undetermined reasons, the compass system had been incorrectly set during initial descent so that it displayed a heading that was 8° to the left of the actual heading. Furthermore, the pilot did not recalibrate the compass after the initial descent, 15 minutes before the crash, though regular recalibration when so near the North Magnetic Pole is necessary; the magnetic influence further increased the initial mis-calibration to 17°, giving the captain the wrong impression that the aircraft was tracking towards regaining the runway centreline.^[4]

In fact the aircraft was flying roughly parallel to the runway, and a wind from the southwest was pushing it even further to the east. Under a significantly increased workload, neither pilot noticed the partial disengagement of the autopilot. The first officer was aware that the aircraft was off course to the right and heading for the hill east of the airport. He tried to warn the captain 18 times, using multiple different variations of phrasing, but failed to find a way to convey the urgency of the situation and make the captain change his course of action.^[9] After the ground proximity warning system (GPWS) issued a 'sink rate' warning, the captain finally commanded a go-around, but there was insufficient distance from terrain to avoid the collision.^[4]

The TSB highlighted how according to First Air's own standard operation procedures, the approach was clearly unstable and should have been aborted at an early stage. The board stressed the risks posed by unstable approaches that are continued to a landing, and called for airlines and authorities to enforce standard operating procedures and crew resource management best practices, to help crews manage workload and communicate effectively in order to make better decisions.^[4][10]

The crash of First Air Flight 6560 was dramatized in "Death in the Arctic", a season 14 (2015) episode of the internationally syndicated Canadian TV documentary series Mayday.^[11]

• First Air press release (Archive) – 22 August 2011
• First Air mourns loss of crew (Archive) – 23 August 2011.
• TSB investigation timeline
• TSB Debris photos
• TSB final report (PDF version)
• TSB final report (PDF version) (in French)
• "A Plane Landing in Arctic Conditions Ends in Tragedy". Smithsonian Channel. 17 February 2017.