Zan front line manager reported of an aircraft had traffic with another target that was unidentified...

Attributes
ACN	1302769
Time
Date	201510
Local Time Of Day	1801-2400
Place
Locale Reference	ZAN.ARTCC
State Reference	AK
Environment
Light	Night
Aircraft 1
Make Model Name	Small Transport Low Wing 2 Turboprop Eng
Flight Phase	Descent
Route In Use	Other Instrument Approach
Flight Plan	IFR
Person 1
Function	Supervisor / CIC
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 1
Events
Anomaly	ATC Issue All Types Deviation - Procedural Other / Unknown

Narrative:

Aircraft X was approximately 15S of bet inbound when another target with the same beacon code appeared in close proximity. A collision alert was generated and continued for several minutes. Aircraft X is ads-B equipped; and this appeared to be a conflict between the aircraft's two transponders. Repeated nuisance conflict alerts desensitize controllers and cics/flms. This can lead to complacency and degradation of response time for legitimate conflicts.nuisance conflict alerts (between a single aircraft's ads-B and radar targets) are an ongoing problem at zan. Perhaps a software patch or equipment upgrade would solve this issue? I also filed a facility trouble report for this event (which includes the aircraft flight progress strip).

Original NASA ASRS Text

Title: ZAN Front Line Manager reported of an aircraft had traffic with another target that was unidentified. FLM reported this was the same aircraft that was ADS-B equipped. FLM reported this type of nuisance conflict alert happens quite often and would like something to be done about it.

Narrative: Aircraft X was approximately 15S of BET inbound when another target with the same beacon code appeared in close proximity. A collision alert was generated and continued for several minutes. Aircraft X is ADS-B equipped; and this appeared to be a conflict between the aircraft's two transponders. Repeated nuisance conflict alerts desensitize controllers and CICs/FLMs. This can lead to complacency and degradation of response time for legitimate conflicts.Nuisance conflict alerts (between a single aircraft's ADS-B and radar targets) are an ongoing problem at ZAN. Perhaps a software patch or equipment upgrade would solve this issue? I also filed a facility trouble report for this event (which includes the aircraft flight progress strip).

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

Zan front line manager reported of an aircraft had traffic with another target that was unidentified. Flm reported this was the same aircraft that was ads-B equipped. Flm reported this type of nuisance conflict alert happens quite often and would like something to be done about it.