Operational error? Near midair collision.

Attributes
ACN	288627
Time
Date	199411
Day	Tue
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : slc
State Reference	UT
Altitude	msl bound lower : 6000 msl bound upper : 8500
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : slc
Operator	common carrier : air carrier
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 121
Flight Phase	descent : approach
Route In Use	approach : visual
Flight Plan	IFR
Aircraft 2
Make Model Name	King Air C90 E90
Operating Under FAR Part	other : unknown
Flight Phase	descent : approach
Route In Use	approach : visual
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : atp pilot : commercial pilot : flight engineer
Experience	flight time last 90 days : 150 flight time total : 11000 flight time type : 6550
ASRS Report	288627
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 180 flight time total : 17000 flight time type : 11000
ASRS Report	288621
Events
Anomaly	conflict : nmac non adherence : required legal separation non adherence : published procedure other anomaly other
Independent Detector	aircraft equipment other aircraft equipment : unspecified
Resolutory Action	flight crew : took evasive action
Consequence	Other
Miss Distance	horizontal : 3000 vertical : 400
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

Narrative:

On radar vectors to runway 16 slc for a visual approach -- approach called out king air traffic on visual runway 17 crossing in front of us. We never saw aircraft or reported aircraft in sight. TCASII did pick up aircraft. Approach asked if we had runway in sight and we answered runway in sight and we were cleared for a visual for runway 16 as TCASII gave us an RA of climb 1500 FPM. TCASII showed traffic 400 ft below left wing of display aircraft. Climb to 8500 ft. Controller then asked if we could land. We were approaching end of runway at 8500 ft declined landing clearance and went around. On 2ND visual approach forgot to hand us off to tower and we had to ask to change frequencys. The controller made a comment that the traffic must have lined up on the wrong runway. The controller was extremely busy at the time of incident and also had a lifeguard flight to get into the airport. Supplemental information from acn: 288621: had center controller on jumpseat who got a great show of how it is on our side of the scope! -- Common practice to cross runway 17 traffic in front of runway 16 traffic -- understand it's because of noise policy of salt lake city -- that will not allow left traffic for runway 17! I guess a midair isn't too noisy.

Original NASA ASRS Text

Title: OPERROR? NMAC.

Narrative: ON RADAR VECTORS TO RWY 16 SLC FOR A VISUAL APCH -- APCH CALLED OUT KING AIR TFC ON VISUAL RWY 17 XING IN FRONT OF US. WE NEVER SAW ACFT OR RPTED ACFT IN SIGHT. TCASII DID PICK UP ACFT. APCH ASKED IF WE HAD RWY IN SIGHT AND WE ANSWERED RWY IN SIGHT AND WE WERE CLRED FOR A VISUAL FOR RWY 16 AS TCASII GAVE US AN RA OF CLB 1500 FPM. TCASII SHOWED TFC 400 FT BELOW L WING OF DISPLAY ACFT. CLB TO 8500 FT. CTLR THEN ASKED IF WE COULD LAND. WE WERE APCHING END OF RWY AT 8500 FT DECLINED LNDG CLRNC AND WENT AROUND. ON 2ND VISUAL APCH FORGOT TO HAND US OFF TO TWR AND WE HAD TO ASK TO CHANGE FREQS. THE CTLR MADE A COMMENT THAT THE TFC MUST HAVE LINED UP ON THE WRONG RWY. THE CTLR WAS EXTREMELY BUSY AT THE TIME OF INCIDENT AND ALSO HAD A LIFEGUARD FLT TO GET INTO THE ARPT. SUPPLEMENTAL INFO FROM ACN: 288621: HAD CTR CTLR ON JUMPSEAT WHO GOT A GREAT SHOW OF HOW IT IS ON OUR SIDE OF THE SCOPE! -- COMMON PRACTICE TO CROSS RWY 17 TFC IN FRONT OF RWY 16 TFC -- UNDERSTAND IT'S BECAUSE OF NOISE POLICY OF SALT LAKE CITY -- THAT WILL NOT ALLOW L TFC FOR RWY 17! I GUESS A MIDAIR ISN'T TOO NOISY.

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.