|37000 Feet||Browse and search NASA's
Aviation Safety Reporting System
|Local Time Of Day||1201 To 1800|
|Locale Reference||atc facility : phl.tracon|
|Affiliation||government : faa|
|Function||controller : approach|
controller : radar
|Qualification||controller : non radar|
controller : radar
|Experience||controller non radar : 5|
controller radar : 23
controller time certified in position1 : 17
|Anomaly||non adherence : published procedure|
|Independent Detector||other controllera|
|Resolutory Action||none taken : anomaly accepted|
|ATC Facility||procedure or policy : phl.tracon|
On nov/xa/06; I was working at phl tower assigned to the TRACON. On 2 occasions during heavy arrival sessions with approximately 20 or more aircraft off of our arrival fixes the supervisors came by and advised us of a tall ship in the channel notice of 10 mins. On both occasions this created havoc in the TRACON. According to phl ATCT N7110.52 the following procedures were not utilized. 1) the city of philadelphia aviation division did not advise phl TRACON with a 20-30 min heads up call. 2) the OM flm failed to advise the arrival sectors when or which aircraft was the last 35 arrival; via the recorded land line. 3) the OM and flm listed above failed to follow all procedures when they instructed the ood controller to keep running 35 arrs and the tower will send them around if need be. I believe this is a serious issue. Instructing a controller to issue approach clearance to a runway that is closed for arrs is a dangerous situation waiting to happen. These procedures need to be addressed and fixed. The city needs to comply with the notice. The supervisors need to comply and follow the notice and use the recorded land line so there is a record of the chain of events.
Original NASA ASRS Text
Title: PHL TRACON CTLR EXPRESSED CONCERN REGARDING MGMNT AND PORT'S FAILURE TO COMPLY WITH PROCS TO PROVIDE TIMELY NOTIFICATIONS ON SHIP ACTIVITY.
Narrative: ON NOV/XA/06; I WAS WORKING AT PHL TWR ASSIGNED TO THE TRACON. ON 2 OCCASIONS DURING HVY ARR SESSIONS WITH APPROX 20 OR MORE ACFT OFF OF OUR ARR FIXES THE SUPVRS CAME BY AND ADVISED US OF A TALL SHIP IN THE CHANNEL NOTICE OF 10 MINS. ON BOTH OCCASIONS THIS CREATED HAVOC IN THE TRACON. ACCORDING TO PHL ATCT N7110.52 THE FOLLOWING PROCS WERE NOT UTILIZED. 1) THE CITY OF PHILADELPHIA AVIATION DIVISION DID NOT ADVISE PHL TRACON WITH A 20-30 MIN HEADS UP CALL. 2) THE OM FLM FAILED TO ADVISE THE ARR SECTORS WHEN OR WHICH ACFT WAS THE LAST 35 ARR; VIA THE RECORDED LAND LINE. 3) THE OM AND FLM LISTED ABOVE FAILED TO FOLLOW ALL PROCS WHEN THEY INSTRUCTED THE OOD CTLR TO KEEP RUNNING 35 ARRS AND THE TWR WILL SEND THEM AROUND IF NEED BE. I BELIEVE THIS IS A SERIOUS ISSUE. INSTRUCTING A CTLR TO ISSUE APCH CLRNC TO A RWY THAT IS CLOSED FOR ARRS IS A DANGEROUS SITUATION WAITING TO HAPPEN. THESE PROCS NEED TO BE ADDRESSED AND FIXED. THE CITY NEEDS TO COMPLY WITH THE NOTICE. THE SUPVRS NEED TO COMPLY AND FOLLOW THE NOTICE AND USE THE RECORDED LAND LINE SO THERE IS A RECORD OF THE CHAIN OF EVENTS.
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.