Traffic Management Unit: Difference between revisions

From New York ARTCC
VisualWikitext
No edit summary
Line 407: Line 407:


</tabber>
</tabber>
=== Ground ===
; Departure Sequencing
<div style="width:40%; float:right;">
{| class="table table-sop table-sop-compact"
! class=nowrap | Exit Gate
! Exits
|-
|'''North'''
|COATE, NEION, HAAYS, GAYEL, SAX
|-
|'''East'''
|GREKI, MERIT, BAYYS, BDR
|-
|'''West'''
|NEWEL, ELIOT, ZIMMZ, PARKE, LANNA, BIGGY, SBJ
|-
|'''South'''
|WHITE, DIXIE
|}
</div>
#Aircraft should be sequenced to depart in the following order:
##By alternating gate group.
##If not the above, then by alternating exit.
##If not the above, then by aircraft type largest to smallest.
# 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.
# 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.
; Taxi Routes
#As the taxiway system is simple, there are no pre-defined routings.
#When the above is not available, hold departures on the ramp until the inbound aircraft is clear of the outbound aircraft. You may use conditional taxi instructions to accomplish this.
=== Tower ===
<tabber>
|-|Tower Procedures=
==== Tower Procedures ====
; Releases
* Releases from Philadelphia is requested per aircraft unless N90 permits blanket releases.
* In order to depart Teterboro under an IFR flight plan, TRACON must issue a release for departure. Departure restrictions such as release times and clearance void times are necessary to separate departures from other traffic in the airspace or to regulate the departure flow. Through land line communications, tower will obtain a release from TRACON for a specific flight after which tower can then issue departure instructions and takeoff clearance
; Separation
The standard departure separation technique to be used is anticipated radar separation. Only use timed separation if the pilot requests it.
; Radar
Teterboro ATCT is equipped with a Remote ARTS Color Display (RACD) and is not certified for any approach control services. By agreement with N90, this tower will not radar identify departing IFR aircraft and will instruct a departure to contact departure control once the aircraft appears to be clear of any traffic.
|-|Runway Selection=
=====Runway Selection=====
If TEB is staffed but the configuration at EWR is not known, use the following table.
{| class="table table-sop"
! width="25%" | Wind Speed (kts)
! width="25%" | Direction (°M)
! width="15%" | Depart
! width="15%" | Land
|-
|'''0-4'''
|Any
|
|If EWR is on a northeast flow then use Runway 6 otherwise use Runway 24
|-
| rowspan=4 | '''5+'''
|331-100
|1
|6
|-
|101-219
|19
|19
|-
|220-280
|24
|19
|-
|281-330
|24
|24
|}
* If Newark lands south, then TEB must be in the following configuration regardless of the winds: land runway 19, depart runway 24.
* If Newark lands north, then TEB must be in the following configuration regardless of the winds: land runway 6, depart runway 1.
* Regardless of the wind speed or direction, when the ceiling is less than 500' or the visibility is less than 1.25 SM and not landing runway 6, then you must switch to runway 6.
* This visibility is calculated using category C aircraft which have a final approach speed of between 121 and 140 knots.
|-|Departure Heading (IFR)=
{| class="table table-sop"
! Runway
! Heading
|-
| 1
| 040 then 280 at 2.3 DME
|-
| 6
| 040 then 280 at 2.3 DME
|-
| 19
| runway heading then 280 at 900'
|-
| 24
| runway heading then 280 at 1,500'
|-|Missed Approach=
<div style="float:left; width:40%; margin-left:1em;">
{| class="table table-sop table-sop-compact"
! width="20%" | Runway
! width="20%" | Heading
! width="20%" | Altitude
|-
|1
|330
|2,000’
|-
|6
|330
|2,000’
|-
|19
|290
|1,500’
|-
|24
|280
|1,500’
|-|VFR Procedures=
=====Airspace=====
* Class Delta
* Teterboro owns 2,500’ and below in the very northern section of the airspace. The tower owns 1,400’ and below in the very eastern section of the airspace west of the GW bridge. The tower owns 1,700’ and below in the rest of the airspace since the floor of the class BRAVO is 1,800’.
* All VFR aircraft must be radar identified and issued a discreet squawk code while operating within the tower's airspace.
; Departures
All departures whose destination is known to be LGA, EWR, LDJ, MMU or CDW should remain on the ground until an approval has been received from the respective Tower that they are able to accept the aircraft into their airspace.
; VFR reporting points
Pilots will often report a geographical location or checkpoint to verify and announce their location and position in relation to the field. Most VFR checkpoints are depicted on sectional aeronautical and terminal area charts.
; Teterboro (TEB) VFR Departures
* Skyline Route: APREQ (approval request) is necessary from EWR Tower for VFR departures requesting Class Bravo entry into EWR Airspace. EWR may approve the APREQ and thus CBA entry up to 1,500’.
* Exclusion Zone (SFRA): Send aircraft entering the exclusion zone direct the George Washington Bridge.
; Pattern Work
Direction of traffic patterns at Teterboro is determined based on the table, unless the pilot specifically requests something different or traffic warrants the use of right hand patterns.
<div style="float:left; width:40%; margin-left:1em;">
{| class="table table-sop table-sop-compact"
! width="20%" | Runway
! width="20%" | Direction
|-
|1
|Right
|-
|6
|Right
|-
|19
|Left
|-
|24
|Left
|}
</tabber>
== TRACON ==
TRACON services for Teterboro are provided by EWR sector of N90 TRACON.
== Appendix ==
=== Changelog ===
{| class="table table-sop table-sop-compact"
! style="white-space: nowrap;" | Change &nbsp;
! style="white-space: nowrap;" | Date Published &nbsp;
! 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
|-
| '''CHG21'''
| 27 Oct 2024
| Converted to new Wiki format
|}

Revision as of 22:58, 18 November 2024

New York ARTCC
Traffic Management Unit

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
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
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 [Show]
  • 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 [Show]
  • 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 [Show]
  • 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 [Show]
  • 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 [Show]
  • 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.

Retrieved from "https://wiki-dev.nyartcc.org/index.php?title=Traffic_Management_Unit&oldid=1631"