Narrative:

In this situation an asde-X go-around alert was generated for an intersecting runway operation between two arriving aircraft. Aircraft 1 (a B737) was on roughly a 2 mile final for runway xxl as aircraft 2 (a CL60) was rolling out on runway yy. The CL60 touched down late; and in my judgment; was moving too quickly to be instructed to hold short of runway xxl. The most expeditious route for the CL60 was to enter runway xxl with a left turn and join the high speed taxiway. This was the instruction the CL60 was issued and the aircraft read the instruction back and complied. When the B737 was on short final an asde-X go-around alert was generated. The CL60 was clearing runway xxl and moving away unobstructed as the alert was generated. In my judgment (and in accordance with 7110.65 3-6-4(b)) I did not issue go-around instructions as appropriate action had already been taken to ensure intersecting runway separation. The asde-X alert was logged by the front line manager as required. In this case runway separation existed at all times and there was no over-flight of the CL60 by the B737. The situation was close but in my judgment would work out. I was aware that the asde-X might generate an alert and was watching both aircraft closely. The asde-X alert does have a 'shock' effect on other controllers in the tower cab unless you warn them that an alert might be generated. I would recommend warning others in the cab in situations like this whenever able as it is far less disturbing to the operation when everyone knows it is coming.

Related reports:

Google
 

Original NASA ASRS Text

Title: Tower Controller described an ASDE-X Alarm event activated even though the conflicting aircraft was obviously clear of the landing runway.

Narrative: In this situation an ASDE-X go-around alert was generated for an intersecting runway operation between two arriving aircraft. Aircraft 1 (a B737) was on roughly a 2 mile final for Runway XXL as Aircraft 2 (a CL60) was rolling out on Runway YY. The CL60 touched down late; and in my judgment; was moving too quickly to be instructed to hold short of Runway XXL. The most expeditious route for the CL60 was to enter Runway XXL with a left turn and join the high speed taxiway. This was the instruction the CL60 was issued and the aircraft read the instruction back and complied. When the B737 was on short final an ASDE-X go-around alert was generated. The CL60 was clearing Runway XXL and moving away unobstructed as the alert was generated. In my judgment (and in accordance with 7110.65 3-6-4(b)) I did NOT issue go-around instructions as appropriate action had already been taken to ensure intersecting runway separation. The ASDE-X alert was logged by the Front Line Manager as required. In this case runway separation existed at all times and there was NO over-flight of the CL60 by the B737. The situation was close but in my judgment would work out. I was aware that the ASDE-X might generate an alert and was watching both aircraft closely. The ASDE-X alert does have a 'shock' effect on other controllers in the Tower cab unless you warn them that an alert might be generated. I would recommend warning others in the cab in situations like this whenever able as it is far less disturbing to the operation when everyone knows it is coming.

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