Narrative:

I was working local control west (lcw; runway 16R) during the busiest bank of the day (the 10:00 arrival and departure bank). I was catching most/all of the arrivals and departing few; while local control center (lcc; runway 16L) was departing most/all aircraft and landing few. I was in the process of 'hitting a hole' between 2 arrivals with a departing aircraft. This was nothing too difficult or abnormal. After clearing the aircraft for take-off; and already cleared the next arrival to land; the asde-X (airport surface detection equipment model X) alarm sounded 2 times in a row for RWY17 stating '...occupied; go around'. This was during a busy moment during the bank; much coordination going on in the tower cab; many continuous transmissions by all controllers; and many aircraft taxiing; landing; and departing. My asde-X screen was set-up to show my runway at the top of the screen; as is usual. The 2 visual asde-X alarms were also at the top of my screen covering my runway. I misinterpreted both the verbal and visual alarm and thought the alarm was for my runway 16R; which in fact it was for RWY17. I did not notice any abnormalities out the window; on either radar; or on my pad with my traffic management. However; due to my misinterpretation of the asde-X alarm and the rules of sending aircraft around when the asde-X alarm does sound for your runway; I sent the closest-in aircraft on final around (aircraft X). At this time he was on about a 2-mile final. Immediately after issuing the go-around instruction I realized my error in misinterpreting the asde-X alarm. However; my go around was already issued and acknowledged. I coordinated/informed the rest of the tower cab of my go-around; separated my aircraft accordingly; and executed the go-around properly.slc was in a south flow. This was the 3rd day of the runway 17/35 construction closure; to last approximately 70 days. Controllers are utilizing the diagonal runway 14/32 a lot more for general aviation aircraft. Due to the runway 17/35 closure; we place 'X's' on the asde-X for that runway. The asde-X misinterpreted an aircraft (aircraft Y) lining up for RWY14 to be lining up for RWY17; and alarmed incorrectly. The asde-X has continuously made incorrect interpretations of aircraft lining up for runway 17/35 instead of runway 14/32; thus causing the loud verbal alarm to sound (many times back-to-back). It is an alarm that all controllers and people in the tower cab 'perk up' to immediately and gets our hearts pumping faster. The day prior; I was working local control east (lce) and city (cty; tower radar position) combined. Three separate times during my 1.5-2 hours on position that day and rotation the asde-X alarm sounded 5 times immediately in a row for RWY35; stating '...occupied; go around'; when in reality my aircraft was lined up for and landing RWY32. As previously stated; this alarm always catches controllers by surprise and startles us.the asde-X will continue to alarm a lot more throughout the RWY17/35 runway closure while the 'X's' are up as it misinterprets aircraft on final for RWY14/32. This of course presents numerous problems and difficulties. Some of them are: startling controllers; more information to interpret and act upon during busy/stressful times; misinterpretations; etc. An idea was discussed to inhibit (if possible) the asde-X alarm for RWY17/35 during this construction time to avoid these numerous problems. However; this could open a new problem if an aircraft really is lined-up for RWY17/35. So this would not be a good solution.I am not sure if there are any equipment remedies that can come during this time. I believe we as controllers will have to become more vigilant during this construction phase.another issue that may arise with the asde-X alarm continually going off during this time is we as controllers may become complacent to hearing this and not react as fast or accordingly in the future; or even during this construction phase.

Related reports:

Google
 

Original NASA ASRS Text

Title: SLC Tower Controller reported of sending an aircraft around due to the Airport Surface Detection Equipment Model X alarming. The Controller did not realize the alarm was going off for a different runway; not the one he was utilizing.

Narrative: I was working Local Control West (LCW; RWY 16R) during the busiest bank of the day (the 10:00 arrival and departure bank). I was catching most/all of the arrivals and departing few; while Local Control Center (LCC; RWY 16L) was departing most/all aircraft and landing few. I was in the process of 'hitting a hole' between 2 arrivals with a departing aircraft. This was nothing too difficult or abnormal. After clearing the aircraft for take-off; and already cleared the next arrival to land; the ASDE-X (Airport Surface Detection Equipment Model X) Alarm sounded 2 times in a row for RWY17 stating '...occupied; go around'. This was during a busy moment during the bank; much coordination going on in the tower cab; many continuous transmissions by all controllers; and many aircraft taxiing; landing; and departing. My ASDE-X screen was set-up to show my RWY at the top of the screen; as is usual. The 2 visual ASDE-X alarms were also at the top of my screen covering my RWY. I misinterpreted both the verbal and visual alarm and thought the alarm was for my RWY 16R; which in fact it was for RWY17. I did not notice any abnormalities out the window; on either radar; or on my pad with my traffic management. However; due to my misinterpretation of the ASDE-X alarm and the rules of sending aircraft around when the ASDE-X alarm does sound for your runway; I sent the closest-in aircraft on final around (Aircraft X). At this time he was on about a 2-mile final. Immediately after issuing the go-around instruction I realized my error in misinterpreting the ASDE-X alarm. However; my go around was already issued and acknowledged. I coordinated/informed the rest of the tower cab of my go-around; separated my aircraft accordingly; and executed the go-around properly.SLC was in a South Flow. This was the 3rd day of the RWY 17/35 construction closure; to last approximately 70 days. Controllers are utilizing the diagonal RWY 14/32 a lot more for General Aviation aircraft. Due to the RWY 17/35 closure; we place 'X's' on the ASDE-X for that runway. The ASDE-X misinterpreted an aircraft (Aircraft Y) lining up for RWY14 to be lining up for RWY17; and alarmed incorrectly. The ASDE-X has continuously made incorrect interpretations of aircraft lining up for RWY 17/35 instead of RWY 14/32; thus causing the loud verbal alarm to sound (many times back-to-back). It is an alarm that all controllers and people in the tower cab 'perk up' to immediately and gets our hearts pumping faster. The day prior; I was working Local Control East (LCE) and City (CTY; tower radar position) combined. Three separate times during my 1.5-2 hours on position that day and rotation the ASDE-X alarm sounded 5 times immediately in a row for RWY35; stating '...occupied; go around'; when in reality my aircraft was lined up for and landing RWY32. As previously stated; this alarm always catches controllers by surprise and startles us.The ASDE-X will continue to alarm a lot more throughout the RWY17/35 runway closure while the 'X's' are up as it misinterprets aircraft on final for RWY14/32. This of course presents numerous problems and difficulties. Some of them are: startling controllers; more information to interpret and act upon during busy/stressful times; misinterpretations; etc. An idea was discussed to inhibit (if possible) the ASDE-X alarm for RWY17/35 during this construction time to avoid these numerous problems. However; this could open a new problem if an aircraft really is lined-up for RWY17/35. So this would not be a good solution.I am not sure if there are any equipment remedies that can come during this time. I believe we as controllers will have to become more vigilant during this construction phase.Another issue that may arise with the ASDE-X alarm continually going off during this time is we as controllers may become complacent to hearing this and not react as fast or accordingly in the future; or even during this construction phase.

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.