Ewr controller elected not to issue mandated asde-X go-around instructions after positively observin...

Narrative:

Airport wind [was] approximately 330 at 25 KTS gusting 35 KTS; landing runway 29 stadium visual approach; departing runway 22R at west intersection; night time operation. Just prior to the incident; an aircraft was disabled on runway 22R in the vicinity of taxiway west; and runway 22R was closed. I was taxiing aircraft to runway 22L at west for departure and issuing a new departure runway which added to my workload. Air carrier X; slowed to approximately 70 KTS ground speed. Air carrier Y; was maintaining visual separation; with an approximate ground speed of 150 KTS. Upon landing and taxiing at a safe speed; I asked air carrier X if he was able to turn off at the next high speed and he responded in the affirmative. I observed air carrier X off of runway 29; and air carrier Y short final when the asde-X issued an alert for air carrie Y to go-around. I said out loud that air carrier X was off the runway and that I was not going to send the aircraft around. I believe that I made the safest decision because air carrier X was off the runway; and air carrier Y was in a critical stage of flight. The safety logic system should not supercede controller judgment. There are many aspects of the asde-X that have proven to be faulty; and this is another.

Original NASA ASRS Text

Title: EWR Controller elected not to issue mandated ASDE-X go-around instructions after positively observing the landing traffic had cleared the runway. The reporter claimed faulty ASDE-X logic as a contributing factor.

Narrative: Airport wind [was] approximately 330 at 25 KTS gusting 35 KTS; landing Runway 29 stadium visual approach; departing Runway 22R at W Intersection; night time operation. Just prior to the incident; an aircraft was disabled on Runway 22R in the vicinity of Taxiway W; and Runway 22R was closed. I was taxiing aircraft to Runway 22L at W for departure and issuing a new departure runway which added to my workload. Air Carrier X; slowed to approximately 70 KTS ground speed. Air Carrier Y; was maintaining visual separation; with an approximate ground speed of 150 KTS. Upon landing and taxiing at a safe speed; I asked Air Carrier X if he was able to turn off at the next high speed and he responded in the affirmative. I observed Air Carrier X off of Runway 29; and Air Carrier Y short final when the ASDE-X issued an alert for Air Carrie Y to go-around. I said out loud that Air Carrier X was off the runway and that I was not going to send the aircraft around. I believe that I made the safest decision because Air Carrier X was off the runway; and Air Carrier Y was in a critical stage of flight. The safety logic system should not supercede Controller judgment. There are many aspects of the ASDE-X that have proven to be faulty; and this is another.

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.

Attributes
ACN	1056240
Time
Date	201212
Local Time Of Day	0001-0600
Place
Locale Reference	EWR.Airport
State Reference	NJ
Aircraft 1
Make Model Name	Dash 8 Series Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Landing
Route In Use	Visual Approach
Flight Plan	IFR
Aircraft 2
Make Model Name	EMB ERJ 145 ER/LR
Operating Under FAR Part	Part 121
Flight Phase	Final Approach
Route In Use	Visual Approach
Flight Plan	IFR
Person 1
Function	Local
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Deviation - Procedural Published Material / Policy

Ewr controller elected not to issue mandated asde-X go-around instructions after positively observing the landing traffic had cleared the runway. The reporter claimed faulty asde-X logic as a contributing factor.