Narrative:

Four F16s climbing southbound; another controller thought they climbed the aircraft to FL280; but climbed them to same altitude as traffic. The F16s showed reported at FL280. I reached out to them for an initial check in and they stated they were level at FL270. I responded you mean FL280 and they responded no; level at FL270. Apparently the other controller thought he/she climbed the aircraft to FL280 and actually climbed them to the altitude of the traffic. From my own experience; sometimes you physically look at the traffic's mode C you mean to miss and inadvertently say the altitude of the traffic not the altitude you mean to separate the traffic.

Google
 

Original NASA ASRS Text

Title: Enroute Controller described a loss of separation event when assigning an altitude in conflict with another aircraft; the reports indicating the controller was thinking one altitude but in fact assigned another; perhaps a Mode C indication.

Narrative: Four F16s climbing southbound; another controller thought they climbed the aircraft to FL280; but climbed them to same altitude as traffic. The F16s showed reported at FL280. I reached out to them for an initial check in and they stated they were level at FL270. I responded you mean FL280 and they responded no; level at FL270. Apparently the other controller thought he/she climbed the aircraft to FL280 and actually climbed them to the altitude of the traffic. From my own experience; sometimes you physically look at the traffic's Mode C you mean to miss and inadvertently say the altitude of the traffic not the altitude you mean to separate the traffic.

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