Narrative:

Small transport X was being vectored from the west for the ILS approach. Inbound had been passed to tower and no sequence was called for me to follow. Tower had 2 heavies in the touch-and-go pattern who were extending downwind to 32R (the ILS runway). Since tower didn't tell me to follow any aircraft, it is understood that they will follow me. As I turned the aircraft on a heading to intercept the localizer, I observed one of the heavies turning final from the east side right for him. I quickly called traffic and asked the aircraft if he was going to be in front of the heavy. The small transport X's altitude was 3100 ft and ground speed 140 KTS. Widebody transport Y's altitude was 3000 ft and ground speed 160. As I am getting a reply, the cabin attendant supervisor is calling and I told him twice to get the heavy jet out of there. He asked if I could give small transport X a 360 degree turn to follow widebody transport Y. I said no, I'm ahead of him. I observed widebody transport Y, approaching small transport X from the east and taking no action to alter course. Small transport X confirmed that and asked for a turn. I gave him a left turn to 270 degrees, since my presentation showed widebody transport Y approaching from the east. He argued with me twice. The targets merged with 100 ft apart vertical. Tower was extending traffic into my airspace and made a bad call turning widebody transport Y. They didn't keep an eye on him. Tower quickly exchanged traffic to widebody transport Y and told him to remain east of small transport X, but never made any effort to get widebody transport Y away from my traffic. Tower was training a developmental and let the situation get out of hand, and then tried to take corrective action. We have procedures in place that tower can run into approach's airspace as long as the traffic has a full data block.

Google
 

Original NASA ASRS Text

Title: SMT X HAD NMAC WITH WDB Y. SEE AND AVOID CONCEPT. EVASIVE ACTION TAKEN.

Narrative: SMT X WAS BEING VECTORED FROM THE W FOR THE ILS APCH. INBOUND HAD BEEN PASSED TO TWR AND NO SEQUENCE WAS CALLED FOR ME TO FOLLOW. TWR HAD 2 HEAVIES IN THE TOUCH-AND-GO PATTERN WHO WERE EXTENDING DOWNWIND TO 32R (THE ILS RWY). SINCE TWR DIDN'T TELL ME TO FOLLOW ANY ACFT, IT IS UNDERSTOOD THAT THEY WILL FOLLOW ME. AS I TURNED THE ACFT ON A HDG TO INTERCEPT THE LOC, I OBSERVED ONE OF THE HEAVIES TURNING FINAL FROM THE E SIDE RIGHT FOR HIM. I QUICKLY CALLED TFC AND ASKED THE ACFT IF HE WAS GOING TO BE IN FRONT OF THE HVY. THE SMT X'S ALT WAS 3100 FT AND GND SPD 140 KTS. WDB Y'S ALT WAS 3000 FT AND GND SPD 160. AS I AM GETTING A REPLY, THE CAB SUPVR IS CALLING AND I TOLD HIM TWICE TO GET THE HVY JET OUT OF THERE. HE ASKED IF I COULD GIVE SMT X A 360 DEG TURN TO FOLLOW WDB Y. I SAID NO, I'M AHEAD OF HIM. I OBSERVED WDB Y, APCHING SMT X FROM THE E AND TAKING NO ACTION TO ALTER COURSE. SMT X CONFIRMED THAT AND ASKED FOR A TURN. I GAVE HIM A L TURN TO 270 DEGS, SINCE MY PRESENTATION SHOWED WDB Y APCHING FROM THE E. HE ARGUED WITH ME TWICE. THE TARGETS MERGED WITH 100 FT APART VERT. TWR WAS EXTENDING TFC INTO MY AIRSPACE AND MADE A BAD CALL TURNING WDB Y. THEY DIDN'T KEEP AN EYE ON HIM. TWR QUICKLY EXCHANGED TFC TO WDB Y AND TOLD HIM TO REMAIN E OF SMT X, BUT NEVER MADE ANY EFFORT TO GET WDB Y AWAY FROM MY TFC. TWR WAS TRAINING A DEVELOPMENTAL AND LET THE SITUATION GET OUT OF HAND, AND THEN TRIED TO TAKE CORRECTIVE ACTION. WE HAVE PROCS IN PLACE THAT TWR CAN RUN INTO APCH'S AIRSPACE AS LONG AS THE TFC HAS A FULL DATA BLOCK.

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.