Narrative:

I was working at phl ATCT. There was ship movement across the corridor of our secondary runway (runway 35). We have specific procedures that all employees must follow. Again; we were not given any notice of an impending maritime activity. When the controllers received the information; we were in the middle of an arrival session with between 15-23 aircraft off the arrival fixes inbound to phl. We had to immediately stop running arrival traffic to the secondary runway and scatter all of the traffic en route to this runway. This is an unsafe operation; disregarding the procedures and putting the controllers and flying public in harm's way. I believe that alert has already been activated on this situation; though it keeps on happening.

Related reports:

Google
 

Original NASA ASRS Text

Title: PHL TRACON CTLR DESCRIBED A COORD FAILURE; SOURCE UNKNOWN; WITH REGARD TO CHANNEL SHIP MOVEMENTS.

Narrative: I WAS WORKING AT PHL ATCT. THERE WAS SHIP MOVEMENT ACROSS THE CORRIDOR OF OUR SECONDARY RWY (RWY 35). WE HAVE SPECIFIC PROCS THAT ALL EMPLOYEES MUST FOLLOW. AGAIN; WE WERE NOT GIVEN ANY NOTICE OF AN IMPENDING MARITIME ACTIVITY. WHEN THE CTLRS RECEIVED THE INFO; WE WERE IN THE MIDDLE OF AN ARR SESSION WITH BTWN 15-23 ACFT OFF THE ARR FIXES INBOUND TO PHL. WE HAD TO IMMEDIATELY STOP RUNNING ARR TFC TO THE SECONDARY RWY AND SCATTER ALL OF THE TFC ENRTE TO THIS RWY. THIS IS AN UNSAFE OP; DISREGARDING THE PROCS AND PUTTING THE CTLRS AND FLYING PUBLIC IN HARM'S WAY. I BELIEVE THAT ALERT HAS ALREADY BEEN ACTIVATED ON THIS SITUATION; THOUGH IT KEEPS ON HAPPENING.

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.