Phl controller described event when adjacent ARTCC host computers were assigning same code resulting...

Attributes
ACN	741684
Time
Date	200706
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : phl.tracon
State Reference	PA
Altitude	msl single value : 11000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : phl.tracon
Operator	general aviation : corporate
Make Model Name	King Air C90 E90
Flight Phase	cruise : level
Person 1
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Experience	controller limited radar : 19 controller radar : 16
ASRS Report	741684
Events
Anomaly	other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : anomaly accepted
Supplementary
Problem Areas	FAA
Primary Problem	FAA

Narrative:

Working very busy departure/overflt sector. Aircraft X appears on my scope northwest of phl descending out of 11000 ft on my tag. This was the call sign of a departure off of one of my satellite airports. I had not released this aircraft for departure and the aircraft was not on my frequency. It took me a min to figure out the problem; distracting me from my actual traffic. We have been having an ongoing problem with traffic from ZDC which are over-flying our airspace being on the same beacon code as traffic in the ZNY computer (usually either a phl arrival; not yet tagged on our scope; or a departure not yet tagged; as in this case). We ended up with 'false' tags moving through our airspace sometimes causing confusion. We then have to suspend these tags; or our own aircraft will not be able to tag on these already 'used' beacon codes. This is a real distraction to the operation; especially when you are busy. I'm not a computer guy but there has to be a way for the ZNY and ZDC computers to talk to each other and ensure that they are not trying to use the same beacon codes in the same area at the same time.

Original NASA ASRS Text

Title: PHL CTLR DESCRIBED EVENT WHEN ADJACENT ARTCC HOST COMPUTERS WERE ASSIGNING SAME CODE RESULTING IN FALSE TARGET INFO ON PHL DISPLAY.

Narrative: WORKING VERY BUSY DEP/OVERFLT SECTOR. ACFT X APPEARS ON MY SCOPE NW OF PHL DSNDING OUT OF 11000 FT ON MY TAG. THIS WAS THE CALL SIGN OF A DEP OFF OF ONE OF MY SATELLITE ARPTS. I HAD NOT RELEASED THIS ACFT FOR DEP AND THE ACFT WAS NOT ON MY FREQ. IT TOOK ME A MIN TO FIGURE OUT THE PROB; DISTRACTING ME FROM MY ACTUAL TFC. WE HAVE BEEN HAVING AN ONGOING PROB WITH TFC FROM ZDC WHICH ARE OVER-FLYING OUR AIRSPACE BEING ON THE SAME BEACON CODE AS TFC IN THE ZNY COMPUTER (USUALLY EITHER A PHL ARR; NOT YET TAGGED ON OUR SCOPE; OR A DEP NOT YET TAGGED; AS IN THIS CASE). WE ENDED UP WITH 'FALSE' TAGS MOVING THROUGH OUR AIRSPACE SOMETIMES CAUSING CONFUSION. WE THEN HAVE TO SUSPEND THESE TAGS; OR OUR OWN ACFT WILL NOT BE ABLE TO TAG ON THESE ALREADY 'USED' BEACON CODES. THIS IS A REAL DISTR TO THE OP; ESPECIALLY WHEN YOU ARE BUSY. I'M NOT A COMPUTER GUY BUT THERE HAS TO BE A WAY FOR THE ZNY AND ZDC COMPUTERS TO TALK TO EACH OTHER AND ENSURE THAT THEY ARE NOT TRYING TO USE THE SAME BEACON CODES IN THE SAME AREA AT THE SAME TIME.

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.

Phl controller described event when adjacent ARTCC host computers were assigning same code resulting in false target information on phl display.