PHL SOP

From New York ARTCC
Revision as of 20:07, 15 December 2023 by [email protected] (talk | contribs)
New York ARTCC
Standard Operating Procedure — Philadelphia ATCT and PHL TRACON

Rev. 19 — Revised: 2023-12-15

Area at a glance

ICAO Code Airport Name Airspace
KPHL Philadelphia Intl B
KPHL Philadelphia Intl B
Purpose
This document prescribes the procedures to be utilized for providing air traffic control services at the Philadelphia Air Traffic Control Tower (ATCT) and any of the positions within the Philadelphia TRACON and the airports it serves. The procedures described herein are supplemental to the New York ARTCC Standard Operating Procedures and FAA Order JO 7110.65.
Distribution
This order is distributed to all New York ARTCC personnel.
Procedural Deviations
Exceptional or unusual requirements may dictate procedural deviations or supplementary procedures to this order. A situation may arise that is not adequately covered herein; in such an event use good judgment to adequately resolve the problem.


Operational Positions

Position Callsign Radio Name Frequency Identifier
Clearance Delivery PHL_DEL Philadelphia Clearance Delivery 118.850 6G
Ground PHL_GND Philadelphia Ground 121.900 6C
Ground (secondary) PHL_W_GND Philadelphia Ground 121.650 6U
Tower PHL_TWR Philadelphia Tower 118.500 6A
Tower (Secondary) PHL_W_TWR Philadelphia Tower 135.100 6B
ATIS KPHL_ATIS 133.400
Position Callsign Radio Name Frequency Identifier
Clearance Delivery ILG_DEL Wilmington Clearance Delivery 119.950 6X
Ground ILG_GND Wilmington Ground 121.700 6Q
Tower ILG_TWR Wilmington Tower 126.000 6O
ATIS KILG_ATIS 123.950
Position Callsign Radio Name Frequency Identifier
Clearance Delivery PNE_DEL Northeast Philadelphia Clearance Delivery 127.250 6M
Ground PNE_GND Northeast Philadelphia Ground 121.700 6K
Tower PNE_TWR Northeast Philadelphia Tower 126.900 6I
ATIS KPNE_ATIS 121.150
Position Callsign Radio Name Frequency Identifier
Ground TTN_GND Trenton Ground 121.900 6K
Tower PNE_TWR Trenton Tower 120.700 6I
ATIS KTTN_ATIS 126.770

ATCT

Clearance Delivery

Template:Tabs

Ground

Departure Sequencing
Exit Gate Exits
North Gates MXE, STOEN, PTW, FJC, MAZIE, ARD
South Gates RUUTH, DITCH, OOD, DQO
  1. Aircraft should be sequenced to depart in the following order:
    1. By alternating gate group.
    2. If not the above, then by alternating exit.
    3. If not the above, then by aircraft type largest to smallest.
  2. Coordinate with Local Control at the beginning of a shift if departures will “monitor” or “contact.” Also ensure to coordinate how Local Control would like departure sequence forwarded.
  3. Due to the complexity of the intersection at 27L, during departure pushes it is imperative that controllers keep track of the departure sequence and which aircraft are on which taxiways. The departure sequence MUST be properly forwarded to Local Control so that there is no confusion on the sequence.
  4. Before switching departing aircraft to Local Control frequency, ensure the aircraft is aware of his or her number for takeoff. This is important for engine start and warm up times.
Prearranged coordination for runway crossing
  1. Ground Control may taxi aircraft across runway 9L, 27R or 26 without coordinating with Local Control so long as
    1. That runway is being utilized for landing only (not takeoffs).
    2. At the time the crossing clearance is issued, the traffic crossing that runway must be either holding short or in a position to cross the runway expeditiously without causing a safety risk to any arriving traffic.
    3. The crossing traffic must initiate crossing of that runway prior to any arriving traffic reaches a 2 mile final.
    4. The procedure must be completed no later than when the arriving traffic reaches a 1 mile final.
  2. Tower has the final authority to suspend or resume the prearranged coordination for runway crossing.
