ZSE controller described an eram anomaly that caused data block jumping; the reporter suggesting the...

Narrative:

Eram operations: aircraft X auto popped onto my scope as the data block passed the portland approach/ZSE boundary. Control of the data block was unk (unknown). The actual code/aircraft appeared to be up by btg VOR around 35NM away from the target that was being tracked incorrectly. The aircraft X data block appeared to be headed for the mmv airport and when the aircraft target was lost the data block moved onto the code by btg VOR. Recommendation; change the parameters for auto-departure and/or auto-acquire to 5NM from the departure airport. Eram should be able to auto-acquire most targets within those parameters and if it doesn't; the controller can always manually start a track. That method seems safer than having automation track any target that happens to be on an unassigned code or that cycles through the wrong code well outside the normal departure path of the correct aircraft. The controller should be the one to start the track if eram cannot do it correctly.

Original NASA ASRS Text

Title: ZSE Controller described an ERAM anomaly that caused Data Block jumping; the reporter suggesting the ERAM auto acquisition parameters be changed to preclude future occurrences.

Narrative: ERAM OPS: Aircraft X auto popped onto my scope as the Data Block passed the Portland Approach/ZSE boundary. Control of the Data Block was UNK (Unknown). The actual code/aircraft appeared to be up by BTG VOR around 35NM away from the target that was being tracked incorrectly. The Aircraft X Data Block appeared to be headed for the MMV airport and when the aircraft target was lost the Data Block moved onto the code by BTG VOR. Recommendation; change the parameters for auto-departure and/or auto-acquire to 5NM from the departure airport. ERAM should be able to auto-acquire most targets within those parameters and if it doesn't; the controller can always manually start a track. That method seems safer than having automation track any target that happens to be on an unassigned code or that cycles through the wrong code well outside the normal departure path of the correct aircraft. The controller should be the one to start the track if ERAM cannot do it correctly.

Data retrieved from NASA's ASRS site as of April 2012 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.

Attributes
ACN	970564
Time
Date	201109
Local Time Of Day	0001-0600
Place
Locale Reference	ZSE.ARTCC
State Reference	WA
Aircraft 1
Make Model Name	PC-12
Flight Phase	Climb
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types

ZSE controller described an eram anomaly that caused data block jumping; the reporter suggesting the eram auto acquisition parameters be changed to preclude future occurrences.