Narrative:

I was working final vector at phl TRACON. I had 7 airplanes on the frequency. I was working air carrier X who was told to expect a visual approach to runway 26 by the south arrival controller. At the same time I hear the supervisor yell down the room that there is ship in the channel for runway 35 in 25 mins. I then get told to get ready because there will be a lot of runway 26 arrs coming to you. Now this is where the confusion begins. I turn to the south arrival controller and asked him why aren't this regional jets and dash 8 taking runway 35 to meter all the inbound traffic. His response was; there is a ship in the channel. I then respond back and said; 'I heard 25 mins.' by this time it is too late to re-sequence aircraft who can take runway 35 back over from the downwind that I was working. He then proceeds in asking the supervisor what is going on; 'is there a ship in the channel or not?' the supervisor who just took over from the mid supervisor responds by saying; '25 mins.' while I'm working final vector I start talking to air carrier X. I ask him to expect vectors across final for spacing and maintain 4000 ft. I turn him on a 240 degree heading to intercept the localizer and ask him to report the airport in sight. By this point I'm expecting to get all the inbound traffic who could take runway 35 who will now go to runway 26 since 20 mins have gone by. Air carrier X calls and asks; 'can I get lower?' by this point I was confused because I had thought I had cleared him for the visual approach. By the time I realized what had happened; air carrier X had a conflict alert with air carrier Y who was at 4000 ft on the right downwind for runway 35.

Related reports:

Google
 

Original NASA ASRS Text

Title: PHL TRACON CTLR EXPERIENCED LOSS OF SEPARATION INCIDENT AT 4000 FT DURING VECTORS FOR VISUAL APCHS WHEN DISTR BY SHIP CHANNEL MOVEMENTS.

Narrative: I WAS WORKING FINAL VECTOR AT PHL TRACON. I HAD 7 AIRPLANES ON THE FREQ. I WAS WORKING ACR X WHO WAS TOLD TO EXPECT A VISUAL APCH TO RWY 26 BY THE S ARR CTLR. AT THE SAME TIME I HEAR THE SUPVR YELL DOWN THE ROOM THAT THERE IS SHIP IN THE CHANNEL FOR RWY 35 IN 25 MINS. I THEN GET TOLD TO GET READY BECAUSE THERE WILL BE A LOT OF RWY 26 ARRS COMING TO YOU. NOW THIS IS WHERE THE CONFUSION BEGINS. I TURN TO THE S ARR CTLR AND ASKED HIM WHY AREN'T THIS REGIONAL JETS AND DASH 8 TAKING RWY 35 TO METER ALL THE INBOUND TFC. HIS RESPONSE WAS; THERE IS A SHIP IN THE CHANNEL. I THEN RESPOND BACK AND SAID; 'I HEARD 25 MINS.' BY THIS TIME IT IS TOO LATE TO RE-SEQUENCE ACFT WHO CAN TAKE RWY 35 BACK OVER FROM THE DOWNWIND THAT I WAS WORKING. HE THEN PROCEEDS IN ASKING THE SUPVR WHAT IS GOING ON; 'IS THERE A SHIP IN THE CHANNEL OR NOT?' THE SUPVR WHO JUST TOOK OVER FROM THE MID SUPVR RESPONDS BY SAYING; '25 MINS.' WHILE I'M WORKING FINAL VECTOR I START TALKING TO ACR X. I ASK HIM TO EXPECT VECTORS ACROSS FINAL FOR SPACING AND MAINTAIN 4000 FT. I TURN HIM ON A 240 DEG HDG TO INTERCEPT THE LOC AND ASK HIM TO RPT THE ARPT IN SIGHT. BY THIS POINT I'M EXPECTING TO GET ALL THE INBOUND TFC WHO COULD TAKE RWY 35 WHO WILL NOW GO TO RWY 26 SINCE 20 MINS HAVE GONE BY. ACR X CALLS AND ASKS; 'CAN I GET LOWER?' BY THIS POINT I WAS CONFUSED BECAUSE I HAD THOUGHT I HAD CLRED HIM FOR THE VISUAL APCH. BY THE TIME I REALIZED WHAT HAD HAPPENED; ACR X HAD A CONFLICT ALERT WITH ACR Y WHO WAS AT 4000 FT ON THE R DOWNWIND FOR RWY 35.

Data retrieved from NASA's ASRS site as of January 2009 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.