Narrative:

After takeoff from runway 16L slc, turning to 280 degree heading, cleared to climb 11000 ft. On heading 280 degrees at about 6500 ft, asked by departure control if we had air carrier Y, a B727, in sight at 7000 ft. We reported that aircraft off our nose about 3-5 mi in sight, and confirmed the altitude on TCASII. We were then cleared to climb to FL230 in a right turn direct to slc VOR, and told to keep air carrier Y in sight 'maintain visual separation.' we started the turn and climb, I was heads down on the FMC when I noticed traffic on TCASII left side, less than 1 NM, descending from 11200 ft. I looked out the captain's left window and saw an air carrier Z B727 close aboard (3000 ft) on a heading of about 330 degrees. We were at closest point of approach about the time I saw him visually and our normal turn was increasing separation. I called departure and questioned them about the traffic. He said that they had no air carrier Z aircraft in the area. I described the traffic and he responded that they assumed we had that traffic in sight. Factors: ATC did direct us to maintain separation from air carrier Y. This was not the aircraft in conflict. ATC assumed we were looking at air carrier Z. Overtasked? Loss of situational awareness? Expected response from crew? This was a TCASII save. I would not have thought of looking for a belly check if I had not noticed the conflict on TCASII (we never had an RA, only traffic for 5-10 seconds). We wre close enough that leveling our wings when we saw the conflict would have caused a collision in short order. I assume air carrier Z never saw us.

Related reports:

Google
 

Original NASA ASRS Text

Title: AN ACR B737-500 FLC HAS A POTENTIAL CONFLICT WITH AN ACR B727 WHILE MAINTAINING VISUAL SEPARATION FROM YET ANOTHER ACR B727.

Narrative: AFTER TKOF FROM RWY 16L SLC, TURNING TO 280 DEG HDG, CLRED TO CLB 11000 FT. ON HDG 280 DEGS AT ABOUT 6500 FT, ASKED BY DEP CTL IF WE HAD ACR Y, A B727, IN SIGHT AT 7000 FT. WE RPTED THAT ACFT OFF OUR NOSE ABOUT 3-5 MI IN SIGHT, AND CONFIRMED THE ALT ON TCASII. WE WERE THEN CLRED TO CLB TO FL230 IN A R TURN DIRECT TO SLC VOR, AND TOLD TO KEEP ACR Y IN SIGHT 'MAINTAIN VISUAL SEPARATION.' WE STARTED THE TURN AND CLB, I WAS HEADS DOWN ON THE FMC WHEN I NOTICED TFC ON TCASII L SIDE, LESS THAN 1 NM, DSNDING FROM 11200 FT. I LOOKED OUT THE CAPT'S L WINDOW AND SAW AN ACR Z B727 CLOSE ABOARD (3000 FT) ON A HDG OF ABOUT 330 DEGS. WE WERE AT CLOSEST POINT OF APCH ABOUT THE TIME I SAW HIM VISUALLY AND OUR NORMAL TURN WAS INCREASING SEPARATION. I CALLED DEP AND QUESTIONED THEM ABOUT THE TFC. HE SAID THAT THEY HAD NO ACR Z ACFT IN THE AREA. I DESCRIBED THE TFC AND HE RESPONDED THAT THEY ASSUMED WE HAD THAT TFC IN SIGHT. FACTORS: ATC DID DIRECT US TO MAINTAIN SEPARATION FROM ACR Y. THIS WAS NOT THE ACFT IN CONFLICT. ATC ASSUMED WE WERE LOOKING AT ACR Z. OVERTASKED? LOSS OF SITUATIONAL AWARENESS? EXPECTED RESPONSE FROM CREW? THIS WAS A TCASII SAVE. I WOULD NOT HAVE THOUGHT OF LOOKING FOR A BELLY CHK IF I HAD NOT NOTICED THE CONFLICT ON TCASII (WE NEVER HAD AN RA, ONLY TFC FOR 5-10 SECONDS). WE WRE CLOSE ENOUGH THAT LEVELING OUR WINGS WHEN WE SAW THE CONFLICT WOULD HAVE CAUSED A COLLISION IN SHORT ORDER. I ASSUME ACR Z NEVER SAW US.

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.