AN A300-600 CREW ON UG437 WAS ISSUED AN ALT AND HDG CHANGE CONCURRENT WITH A TCAS WARNING AFTER ENCOUNTERING OPPOSITE DIRECTION TFC WHICH WAS AT THE INCORRECT ALT FOR AIRWAY DIRECTION.

Narrative

FLT PLAN GAVE UG437(R43) AT FL330-350. GYE CLRNC GAVE FL320. REQUESTED FL350. GIVEN. WAS IN E HEMISPHERE FOR FL. JUST S OF TBG PTY ATC TOLD ME TO TURN R 10 DEGS AND DSND TO FL340 IMMEDIATELY. REASON WAS ONCOMING SBND TFC AT FL350. TCAS ACTIVATED IN TURN AND DSCNT. ASKED BY PTY WHO GAVE US FL350. TOLD GYE. PTY DID ACCEPT US AT THEIR FIR AT FL350. TURNS OUT THAT UG437 IS NOTED TO HAVE OPPOSITE FLT LEVELS WHICH WAS NOT CAUGHT BY ANY CONCERNED UNTIL POSSIBLE CONFLICT. VERY UN-STANDARD PROCS ON THIS JETWAY. FO CAUGHT THE PROB AND OBSCURE JETWAY NOTE. I UNDERSTAND THAT IT IS MY ULTIMATE RESPONSIBILITY TO CATCH ANY DIFFERENCES; BUT I RELIED ON COMPUTER FLT PLANNING. I IMMEDIATELY NOTIFIED ATC VIA ACARS. I SUGGEST THAT THIS RTE BE REMOVED FROM SYSTEM AND REPLACED WITH RTE 14. RPTED INCIDENT TO THE CHIEF PLT AND THE AC MGR. POINT IS THAT I FLEW ALL THE WAY TO PTY AIRSPACE AGAINST THE GRAIN AND NO ONE CAUGHT THE MISTAKE UNTIL CONFLICT SHOWED UP. THIS IS A POTENTIAL DANGEROUS SIT THAT NEEDS TO BE DEALT WITH ASAP. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATED THAT ALONG UG437 THE CHART SYMBOL 'E>' NEAR THE RTE NUMBER WAS THE ONLY INDICATION OF ALT/DIRECTION CONSTRAINTS. THE CREW HAD NOT SEEN THAT SYMBOL EVEN AFTER FLYING THE RTE FOR 10+ YRS. THE RPTR SUGGESTED THAT THE SYMBOLOGY BE MORE VISIBLE AND PRINTED MORE FREQUENTLY WITH TEXT OR OTHER MEANS. THE RPTR IS CONCERNED THAT SINCE HE; HIS CREW; AND THEIR DISPATCHER MISSED THE IMPLICATIONS OF THE CONSTRAINT; THAT A WORST CASE SCENARIO COULD OCCUR SINCE ATC ALSO DID NOT CATCH THE CONFLICT UNTIL VERY LATE IN THEIR APCH TO ONE ANOTHER.