Air carrier X had less than standard separation from air carrier Y visual approach assigned same run...

Attributes
ACN	208172
Time
Date	199204
Day	Mon
Local Time Of Day	1801 To 2400
Place
Locale Reference	atc facility : day
State Reference	OH
Altitude	msl bound lower : 2100 msl bound upper : 2300
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : day tracon : las
Operator	common carrier : air carrier
Make Model Name	Light Transport, Low Wing, 2 Turboprop Eng
Flight Phase	descent other
Route In Use	enroute : on vectors
Flight Plan	IFR
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	Light Transport, Low Wing, 2 Turboprop Eng
Flight Phase	descent other
Route In Use	enroute : on vectors
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : approach
Qualification	controller : developmental controller : radar
Experience	controller military : 3 controller radar : 1
ASRS Report	208172
Person 2
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
Events
Anomaly	conflict : airborne less severe non adherence : published procedure non adherence : required legal separation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance other
Consequence	faa : investigated
Miss Distance	horizontal : 3000 vertical : 200
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Inter Facility Coordination Failure Intra Facility Coordination Failure Operational Error

Narrative:

Vectored air carrier X (cited above) for a visual approach to runway 24L departing rosewood VORTAC on the 200 degree radial, eventually descending to 3000. ARTS had a surprise 'cold start' and I began to re-enter ARTS data. After near completion of re-entered data, air carrier X reported the field in sight and I cleared him for the visual approach to 24L. There was another surprise 'scatter' and I began to re-enter ARTS data. I was experiencing difficulties in obtaining acceptance on some entries. South called to run air carrier Y to runway 24L, which I approved. I then returned to finishing my ARTS entries. I began a briefing to another controller who was relieving me and local called to ask about what air carrier X was doing, as she had no communication with the aircraft. I made a broadcast to air carrier X with a turn and traffic call. Air carrier X reported aircraft in sight and I reclred air carrier X to runway 24R. Due to numerous ARTS failures, south could not get a tag on my aircraft and thought my aircraft was landing runway 24R. He cleared air carrier Y for visual approach to 24L.

Original NASA ASRS Text

Title: ACR X HAD LTSS FROM ACR Y VISUAL APCH ASSIGNED SAME RWY. SYS ERROR.

Narrative: VECTORED ACR X (CITED ABOVE) FOR A VISUAL APCH TO RWY 24L DEPARTING ROSEWOOD VORTAC ON THE 200 DEG RADIAL, EVENTUALLY DSNDING TO 3000. ARTS HAD A SURPRISE 'COLD START' AND I BEGAN TO RE-ENTER ARTS DATA. AFTER NEAR COMPLETION OF RE-ENTERED DATA, ACR X RPTED THE FIELD IN SIGHT AND I CLRED HIM FOR THE VISUAL APCH TO 24L. THERE WAS ANOTHER SURPRISE 'SCATTER' AND I BEGAN TO RE-ENTER ARTS DATA. I WAS EXPERIENCING DIFFICULTIES IN OBTAINING ACCEPTANCE ON SOME ENTRIES. S CALLED TO RUN ACR Y TO RWY 24L, WHICH I APPROVED. I THEN RETURNED TO FINISHING MY ARTS ENTRIES. I BEGAN A BRIEFING TO ANOTHER CTLR WHO WAS RELIEVING ME AND LCL CALLED TO ASK ABOUT WHAT ACR X WAS DOING, AS SHE HAD NO COM WITH THE ACFT. I MADE A BROADCAST TO ACR X WITH A TURN AND TFC CALL. ACR X RPTED ACFT IN SIGHT AND I RECLRED ACR X TO RWY 24R. DUE TO NUMEROUS ARTS FAILURES, S COULD NOT GET A TAG ON MY ACFT AND THOUGHT MY ACFT WAS LNDG RWY 24R. HE CLRED ACR Y FOR VISUAL APCH TO 24L.

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.

Air carrier X had less than standard separation from air carrier Y visual approach assigned same runway. System error.