Narrative:

Aircraft X had departed msp and was climbing to FL350 north of alo; passing through FL265. A red alert notified me on my enroute decision support tool (edst) that it was a conflict with aircraft Y. I had handed off aircraft Y to msp center sector P17 (mason city). I called P17 and told them coton (ZAU75) will work aircraft X at FL310; in order to miss the aircraft Y at FL330. The P17 controller stated aircraft X was issued a crossing restriction to top aircraft Y. The aircraft began to flash when I had noticed aircraft X was leveling off at FL330. I called P17 and said I am turning aircraft Y to avoid a traffic alert and loss of separation. He said the aircraft was issued a crossing and could not make it. I said I was going to turn aircraft Y 25R [25 degrees right]. Mason city turned aircraft X to a 090 heading. At 6.10 miles I called a traffic alert to aircraft Y and descended the aircraft to ensure vertical separation. The aircraft lost separation at approximately 300 feet vertically and 4.61 miles laterally. Mason city called me back to say aircraft X missed his crossing restriction to top aircraft Y and apreqed direct to iow after the aircraft was free of conflict from aircraft Y and positive separation was reestablished. When mason city takes radar or a hand off on an aircraft they need to miss their traffic and not use crossing restrictions for aircraft climbing. This does not seem efficient at all and does not always work.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZAU Center Controller reported a loss of separation when an aircraft was unable to comply with their issued crossing restriction.

Narrative: Aircraft X had departed MSP and was climbing to FL350 north of ALO; passing through FL265. A red alert notified me on my Enroute Decision Support Tool (EDST) that it was a conflict with Aircraft Y. I had handed off Aircraft Y to MSP Center Sector P17 (Mason City). I called P17 and told them COTON (ZAU75) will work Aircraft X at FL310; in order to miss the Aircraft Y at FL330. The P17 controller stated Aircraft X was issued a crossing restriction to top Aircraft Y. The aircraft began to flash when I had noticed Aircraft X was leveling off at FL330. I called P17 and said I am turning Aircraft Y to avoid a traffic alert and loss of separation. He said the aircraft was issued a crossing and could not make it. I said I was going to turn Aircraft Y 25R [25 degrees right]. Mason City turned Aircraft X to a 090 heading. At 6.10 miles I called a traffic alert to Aircraft Y and descended the aircraft to ensure vertical separation. The aircraft lost separation at approximately 300 feet vertically and 4.61 miles laterally. Mason City called me back to say Aircraft X missed his crossing restriction to top Aircraft Y and APREQed direct to IOW after the aircraft was free of conflict from Aircraft Y and positive separation was reestablished. When Mason City takes RADAR or a hand off on an aircraft they need to miss their traffic and not use crossing restrictions for aircraft climbing. This does not seem efficient at all and does not always work.

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