PHL CTLR EXPRESSED CONCERN REGARDING THE ARPT'S FAILURE TO COMPLY WITH NOTIFICATION PROCS DURING SHIP MOVEMENTS CAUSING A GAR.

Date: 2006-10 · Aircraft: EMB ERJ 170/175 ER/LR · Phase: approach

Anomalies: deviation-discrepancy-procedural-published-material-policy

Synopsis

PHL CTLR EXPRESSED CONCERN REGARDING THE ARPT'S FAILURE TO COMPLY WITH NOTIFICATION PROCS DURING SHIP MOVEMENTS CAUSING A GAR.

Narrative

THE TALL SHIP PROC HERE AT PHL CONTINUES TO NOT BE FOLLOWED. THE PROC TO DEAL WITH TALL SHIP TFC XING THE ARR PATH FOR RWY 35 ARRS IS AS FOLLOWS: THE CITY OF PHILADELPHIA IS SUPPOSED TO CALL AND ADVISE WHEN THERE WILL BE A SHIP IN THE CHANNEL; AND A TIME WHEN TO SUSPEND RWY 25 ARRS. AFTER THE SHIP PASSES THE ARR PATH; THE CITY OF PHILADELPHIA SHALL CALL THE ATCT TO ADVISE THAT THE SHIP IS CLR AND ARRS MAY RESUME. BECAUSE THE CITY OF PHILADELPHIA IS NOT FOLLOWING THE PROC; WE DEAL WITH CALLS OF 'THE SHIP IS HERE NOW; SEND THAT ACFT AROUND.' AS HAPPENED IN THIS INSTANCE WITH ACFT X; SENT AROUND SHORT FINAL BECAUSE OF THE FAILURE OF THIS PROC. THIS HAPPENS ALMOST ON A DAILY BASIS. IT ALSO RESULTS IN THE APCH CTL SCRAMBLING ON SHORT NOTICE TO VECTOR ACFT OFF OF VECTORS FOR RWY 35 AND RE-VECTOR FOR ANOTHER RWY. THIS CONTINUES TO BE AN UNSAFE CONDITION HERE AT PHILADELPHIA. FOR A RWY THAT WE LAND ON OVER 90% OF OUR OP; IT IS NOT ACCEPTABLE THAT THIS PROC IS NOT FOLLOWED. RWY 35 SHOULD NOT BE USED AS AN ARR RWY UNTIL A PROC IS DEVELOPED AND ADHERED TO THAT REMOVES THIS UNSAFE CONDITION.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.