SEPARATION WAS LOST BTWN A MIL C9 AND A DC10 WHILE OPPOSITE DIRECTION AT FL330; AND ON AN AIRWAY N OF UNZ; GU. THE DC10 FLC RESPONDED TO A TCASII RA AS A RESULT OF THE CLOSE PROX TO THE C9. FL370 (FOR THE DC10) HAD BEEN COORDINATED WITH TOKYO CTR; BUT WAS MISTAKENLY CALLED TO PGUA AT FL330; BY ZOA. THE PGUA CTLR TERMINATED RADAR WITH THE DC10 AND DIDN'T NOTICE THE CONFLICT PARTLY BECAUSE THE STRIP ON THE C9 WAS NOT IN THE BAY DURING A HVY WORKLOAD PERIOD.
Synopsis
SEPARATION WAS LOST BTWN A MIL C9 AND A DC10 WHILE OPPOSITE DIRECTION AT FL330; AND ON AN AIRWAY N OF UNZ; GU. THE DC10 FLC RESPONDED TO A TCASII RA AS A RESULT OF THE CLOSE PROX TO THE C9. FL370 (FOR THE DC10) HAD BEEN COORDINATED WITH TOKYO CTR; BUT WAS MISTAKENLY CALLED TO PGUA AT FL330; BY ZOA. THE PGUA CTLR TERMINATED RADAR WITH THE DC10 AND DIDN'T NOTICE THE CONFLICT PARTLY BECAUSE THE STRIP ON THE C9 WAS NOT IN THE BAY DURING A HVY WORKLOAD PERIOD.
Narrative
A MIL C9 AT FL330 WAS SBOUND AT OWLSS; TIME XA51Z. AN ACR ACFT WAS NBOUND AT OWLSS; XA52Z; AT FL330 -- WRONG ALT FOR DIRECTION. GUAM CTR HAD BEEN GIVEN A XFER ON THE C9 AT OWLSS (THE XFER WAS MADE AT APPROX XA20Z). GUAM CTR CALLED AT APPROX XA30 WITH A XFER NBOUND OF THE ACR AT OWLSS; XA52Z; AT FL310; REQUESTING HIGHER UP TO FL390. GUAM WAS TOLD TO STAND BY TO SEE IF FL370 WAS AVAILABLE BECAUSE FL330 AND FL350 AND FL390 WERE ALL BLOCKED WITH TFC. COORD WAS MADE WITH TOKYO CTR FOR FL370; THE ALT WAS APPROVED. ON THE RETURN CALL TO GUAM CTR; THE CTLR AT OAKLAND MISTAKENLY STATED FL330 WAS APPROVED. CONTRIBUTING FACTORS: VERBAL COORD; ALL SEPARATION DONE ON STRIPS; LOOKING AT SEVERAL DIFFERENT ALTS WHILE MAKING VERBAL COORD. SUPPLEMENTAL INFO FROM ACN 332000: DATA PERSON REQUESTED FL370; WRONG ALT FOR DIRECTION; WITH ZOA. WHEN ZOA CALLED BACK THEY APPROVED FL330 AND ALSO XFERED ANOTHER ACFT ON SAME AIRWAY. BOTH CTLRS MISSED THE CONFLICTION DUE TO THE NUMBER OF ACFT; OUR BAY WAS FULL; AND THE SECOND ACFT'S STRIP WAS NOT PLACED IN THE ACTIVE BAY. FIRST ACFT WAS CLRED TO CLB TO FL330. I RELIEVED THE RADAR CTLR; WAS BRIEFED ON ALL TFC INCLUDING FIRST ACFT CLBING TO FL350 AS APPROVED. UPON SEEING ACFT LEVEL AT FL330 AND CHKING ACTIVE BAY FOR CONFLICTIONS OR TFC CALLS AND SEEING NONE (SECOND ACFT'S STRIP WAS STILL NOT IN ACTIVE BAY) I TERMINATED RADAR WITH HIM. WHEN THE SECOND ACFT CHKED IN AT FL330 THE STRIP WAS IN THE ACTIVE BAY. A MIN AFTER SECOND ACFT CHKED IN THE FIRST CALLED BACK AND SAID HE HAD A TCASII ALERT AND HAD TO DSND. PART OF THE PROB AROSE DUE TO THE VOLUME OF WORK THE DATA POS MUST DO WHEN BUSY. HE MISSED THE ALTS BECAUSE HE HAD XFERS TO MAKE; ACFT TO RELEASE AND ESTIMATED TIMES TO CALCULATE. ADDITIONALLY OUR BAYS ARE TOO SMALL TO HOLD ALL THE ACTIVE STRIPS DURING A RUSH NECESSITATING OUR PLACING ACTIVE STRIPS OFF TO THE SIDE WHERE THEY CAN BE FORGOTTEN. THIS PROB COULD HAVE BEEN AVOIDED IF WE HAD A COORDINATOR TO HANDLE SOME OF THE CALLS AND A PRINTER THAT PRINTS OUR STRIPS. WE HAVE TO HAND WRITE STRIPS NOW. SUPPLEMENTAL INFO FROM ACN 331158: OUR FLT WAS CRUISING AT FL330 AS ASSIGNED BY GUAM CTR. JUST PAST OWLSS WAYPOINT WE RECEIVED A TCASII RA TO 'DSND; DSND NOW.' AS THE CAPT STARTED A 2000+ FPM DSCNT; ALL 3 COCKPIT CREW MEMBERS SAW XING TFC FROM R TO L AT THE 2 O'CLOCK POS AT ABOUT 1/4 MI; FL330. LOSS OF ALT WAS BTWN 250-350 FT. THE CAPT CONTACTED THE XING TFC ON GUAM CTR FREQ AND CONFIRMED THE ACFT WAS A C9 MIL AIR EVAC FLT AT FL330 THAT DID NOT HAVE VISUAL CONTACT WITH US. THE C9 WAS INBOUND TO GUAM ON OUR TRACK.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.