Phl controller described a recurring anomaly with the asde-X equipment; involving a data block ident...

Narrative:

This is the 3rd example of this problem I've seen in the last 2 days. Air carrier X; [a CRJ2]; was correctly depicted on the asde-X when he was rolling out on runway 26. He then taxied via delta and gulf to hold short of runway 35. When I noticed the change; he was holding short; but his call sign showed aircraft Y; beacon code ZZZZ; aircraft type PA28. The other aircraft was not taxiing. When I full-routed the call sign later; aircraft Y was not in the host.

Original NASA ASRS Text

Title: PHL Controller described a recurring anomaly with the ASDE-X equipment; involving a data block identification change as a landing aircraft exited the runway.

Narrative: This is the 3rd example of this problem I've seen in the last 2 days. Air Carrier X; [a CRJ2]; was correctly depicted on the ASDE-X when he was rolling out on Runway 26. He then taxied via Delta and Gulf to hold short of Runway 35. When I noticed the change; he was holding short; but his call sign showed aircraft Y; beacon code ZZZZ; aircraft type PA28. The other aircraft was not taxiing. When I full-routed the call sign later; aircraft Y was not in the host.

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	959144
Time
Date	201107
Local Time Of Day	1801-2400
Place
Locale Reference	PHL.Airport
State Reference	PA
Environment
Light	Night
Aircraft 1
Make Model Name	Regional Jet 200 ER/LR (CRJ200)
Operating Under FAR Part	Part 121
Flight Phase	Taxi
Flight Plan	IFR
Person 1
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types

Phl controller described a recurring anomaly with the asde-X equipment; involving a data block identification change as a landing aircraft exited the runway.