Widebody; Low Wing; 2 Turbojet Eng
Air Traffic Control Fully Certified
Air Traffic Control Time Certified In Pos 1 (yrs) 22.6
Situational Awareness; Confusion; Human-Machine Interface
ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Air Traffic Control Issued New Clearance
Human Factors; Procedure
Aircraft Y requested climb from FL370 to FL390. I looked at the data block for Aircraft Z; about 60 miles behind Aircraft Y; thinking this was the aircraft requesting higher. I assessed the traffic situation for Aircraft Z; and issued a climb to Aircraft Y. I was alerted to the loss of separation via conflict alert and traffic Aircraft X who was at FL380 opposite direction.
During a high volume session with bad rides and weather deviations Aircraft Y asked for a climb to FL390. He then climbed him from FL370 to FL390 but entered the data on Aircraft Z's data block who was about 40 miles behind him. During the transmission I was scanning potential conflicts and checking routes and did not catch that the data was entered on the wrong aircraft. Conflict Alert went off after the aircraft started to climb out of FL375 and the radar controller issued him a 20 degree left turn to give more room in between aircraft although they would have not collided. Busy workload and maybe a little bit of complacency or hearing what you want to hear may have played a role in this incident on both the radar and D side positions.I don't have any recommendations as to prevent it. I think it was an honest mistake during busy workload and just the one time is enough to make a person more vigilant and aware of possible mistakes.
ZBW Center controllers reported that the Controller working radar assigned a climb to the wrong aircraft which lead to a loss of separation.