Open main menu

First Air Flight 6560 was a domestic charter flight that crashed on landing at Resolute Bay, Nunavut, Canada, on 20 August 2011. Of the 15 people on board, 12 were killed and the remaining three were severely injured. The Boeing 737-200 of First Air was operating a service from Yellowknife, Northwest Territories, when it struck a hill in cloud near Resolute Bay Airport.[1][2][3]

First Air Flight 6560
First Air Flight 6560 wreckage - Resolute Bay - August 2011.jpg
The wreckage of Flight 6560 at the crash site
Accident
Date20 August 2011 (2011-08-20)
SummaryControlled flight into terrain
Site1 nm east of Resolute Bay Airport, Nunavut, Canada
74°42′57″N 094°55′04″W / 74.71583°N 94.91778°W / 74.71583; -94.91778Coordinates: 74°42′57″N 094°55′04″W / 74.71583°N 94.91778°W / 74.71583; -94.91778
Aircraft
Aircraft typeBoeing 737-210C
OperatorFirst Air
IATA flight No.7F 6560
ICAO flight No.FAB6560
RegistrationC-GNWN
Flight originYellowknife Airport, Yellowknife, Northwest Territories, Canada
DestinationResolute Bay Airport, Resolute Bay, Nunavut, Canada
Occupants15
Passengers11
Crew4
Fatalities12
Injuries3
Survivors3

The subsequent investigation found that a late initiation of the descent, the inadvertent partial disengagement of the autopilot during final approach, a drift in the aircraft compass system and poor communication between the flight crew resulted in the aircraft drifting significantly off course from the final approach path, descending into the ground moments after the crew initiated a go-around.[4]

Contents

History of the flightEdit

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. The captain was designated as pilot flying for the segment, and the first officer as the pilot not flying. The flight was to be conducted in accordance with instrument flight rules. Reports received shortly after take-off indicated deteriorating weather at Resolute Bay, 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, 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 nautical mile (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 Bay as part of the 2011 Operation Nanook military exercise, which happened to focus on a major air disaster as main training scenario.[5]

AircraftEdit

 
C-GNWN, the aircraft involved, seen in 2009

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.[6]

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]

InvestigationEdit

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. It stated that the go-around manoeuvre was initiated two seconds before impact.[7]

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 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.[7]

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.

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 to display a heading that was 8° to the left of the actual heading, and during the approach the heading error further increased 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 multiple times to warn the captain, but in a way that failed to convey the urgency of the situation and make the captain change his course of action. After the ground proximity warning system 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][8]

ReferencesEdit

  1. ^ Hradecky, Simon (20 August 2011). "Crash: First Air B732 near Resolute Bay on Aug 20th 2011, impacted terrain". The Aviation Herald. Retrieved 21 August 2011.
  2. ^ "12 killed in Boeing 737 crash near Resolute Bay". Nunatsiaq News. 20 August 2011. Retrieved 28 April 2019.
  3. ^ White, Patrick; Hannay, Chris (20 August 2011). "Nunavut town reeling after plane crash kills 12". The Globe and Mail. Retrieved 21 April 2019.
  4. ^ a b c d e f g h Aviation Investigation Report A11H0002 (Report). Transportation Safety Board of Canada. Retrieved 20 April 2019.
  5. ^ "Training, luck guided Resolute Bay air disaster response: military". Nunatsiaq News. 28 September 2011. Retrieved 28 April 2019.
  6. ^ "ASN Aircraft accident Boeing 737-210C C-GNWN Resolute Airport, NU (YRB)". Aviation Safety Network. Retrieved 21 April 2019.
  7. ^ a b "First Air Flight 6560, Boeing 737 Accident, 20 August 2011, Resolute Bay (A11H0002)" (Press release). Transportation Safety Board of Canada. 5 January 2012. Archived from the original on 29 October 2018.
  8. ^ "TSB highlights worldwide problem with unstable approaches and calls for improved crew communications following 2011 crash in Resolute Bay, Nunavut" (Press release). Gatineau, Quebec: Transportation Safety Board of Canada. 25 March 2014. Retrieved 28 April 2019.

External linksEdit