Narrative:

A PA28 was overflying corpus christi on an IFR clearance from bro to vct. He entered my airspace at approximately XA10Z and exited my airspace at approximately XA50Z. The aircraft was assigned a transponder code of xaxb. Throughout my airspace, the crp ARTS iia showed xbxb for the code. Adjacent facilities showed the proper code of xaxb. Due to the incorrect code being displayed, I had to manually track and update the data tag to prevent losing the track. In busy traffic, this could be a serious safety concern if the tag dropped off and the controller forgot about the aircraft.

Google
 

Original NASA ASRS Text

Title: APCH CTLR COMPLAINT THAT A PA28 WAS ASSIGNED A XPONDER CODE AND THAT THE ARTS II EQUIP SHOWED THE ACFT ONE NUMBER OFF ON HER RADAR, BUT ADJACENT FACILITIES SHOWED THE ACFT WAS SQUAWKING THE CORRECT CODE. CTLR SAID SHE HAD TO CONTINUE TO UPDATE THE PA28 TARGET TO TRACK IT.

Narrative: A PA28 WAS OVERFLYING CORPUS CHRISTI ON AN IFR CLRNC FROM BRO TO VCT. HE ENTERED MY AIRSPACE AT APPROX XA10Z AND EXITED MY AIRSPACE AT APPROX XA50Z. THE ACFT WAS ASSIGNED A XPONDER CODE OF XAXB. THROUGHOUT MY AIRSPACE, THE CRP ARTS IIA SHOWED XBXB FOR THE CODE. ADJACENT FACILITIES SHOWED THE PROPER CODE OF XAXB. DUE TO THE INCORRECT CODE BEING DISPLAYED, I HAD TO MANUALLY TRACK AND UPDATE THE DATA TAG TO PREVENT LOSING THE TRACK. IN BUSY TFC, THIS COULD BE A SERIOUS SAFETY CONCERN IF THE TAG DROPPED OFF AND THE CTLR FORGOT ABOUT THE ACFT.

Data retrieved from NASA's ASRS site as of July 2007 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.