Narrative:

Air carrier X was being vectored back for an approach to runway 23L at ind after a missed approach on the same runway. On our downwind and abeam the approach end of runway 23L we told approach 'runway in sight.' we were assigned heading 040 and issued traffic calls. We could see traffic but the clock given didn't correspond so we said we didn't have the traffic. Even though we had the runway in sight the approach controller made us continue on the downwind. We were issued a left turn to 360 degree. The controller continued to give traffic that he expected us to say we had. The traffic he was issuing was going to runway 23R and I was more concerned in maintaining a visual on the runway since that was the only thing I had in sight for sure. The controller issued a left turn to 250 degree. We accepted the heading expecting to be cleared for a visual as we arrived at the final approach course. No clearance was given until we were mid distance between runways 23L and 23R final. Simultaneously we (or the first officer) spotted the traffic Y slightly below our altitude approximately 500 ft toward our 12 O'clock and the controller asked if we had the runway. We started a turn away from the traffic Y at about the same time clearance for the visual was given but I'm sure normal separation was busted. We asked the controller where he saw us relative to the final. He said we were on centerline; not even close! Supplemental information from acn 201517. Air carrier X avoided traffic that was vectored to visual to 23R was forced to maintain at least 4000 ft (had to climb a few hundred to ensure separation) after being told that traffic was no factor, then cleared a visual approach for 23L.

Related reports:

Google
 

Original NASA ASRS Text

Title: ACR X MULTIPLE RWY OP PARALLEL RWYS VECTORED FOR VISUAL APCH HAD POTENTIAL NMAC WITH Y. EVASIVE ACTION TAKEN. SEE AND AVOID CONCEPT.

Narrative: ACR X WAS BEING VECTORED BACK FOR AN APCH TO RWY 23L AT IND AFTER A MISSED APCH ON THE SAME RWY. ON OUR DOWNWIND AND ABEAM THE APCH END OF RWY 23L WE TOLD APCH 'RWY IN SIGHT.' WE WERE ASSIGNED HDG 040 AND ISSUED TFC CALLS. WE COULD SEE TFC BUT THE CLOCK GIVEN DIDN'T CORRESPOND SO WE SAID WE DIDN'T HAVE THE TFC. EVEN THOUGH WE HAD THE RWY IN SIGHT THE APCH CTLR MADE US CONTINUE ON THE DOWNWIND. WE WERE ISSUED A L TURN TO 360 DEG. THE CTLR CONTINUED TO GIVE TFC THAT HE EXPECTED US TO SAY WE HAD. THE TFC HE WAS ISSUING WAS GOING TO RWY 23R AND I WAS MORE CONCERNED IN MAINTAINING A VISUAL ON THE RWY SINCE THAT WAS THE ONLY THING I HAD IN SIGHT FOR SURE. THE CTLR ISSUED A L TURN TO 250 DEG. WE ACCEPTED THE HDG EXPECTING TO BE CLRED FOR A VISUAL AS WE ARRIVED AT THE FINAL APCH COURSE. NO CLRNC WAS GIVEN UNTIL WE WERE MID DISTANCE BTWN RWYS 23L AND 23R FINAL. SIMULTANEOUSLY WE (OR THE FO) SPOTTED THE TFC Y SLIGHTLY BELOW OUR ALT APPROX 500 FT TOWARD OUR 12 O'CLOCK AND THE CTLR ASKED IF WE HAD THE RWY. WE STARTED A TURN AWAY FROM THE TFC Y AT ABOUT THE SAME TIME CLRNC FOR THE VISUAL WAS GIVEN BUT I'M SURE NORMAL SEPARATION WAS BUSTED. WE ASKED THE CTLR WHERE HE SAW US RELATIVE TO THE FINAL. HE SAID WE WERE ON CTRLINE; NOT EVEN CLOSE! SUPPLEMENTAL INFO FROM ACN 201517. ACR X AVOIDED TFC THAT WAS VECTORED TO VISUAL TO 23R WAS FORCED TO MAINTAIN AT LEAST 4000 FT (HAD TO CLB A FEW HUNDRED TO ENSURE SEPARATION) AFTER BEING TOLD THAT TFC WAS NO FACTOR, THEN CLRED A VISUAL APCH FOR 23L.

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.