Reporter was involved in an operational error after data tag dropped from his tracked target and went into the coast tab list. Reporter takes responsibility for the error, but alleges poor secondary radar coverage exists in that area. The facility operates with an ASR-8 radar and the MVA for the area where the error occurred is 1600 ft.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	336109
Time
Date	199605
Day	Thu
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : ilm
State Reference	NC
Altitude	msl bound lower : 6000 msl bound upper : 6000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : ilm
Make Model Name	Baron 55/Cochise
Operating Under FAR Part	Part 91
Flight Phase	cruise other
Route In Use	departure other
Flight Plan	IFR
Aircraft 2
Make Model Name	Baron 55/Cochise
Operating Under FAR Part	Part 91
Flight Phase	cruise other
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
Experience	controller military : 5 controller radar : 13
ASRS Report	336109
Person 2
Function	flight crew : single pilot
Qualification	pilot : instrument pilot : private
Events
Anomaly	conflict : airborne less severe non adherence : required legal separation other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : unable
Consequence	faa : investigated
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

Narrative:

A baron departs ilm en route igx climbing to 6000 ft. Another baron is swbound on V1 level at 6000 ft and dropped his data tag due to poor secondary beacon equipment at ilm and targets merged at same altitude. We have been losing beacon targets on a regular basis at ilm for months now. It is my intention to file a ucr to get this garbage we have for equipment fixed or replaced. I realize this situation was my responsibility but our equipment problems will lead to a tragedy someday until fixed. Callback conversation with reporter revealed the following information: reporter stated that terrain is no factor for the poor secondary coverage and that their radar is an ASR-8. He states that at altitudes 8000 ft and above secondary coverage is satisfactory in the area where the operational error occurred. A ucr has been filed regarding the secondary coverage, but it's too soon for a response from facility management.

Original NASA ASRS Text

Title: RPTR WAS INVOLVED IN AN OPERROR AFTER DATA TAG DROPPED FROM HIS TRACKED TARGET AND WENT INTO THE COAST TAB LIST. RPTR TAKES RESPONSIBILITY FOR THE ERROR, BUT ALLEGES POOR SECONDARY RADAR COVERAGE EXISTS IN THAT AREA. THE FACILITY OPERATES WITH AN ASR-8 RADAR AND THE MVA FOR THE AREA WHERE THE ERROR OCCURRED IS 1600 FT.

Narrative: A BARON DEPARTS ILM ENRTE IGX CLBING TO 6000 FT. ANOTHER BARON IS SWBOUND ON V1 LEVEL AT 6000 FT AND DROPPED HIS DATA TAG DUE TO POOR SECONDARY BEACON EQUIP AT ILM AND TARGETS MERGED AT SAME ALT. WE HAVE BEEN LOSING BEACON TARGETS ON A REGULAR BASIS AT ILM FOR MONTHS NOW. IT IS MY INTENTION TO FILE A UCR TO GET THIS GARBAGE WE HAVE FOR EQUIP FIXED OR REPLACED. I REALIZE THIS SIT WAS MY RESPONSIBILITY BUT OUR EQUIP PROBS WILL LEAD TO A TRAGEDY SOMEDAY UNTIL FIXED. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATED THAT TERRAIN IS NO FACTOR FOR THE POOR SECONDARY COVERAGE AND THAT THEIR RADAR IS AN ASR-8. HE STATES THAT AT ALTS 8000 FT AND ABOVE SECONDARY COVERAGE IS SATISFACTORY IN THE AREA WHERE THE OPERROR OCCURRED. A UCR HAS BEEN FILED REGARDING THE SECONDARY COVERAGE, BUT IT'S TOO SOON FOR A RESPONSE FROM FACILITY MGMNT.

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.