Bay approach controller lost separation with traffic inbound to sjc on visual approachs.

Attributes
ACN	553010
Time
Date	200207
Day	Tue
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : sjc.airport
State Reference	CA
Altitude	msl single value : 3000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : o90.tracon
Operator	common carrier : air carrier
Make Model Name	Regional Jet CL65, Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	descent : approach
Route In Use	approach : visual approach : traffic pattern
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tracon : o90.tracon
Operator	common carrier : air carrier
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	descent : approach
Route In Use	approach : visual approach : traffic pattern
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 200 flight time total : 15300 flight time type : 1000
ASRS Report	553010
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	conflict : airborne critical non adherence : published procedure other anomaly other
Independent Detector	atc equipment : conflict alert other controllera other flight crewa other flight crewb
Resolutory Action	flight crew : took evasive action
Miss Distance	horizontal : 6000 vertical : 500
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

Narrative:

Center, heading given on arrival to sjc. Handoff to bay approach. Reported airport in sight. Received visual clearance runway 30L, speed 210 KTS. Bay called traffic on base for us to follow. Responded not in sight. Saw traffic too close on a high base. Too close. Bay called 'aircraft X turn right 20 degrees, climb immediately 4000 ft.' called 3 or 4 times. Bay had the wrong carrier in his call. We were 'aircraft Y.' we deviated to the right. Asked ATC. He stated that he was trying to call us. The rest normal. Called bay on phone line. They said it was the controller, they would correct the problem. Supplemental information from acn 552846: B737 was base to final. Carj was on final. Both visuals. I called traffic at 4 mi. Neither would call in sight. The carj only acknowledged 1 in 3 xmissions. When he finally answered, I broke him out. At this point, separation was lost.

Original NASA ASRS Text

Title: BAY APCH CTLR LOST SEPARATION WITH TFC INBOUND TO SJC ON VISUAL APCHS.

Narrative: CTR, HDG GIVEN ON ARRIVAL TO SJC. HDOF TO BAY APCH. RPTED ARPT IN SIGHT. RECEIVED VISUAL CLRNC RWY 30L, SPD 210 KTS. BAY CALLED TFC ON BASE FOR US TO FOLLOW. RESPONDED NOT IN SIGHT. SAW TFC TOO CLOSE ON A HIGH BASE. TOO CLOSE. BAY CALLED 'ACFT X TURN R 20 DEGS, CLB IMMEDIATELY 4000 FT.' CALLED 3 OR 4 TIMES. BAY HAD THE WRONG CARRIER IN HIS CALL. WE WERE 'ACFT Y.' WE DEVIATED TO THE R. ASKED ATC. HE STATED THAT HE WAS TRYING TO CALL US. THE REST NORMAL. CALLED BAY ON PHONE LINE. THEY SAID IT WAS THE CTLR, THEY WOULD CORRECT THE PROB. SUPPLEMENTAL INFO FROM ACN 552846: B737 WAS BASE TO FINAL. CARJ WAS ON FINAL. BOTH VISUALS. I CALLED TFC AT 4 MI. NEITHER WOULD CALL IN SIGHT. THE CARJ ONLY ACKNOWLEDGED 1 IN 3 XMISSIONS. WHEN HE FINALLY ANSWERED, I BROKE HIM OUT. AT THIS POINT, SEPARATION WAS LOST.

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.