Narrative:

A military airspace (red river atacc) was released FL190 through FL310. Light transport was en route from about 20 north fargo, nd, to minot, nd, at FL310. The light transport could not be moved above the airspace until he was clear 2 eastbound aircraft, a medium large transport and a widebody transport en route to and landing at minneapolis. The medium large transport and widebody transport aircraft needed to be sequenced and the sector was being worked by a trnee being monitored by a supervisor. The sector was moderately busy and the trnee was not performing very well. He needed to be talked through several situations. He (the trnee) had just turned the widebody transport to sequence him behind the medium large transport but did not give an appropriate turn and was creating a situation that needed immediate attention, while dealing with keeping the 2 jets apart, I was distraction from the light transport moving towards the red river airspace. The 2 aircraft took several xmissions and a relatively long period of time to separate and get sequenced and the light transport was allowed to enter the atacc at the top altitude. The alert controller at the next sector caught the situation and took appropriate action. There is currently a computer program that is supposed to be in the works that would have probably prevented this deviation. It will work the same as the conflict alert would only it would work between aircraft and airspace. The program to my knowledge has been put on hold for higher priority items.

Related reports:

Google
 

Original NASA ASRS Text

Title: ACFT ENTRERED MILITARY ASSIGNED AIRSPACE WITHOUT AUTH FROM CTLING AGENCY.

Narrative: A MIL AIRSPACE (RED RIVER ATACC) WAS RELEASED FL190 THROUGH FL310. LTT WAS ENRTE FROM ABOUT 20 N FARGO, ND, TO MINOT, ND, AT FL310. THE LTT COULD NOT BE MOVED ABOVE THE AIRSPACE UNTIL HE WAS CLR 2 EBND ACFT, A MLG AND A WDB ENRTE TO AND LNDG AT MINNEAPOLIS. THE MLG AND WDB ACFT NEEDED TO BE SEQUENCED AND THE SECTOR WAS BEING WORKED BY A TRNEE BEING MONITORED BY A SUPVR. THE SECTOR WAS MODERATELY BUSY AND THE TRNEE WAS NOT PERFORMING VERY WELL. HE NEEDED TO BE TALKED THROUGH SEVERAL SITUATIONS. HE (THE TRNEE) HAD JUST TURNED THE WDB TO SEQUENCE HIM BEHIND THE MLG BUT DID NOT GIVE AN APPROPRIATE TURN AND WAS CREATING A SITUATION THAT NEEDED IMMEDIATE ATTN, WHILE DEALING WITH KEEPING THE 2 JETS APART, I WAS DISTR FROM THE LTT MOVING TOWARDS THE RED RIVER AIRSPACE. THE 2 ACFT TOOK SEVERAL XMISSIONS AND A RELATIVELY LONG PERIOD OF TIME TO SEPARATE AND GET SEQUENCED AND THE LTT WAS ALLOWED TO ENTER THE ATACC AT THE TOP ALT. THE ALERT CTLR AT THE NEXT SECTOR CAUGHT THE SITUATION AND TOOK APPROPRIATE ACTION. THERE IS CURRENTLY A COMPUTER PROGRAM THAT IS SUPPOSED TO BE IN THE WORKS THAT WOULD HAVE PROBABLY PREVENTED THIS DEV. IT WILL WORK THE SAME AS THE CONFLICT ALERT WOULD ONLY IT WOULD WORK BTWN ACFT AND AIRSPACE. THE PROGRAM TO MY KNOWLEDGE HAS BEEN PUT ON HOLD FOR HIGHER PRIORITY ITEMS.

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