Date: 201505
Local time of day: 0001-0600
Location: ZSE.ARTCC, WA
Light: Night
Aircraft: Medium Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZSE
ATC / advisory: Center ZSE
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Confusion; Distraction; Situational Awareness; Time Pressure
Second reporter function: Enroute
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: Aircraft X departed SEA filed for FL230 via V298 - YKM - ZZZ.  Departed and on initial contact was climbed to FL230. Approximately 10 miles West of the BEEZR intersection Aircraft X was issued direct routing to DEVLE changing aircraft routing/flight path to approximately 10 miles North of YKM/V298 at the time of crossing the sector boundary. Approximately 5 miles later the aircraft was assigned FL210 for traffic (aircraft descending to FL220 west-bound). Approximately 5 miles West of the sector boundary Aircraft X was clear of traffic and climbed to FL230 and communications was transferred to the next sector. At this time the aircraft was approximately 12 - 13 miles west of R6714 (active to FL220). The aircraft's last observed climb rate was approximately 1;500 feet per minute. The next sector did not call to gain control of the aircraft for turns or to increase climb; etc. 2.5 miles past the boundary the data block was dropped from the scope. I was not aware that Aircraft X did not climb the necessary 2;000 feet to top R6714. The observed limited data block made no turns to avoid the military airspace.  I'm not sure. I did not speak to the receiving controller to find out if he/she was too busy to notice the climb rate or too busy to turn the aircraft to the south to miss the airspace laterally. I also did not speak to the pilot to find out if there was some circumstance that led to a decrease in climb rate; etc.  I will in the future not issue direct routing in these circumstances or assign a climb rate that will guarantee altitude separation even further West of R6714.


Second narrative: I was working R18 and took a handoff from sector 01 on a Aircraft X showing climbing to FL230 currently at FL210. The Yakima Firing Center was in use up to FL220 with aircraft operations. The aircraft was a Medium Large Transport. The handoff was taken 2 minutes from the boundary. Normally with the firing center in use these aircraft headed to ZZZ like this one was; are routed around the firing center via Yakima. When the aircraft checked on he was on the the boundary between sector 01/18 and 'leaving FL210 climbing to FL230'.  The aircraft then was 4 miles from the Firing center and 5 seconds later when I noticed he was not routed over Yakima and his climb rate was insufficent to top the airspace I issued right turn 15 degrees to keep him out. It was too little to late. If the last controller hadn't waited to the last minute to ship and climb the aircraft; or had he not short-cutted him than it would of prevented this.


Synopsis: ZSE Controller reports of an aircraft that doesn't climb at a faster rate and enters a restricted area after change of communications. Second Controller reports of the same operation; but states it was the Controllers fault for not shipping the aircraft and waiting to the last minute to climb the aircraft.