Narrative:

Aircraft X checked onto my frequency requesting a right deviation for weather that was impacting my sector further north. I went ahead and approved the right deviation. Approximately 3 to 4 minutes prior to aircraft X checking on frequency I had aircraft Y check on as well flying a similar route that of aircraft X; that had also requested right deviations for weather. Both aircraft at the time were at interim altitudes. My plan was to climb aircraft Y to 35000 feet and to hand that aircraft off to the next sector. Instead; I inadvertently climbed aircraft X to 35000 feet updating the data block for aircraft Y to FL350. Within 15 to 20 seconds of issuing the climb aircraft X reported an RA with aircraft Z southbound descending to 34000 feet. It caught me completely off guard for I still showed the interim of FL330 in the data block of aircraft X. Aircraft X proceeded to level off below the other aircraft Z. When aircraft X was clear of that aircraft I descended aircraft X back down to 33000 feet.I have played this event over and over again in my head as to what and why this situation occurred. I knew all about the traffic; as well as the weather conditions during that session. It was just like any other day here at the center during the summer period. You must be extremely vigilant when you have periods like this. As I look back; and as focused/aware of the situation I felt that I was in; I got into a hurry to climb aircraft Y to his requested altitude of 35000 feet; as well as handing the aircraft off to the next sector. This lead to the transposing of the call signs of aircraft Y and aircraft X. This simply comes down to being a bit more patient therefore maintaining a better focus of the situation at hand.

Google
 

Original NASA ASRS Text

Title: ZJX Center Controller inadvertently climbed the wrong aircraft into conflict with a descending traffic.

Narrative: Aircraft X checked onto my frequency requesting a right deviation for weather that was impacting my sector further north. I went ahead and approved the right deviation. Approximately 3 to 4 minutes prior to Aircraft X checking on frequency I had Aircraft Y check on as well flying a similar route that of Aircraft X; that had also requested right deviations for weather. Both aircraft at the time were at interim altitudes. My plan was to climb Aircraft Y to 35000 feet and to hand that aircraft off to the next sector. Instead; I inadvertently climbed Aircraft X to 35000 feet updating the data block for Aircraft Y to FL350. Within 15 to 20 seconds of issuing the climb Aircraft X reported an RA with Aircraft Z southbound descending to 34000 feet. It caught me completely off guard for I still showed the interim of FL330 in the data block of Aircraft X. Aircraft X proceeded to level off below the other Aircraft Z. When Aircraft X was clear of that aircraft I descended Aircraft X back down to 33000 feet.I have played this event over and over again in my head as to what and why this situation occurred. I knew all about the traffic; as well as the weather conditions during that session. It was just like any other day here at the Center during the summer period. You must be extremely vigilant when you have periods like this. As I look back; and as focused/aware of the situation I felt that I was in; I got into a hurry to climb Aircraft Y to his requested altitude of 35000 feet; as well as handing the aircraft off to the next sector. This lead to the transposing of the call signs of Aircraft Y and Aircraft X. This simply comes down to being a bit more patient therefore maintaining a better focus of the situation at hand.

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.