ZID center controller reported climbing an aircraft into conflict with another enroute aircraft.

Attributes
ACN	1464254
Time
Date	201707
Local Time Of Day	0601-1200
Place
Locale Reference	ZID.ARTCC
State Reference	IN
Environment
Light	Daylight
Aircraft 1
Make Model Name	Large Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 121
Flight Phase	Cruise
Route In Use	Vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	Medium Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 121
Flight Phase	Climb
Route In Use	Vectors
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 6
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types Inflight Event / Encounter Weather / Turbulence

Narrative:

Aircraft X was leveled at FL300 direct vhp after reroute for weather. Aircraft Y was turning to flm after emege at FL290 looking for higher. Aircraft Y checks on and I immediately climbed to FL310 missing a keystroke for the interim altitude (which would've resulted in an immediate conflict alert). After mode C showed FL292; conflict alert goes off to which I responded with a vector of 40 degrees left on both aircraft. Right after vectors were issued; pilots started responding to ras. Traffic was never called since I was focused on the situation analyzing how to avoid it from becoming worse than what it was. After falcon review the closest point was 2.55 miles and 800 ft. This was all a personal issue. Traffic was overlooked and keyboard entry for interim altitude was missed which would've resulted in immediate conflict alert. This would've given me time to react and stop aircraft Y at FL290.

Original NASA ASRS Text

Title: ZID Center Controller reported climbing an aircraft into conflict with another enroute aircraft.

Narrative: Aircraft X was leveled at FL300 direct VHP after reroute for weather. Aircraft Y was turning to FLM after EMEGE at FL290 looking for higher. Aircraft Y checks on and I immediately climbed to FL310 missing a keystroke for the interim altitude (which would've resulted in an immediate conflict alert). After Mode C showed FL292; conflict alert goes off to which I responded with a vector of 40 degrees left on both aircraft. Right after vectors were issued; pilots started responding to RAs. Traffic was never called since I was focused on the situation analyzing how to avoid it from becoming worse than what it was. After FALCON review the closest point was 2.55 miles and 800 ft. This was all a personal issue. Traffic was overlooked and keyboard entry for interim altitude was missed which would've resulted in immediate conflict alert. This would've given me time to react and stop Aircraft Y at FL290.

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.