ZAU controller described possible loss of separation event when weather deviation clearance was not ...

Narrative:

A B767 at FL380; had been shipped to P17 deviating to the right for weather; approximately a 310 heading. Aircraft X checked on at FL370 requesting FL430. I called from the d-side to P17 and asked for control for higher on aircraft X since the aircraft was still about 10 miles outside of our airspace. P17 approved the request. I informed the r-side that aircraft X was their control for higher. The r-side then climbed aircraft X. I had now moved over to relieve the r-side and the r-side was coordinating with P17 when we noticed that the B767 appeared to be turning hard left; right at aircraft X. The r-side asked P17 if they were turning the B767; the controller did not seem to understand what the r-side was asking. The r-side hung up the line and immediately told aircraft X to expedite and to turn as hard right as feasible with the weather; issuing the traffic. Aircraft X stated that he saw the traffic and was expediting the climb. The B767 also climbed; I assume a TCAS advisory; as I saw the altitude read FL383. I would guess that separation was less than 5 miles and 1000 feet but I am not sure of the exact distance. Aircraft X stated that he had the B767 in sight the entire time. Recommendation; making sure that deviating aircraft are aware of what a controller's expectations are...ie - right means right; not as necessary.

Original NASA ASRS Text

Title: ZAU Controller described possible loss of separation event when weather deviation clearance was not followed as expected by the Controller and a conflict with other traffic developed.

Narrative: A B767 at FL380; had been shipped to P17 deviating to the right for weather; approximately a 310 heading. Aircraft X checked on at FL370 requesting FL430. I called from the D-Side to P17 and asked for control for higher on Aircraft X since the aircraft was still about 10 miles outside of our airspace. P17 approved the request. I informed the R-Side that Aircraft X was their control for higher. The R-Side then climbed Aircraft X. I had now moved over to relieve the R-Side and the R-Side was coordinating with P17 when we noticed that the B767 appeared to be turning hard left; right at Aircraft X. The R-Side asked P17 if they were turning the B767; the Controller did not seem to understand what the R-Side was asking. The R-Side hung up the line and immediately told Aircraft X to expedite and to turn as hard right as feasible with the weather; issuing the traffic. Aircraft X stated that he saw the traffic and was expediting the climb. The B767 also climbed; I assume a TCAS advisory; as I saw the altitude read FL383. I would guess that separation was less than 5 miles and 1000 feet but I am not sure of the exact distance. Aircraft X stated that he had the B767 in sight the entire time. Recommendation; making sure that deviating aircraft are aware of what a controller's expectations are...ie - right means right; not as necessary.

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	882230
Time
Date	201004
Local Time Of Day	1801-2400
Place
Locale Reference	ZAU.ARTCC
State Reference	IL
Aircraft 1
Make Model Name	Small Transport Low Wing 2 Turbojet Eng
Flight Phase	Climb
Flight Plan	IFR
Person 1
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Deviation - Procedural Clearance Deviation - Track / Heading All Types Inflight Event / Encounter Weather / Turbulence

ZAU controller described possible loss of separation event when weather deviation clearance was not followed as expected by the controller and a conflict with other traffic developed.