Narrative:

On oct/xa/06; during an extremely heavy arrival period with both finals to runway 27R and runway 35. The city of philadelphia advised us there was a ship movement. Under our current tall ship notice; you are not allowed to run runway 35 arrs during this period. They are required to give us a 10 min notice; which they did not. Since they failed to do this; it created an extremely dangerous and stressful situation at TRACON. All arrs to runway 35 were suspended and were required to go to runway 26 or runway 27R. This requires a lot of coordination and since the final was already full to our primary runway; excessive vectors had to be given to keep aircraft in our airspace. The procedure in place for tall ship movement is unsatisfactory and needs to be changed.

Related reports:

Google
 

Original NASA ASRS Text

Title: PHL CTLR DESCRIBED INCIDENT WHEN CITY FAILED TO PROVIDE TIMELY INFO REGARDING SHIP MOVEMENTS THAT AFFECT ACFT OPS TO RWY 35.

Narrative: ON OCT/XA/06; DURING AN EXTREMELY HVY ARR PERIOD WITH BOTH FINALS TO RWY 27R AND RWY 35. THE CITY OF PHILADELPHIA ADVISED US THERE WAS A SHIP MOVEMENT. UNDER OUR CURRENT TALL SHIP NOTICE; YOU ARE NOT ALLOWED TO RUN RWY 35 ARRS DURING THIS PERIOD. THEY ARE REQUIRED TO GIVE US A 10 MIN NOTICE; WHICH THEY DID NOT. SINCE THEY FAILED TO DO THIS; IT CREATED AN EXTREMELY DANGEROUS AND STRESSFUL SITUATION AT TRACON. ALL ARRS TO RWY 35 WERE SUSPENDED AND WERE REQUIRED TO GO TO RWY 26 OR RWY 27R. THIS REQUIRES A LOT OF COORD AND SINCE THE FINAL WAS ALREADY FULL TO OUR PRIMARY RWY; EXCESSIVE VECTORS HAD TO BE GIVEN TO KEEP ACFT IN OUR AIRSPACE. THE PROC IN PLACE FOR TALL SHIP MOVEMENT IS UNSATISFACTORY AND NEEDS TO BE CHANGED.

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.