Narrative:

Aircraft X was descending from FL330 to FL240. The aircraft checked on and was given clearance to FL190. Conflict alert went off. Aircraft Y, eastbound at FL250, was in conflict with aircraft X. The bae sector controller called and stated that aircraft Y was turned to a 130 degree heading. Lnr issued traffic to aircraft X. The bae controller called again to say aircraft Y is on a 160 degree heading. I turned aircraft X to a 120 degree heading. Conflict alert went off, 4.1 mi horizontal, 500 ft vertical. Supplemental information from acn 415548: I was working a high altitude sector and sequencing aircraft for msp. An ord arrival was forgot about at FL330. When I realized, I descended aircraft #1 to FL240 and shipped him right away to the low altitude sector so he could be descended for ord. About this time I got a handoff on aircraft #2 at FL250 about 15 mi west msn. The conflict alert activated right away as aircraft #2 was checking on frequency. Aircraft #2 was issued a right turn to a 130 degree heading. Then I immediately called the low altitude sector and told him what I was doing and asked him to take action. His aircraft wasn't turning so I turned aircraft #2 to a 160 degree heading. I then called back and asked the other controller to specifically turn the aircraft. Separation was lost. 2 things could have helped this situation. I was getting busy and asked for help approximately 30 seconds prior to conflict alert activating. I should have asked for help sooner. Be more specific in my coordination with other controller. I assumed when I told him I was turning south and asked him to take action, he would turn his aircraft east. He took no action for 1 1/2 mins. This was too late to be of any help.

Related reports:

Google
 

Original NASA ASRS Text

Title: 2 ARTCC RADAR CTLRS ARE INVOLVED IN A LOSS OF SEPARATION BTWN A B737 AND A B727 WHEN INTRAFAC COORD IS NOT COMPLETE OR TIMELY.

Narrative: ACFT X WAS DSNDING FROM FL330 TO FL240. THE ACFT CHKED ON AND WAS GIVEN CLRNC TO FL190. CONFLICT ALERT WENT OFF. ACFT Y, EBOUND AT FL250, WAS IN CONFLICT WITH ACFT X. THE BAE SECTOR CTLR CALLED AND STATED THAT ACFT Y WAS TURNED TO A 130 DEG HDG. LNR ISSUED TFC TO ACFT X. THE BAE CTLR CALLED AGAIN TO SAY ACFT Y IS ON A 160 DEG HDG. I TURNED ACFT X TO A 120 DEG HDG. CONFLICT ALERT WENT OFF, 4.1 MI HORIZ, 500 FT VERT. SUPPLEMENTAL INFO FROM ACN 415548: I WAS WORKING A HIGH ALT SECTOR AND SEQUENCING ACFT FOR MSP. AN ORD ARR WAS FORGOT ABOUT AT FL330. WHEN I REALIZED, I DSNDED ACFT #1 TO FL240 AND SHIPPED HIM RIGHT AWAY TO THE LOW ALT SECTOR SO HE COULD BE DSNDED FOR ORD. ABOUT THIS TIME I GOT A HDOF ON ACFT #2 AT FL250 ABOUT 15 MI W MSN. THE CONFLICT ALERT ACTIVATED RIGHT AWAY AS ACFT #2 WAS CHKING ON FREQ. ACFT #2 WAS ISSUED A R TURN TO A 130 DEG HDG. THEN I IMMEDIATELY CALLED THE LOW ALT SECTOR AND TOLD HIM WHAT I WAS DOING AND ASKED HIM TO TAKE ACTION. HIS ACFT WASN'T TURNING SO I TURNED ACFT #2 TO A 160 DEG HDG. I THEN CALLED BACK AND ASKED THE OTHER CTLR TO SPECIFICALLY TURN THE ACFT. SEPARATION WAS LOST. 2 THINGS COULD HAVE HELPED THIS SIT. I WAS GETTING BUSY AND ASKED FOR HELP APPROX 30 SECONDS PRIOR TO CONFLICT ALERT ACTIVATING. I SHOULD HAVE ASKED FOR HELP SOONER. BE MORE SPECIFIC IN MY COORD WITH OTHER CTLR. I ASSUMED WHEN I TOLD HIM I WAS TURNING S AND ASKED HIM TO TAKE ACTION, HE WOULD TURN HIS ACFT E. HE TOOK NO ACTION FOR 1 1/2 MINS. THIS WAS TOO LATE TO BE OF ANY HELP.

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.