Date: 201309
Local time of day: 1801-2400
Location: ZJX.ARTCC, FL
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZJX
ATC / advisory: Center ZJX
Second aircraft: Small Transport; Low Wing; 2 Turbojet Eng
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
Result: Air Traffic Control Issued New Clearance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: While working R34 and R33 combined; I was 'cleaning up' a rather complex MCO sequencing situation that was left from the previous Controller. I had 6 Orlando landing aircraft on a vector with two others on course leading the line. I had approximately 12 other tracks at the time; equally divided between other landers; climbers; and overflight aircraft. The CIC who was in charge was relieved when the Supervisor returned. Upon returning to the area; he immediately ordered 33 to be split from 34. I flashed all appropriate aircraft to the new R33 Controller and shipped them. The large transport was flashed to R17 and a few minutes later; I shipped the large transport to 17's frequency. The large transport read it back but apparently never flipped the switch. He was level at FL410; direct to BALKE; which required a Point out to R78 (that was completed). R17 also had a hand-off on a small transport at FL410 enroute to RDU. I am not sure if R17 ever made initial contact with the small transport; but he did try contacting him many times (at least 7) and other controllers also called previous sectors for him looking for that aircraft. As it developed; the R17 Controller asked me to 'try the large transport again.' So I called him and he responded. I gave him an initial turn of 'RIGHT H090;' bad move; I meant left; I was thinking left; flustered; I said right. I corrected it right away and told him to turn left immediately to H090 and issued the traffic alert phraseology at 2 o'clock and 8 miles. The large transport; although issued a traffic alert and having used 'immediately;' still did not turn in a timely manner (probably delayed for about a minute; at least). I called R78 to coordinate the turn. Then R17 told me to descend the large transport to FL390. So I did and again I used 'immediately' and re-issued a traffic alert; at which time; the pilot responded with 'Roger; we see the traffic' very nonchalantly. I re-coordinated with R78. It wasn't until the two aircraft's closest hit (I think at 3.8) did my RADAR show the large transport aircraft finally beginning his turn and he started his descent a few seconds later; but it was too late at that point. Recommendation; I should have called the large transport back using some imminent and adamant plain language telling him to basically; 'Crank it; like yesterday.' I will listen more closely if a controller is trying to find an aircraft that I shipped to him. I will not issue the wrong direction of turn next time; but with how slowly the large transport did turn; he probably never began an initial right turn before going left.




Synopsis: ZJX Controller described a loss of separation event when issuing a turn direction opposite of what was needed.