Zic controller reports issuing a descent to FL240 to an air carrier in preparation for landing. Mome...

Narrative:

Air carrier was level at FL320 and landing sdf. I gave a descent clearance to FL240. The pilot read back 240 and the call sign. I then received a land line call from an adjacent sector. While we were talking about another aircraft; conflict alert went of with air carrier and an aircraft at FL360. Air carrier X's altitude was above FL330 and climbing (which is sector 93 - FL330-FL360). After a moment of disbelief that an aircraft landing sdf could possibly be climbing; I asked the pilot to say altitude. He answered; 'leveling at FL340.' the controller above me had no traffic other than the one at FL360; so I restated the clearance to descend and maintain FL240 and verified that my flight plan information was correct and he was landing sdf. I'm not really sure [about any recommendations]. The pilot read back the correct altitude; but obviously entered a 3 instead of a 2. It does seem strange that it didn't click with the crew when they started to climb instead of descend; but I know they have their own checklists to go through for landing and could have been focusing on that. I usually give a crossing [restriction] at yocky at FL240; but I don't know if that would have changed anything.

Original NASA ASRS Text

Title: ZIC Controller reports issuing a descent to FL240 to an air carrier in preparation for landing. Moments later the conflict alert goes off and the flight is detected climbing to FL340. The clearance to FL240 is reiterated.

Narrative: Air Carrier was level at FL320 and landing SDF. I gave a descent clearance to FL240. The pilot read back 240 and the call sign. I then received a land line call from an adjacent sector. While we were talking about another aircraft; conflict alert went of with Air Carrier and an aircraft at FL360. Air Carrier X's altitude was above FL330 and climbing (which is sector 93 - FL330-FL360). After a moment of disbelief that an aircraft landing SDF could possibly be climbing; I asked the pilot to say altitude. He answered; 'Leveling at FL340.' The Controller above me had no traffic other than the one at FL360; so I restated the clearance to descend and maintain FL240 and verified that my flight plan information was correct and he was landing SDF. I'm not really sure [about any recommendations]. The pilot read back the correct altitude; but obviously entered a 3 instead of a 2. It does seem strange that it didn't click with the crew when they started to climb instead of descend; but I know they have their own checklists to go through for landing and could have been focusing on that. I usually give a crossing [restriction] at YOCKY at FL240; but I don't know if that would have changed anything.

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

Attributes
ACN	957634
Time
Date	201107
Local Time Of Day	1801-2400
Place
Locale Reference	SDF.Airport
State Reference	KY
Environment
Light	Night
Aircraft 1
Make Model Name	EMB ERJ 145 ER&LR
Operating Under FAR Part	Part 121
Flight Phase	Climb
Flight Plan	IFR
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	Cruise
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance

Zic controller reports issuing a descent to FL240 to an air carrier in preparation for landing. Moments later the conflict alert goes off and the flight is detected climbing to FL340. The clearance to FL240 is reiterated.