ZAB controller described a TCAS RA event involving a phx departure apparently conflicting with a VFR...

Narrative:

[Air carrier] westbound off of phx checked on climbing to FL210 which is standard procedure. I climbed [him] to FL250 top of my airspace. After the pilot read back the clearance; he keyed up again and told me he was going to level off in response to an RA. I then looked for the traffic and saw a mode C intruder north of the aircraft southbound at 124 indicated altitude climbing. Unfortunately; they did not appear to me to be converging. We do not get conflict alerts with VFR's in phx approach's airspace so there is no leader line from the mci. The histories indicated a slow aircraft. I never observed the B757 above 120; so when the pilot said he was going to level off that resolved him from conflicting with any traffic on my scope. I acknowledged the pilots report of the RA and and told him to advise me when he was able to resume his climb. We do not receive conflict alerts on VFR aircraft in phx approach's airspace which is necessary to stop thousands of unwarranted and false alerts. Even though it was the phx controller's responsibility to call the traffic before shipping the aircraft; I wish I would have picked up the slack. Hind sight is 20/20. Recommendation; more diligence in looking for and 'seeing' limited data blocks. Not becoming complacent with the VFR 'clutter' on the scope.

Original NASA ASRS Text

Title: ZAB Controller described a TCAS RA event involving a PHX departure apparently conflicting with a VFR aircraft that had not prompted a conflict alert at ZAB.

Narrative: [Air carrier] westbound off of PHX checked on climbing to FL210 which is standard procedure. I climbed [him] to FL250 top of my airspace. After the pilot read back the clearance; he keyed up again and told me he was going to level off in response to an RA. I then looked for the traffic and saw a Mode C intruder north of the aircraft southbound at 124 indicated altitude climbing. Unfortunately; they did not appear to me to be converging. We do not get conflict alerts with VFR's in PHX Approach's airspace so there is no leader line from the MCI. The histories indicated a slow aircraft. I never observed the B757 above 120; so when the pilot said he was going to level off that resolved him from conflicting with any traffic on my scope. I acknowledged the pilots report of the RA and and told him to advise me when he was able to resume his climb. We do not receive conflict alerts on VFR aircraft in PHX Approach's airspace which is necessary to stop thousands of unwarranted and false alerts. Even though it was the PHX Controller's responsibility to call the traffic before shipping the aircraft; I wish I would have picked up the slack. Hind sight is 20/20. Recommendation; more diligence in looking for and 'seeing' limited data blocks. Not becoming complacent with the VFR 'clutter' on the scope.

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	963126
Time
Date	201108
Local Time Of Day	1201-1800
Place
Locale Reference	ZAB.ARTCC
State Reference	NM
Aircraft 1
Make Model Name	B757 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Climb
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types

ZAB controller described a TCAS RA event involving a phx departure apparently conflicting with a VFR aircraft that had not prompted a conflict alert at ZAB.