ZAB controller described a conflict event involving a VFR aircraft descending for prc and an air car...

Narrative:

After a busy session with weather deviations on both arrivals and departures into phoenix airspace; the traffic was getting lighter. I was sending a VFR aircraft at 17;500 northeast bound through luke (luf) approaches airspace to land at prescott. The radar hand off was completed and the data block was dropped as soon as it entered luf airspace. An A320 was a departure out of phoenix deviated northwards approximately 12 miles north of bxk. At the time I dropped the VFR target; I determined that the A320 and the VFR would not be a factor due to altitude differences. While I was giving a briefing to a relieving controller; the A320 reported an RA that they had to climb faster. One factor may have been that the VFR also deviated north as well as the A320; tying them up further. The big factor is that this confliction occurred in luf's airspace thus there was no conflict alert. Another factor is the winding down from a very busy session and that the controller in charge acted as a limited d-side during the busy session and I didn't have a d-side at the time of the incident. Recommendation; I think that I should have had a d-side at the time or at least during the busy session; in fact; I requested a d-side. The other problem is the way that the system is set up. The aircraft was leaving phoenix approach; transiting luf approach and talking to ZAB. In this area; there is not conflict alert. This is an issue that has occurred before with phoenix approach.

Original NASA ASRS Text

Title: ZAB Controller described a conflict event involving a VFR aircraft descending for PRC and an air carrier departure from PHX; causal factors included weather deviations; dropped Data Block and absent Conflict Alert capabilities.

Narrative: After a busy session with weather deviations on both arrivals and departures into Phoenix airspace; the traffic was getting lighter. I was sending a VFR aircraft at 17;500 northeast bound through Luke (LUF) Approaches airspace to land at Prescott. The RADAR hand off was completed and the Data Block was dropped as soon as it entered LUF airspace. An A320 was a departure out of Phoenix deviated northwards approximately 12 miles north of BXK. At the time I dropped the VFR target; I determined that the A320 and the VFR would not be a factor due to altitude differences. While I was giving a briefing to a relieving controller; the A320 reported an RA that they had to climb faster. One factor may have been that the VFR also deviated north as well as the A320; tying them up further. The big factor is that this confliction occurred in LUF's airspace thus there was no Conflict Alert. Another factor is the winding down from a very busy session and that the CIC acted as a limited D-Side during the busy session and I didn't have a D-side at the time of the incident. Recommendation; I think that I should have had a D-Side at the time or at least during the busy session; in fact; I requested a D-Side. The other problem is the way that the system is set up. The aircraft was leaving Phoenix Approach; transiting LUF Approach and talking to ZAB. In this area; there is not Conflict Alert. This is an issue that has occurred before with Phoenix Approach.

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	976369
Time
Date	201110
Local Time Of Day	1801-2400
Place
Locale Reference	ZAB.ARTCC
State Reference	NM
Aircraft 1
Make Model Name	A320
Operating Under FAR Part	Part 121
Flight Phase	Climb
Flight Plan	IFR
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	Descent
Route In Use	None
Flight Plan	VFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict

ZAB controller described a conflict event involving a VFR aircraft descending for prc and an air carrier departure from phx; causal factors included weather deviations; dropped data block and absent conflict alert capabilities.