Reported situation in which departures off runway 33 would not tag (automatic acquire) for 3-5 mi du...

Attributes
ACN	345788
Time
Date	199608
Day	Thu
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : bdl
State Reference	CT
Environment
Flight Conditions	VMC
Light	Daylight
Person 1
Affiliation	government : faa
Function	controller : departure
Qualification	controller : radar
Experience	controller radar : 9
ASRS Report	345788
Events
Anomaly	other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : unable
Consequence	Other
Supplementary
Air Traffic Incident	other

Narrative:

On aug/thu/96, I worked XA30 local to XH30 local at bradley approach. Consistently throughout the shift all bdl departures off runway 33 would not tag with beacon or ARTS tag for 3-5 mi. The display was primary only, causing controllers to divert extra attention to ensure flts tagged normally for traversing the coordinated climb area. This problem continues with occasional frequency.

Original NASA ASRS Text

Title: RPTED SIT IN WHICH DEPS OFF RWY 33 WOULD NOT TAG (AUTO ACQUIRE) FOR 3-5 MI DURING SHIFT.

Narrative: ON AUG/THU/96, I WORKED XA30 LCL TO XH30 LCL AT BRADLEY APCH. CONSISTENTLY THROUGHOUT THE SHIFT ALL BDL DEPS OFF RWY 33 WOULD NOT TAG WITH BEACON OR ARTS TAG FOR 3-5 MI. THE DISPLAY WAS PRIMARY ONLY, CAUSING CTLRS TO DIVERT EXTRA ATTN TO ENSURE FLTS TAGGED NORMALLY FOR TRAVERSING THE COORDINATED CLB AREA. THIS PROB CONTINUES WITH OCCASIONAL FREQUENCY.

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.

Reported situation in which departures off runway 33 would not tag (automatic acquire) for 3-5 mi during shift.