Narrative:

Aircraft #1 was on runway heading for base leg traffic which would have interfered with the departure procedure. Departed las runway 25R. Aircraft #2 was in VFR descent from vicinity of clarr intersection to vgt. Aircraft #2 descended into a conflict with aircraft #1 which was climbing to 7000 ft, then stopped at 6500 ft. Aircraft #2 was under control of dag sector. Aircraft #1 was with med sector (myself). Med accepted an automated handoff on aircraft #2 about 25 mi southwest of las. Aircraft #1 was in dab airspace, using a procedure which requires both controllers to 'quick-look' each other. I, the med controller, was distracted by the base leg traffic and vectors required to miss it. I became aware of the situation too late to affect the loss of separation. Better scanning could have avoided the situation. The dag controller became aware of the situation sooner, but used poor judgement in attempting corrective action. He used a vector, when altitude would have worked easily. An earlier xfer of communication of aircraft #2 to med would also have been beneficial. Supplemental information from acn 487854: I was xferring communications on the lear, I noticed the B727 was further west than normal, so I issued traffic and turned the lear northbound to avoid the B727, not realizing the B727 was not flying the pdr, and shipped him to the other frequency. I asked the other controller what the B727 was doing and he replied that he was vectoring him to avoid the lear. He was referring to the other inbound lear, but I didn't know that. I was under the impression that he was resolving the situation. Lack of communication was probably a contributing factor.

Related reports:

Google
 

Original NASA ASRS Text

Title: TWO RADAR CTLRS AT LAS WORKING TFC IN THE SAME AIRSPACE RESULT IN TFC CONFLICT.

Narrative: ACFT #1 WAS ON RWY HEADING FOR BASE LEG TFC WHICH WOULD HAVE INTERFERED WITH THE DEP PROC. DEPARTED LAS RWY 25R. ACFT #2 WAS IN VFR DSCNT FROM VICINITY OF CLARR INTXN TO VGT. ACFT #2 DSNDED INTO A CONFLICT WITH ACFT #1 WHICH WAS CLBING TO 7000 FT, THEN STOPPED AT 6500 FT. ACFT #2 WAS UNDER CTL OF DAG SECTOR. ACFT #1 WAS WITH MED SECTOR (MYSELF). MED ACCEPTED AN AUTOMATED HDOF ON ACFT #2 ABOUT 25 MI SW OF LAS. ACFT #1 WAS IN DAB AIRSPACE, USING A PROC WHICH REQUIRES BOTH CTLRS TO 'QUICK-LOOK' EACH OTHER. I, THE MED CTLR, WAS DISTRACTED BY THE BASE LEG TFC AND VECTORS REQUIRED TO MISS IT. I BECAME AWARE OF THE SIT TOO LATE TO AFFECT THE LOSS OF SEPARATION. BETTER SCANNING COULD HAVE AVOIDED THE SIT. THE DAG CTLR BECAME AWARE OF THE SIT SOONER, BUT USED POOR JUDGEMENT IN ATTEMPTING CORRECTIVE ACTION. HE USED A VECTOR, WHEN ALT WOULD HAVE WORKED EASILY. AN EARLIER XFER OF COM OF ACFT #2 TO MED WOULD ALSO HAVE BEEN BENEFICIAL. SUPPLEMENTAL INFO FROM ACN 487854: I WAS XFERRING COMS ON THE LEAR, I NOTICED THE B727 WAS FURTHER W THAN NORMAL, SO I ISSUED TFC AND TURNED THE LEAR NBOUND TO AVOID THE B727, NOT REALIZING THE B727 WAS NOT FLYING THE PDR, AND SHIPPED HIM TO THE OTHER FREQ. I ASKED THE OTHER CTLR WHAT THE B727 WAS DOING AND HE REPLIED THAT HE WAS VECTORING HIM TO AVOID THE LEAR. HE WAS REFERRING TO THE OTHER INBOUND LEAR, BUT I DIDN'T KNOW THAT. I WAS UNDER THE IMPRESSION THAT HE WAS RESOLVING THE SIT. LACK OF COM WAS PROBABLY A CONTRIBUTING FACTOR.

Data retrieved from NASA's ASRS site as of July 2007 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.