Crp controller concerned with ARTS iie tracking problems.

Attributes
ACN	473251
Time
Date	200005
Day	Fri
Local Time Of Day	0601 To 1200
Place
Locale Reference	navaid : crp.vortac
State Reference	TX
Altitude	msl single value : 9000
Environment
Flight Conditions	Marginal
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : crp.tracon tower : sfo.tower
Operator	common carrier : air taxi
Make Model Name	Merlin IV A
Operating Under FAR Part	Part 135
Flight Phase	cruise : level
Route In Use	arrival : on vectors
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
Experience	controller non radar : 5 controller radar : 5
ASRS Report	473251
Person 2
Affiliation	company : air taxi
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	other anomaly other
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance
Consequence	faa : investigated
Supplementary
Problem Areas	ATC Facility
Primary Problem	ATC Facility
Situations
ATC Facility	computer equipment : crp.tracon other physical facility

Narrative:

Aircraft was not observed on radar 13 northwest crp VOR at 9000 ft. This is only 27.5 mi from the radar antennae. This has been happening now with almost all our aircraft for about 6-8 months, ever since we had our 'new' ARTS iie installed. This is a safety issue when we average 90 planes per hour and can't see them. Sometimes we can't see aircraft that are at flight levels 25-30 mi from our airport and we work the airspace up to 10000 ft and 40-45 mi inclusive. We also work valley approach and have been having the same problem and it had the same ARTS system installed at the same time. Callback conversation with reporter revealed the following information: reporter advised the crp TRACON is also valley TRACON, co-located, with dual radar sites -- an ASR 8 and ASR 9. The controller alleges that IFR tracked targets consistently fail to track from ZHU/crp boundary to approximately 25 mi north of crp. ZHU advised, in the reporter's situation, the SW4 was in tracked status, but the aircraft showed 'nat' status until approximately 25 mi north of the crp VORTAC. Although there is a facility automation specialist, the reporter advised that he has been unable to resolve the problem. The controller states that the tracking problem has been shown on the facility daily log for approximately 4 months.

Original NASA ASRS Text

Title: CRP CTLR CONCERNED WITH ARTS IIE TRACKING PROBS.

Narrative: ACFT WAS NOT OBSERVED ON RADAR 13 NW CRP VOR AT 9000 FT. THIS IS ONLY 27.5 MI FROM THE RADAR ANTENNAE. THIS HAS BEEN HAPPENING NOW WITH ALMOST ALL OUR ACFT FOR ABOUT 6-8 MONTHS, EVER SINCE WE HAD OUR 'NEW' ARTS IIE INSTALLED. THIS IS A SAFETY ISSUE WHEN WE AVERAGE 90 PLANES PER HOUR AND CAN'T SEE THEM. SOMETIMES WE CAN'T SEE ACFT THAT ARE AT FLT LEVELS 25-30 MI FROM OUR ARPT AND WE WORK THE AIRSPACE UP TO 10000 FT AND 40-45 MI INCLUSIVE. WE ALSO WORK VALLEY APCH AND HAVE BEEN HAVING THE SAME PROB AND IT HAD THE SAME ARTS SYS INSTALLED AT THE SAME TIME. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR ADVISED THE CRP TRACON IS ALSO VALLEY TRACON, CO-LOCATED, WITH DUAL RADAR SITES -- AN ASR 8 AND ASR 9. THE CTLR ALLEGES THAT IFR TRACKED TARGETS CONSISTENTLY FAIL TO TRACK FROM ZHU/CRP BOUNDARY TO APPROX 25 MI N OF CRP. ZHU ADVISED, IN THE RPTR'S SIT, THE SW4 WAS IN TRACKED STATUS, BUT THE ACFT SHOWED 'NAT' STATUS UNTIL APPROX 25 MI N OF THE CRP VORTAC. ALTHOUGH THERE IS A FAC AUTOMATION SPECIALIST, THE RPTR ADVISED THAT HE HAS BEEN UNABLE TO RESOLVE THE PROB. THE CTLR STATES THAT THE TRACKING PROB HAS BEEN SHOWN ON THE FAC DAILY LOG FOR APPROX 4 MONTHS.

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.