Obstructions to Arriving and Departing Aircraft
  1. The areas of consideration at PHL airport where a taxiing aircraft could become a potential obstacle to departing or arriving aircraft are as follows:
    1. Aircraft utilizing taxiway Yankee:
      • Could conflict with aircraft departing runway 27R (Simultaneous Approaches to Parallel Runways #2).
      • Could conflict with aircraft arriving and departing runway 9L.
      • Some simulators show hold short lines on Yankee. This ensures that when approaches to runway 9L are in use, aircraft will hold short of the approach path.
      PHRASEOLOGY
      Hold short of runway niner left approach on taxiway yankee.
    • Taxiways A, A1, A2, and A3 are limited to Airplane Design Group III (wingspan up to but not including 118 feet) aircraft and smaller (B727/MD80/B737, A319, A320).
  2. Controllers shall ensure that taxiing aircraft operating on non-intersecting runways do not become potential obstacles to arriving and departing aircraft.
Aircraft Exiting the Runway
Arriving aircraft shall be issued a turn onto one of the taxiways adjacent to the landing runway to ensure the aircraft continues its taxi away from the runway exit. Ground Control will receive the handoff after the aircraft starts taxiing away from the active runway. Whenever necessary, adjust the ground traffic flow so as to allow arrival aircraft to exit the runway unimpeded.
Simultaneous Approaches to Parallel Runways #2
During a Simultaneous Approaches to Parallel Runways #2 (SAPR2) operation, taxi aircraft to runway 27R or runway 35 at Kilo taxiway for departure. (SAPR2 is explained in the Tower section, under the Runway Selection tab).
Runways 17/35 and 8/26 Restrictions
Runway 17/35 is limited to Airplane Design Group III (wingspan up to but not including 118 feet) aircraft and smaller (B727/MD80/B737, A319, A320). Runway 8/26 is available for props only and small regional jets. Runway 8/26 departures must utilize runway 8 and arrivals must utilize runway 26.
Aircraft Movement
File:PHL-spots.png
Ramp entering and exiting spots (click to enlarge)
  1. Almost all taxi routes require a runway crossing. It is required per 7110.65 that taxiing aircraft receive and read back a hold short instruction for each runway crossing whether or not the runway is active.
    PHRASEOLOGY
    Runway 35, taxi via alpha, delta, hold short runway 26.
  1. When reaching 26:
    PHRASEOLOGY
    Cross runway 26 at delta, hold short runway 27R at delta.
  1. When reaching 27R:
    PHRASEOLOGY
    Cross runway 27R at delta, continue runway 35 via delta and sierra.
  1. It is suggested that departing aircraft exit the ramp as follows:
    1. East Flow: Spots 5, 6, 7, or 9
    2. West Flow: Spots 5, 8 , or 9
    3. NOTE: When a large departure push occurs during PHL West Ops, have aircraft taxi via Juliet to spot 2 and then exit the ramp. This procedure will allow a large amount of traffic to be sequenced via Yankee and Sierra to 27L.
  2. It is suggested that arriving aircraft enter the ramp as follows:
    1. East Flow: Spots 5, 8, or 9
    2. West Flow: Spots 5, 6, 7, or 9
  3. For PHL West Ops, arriving aircraft shall utilize taxiway Kilo as much as practical. For PHL East Ops, arriving aircraft shall utilize taxiway Juliet as much as practical.

Template:ShowHide

Template:ShowHide

Intersection Departures and Usable Runway Lengths
  1. The sequencing for intersection departures is a bit more involved as it will require Ground Control to properly push the strip to the tower controller in the correct order.
  2. For intersection departures, state the usable runway distance if that distance is not broadcast in the ATIS. Below is a list of usable runway lengths from common intersections. If the numbers are not divisible to 50, you must round them down to the nearest 50 feet before providing the information to the pilot.
    PHRASEOLOGY
    Runway two seven right at echo, taxi via left on kilo, hold short echo. Runway two seven right at echo intersection departure, seven thousand two hundred and fifty feet available
27L 27R 9L 9R 17 35 8
S2 (11,696') H (9,301') W (9,301') S12 (11,479') E2/D2 (5,410') S (5,990') A3 (4,701')
S3 (10,459') K1 (8,799') K6 (9,101') Z (9,179') E3 (4,498') 27R/9L (5,341')
S4 (9,980') D (8,051') K5 (7,700') S11 (8,300') K (4,940’)
S5 (8,300') 17/35 (7,598’) T (7,250') S10(8,061')
U (7,598') E (7,201') K4 (5,449') S9(7,778')
S6(6,269') F(6,860') N (5,200') S8(6,699')
S7(5,800') C(5,400') Y(6,476')
Y(5,324') M(5,141') S7(5,600')
S6(5,298')

Template:-

Tower

Template:Tabs

TRACON

Template:Tabs

Departure

Template:Tabs

Approach

Template:Tabs

Appendix

Ground Metering

Purpose
Ground Metering’s primary responsibility is to create a departure sequence before aircraft are taxied out for takeoff. Ground Metering sequences aircraft by alternating gate, exit, or type aircraft and then provides the active Ground controller with flight strips in that order. Philadelphia’s Ground Metering frequency is 121.9 (6C). Ground metering operation must be authorized by the TMU
Ground Metering Procedures and Phraseology
  1. Once aircraft are ready to taxi, they will call Ground Metering on the published Ground Control frequency that appears on the airport diagram (121.9).
  2. Aircraft calling Ground Metering should inform the controller of the following information; however, be aware that many pilots will call and advise “ready for taxi” and Ground Metering will have to find them on the field:
    1. Call-sign
    2. Location at the airport
    3. ATIS code
  3. The Ground Metering controller shall inform the aircraft to hold short of the main outbound taxiway and monitor the active Ground Control frequency.
    PHRASEOLOGY
    JetBlue Four Fifty-Two, Philadelphia Ground, hold short of Echo, monitor ground on one two one point six fife, wait for the controller to call you
Ground Metering VRC Procedural Settings
  1. Because the metering operations require effective use of flight strips as control elements, the flight strip bay should be used and set up as follows.
  2. Ground Control 121.65 (6D) should set the following options under Settings > General > Flight Strips:
    • Unchecked:
      • Auto-Add Arrival Strips
      • Auto-Add Departure Strips
      • Ignore Pushed Strips
    • Checked:
      • Delete Strip When Pushed Manually
  3. Ground Metering 121.9 (6C) should set the following options under Settings > General > Flight Strips:
    • Unchecked:
      • Auto-Add Arrival Strips
      • Auto-Add Departure Strips
      • Ignore Pushed Strips
    • Checked:
      • Delete Strip When Pushed Manually
  4. Both controllers will utilize the two-column flight strip bay (Settings > General > Flight Strips > Two-column Flight Strip Bay). Separators can be used for additional organization at the ATC’s discretion. Separators can be added by typing .sep NAME1|NAME2|NAME3 <Enter> (refer to VRC documentation for further details on separators).
Transfer of Control and Pushing Strips
  1. After Ground Metering 121.9 (6C) has sequenced aircraft that have called for taxi, he or she shall push the strip in the appropriate sequenced order to the active Ground controller on 121.65 (6D) and advise the pilot to monitor that frequency. Ground Control 121.65 (6D) will receive strips in the left hand column of the strip bay and then will move them to the right hand column, in the appropriate order, once taxi instructions have been given.
  2. After additional taxi instructions are not required, the active Ground controller 121.65 (6D) shall push the strip in sequenced order to Local Control and instruct the aircraft to monitor Philadelphia Tower on the appropriate frequency.

Changelog

Change Date Description
CHG1 18 Oct 2005 Initial release.
CHG2 27 Dec 2005 Added suggested vectors to final, brought frequencies up to date with POF, added "bookmarks".
CHG3 20 Oct 2006 Added departure/arrival flow diagrams and other changes.
CHG4 23 Mar 2007 New airspace, new departure/arrival flow diagrams, added video map, expanded instrument approach procedures, removed unneeded positions.
CHG5 20 Jul 2007 Updated flow diagrams touch-up and typo fixes.
CHG6 31 Jul 2008 Updated to PHL8, touched up flow diagrams, position ID fix/changes for TRACON.
CHG7 14 Mar 2014 MAJOR REVISION. Total SOP overhaul with many procedural changes. Updated to Wiki format.
CHG8 25 May 2014 Update the pattern work table. Clarified the assignment of departure frequencies with both ND and SD are online.
CHG9 04 Sep 2014 Distances of parallel runways were added.
CHG10 02 Nov 2014 Airspace delegation chart was updated. A new video map was added showing the STARs that transition through/above PHL airspace. New procedure regarding prearranged coordinated for runway crossing was added in Ground section. Stylistic changes.
CHG11 04 May 2015 East and West Tower positions were explained. Precoordinated runway crossing was expanded to include runway 26 as well.
CHG12 16 Jan 2016 Departure headings for 17/35 were amended. Wake turbulence separation recategorization.
CHG13 26 Jan 2019 Runway Distances for 27L/9R were Amended.
CHG14 21 Jul 2019 Amended the IFR departure headings. Fixed some broken links.
CHG15 22 May 2020 Amended the IFR Squawk Code Range.
CHG16 20 June 2020 Removed PNE as a valid exit (VOR decommissioned). Updated "Common Amendments" section.
CHG17 10 Mar 2021 Minor phraseology. Updated positions. Added colloquialisms. Clarified LAHSO/LUAW. Updated "Common Amendments" section.
CHG18 09 Jun 2021 Minor formatting changes.
CHG19 19 Mar 2023 Updated VFR procedures.
CHG20 27 Apr 2023 NEC ACR changes to Common Amendments
Retrieved from "https://wiki-dev.nyartcc.org/index.php?title=PHL_SOP&oldid=85"