Narrative:

Aircraft #2 was pointed out to ZOB. ZOB controller advised 'pointout approved, miss the traffic you're giving me.' aircraft #2 was in conflict with another aircraft just to his north, converging. I vectored aircraft #2 behind this traffic, putting him in conflict with aircraft #1. Aircraft #1 was due to be descended into pit, but the last altitude verbally coordinated was FL210. I initiated coordination several times with the ZOB controller, but no calls were acknowledged. I stopped aircraft #2's climb at FL200. Aircraft #1 was descended by ZOB below FL210. 7110.65B is very unclr as to whether the receiving controller of a pointout can alter the heading or altitude of traffic that he is requiring the controller that initiated the pointout to separate. It's very hard to separate 2 aircraft when the aircraft is changing altitude and heading without coordination.

Google
 

Original NASA ASRS Text

Title: ZID CTLR INVOLVED WITH AN OPERROR BTWN A321 AND CARJ DUE TO INCOMPLETE COORD WITH ADJOINING ZID CTLR.

Narrative: ACFT #2 WAS POINTED OUT TO ZOB. ZOB CTLR ADVISED 'POINTOUT APPROVED, MISS THE TFC YOU'RE GIVING ME.' ACFT #2 WAS IN CONFLICT WITH ANOTHER ACFT JUST TO HIS N, CONVERGING. I VECTORED ACFT #2 BEHIND THIS TFC, PUTTING HIM IN CONFLICT WITH ACFT #1. ACFT #1 WAS DUE TO BE DSNDED INTO PIT, BUT THE LAST ALT VERBALLY COORDINATED WAS FL210. I INITIATED COORD SEVERAL TIMES WITH THE ZOB CTLR, BUT NO CALLS WERE ACKNOWLEDGED. I STOPPED ACFT #2'S CLB AT FL200. ACFT #1 WAS DSNDED BY ZOB BELOW FL210. 7110.65B IS VERY UNCLR AS TO WHETHER THE RECEIVING CTLR OF A POINTOUT CAN ALTER THE HDG OR ALT OF TFC THAT HE IS REQUIRING THE CTLR THAT INITIATED THE POINTOUT TO SEPARATE. IT'S VERY HARD TO SEPARATE 2 ACFT WHEN THE ACFT IS CHANGING ALT AND HDG WITHOUT COORD.

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.