| Position | Callsign | Combined at | Voice Channel |
|---|---|---|---|
| ZNY STMC | NY_TM_CTR | Primary | ZNY_TU |
| ZNY Enroute Coordinator | NY_EC_CTR | NY_TM_CTR (STMC) | ZNY_EC |
| ZNY Arrival Coordinator | NY_AC_CTR | NY_EC_CTR | ZNY_AC (ZNY_A1 when ABE_DEL is active) |
| ZNY Departure Coordinator | NY_DC_CTR | NY_EC_CTR | ZNY_DC (ZNY_D1 when UNV_TWR is active) |
| ZNY Weather Coordinator | NY_WX_CTR | NY_TM_CTR (STMC) | ZNY_WX |
| ZNY Military/Security Coordinator | NY_MS_CTR | NY_TM_CTR (STMC) | ZNY_MS |
| ZNY Departure Director | NY_DD_CTR | NY_DC_CTR | ZNY_DD (ZNY_DR when UNV_GND is active) |
| ZNY Departure Complex (57) | NY_57_CTR | Primary PIT > NY_DC_CTR | ZNY_57 |
| ZNY Departure Complex (59) | NY_59_CTR | Position 57 | ZNY_59 |
| ZNY Departure Complex (60) | NY_60_CTR | Secondary PIT > Position 57 | ZNY_60 |
| ZNY Departure Complex (62) | NY_62_CTR | Position 60 | ZNY_62 |
| ZNY Departure Complex (64) | NY_64_CTR | Position 57 | ZNY_64 |
Rev. 6 — Revised: 2024-11-18
Area at a glance
- Purpose
This order prescribes the procedures to be utilized by personnel providing traffic flow management services at ZNY and N90.
- Distribution
This order is distributed to all ZNY and vATCSCC personnel.
- Cancellation
ZNY Order 7210.23C, Traffic Flow Management Standard Operating Procedures, dated October 26, 2017, and all unincorporated changes to it are canceled.
- Procedureal 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.
Operations
This document describes how traffic management can be implemented for ZNY when sufficient staffing exists to support TMU functions. This document includes highly detailed information as to who is responsible for what, how TMIs are implemented, and how ZNY is able to manage traffic management constraints. It does not serve as operational documentation, but instead gives insight into the numerous things TMU personnel should be aware of when running ZNY operations from a traffic management perspective.
Operational Positions
| Position | Callsign | Combined at | Voice Channel |
|---|---|---|---|
| N90 STMC | NY_TMU_APP | NY_TMU_CTR | ZNY_N9 |
| N90 Arrival Coordinator | NY_ARR_APP | NY_TMU_APP | ZNY_NA |
| N90 Depature Coordinator | NY_TMU_DEP | NY_TMU_APP | ZNY_ND |
| N90 NAS Coordinator | NY_NAS_APP | NY_TMU_APP | ZNY_NN |
| N90 TBFM Coordinator | NY_TBM_APP | NY_ARR_APP | ZNY_TB |
| Position | Callsign | Line Name | IA Code [Type] |
|---|---|---|---|
| LaGuardia Coordinator | LGA_COR | L-T-COR | 122 [OVR] |
| LaGuardia Flight Data | LGA_FD | L-T-F/D | 123 [SHOUT] |
| LaGuardia Sequencer | LGA_SEQ | L-TSEQ | 128 [SHOUT] |
| LaGuardia Tower Supervisor | LGA_TS | L-T-T/S | 129 [SHOUT] |
| Westchester Coordinator | HPN_COR | H-T-F/D | 140 [SHOUT] |
| Westchester Flight Data | HPN_FD | H-T-F/D | 141 [SHOUT] |
| DXR/POU Line | DXR-684 | 684 [SHOUT] | |
| Kennedy Tower Supervisor | JFK-TS | C-CRT | 220 [OVR] |
| Kennedy Coordinator | JFK-COR | J-T-COR | 213 [OVR] |
| Kennedy Tower Supervisor Primary | JFK-TS | C-CRT | 220 [OVR] |
| Kennedy Flight Data | JFK-FD | J-T-F/D | 223 [SHOUT] |
| Kennedy Tower Supervisor Secondary | JFK-T2 | J-T-TS | 223 [SHOUT] |
| Farmingdale Shout Line | FRG-235 | 235 [SHOUT] | |
| Islip Coordinator | ISP-COR | I-T-COR | 879 [SHOUT] |
| Islip Flight Data | ISP-FD | I-T-F/D | 877 [SHOUT] |
| Islip Tower Supervisor | ISP-TS | LIT-T/S | 878 [SHOUT] |
| Suffolk Shout Line | FOK-860 | 860 [SHOUT] | |
| BDR/DXR/HVN/OXC/B-FSS Shout Line | BDR-766 | 766 [SHOUT] | |
| BDR/HVN/OXC Tower Common Line | HVN-821 | 821 [SHOUT] | |
| East Hampton Shout Line | 378 | 378 [SHOUT] | |
| Newark Coordinator Primary | EWR_COR | E-T-COR | 424 [SHOUT] |
| Newark Coordinator Secondary | EWR_CO2 | E-T-CO2 | 423 [SHOUT] |
| Newark Flight Data | EWR_FD | E-T-FD | 425 [SHOUT] |
| Newark Tower Supervisor Primary | EWR_TS | E-T-T/S | 427 [SHOUT] |
| Newark Tower Supervisor Secondary | EWR_T2 | E-T-TS2 | 427 [SHOUT] |
| Teterboro Local/Coordinator | TEB_COR | TEB-801 | 801 [SHOUT] |
| Teterboro Flight Data | TEB_FD | TEB-638 | 638 [SHOUT] |
| CDW/MMU Tower Common Line | CDR-048 | 048 [SHOUT] |
Organizational Responsibilities
Supervisory Traffic Management Coordinator
- Authorize and maintain daily traffic management responsibilities and all administrative duties associated with TM personnel.
- Function as Traffic Management Controller-in-Charge (TMCIC) when designated as such by the Air Traffic Manager (ATM).
- Participate in all planning telcons for the development of the Operations Plan and status of the airspace.
- Keep the Operations Manager in Charge (OMIC), Front Line Manager (FLM), or Controller-in-Charge (CIC) informed of any actions that have a significant impact on operations.
- Provide oversight and monitoring of all Traffic Management Coordinator (TMC) positions.
- Monitor and delegate participation, as necessary, all required hotlines.
- Assume the responsibilities of any traffic management positions which remain unstaffed.
Traffic Management Coordinator
- Evaluate proposed TMIs to ensure appropriateness.
- Develop, implement, monitor, and analyze facility specific TMIs.
- Periodically analyze and review TM procedures to ensure effectiveness and adherence to TMIs.
- Adjust or cancel TMIs promptly when no longer needed.
TMS
Enroute- Under general supervision of the STMC:
- Perform pre-duty familiarization to acquire an acceptable level of situational awareness and to establish an idea of potential constraints on the system.
- Advise all necessary areas of pertinent operational information.
- Coordinate all vATCSCC Playbook, SWAP, advisory, and Ad Hoc reroutes and if necessary, forward them to the Departure Director.
- Manage flows of traffic that traverse the facility.
- Monitor and mitigate sector capacity.
- Monitor the Diversion Recovery Tool (DRT) when necessary.
- Provide enroute spacing for departing aircraft into overhead flow.
- Ensure TMIs are operating effectively or coordinate TMI issues with relevant controllers and the STMC.
- Log all TMU actions in NTML.
Arrival - This specialist manages arrival flows into the New York Metro Airports (JFK, LGA, EWR), PHL, and DC Metro (BWI, DCA, IAD).
- Perform pre-duty familiarization to acquire an acceptable level of situational awareness and to establish an idea of potential constraints on arrival flows.
- Analyze the arrival traffic flow, demand, capacity, runway configuration, overflow capabilities, and weather information. The specialist should notify the STMC whenever s/he believes there is potential for arrival impacts.
- Implement arrival flow TMIs to reduce arrival delays on users without exceeding sector capacity.
- Advised affected operational areas of time based metering including the arrival airport and metering period.
- Monitor all appropriate traffic management tools as necessary in managing arrival flows.
- Log all TMU actions in NTML.
Departure - This specialist manages departure flows from designated ZNY airports and PHL.
- Perform pre-duty familiarization to acquire an acceptable level of situational awareness and to establish an idea of potential constraints on departure flows.
- Analyze the departure traffic flow, demand, NAVAID usability, weather conditions, airport conditions, and delays.
- Reroute traffic via alternate routes through designated sectors or centers as necessary and advise area managers (FLMs/CICs) of reroutes affecting their airspace.
- Inform the STMC of TMIs.
- Disseminate reroutes to the Departure Complex positions.
- Coordinate with towers/N90/PHL TRACONs concerning fix balancing and reroutes.
- Ensure throughput – balance arrivals and departures.
- Initiate departure restrictions to manage sector volume and forward this information with the Enroute Coordinator.
- Assist the Departure Complex with vATCSCC reroutes and Severe Weather Avoidance Plan (SWAP) implementation.
- Monitor and ensure compliance with all TMIs, especially reroutes.
- Log all TMU actions in NTML.
Military/Security - This specialist manages all military, special operations, and security initiatives in ZNY, ZWY, and other facilities.
- Coordinate all Special Use Airspace.
- Update the SUA Status Page.
- Control sensitive and classified information.
- Responsible for Mission Support.
New York Center operates up to five (5) manual departure positions in a centralized Departure Complex (also known as The Pit). The Complex is overseen by the Departure Director (DD [TMC]) and issues clearances for traffic departing all New York and Philadelphia metro airports. Due to the proximity of high density airports and the commonality of route fixes, the centralization of the Complex provides the Departure Director with advance warning of route or fix saturation. Judicious and timely reroutes are employed to mitigate or avoid bottlenecks, eliminating or reducing departure delays. During periods of high airspace complexity or severe airspace constraint, the Complex is invaluable in rerouting aircraft.
- Sector 57 issues amended routings to Philadelphia (PHL), McGuire (WRI), and satellites.
- When directed, issue alternate route clearances for aircraft departing PHL/WRI and satellites.
- Monitor all systems for routing errors and proactively issue correct route clearances.
NOTE: This is the primary Departure Complex position.
- Sector 59 issues amended routings to Kennedy (JFK), Islip (ISP), and satellites.
- When directed, issue alternate route clearances for aircraft departing JFK/ISP and satellites.
- N90 will accept ISP and ISP Satellite departures via the following routes, in addition to those routes depicted in the ZNY/N90 LOA:
- GREKI, BDR, MERIT
- BEADS, SARDI
- All other routes must be pre-coordinated with and approved by the N90 STMC, N90 Operations Manager, or his/her representative.
- Monitor all systems for routing errors and proactively issue correct route clearances.
Notes
- SIDs that are VECTOR or PILOT NAV require users file from the airport direct to the first fix, for all departure fixes.
- This position combines at position 57.
- OXC Waterbury-Oxford Procedures
- Amend routings in accordance with ZNY Preferred Routes -- i.e., if a proposed flight plan requires a reroute over a North gate fix, amend the route accordingly. After this, your responsibility is complete.
- It is the tower's responsibility to amend the flight plan and ensure the correct routing to the pilot.
- Sector 60 issues amended routings to Newark (EWR), Teterboro (TEB), and satellites.
- When directed, issue alternate route clearances for aircraft departing EWR/TEB.
- Monitor all systems for routing errors and proactively issue correct route clearances.
Notes
- SIDs that are VECTOR or PILOT NAV require users file from the airport direct to the first fix, for all departure fixes.
- This is a second normal position during the day (the other being position 57) but combines at position 57 at night.
- Sector 62 issues amended routings to LaGuardia (LGA) and Westchester (HPN).
- When directed, issue alternate route clearances for aircraft departing LGA/HPN.
- Monitor all systems for routing errors and proactively issue correct route clearances.
Notes
- SIDs that are VECTOR or PILOT NAV require users file from the airport direct to the first fix, for all departure fixes.
- This position combines at position 60 during the day and position 57 at night.
- Sector 64 issues amended routings to Teterboro (TEB), Westchester (HPN), and Newark (EWR) satellites.
- When directed, issue alternate route clearances for aircraft departing satellites.
- Monitor all systems for routing errors and proactively issue correct route clearances.
Notes
- SIDs that are VECTOR or PILOT NAV require users file from the airport direct to the first fix, for all departure fixes.
- This position combines at position 57.
