No fatalities

6 Nov 2009: AIRBUS A320 211 (N613WF) — Air Canada — Cortez, CO

Cortez, CO, United States

On 6 Nov 2009, an AIRBUS A320 211 (registration N613WF) operated by Air Canada was involved in an aviation accident near Cortez, CO. No fatalities were reported. Investigators recorded the probable cause as: The failure of the ACA795 flight crew to monitor and/or switch to the appropriate air traffic control frequency. This summary draws on records from NTSB; 17 related events involving the same aircraft type or operator are linked below.

SourcesNTSBPrimary reportUpdated 1778583330Data APIEditorial standards
AIRBUS A320 211
Photo: Tosaka / CC BY 3.0, via Wikimedia Commons

On November 5, 2009, Air Canada Flight 795 lost radio contact with air traffic control for 37 minutes over Denver and Los Angeles airspace. Communication was reestablished via air-to-air relay. The incident was attributed to the crew turning down the volume on guard frequency 121.5 due to static.

Overview

On November 5, 2009, Air Canada Flight 795 (ACA795) departed Toronto's Lester B. Pearson International Airport at approximately 2010 eastern standard time (0010 UTC November 6) on a non-stop flight to Los Angeles International Airport. The aircraft, whose type and registration are not specified in the source, was cruising at flight level 360 when it checked in with Denver Air Route Traffic Control Center (ZDV) at 2115 Mountain Standard Time. The aircraft's radios were configured with COMM1 on the ATC frequency and COMM2 on 121.5 MHz.

Timeline of Events

At 2134, ZDV radar sector 37 directed ACA795 to contact ZDV on frequency 132.87. ACA795 did not respond. Over the next 37 minutes, multiple attempts were made by ZDV controllers to reestablish communication. This included radio checks on various frequencies, requests to other aircraft (Frontier flights 860, 778, 780, 266, and Continental flight 752) to attempt air-to-air communication, and the use of ACARS messages via Air Canada dispatch. An initial ACARS message from dispatch failed because the airborne ACARS set was on a frequency not available at the New Mexico ground station, and the system did not notify dispatch of the failure for 30 minutes (subsequently changed to 8 minutes).

At 2157, ACA795 used ACARS to obtain LAX weather and ATIS from the San Francisco ARINC server, but this did not reestablish the ACARS link with dispatch. At 2211, ZDV requested N613WF to transmit to ACA795 to contact ZLA. ACA795 received the transmission, and at 2212 N613WF reported establishing communications. N613WF advised ACA795 that ATC had been trying to reach them for 45 minutes. At 2214, ZLA was informed that ACA795 reported being on frequency 125.67 during the NORDO period.

At 2227, ACA795 began its descent into LAX, triggering automatic ACARS reporting that reestablished the link with dispatch. Communication with ZDV was reestablished via air-to-air relay through N613WF at FL490, and ACA795 was directed to contact Los Angeles ARTCC on 127.35.

Aftermath

According to the FAA preliminary pilot deviation report, after landing, the pilot of ACA795 contacted the ZDV Operations Manager-in-Charge and explained that they were receiving static on frequency 121.5 and had turned the volume down. The pilot also stated that they had received ACARS messages after contacting ZLA. Notably, the aircraft's VHF SELCAL notification lacked an audio feature, and the aircraft did not have HF SELCAL.

Contributing factors

Causes

Cabin crew

Other contributing factors

Flight crew