Date: 201304
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Aircraft: Gulfstream IV / G350 / G450
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Second aircraft: B737 Undifferentiated or Other Model
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Communication Breakdown; Situational Awareness
Second reporter function: Captain
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Aircraft RA; Person Air Traffic Control; Person Flight Crew
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was working Sector X combined. A Gulfstream was on the [SID] departure out of the terminal area. He was issued the climb to FL410. Sector Y had traffic and suggested he go direct [to the fix]. I issued the clearance. Later on after the hand off was taken by Sector Y; the Controller said 'you may want to stop him.' I was in the process of switching him when he put an interim altitude of FL390 in the data block. I said; 'Oh; I'm sorry; I see he didn't get the altitude.' The other Controller said no worries; I got it. In the meantime the Gulfstream is out of FL360 still climbing. The Gulfstream checked on to [Sector] Y's frequency climbing to FL410; and the Controller 'rogered' him. The Controller on Sector Y then gave a briefing. Within about 1 minute of the new Controller sitting down; the Gulfstream and the B737 start flashing. FL390 was in the data block; but the Gulfstream was out of FL391. He was never stopped at the appropriate altitude. The new Controller immediately descended him and the B737 responded to an RA. They never got within the 5 miles and 1;000 FT because of the quick action of the new Controller and the RA. Basically; it was a communication break down. I assumed the Controller understood what I was saying; and he thought I had stopped him. He did not catch it on the initial check on of the Gulfstream; which lead to potentially terrible situation. I should have made sure the aircraft was stopped.


Second narrative: This report is from a TCAS RA which required us to climb from our cruise altitude. We were at cruise at FL400. We got a TCAS Alert that went immediately to an RA from an aircraft climbing from below. I immediately disconnected the autopilot and selected emergency thrust and started a climb using TCAS guidance. I notified ATC we were responding to an RA and were climbing. We climbed to FL410 before we got a clear of conflict. The Gulfstream came within 300 FT of us before we started to get separation. During the maneuver; it was the closest I ever came to another aircraft not in a formation flight! ATC started inquiring to the Gulfstream when they continued to climb through FL390. The Gulfstream said they were clear to FL410. ATC said he was 'sorry;' that he had just sat down. TCAS saved this flight!


Synopsis: Enroute Controller described a loss of separation event when coordination during the ATC position relief briefing was confused reference the climb clearance resulting in the TCAS RA.