Narrative:

I had an aircraft which was going to denver at FL360 in level flight going to denver 28 sector (aircraft X). Denver 28 had an aircraft at FL350 (aircraft Y) which they chose to climb to FL370 for another aircraft they took a point out on coming from denver 17 at FL350 (aircraft Z) which was on a vector to miss aircraft Y. Denver 28 called and said that aircraft Y was climbing to FL370 and they would be level by the boundary in order to miss aircraft X. I showed FL370 in the datablock for aircraft Y and started aircraft Y flashing at the next sector. Denver turned aircraft Z back on course from the vector putting him on a converging course with aircraft X. A couple of minutes later; denver 28 called and said that aircraft Y which they climbed was not going to make the altitude to miss aircraft X. Instead of vectoring either aircraft they said they needed aircraft X at FL340 instead. This was an issue because they turned back aircraft Z from the vector and put him in direct conflict with aircraft X. I expedited and had aircraft X report level at FL340 to miss the climbing traffic they had climbed into him and to get him below the additional traffic they turned back into aircraft X. I was not given communication with either aircraft Y or Z while I was attempting to fix the situation they had created until it was over. This unfortunately is not an uncommon occurrence with denver 17/18 and denver 28/39. Poor coordination; poor understanding of traffic situations; lack of care for the flying public; lack of positive control and a reliance in someone else fixing problems created by their controllers is observed on a daily basis. Additionally; if you are not capable of fixing the situation you caused; communications need to be transferred to the controller who is attempting to fix your mess up in their area. Provide controllers at those sectors additional training on communication best practices; separation standards; vectoring; and proper coordination procedures. This is a real problem. Instances like this and worse happen daily. It needs to stop for the sake of the flying public.

Related reports:

Google
 

Original NASA ASRS Text

Title: Kansas City Center Controller reported an unsafe situation due to the poor coordination from Denver Center Control.

Narrative: I had an aircraft which was going to Denver at FL360 in level flight going to Denver 28 sector (Aircraft X). Denver 28 had an aircraft at FL350 (Aircraft Y) which they chose to climb to FL370 for another aircraft they took a point out on coming from Denver 17 at FL350 (Aircraft Z) which was on a vector to miss Aircraft Y. Denver 28 called and said that Aircraft Y was climbing to FL370 and they would be level by the boundary in order to miss Aircraft X. I showed FL370 in the datablock for Aircraft Y and started Aircraft Y flashing at the next sector. Denver turned Aircraft Z back on course from the vector putting him on a converging course with Aircraft X. A couple of minutes later; Denver 28 called and said that Aircraft Y which they climbed was not going to make the altitude to miss Aircraft X. Instead of vectoring either aircraft they said they needed Aircraft X at FL340 instead. This was an issue because they turned back Aircraft Z from the vector and put him in direct conflict with Aircraft X. I expedited and had Aircraft X report level at FL340 to miss the climbing traffic they had climbed into him and to get him below the additional traffic they turned back into Aircraft X. I was not given communication with either Aircraft Y or Z while I was attempting to fix the situation they had created until it was over. This unfortunately is not an uncommon occurrence with Denver 17/18 and Denver 28/39. Poor coordination; poor understanding of traffic situations; lack of care for the flying public; lack of positive control and a reliance in someone else fixing problems created by their Controllers is observed on a daily basis. Additionally; if you are not capable of fixing the situation you caused; communications need to be transferred to the Controller who is attempting to fix your mess up in their area. Provide Controllers at those sectors additional training on communication best practices; separation standards; vectoring; and proper coordination procedures. This is a real problem. Instances like this and worse happen daily. It needs to stop for the sake of the flying public.

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.