A310 crew had track deviation in S56 class east airspace.

Attributes
ACN	496080
Time
Date	200012
Day	Sat
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : slc.airport
State Reference	UT
Altitude	msl single value : 12000
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	tracon : s56.tracon tracon : d01.tracon
Operator	common carrier : air carrier
Make Model Name	A310
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	descent : intermediate altitude
Route In Use	arrival star : bearr 4
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : multi engine pilot : commercial pilot : instrument
Experience	flight time total : 5000
ASRS Report	496080
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
ASRS Report	496083
Events
Anomaly	aircraft equipment problem : less severe non adherence : published procedure non adherence : clearance non adherence : company policies other anomaly other other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued alert flight crew : returned to original clearance none taken : detected after the fact
Consequence	other
Supplementary
Problem Areas	Flight Crew Human Performance Aircraft
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

On bearr 4 arrival to slc landing runway 34R. After passing bearr, aircraft tracked toward ogd versus dyann. Controller questioned us. Upon inspection, discovered FMS's were not talking to one another and aircraft was tracking the runway 16L arrival versus the runway 34R arrival via dyann. Both runway 16L and runway 34R were programmed into FMS #1 and #2, respectfully. I (first officer) was flying with runway 16L arrival set in FMS #1. Captain's selected secondary flight plan and activated, but nothing registered my side. Captain remarked 'we are not tracking to dyann' and controller shortly thereafter questioned us. We were in process of going to dyann at that time. Incident was short-lived, corrected by us and uneventful.

Original NASA ASRS Text

Title: A310 CREW HAD TRACK DEV IN S56 CLASS E AIRSPACE.

Narrative: ON BEARR 4 ARR TO SLC LNDG RWY 34R. AFTER PASSING BEARR, ACFT TRACKED TOWARD OGD VERSUS DYANN. CTLR QUESTIONED US. UPON INSPECTION, DISCOVERED FMS'S WERE NOT TALKING TO ONE ANOTHER AND ACFT WAS TRACKING THE RWY 16L ARR VERSUS THE RWY 34R ARR VIA DYANN. BOTH RWY 16L AND RWY 34R WERE PROGRAMMED INTO FMS #1 AND #2, RESPECTFULLY. I (FO) WAS FLYING WITH RWY 16L ARR SET IN FMS #1. CAPT'S SELECTED SECONDARY FLT PLAN AND ACTIVATED, BUT NOTHING REGISTERED MY SIDE. CAPT REMARKED 'WE ARE NOT TRACKING TO DYANN' AND CTLR SHORTLY THEREAFTER QUESTIONED US. WE WERE IN PROCESS OF GOING TO DYANN AT THAT TIME. INCIDENT WAS SHORT-LIVED, CORRECTED BY US AND UNEVENTFUL.

Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.