Enroute controller described a conflict event at FL350/370; claiming one of the aircraft was slow to...

Narrative:

An A319 was in level flight at FL350 and he requested a climb to FL370. I did not do an adequate traffic search and climbed him. Within one minute; the A319 and air carrier Y started flashing. Air carrier Y was in level flight at FL360. I quickly turned the A319 thirty degrees left for traffic and he complied. I then turned air carrier Y thirty degrees left and descended him to FL340 for traffic. Air carrier Y then asked if he could climb to FL380. I came back on the frequency and told him to turn thirty degrees left and descend immediately. He came back questioning the turn and I told him to just descend and turn now. Luckily the A319 understood the gravity of the situation and picked up his climb rate and when I asked for altitude reports from both aircraft I had five miles and 1;000 ft. Air carrier Y actions were not good enough. When a control instruction is issued for traffic; it needs to be accomplished and not debated. I was extremely concerned for about 30 seconds that the two aircraft might collide mid-air. I need to do a better traffic scan that is basic ATC. The pilots need to act quicker and accordingly and not drag their feet on these clearances.

Original NASA ASRS Text

Title: Enroute Controller described a conflict event at FL350/370; claiming one of the aircraft was slow to respond when given an instruction contributing to the occurrence.

Narrative: An A319 was in level flight at FL350 and he requested a climb to FL370. I did not do an adequate traffic search and climbed him. Within one minute; the A319 and Air Carrier Y started flashing. Air Carrier Y was in level flight at FL360. I quickly turned the A319 thirty degrees left for traffic and he complied. I then turned Air Carrier Y thirty degrees left and descended him to FL340 for traffic. Air Carrier Y then asked if he could climb to FL380. I came back on the frequency and told him to turn thirty degrees left and descend immediately. He came back questioning the turn and I told him to just descend and turn now. Luckily the A319 understood the gravity of the situation and picked up his climb rate and when I asked for altitude reports from both aircraft I had five miles and 1;000 FT. Air Carrier Y actions were not good enough. When a control instruction is issued for traffic; it needs to be accomplished and not debated. I was extremely concerned for about 30 seconds that the two aircraft might collide mid-air. I need to do a better traffic scan that is basic ATC. The pilots need to act quicker and accordingly and not drag their feet on these clearances.

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.

Attributes
ACN	1097978
Time
Date	201306
Local Time Of Day	1201-1800
Place
Locale Reference	ZZZ.ARTCC
State Reference	US
Aircraft 1
Make Model Name	A319
Operating Under FAR Part	Part 121
Flight Phase	Climb
Flight Plan	IFR
Aircraft 2
Make Model Name	Medium Large Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 121
Flight Phase	Descent
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Altitude Overshoot Deviation - Procedural Clearance Deviation - Track / Heading All Types

Enroute controller described a conflict event at FL350/370; claiming one of the aircraft was slow to respond when given an instruction contributing to the occurrence.