CPR Y LOST COM TCASII TA RA HAD LTSS WITH ACR X. EVASIVE ACTION TAKEN. PLTDEV. SYS ERROR.

Narrative

ACR X HANDED OFF TO AN INCORRECT ZFW FREQ. WE CHKED IN ON THE FREQ AND WERE UNAWARE THAT THE FREQ WAS INCORRECT. ABOUT 5 MINS LATER WE QUERIED THE CTLR ABOUT THE POSSIBILITY OF PROCEEDING DIRECT TO IRW. AFTER A MOMENT OF CONFUSION WITH BLOCKED XMISSIONS; HE CALMLY HANDED US OFF TO ANOTHER ZFW FREQ. THIS CTLR COMMANDED US TO DSND IMMEDIATELY TO FL330 AND INFORMED US OF OPPOSITE DIRECTION TFC AT 5 MI; SAME ALT; CLOSING VERY FAST. I RESPONDED IMMEDIATELY BY DSNDING RAPIDLY TO FL330. THE TFC; CPR Y; WAS SIGHTED VISUALLY AT ABOUT 4 MI AWAY. WE PASSED ABOUT 1/2 MI HORIZ AND 2000 FT VERTICALLY BELOW CPR Y. WE LATER LEARNED THAT CPR Y WAS NOT IN COM CONTACT WITH ZFW. IT WAS EQUIPPED WITH TCASII AND PERFORMED A CLB IN RESPONSE TO AN RA COMMAND. OUR MLG WAS NOT TCASII EQUIPPED. SUPPLEMENTAL INFO FROM ACN 241294: CPR Y DID NOT RECEIVE A CTR FREQ CHANGE; OUR LAST BELIEVED FREQ WAS ZKC ON 132.65. EVEN THOUGH WE HAD FLOWN OUTSIDE OF KANSAS CITY'S AIRSPACE WE DID NOT REALIZE THAT WE HAD LOST COMS WITH KANSAS CITY DUE TO THE FACT THAT WE KEPT HEARING OTHER ACFT ON THE FREQ. WE WERE APPROX 70-100 MI N OF ACT AT FL350 WHEN WE RECEIVED A TCASII TA. WE HAD THE TCASII ON THE 40 MI SCALE AND IN THE NORMAL POS WHICH COVERS 2700 FT ABOVE AND BELOW OUR ALT ON THIS SYSTEM. THERE WAS NO TARGET ON THE TCASII SCREEN UNTIL WE RECEIVED THE ADVISORY AND THE TCASII ALERTED 'TFC; 'TFC.' THE TARGET AT THIS TIME WAS ABOUT 4-6 MI AWAY (THIS IS ACCORDING TO ZFW'S RADAR TAPES WHEN WE STARTED OUR CLB). WE IMMEDIATELY SCANNED THE AREA FOR THE TFC; DID NOT SEE ANYTHING; AND THEN I WENT BACK INSIDE TO LOOK AT THE TCASII AGAIN.(AT THAT MOMENT THE THOUGHT CROSSED MY MIND THAT THIS WAS A FALSE ALERT.) WHEN I LOOKED AT THE TCASII I SAW THE TARGET TURN FROM YELLOW TO RED AND WAS ALERTED 'CLB; CLB' AND WAS PRESENTED WITH A 1500 FPM CLB RESOLUTION. I IMMEDIATELY DISCONNECTED THE AUTOPLT AND CLBED THE ACFT AT THE PRESCRIBED 1500 FPM. AT ABOUT 600 FT ABOVE OUR ALT THE TCASII ALERTED 'MONITOR VERT SPD;' AT THAT TIME I BELIEVE I STOPPED THE CLB. SHORTLY AFTER TCASII ALERTED 'CLR OF CONFLICT' AND I THEN DSNDED BACK TO OUR ASSIGNED ALT OF FL350. WE THEN TRIED TO CALL CTR TO FIND OUT ABOUT THE TFC AND REALIZED THAT WE WERE WELL OUTSIDE OF KANSAS CITY AIRSPACE; HOWEVER BEFORE WE SWITCHED FREQS WE STILL HEARD AN ACFT CHK IN WITH KANSAS CITY; WE WENT TO THE CHART AND FOUND A HIGH ALT WX FREQ CONTACTED THEM AND THEY GAVE US A FREQ FOR ZFW WHO WE THEN CONTACTED. I FEEL THAT AN INCREASED SITUATIONAL AWARENESS AS TO CTR BOUNDARIES ON OUR PART WOULD HAVE AVOIDED THIS SIT ALL TOGETHER; BECAUSE WE WOULD HAVE QUESTIONED CTR ABOUT A FREQ CHANGE FAR SOONER. I ALSO FEEL THAT BEING ABOUT 11 HRS INTO OUR DUTY DAY MIGHT HAVE PLAYED A PART IN OUR BEING LURED INTO A FALSE SENSE OF SECURITY REGARDING COMS. SUPPLEMENTAL INFO FROM ACN 241845: I WAS WORKING THE RADAR ASSOCIATE POS ON A SECTOR 100 MI OR MORE E OF THIS OCCURRENCE. MY INVOLVEMENT IS BECAUSE ACR X WAS PUT ON MY FREQ BY MISTAKE BY ZHU. THE SECTOR I WAS WORKING WAS HEARING OVERLOAD AND A RADAR HDOF CTLR WAS ADDED WITHIN 1 MIN OF WHEN I WAS ADVISED THAT ACR X WAS ERRONEOUSLY SWITCHED TO MY FREQ. I DID NOT HEAR ACR X CHK ON FREQ AND BECAME AWARE THAT HE WAS ON MY FREQ WHEN HE REQUESTED DIRECT IRW. I ADVISED MY R-SIDE TO SWITCH ACR X TO DALLAS HI; THE SECTOR IN WHICH THE ERROR OCCURRED. AT THAT TIME; NEITHER MY R-SIDE NOR I WAS AWARE THAT ACR X WAS IN POTENTIAL CONFLICTION WITH THE CPR Y. CPR Y WAS LOST ON A ZKC FREQ.