[24 Jan 2020 2359-0500z] Northeast Corridor FNO

[Austin Cirulli]

Boston, New York, and Washington ARTCC's are teaming up for the annual Northeast Corridor event on January 24th. Join us from 7-12pm ET (and maybe a bit after) for a heavy rush of traffic along one of the most congested corridors in the world. We'll be fully staffing Washington National, JFK, and Boston for the evening. Come join the rush and make sure to leave enough time to visit all three airports.

1-24-2020 7-12pm ET (2359-0500z)

[Jeremy Peterson]

(Posted on the NTOS):
See the following advisories for information about routing and traffic management concerning the Northeast Corridor FNO: (Advisories 1 - 5)

[Dhruv Kalra]

(Posted on the NTOS):
See the following advisories for information about routing and traffic management concerning the Northeast Corridor FNO: (Advisories 1 - 5)

Not to cry foul, but isn’t the purpose of NTOS to be transparent about advisories rather than drive people to discord to have to actually get at the content of the message?

[Adam Kilgore]

I can't access the information.

[Colin Levy]

(Posted on the NTOS):
See the following advisories for information about routing and traffic management concerning the Northeast Corridor FNO: (Advisories 1 - 5)

Not to cry foul, but isn’t the purpose of NTOS to be transparent about advisories rather than drive people to discord to have to actually get at the content of the message?

Tend to agree there. I don't really do the whole discord thing.

If you all can make that information public, that would be awesome.

[Jeremy Peterson]

(Posted on the NTOS):
See the following advisories for information about routing and traffic management concerning the Northeast Corridor FNO: (Advisories 1 - 5)

Not to cry foul, but isn’t the purpose of NTOS to be transparent about advisories rather than drive people to discord to have to actually get at the content of the message?

There's a character limit 

[Jeremy Peterson]

Here are the routes (first in brief, then in full w/ associated restrictions):

Advisory 2:
PHL to BOS >DITCH J225 JFK MERIT< ROBUC3

Advisory 3:
BOS to DCA >SSOXS BUZRD SEY HTO J174 ZIZZI ATR LAFLN< DEALE3
JFK to DCA >RBV J230 COPES J75 MXE< CLIPR2

Advisory 4:
BWI/DCA/IAD to BOS >SWANN BROSS J42 RBV J222 JFK< ROBUC3
JFK/EWR/LGA to BOS >MERIT< ROBUC3

Code: [Select]

vATCSCC ADVZY 002 DCC 01/24/2020 ROUTE RQD
NAME: PHL_TO_BOS_MERIT
IMPACTED AREA: ZNY
REASON: VOLUME
INCLUDE TRAFFIC: PHL DEPARTURES TO BOS
VALID: ETD 242359 TO 250459
FACILITIES INCLUDED: ZBW/ZDC/ZNY
PROBABILITY OF EXTENSION: LOW
REMARKS: MAKES ROUTE REQUIRED
ASSOCIATED RESTRICTIONS: MERIT 15MIT
MODIFICATIONS:
ROUTE:

ORIG    DEST    ROUTE
----    ----    -----
PHL     BOS     >DITCH J225 JFK MERIT< ROBUC3

TMI ID: RRDCC002
242359-250459
20/01/24 01:48

Code: [Select]

vATCSCC ADVZY 003 DCC 01/24/2020 ROUTE RQD
NAME: DCA_ARRIVALS
IMPACTED AREA: ZDC
REASON: VOLUME
INCLUDE TRAFFIC: BOS/JFK DEPARTURES TO DCA
VALID: ETD 242359 TO 250459
FACILITIES INCLUDED: ZBW/ZDC/ZNY
PROBABILITY OF EXTENSION: LOW
REMARKS:
ASSOCIATED RESTRICTIONS: J174/J75 15MIT EACH
MODIFICATIONS:
ROUTE:

ORIG    DEST    ROUTE
----    ----    -----
BOS     DCA     >SSOXS BUZRD SEY HTO J174 ZIZZI ATR LAFLN< DEALE3
JFK     DCA     >RBV J230 COPES J75 MXE< CLIPR2

TMI ID: RRDCC003
242359-250459
20/01/24 01:52

Code: [Select]

vATCSCC ADVZY 004 DCC 01/24/2020 ROUTE RQD
NAME: BOS_ARRIVALS
IMPACTED AREA: ZBW
REASON: VOLUME
INCLUDE TRAFFIC: BWI/DCA/IAD/JFK/EWR/LGA DEPARTURES TO BOS
VALID: ETD 242359 TO 250459
FACILITIES INCLUDED: ZBW/ZDC/ZNY
PROBABILITY OF EXTENSION: LOW
REMARKS:
ASSOCIATED RESTRICTIONS: ZNY REQUESTS 15MIT AS ONE
MODIFICATIONS:
ROUTE:

ORIG            DEST    ROUTE
----            ----    -----
BWI DCA IAD     BOS     >SWANN BROSS J42 RBV J222 JFK< ROBUC3
JFK EWR LGA     BOS     >MERIT< ROBUC3

TMI ID: RRDCC004
242359-250459
20/01/24 01:55