Narrative:

I was working sector 14 at ZMP. In the previous sector, air carrier X widebody transport, from dtw to kjaa, had requested and received permission to deviate. This information was circled in red on the flight progress strip to indicate that the information was relayed to me. I do not remember being informed of this, and there was no evidence of the coordination on the facility tapes of the incident. Air carrier X's route was to take it over yqt. When he checked on my frequency, he stated that he was deviating south and west. However, an interphone call was placed to my sector at the time he checked in about an unrelated aircraft, and I didn't hear nor acknowledge his call. 10 seconds later he checked in, 'air carrier X FL310, ' with no mention of deviation. I handed him off to winnipeg center when he was 15 south of cmx and shipped him. Approximately 4 mins later I noticed him about 10 mi from R4305, and called zwg and advised him to turn the aircraft. There were no fgt's within 30 mi of air carrier X. After informing the supervisor, I called zwg and asked where air carrier X was going, and they told me he was deviating for build-ups. Air carrier X was in the airspace for 10 mi, and it was notamed active from 000b450. Although the ntap seemed to show the aircraft on a constant heading toward the restr area, it looked like he was going direct yqt to me. He was cleared direct yqt approximately 80 southeast of tvc. There were at least 10 limited data blocks, and 3 airspace data blocks near air carrier X's route from saw to yqt, perhaps affecting my ability to take corrective action sooner. However,I had no reason to believe his flight plan would come in close proximity to the restr area.

Related reports:

Google
 

Original NASA ASRS Text

Title: ACR DEVIATING FOR WX PENETRATED RESTRICTED AIRSPACE.

Narrative: I WAS WORKING SECTOR 14 AT ZMP. IN THE PREVIOUS SECTOR, ACR X WDB, FROM DTW TO KJAA, HAD REQUESTED AND RECEIVED PERMISSION TO DEVIATE. THIS INFO WAS CIRCLED IN RED ON THE FLT PROGRESS STRIP TO INDICATE THAT THE INFO WAS RELAYED TO ME. I DO NOT REMEMBER BEING INFORMED OF THIS, AND THERE WAS NO EVIDENCE OF THE COORD ON THE FAC TAPES OF THE INCIDENT. ACR X'S ROUTE WAS TO TAKE IT OVER YQT. WHEN HE CHKED ON MY FREQ, HE STATED THAT HE WAS DEVIATING S AND W. HOWEVER, AN INTERPHONE CALL WAS PLACED TO MY SECTOR AT THE TIME HE CHKED IN ABOUT AN UNRELATED ACFT, AND I DIDN'T HEAR NOR ACKNOWLEDGE HIS CALL. 10 SECS LATER HE CHKED IN, 'ACR X FL310, ' WITH NO MENTION OF DEVIATION. I HANDED HIM OFF TO WINNIPEG CENTER WHEN HE WAS 15 S OF CMX AND SHIPPED HIM. APPROX 4 MINS LATER I NOTICED HIM ABOUT 10 MI FROM R4305, AND CALLED ZWG AND ADVISED HIM TO TURN THE ACFT. THERE WERE NO FGT'S WITHIN 30 MI OF ACR X. AFTER INFORMING THE SUPVR, I CALLED ZWG AND ASKED WHERE ACR X WAS GOING, AND THEY TOLD ME HE WAS DEVIATING FOR BUILD-UPS. ACR X WAS IN THE AIRSPACE FOR 10 MI, AND IT WAS NOTAMED ACTIVE FROM 000B450. ALTHOUGH THE NTAP SEEMED TO SHOW THE ACFT ON A CONSTANT HDG TOWARD THE RESTR AREA, IT LOOKED LIKE HE WAS GOING DIRECT YQT TO ME. HE WAS CLRED DIRECT YQT APPROX 80 SE OF TVC. THERE WERE AT LEAST 10 LIMITED DATA BLOCKS, AND 3 AIRSPACE DATA BLOCKS NEAR ACR X'S ROUTE FROM SAW TO YQT, PERHAPS AFFECTING MY ABILITY TO TAKE CORRECTIVE ACTION SOONER. HOWEVER,I HAD NO REASON TO BELIEVE HIS FLT PLAN WOULD COME IN CLOSE PROX TO THE RESTR AREA.

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