ZAN CTLR EXPERIENCED OPERROR AT FL330 DURING COMBINED SECTOR OPS AND COORD WITH ADJACENT FACILITIES.

Date: 2005-08 · Aircraft: A340 · Phase: cruise

Anomalies: atc-issue-all-types|conflict-airborne-conflict

Synopsis

ZAN CTLR EXPERIENCED OPERROR AT FL330 DURING COMBINED SECTOR OPS AND COORD WITH ADJACENT FACILITIES.

Narrative

AT XA05 I RELIEVED A PRIOR SHIFT CTLR ON SECTOR 11. SECTORS 10D; 10R; 11D; AND 11A WERE COMBINED TO SECTOR 11R. TRACK J AND K (TRANSITION TRACKS FROM ZOA) WERE IN ZAN AIRSPACE. MOST WERE FLT PLANNED TO R220. SEVERAL WERE NEAR POS NATES WHEN I SIGNED ON THE SECTOR. THERE WERE SEVERAL ACFT FLT PLANNED EBOUND ON A590. ONE OF THOSE ACFT WAS EXITING A590 XING TRACK J TFC AND PROCEEDING TO EIL. DURING THE TIME THAT I WAS TAKING POS RPTS AT NATES; I GAVE C-17 AT FL330 DIRECT ROUTING FROM POKNO TO EIL. I ALSO CLBED A340 TO FL330. A340 HAD BEEN REQUESTING FL340 FOR A WHILE AND I HAD TFC AT FL340. I WAS UNABLE TO PROVIDE HIGHER ALT TO AN ACR Z ACFT OVER NATES; SO I OFFERED A RERTE. THE ACR Z ACCEPTED THE RERTE; BUT IT TOOK A FEW MINS TO ISSUE IT AND I HAD TO REPEAT IT A SECOND TIME. THEN I HAD TO PUT THE INFO IN THE MEARTS SO THAT TOKYO APCH CTL WOULD HAVE AN ACCURATE XFER. I WAS ALSO GETTING INFO FROM ZOA ABOUT AN ACFT THAT WAS DIVERTING 15 MI N OF COURSE ON A TRACK JUST S OF MY AIRSPACE. ZOA THEN CALLED BACK TO COORD THE ACFT DIVERTING 30 MI N OF COURSE. ADDITIONALLY TOKYO APCH CTL CALLED WITH XFER INFO ON 5 ACFT. DURING ALL THIS; SEVERAL ACFT WERE CALLING ON FREQ. I KNEW THAT THERE WERE MORE CTLRS COMING IN AT XA30; SO I KNEW I WOULD SOON GET A D-SIDE. AT APPROX XA23 ONE OF THE XA30 CTLRS CAME IN AND ASKED IF I WANTED A BREAK. I SAID NO; BUT THAT I NEEDED A D-SIDE. HE WENT TO GET HIS HEADSET AND SIGN IN. DURING THAT TIME; A320 RPTED A TCAS ADVISORY.

More incidents for this aircraft family →

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.