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.

Related reports:

Google
 

Original NASA ASRS Text

Title: 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.

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.

Data retrieved from NASA's ASRS site 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.