B737-700
Air Traffic Control Fully Certified
Human-Machine Interface; Situational Awareness
ATC Issue All Types
Air Traffic Control Issued New Clearance
ATC Equipment / Nav Facility / Buildings; Procedure; Human Factors
Air Carrier X was a MAIER arrival; had descended him to 4;000 feet; planning a base turn for a 6-8 NM final. He was number 1 for Runway 26 and I had coordinated with Verde Air Carrier Y to fit into my sequence. I subsequently turned Air Carrier Y EAGUL arrival toward a 5 NM final for spacing and descended to 6;000 feet. I turned Air Carrier X to the base leg; however; never got a read back. The Air Carrier Y EAGUL reported the airport in sight so I issued the visual approach clearance; expecting to clear Air Carrier X on the next transmission. However; I noticed Air Carrier X had not turned; tried to turn him further right with no response. I immediately cancelled the Air Carrier Y clearance with a maintain 6;000 feet; and a turn to the South. I tried Air Carrier X again and this time got a response. Wound up turning the Air Carrier Y back towards the Northwest; then to the final. This is the first day we were running 'fused RADAR' in STARS. I believe the unfamiliarity of the movements of the data blocks and history trails contributed to this event. Until I become more accustomed to the quirks of the fusion display; I will go into the finals (base legs; turns and clearances) with a more conservative technique. I have noticed that the PTL lines and the 'baseball bat' cones seem to lag behind more than traditional RADAR. This may just be an optical illusion.
P50 Controller experienced a developing conflict event listing the unfamiliarity with 'fused RADAR' as a causal factor.