Narrative:

Air carrier X was a san francisco departure en route to vhhh via 56n150w 58n160w oggoe R580; level at FL320. Coordination had already been accomplished with vancouver center. Prior to the vancouver center boundary; air carrier X requested a route change; which I verbally coordinated with vancouver center. Now that verbal coordination has been accomplished I now needed to show this to OCEAN21. At this point I opened the coordination window and did not realize that anchorage center; not vancouver center was displayed in the window. I processed the coordination manually. Because of this; the OCEAN21 system did not warn the next sector that coordination needed to be accomplished with anchorage center. Therefore the aircraft went into anchorage center's airspace with no coordination. I along with many others feel that changes in the ocean 21 system need to be made to prevent this from happening again; as this is not the first occurrence of this same type of deviation. On that particular day the pacot track went in and out of vancouver center's airspace; then back to OC1's airspace. OCEAN21 automatically displays the next controlling facility in the coordination window; and since air carrier X was in and out; the next facility was anchorage center. But on most occasions this is not the case; the aircraft remain outside of oakland centers airspace and continue up to anchorage and fly along the polar routes. This is why I did not realize that the facility indicator was for anchorage and not vancouver. A simple solution to this would be for OCEAN21 to leave the facility indicator blank; so that each time the coordination window is opened the controller would have to select the facility for which coordination is to be accomplished.

Google
 

Original NASA ASRS Text

Title: ZOA CTLR EXPERIENCED OPDEV WHEN MISINTERPRETATION OF INFO AVAILABLE ON OCEAN21 EQUIP RESULTED IN UNAUTH ENTRY INTO ADJACENT CENTER'S AIRSPACE.

Narrative: ACR X WAS A SAN FRANCISCO DEPARTURE EN ROUTE TO VHHH VIA 56N150W 58N160W OGGOE R580; LEVEL AT FL320. COORDINATION HAD ALREADY BEEN ACCOMPLISHED WITH VANCOUVER CENTER. PRIOR TO THE VANCOUVER CENTER BOUNDARY; ACR X REQUESTED A ROUTE CHANGE; WHICH I VERBALLY COORDINATED WITH VANCOUVER CENTER. NOW THAT VERBAL COORDINATION HAS BEEN ACCOMPLISHED I NOW NEEDED TO SHOW THIS TO OCEAN21. AT THIS POINT I OPENED THE COORDINATION WINDOW AND DID NOT REALIZE THAT ANCHORAGE CENTER; NOT VANCOUVER CENTER WAS DISPLAYED IN THE WINDOW. I PROCESSED THE COORDINATION MANUALLY. BECAUSE OF THIS; THE OCEAN21 SYSTEM DID NOT WARN THE NEXT SECTOR THAT COORDINATION NEEDED TO BE ACCOMPLISHED WITH ANCHORAGE CENTER. THEREFORE THE ACFT WENT INTO ANCHORAGE CENTER'S AIRSPACE WITH NO COORDINATION. I ALONG WITH MANY OTHERS FEEL THAT CHANGES IN THE OCEAN 21 SYSTEM NEED TO BE MADE TO PREVENT THIS FROM HAPPENING AGAIN; AS THIS IS NOT THE FIRST OCCURRENCE OF THIS SAME TYPE OF DEVIATION. ON THAT PARTICULAR DAY THE PACOT TRACK WENT IN AND OUT OF VANCOUVER CENTER'S AIRSPACE; THEN BACK TO OC1'S AIRSPACE. OCEAN21 AUTOMATICALLY DISPLAYS THE NEXT CONTROLLING FACILITY IN THE COORDINATION WINDOW; AND SINCE ACR X WAS IN AND OUT; THE NEXT FACILITY WAS ANCHORAGE CENTER. BUT ON MOST OCCASIONS THIS IS NOT THE CASE; THE ACFT REMAIN OUTSIDE OF OAKLAND CENTERS AIRSPACE AND CONTINUE UP TO ANCHORAGE AND FLY ALONG THE POLAR ROUTES. THIS IS WHY I DID NOT REALIZE THAT THE FACILITY INDICATOR WAS FOR ANCHORAGE AND NOT VANCOUVER. A SIMPLE SOLUTION TO THIS WOULD BE FOR OCEAN21 TO LEAVE THE FACILITY INDICATOR BLANK; SO THAT EACH TIME THE COORDINATION WINDOW IS OPENED THE CONTROLLER WOULD HAVE TO SELECT THE FACILITY FOR WHICH COORDINATION IS TO BE ACCOMPLISHED.

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