Narrative:

I was on a routine IFR flight plan sbound from bartlesville; ok; to victoria; tx; and was being worked by ft worth center. I was handed off to a controller whom I reported in with and he acknowledged me. He never called me after that; but I listened closely to all the routine traffic on his frequency and am pretty certain that he never handed me off to the next sector and if he did I certainly did not acknowledge and he certainly never made a second call to me. After what seemed like an unusually long time on his frequency; I noticed an aircraft crossing my path approximately 1 mi ahead so I called and asked if he saw that traffic. He did not recognize my call and said I was '100 mi past his airspace' and then gave me the correct frequency to call. I then called that controller and he said I had been listed in the system as 'NORDO' but I certainly was not! I can understand that mistakes like this can happen but this is the second time in the last six weeks that this has happened to me in almost the exact same place! An associate that has also flown that route 2 times in the last 6 months had this same event happen to him both times also. There must be some kind of glitch in fort worth center's software or procedures affecting this route of flight. There is a potential for disaster with IFR traffic that is not in contact with the correct ATC controller. This should be investigated with center personnel.

Related reports:

Google
 

Original NASA ASRS Text

Title: IFR C210 AT 8000 FT WITH ZFW DESCRIBES RECURRING ATC COM ISSUE APPROX 40 E OF DFW.

Narrative: I WAS ON A ROUTINE IFR FLT PLAN SBOUND FROM BARTLESVILLE; OK; TO VICTORIA; TX; AND WAS BEING WORKED BY FT WORTH CTR. I WAS HANDED OFF TO A CTLR WHOM I RPTED IN WITH AND HE ACKNOWLEDGED ME. HE NEVER CALLED ME AFTER THAT; BUT I LISTENED CLOSELY TO ALL THE ROUTINE TFC ON HIS FREQUENCY AND AM PRETTY CERTAIN THAT HE NEVER HANDED ME OFF TO THE NEXT SECTOR AND IF HE DID I CERTAINLY DID NOT ACKNOWLEDGE AND HE CERTAINLY NEVER MADE A SECOND CALL TO ME. AFTER WHAT SEEMED LIKE AN UNUSUALLY LONG TIME ON HIS FREQUENCY; I NOTICED AN ACFT CROSSING MY PATH APPROX 1 MI AHEAD SO I CALLED AND ASKED IF HE SAW THAT TFC. HE DID NOT RECOGNIZE MY CALL AND SAID I WAS '100 MI PAST HIS AIRSPACE' AND THEN GAVE ME THE CORRECT FREQUENCY TO CALL. I THEN CALLED THAT CTLR AND HE SAID I HAD BEEN LISTED IN THE SYSTEM AS 'NORDO' BUT I CERTAINLY WAS NOT! I CAN UNDERSTAND THAT MISTAKES LIKE THIS CAN HAPPEN BUT THIS IS THE SECOND TIME IN THE LAST SIX WEEKS THAT THIS HAS HAPPENED TO ME IN ALMOST THE EXACT SAME PLACE! AN ASSOCIATE THAT HAS ALSO FLOWN THAT RTE 2 TIMES IN THE LAST 6 MONTHS HAD THIS SAME EVENT HAPPEN TO HIM BOTH TIMES ALSO. THERE MUST BE SOME KIND OF GLITCH IN FORT WORTH CTR'S SOFTWARE OR PROCS AFFECTING THIS RTE OF FLT. THERE IS A POTENTIAL FOR DISASTER WITH IFR TFC THAT IS NOT IN CONTACT WITH THE CORRECT ATC CTLR. THIS SHOULD BE INVESTIGATED WITH CTR PERSONNEL.

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.