Mem controller described an apparent false asde-X alarm resulting in a go around for runway 27 landi...

Narrative:

An SF34 was on short final to runway 27. Our new asd-X issued an alert to send the runway 27 traffic around based on vehicle traffic that was on a taxi way approaching the hold line at the approach end; but still north of the hold line. A crj was on about a mile final to runway 18R and a CRJ2 was on about a 4 1/2 to 5 mile final to runway 18R. This was determined to be a false alert by asd-X but we're still using the equipment. Our procedures; (including crda); do not account for a missed approach or if a go around occurs off of runway 27 and there's traffic on runway 18L/right; there's potential for a problem. Controllers have been told that we don't protect for go arounds; but this is a potentially dangerous situation. This is the third instance of a false alert from asd-X resulting in a go around in the last 2 days. Stop running simultaneously to runways 18 and 27.

Original NASA ASRS Text

Title: MEM Controller described an apparent false ASDE-X alarm resulting in a go around for Runway 27 landing traffic; traffic was also on final for Runway 18R; the reporter expressing concern regarding the simultaneous Runway 18 and 27 operations.

Narrative: An SF34 was on short final to Runway 27. Our new ASD-X issued an alert to send the Runway 27 traffic around based on vehicle traffic that was on a taxi way approaching the hold line at the approach end; but still north of the hold line. A CRJ was on about a mile final to Runway 18R and a CRJ2 was on about a 4 1/2 to 5 mile final to Runway 18R. This was determined to be a false alert by ASD-X but we're still using the equipment. Our procedures; (including CRDA); do NOT account for a missed approach or if a go around occurs off of Runway 27 and there's traffic on Runway 18L/R; there's potential for a problem. Controllers have been told that we don't protect for go arounds; but this is a potentially dangerous situation. This is the third instance of a false alert from ASD-X resulting in a go around in the last 2 days. STOP running simultaneously to Runways 18 and 27.

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	962440
Time
Date	201108
Local Time Of Day	1801-2400
Place
Locale Reference	MEM.Airport
State Reference	TN
Aircraft 1
Make Model Name	SF 340B
Operating Under FAR Part	Part 121
Flight Phase	Final Approach
Route In Use	Visual Approach
Flight Plan	IFR
Person 1
Function	Approach
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Deviation - Procedural Published Material / Policy

Mem controller described an apparent false asde-X alarm resulting in a go around for runway 27 landing traffic; traffic was also on final for runway 18R; the reporter expressing concern regarding the simultaneous runway 18 and 27 operations.