Letter of Agreement
New York ARTCC (ZNY) & Boston ARTCC (ZBW)
Rev. 7 — Dec 23, 2019
This agreement prescribes transfer of control procedures, radar handoff procedures, route/altitude assignments, and delegation of airspace between New York ARTCC (ZNY) and Boston ARTCC (ZBW).
New York ARTCC (ZNY) and Boston ARTCC (ZBW) Letter of Agreement, dated Sep 12, 2017, is hereby cancelled.
The procedures contained herein must apply unless prior coordination is effected.
vZNY and any other facilities mentioned in this document are affiliated with the Virtual Air Traffic Simulation (VATSIM) network. The procedures outlined in this document are intended exclusively for use in the VATSIM flight simulation environment and must never be used for actual flight or air traffic control operations. vZNY and any other facility mentioned in this document are not affiliated with the FAA in any manner.
General Procedures
  1. ZBW/ZNY ATC must at all times:
    1. Coordinate and resolve, in a practical manner that provides the smoothest experience to the pilot, all deviations from, and situations not addressed by, this document (e.g., non-standard sectorization, holding, pilots unable to accept LOA routes, aircraft above/below LOA altitudes, etc.).
    2. Ensure that all aircraft are at a 1X simulation rate prior to initiating handoff.
    3. Unless otherwise stated in this document or coordinated via verbal or textual means, aircraft must be climbing to, descending to, or level at the correct altitude for direction of flight prior to any handoff.
    4. Ensure that aircraft on the same route segment at the same altitude (or different altitudes, but same destination airport within ZBW or ZNY) are separated by not less than 10nm (steady or increasing) or other value specified herein unless greater MIT separation is requested real-time by ZBW/ZNY.
      NOTE: Separation of less than 10nm is permitted provided the trailing aircraft is operating at a speed that will permit it to overtake the lead aircraft, and both are vertically separated.
    5. Ensure that handoff requests are made at least 10nm prior to the relevant airspace boundary unless otherwise specified in this document. Handoff requests may be initiated up to 50nm without prior coordination.
      NOTE: Transfer of radio communications can be delayed no later than the lateral boundary.
    6. Ensure that all conflicts, imminent situations, and MIT separation issues are resolved prior to handoff.
    7. Ensure that all scratchpad entries are cleared unless required to convey operational information (e.g. “M80” for assigned Mach number, “H###” for assigned heading) not coordinated by other means (e.g. private message, verbally, etc.).
    8. Ensure the datablock is formatted as follows:
      1. For aircraft climbing to an altitude lower than the flight planned altitude:
        1. If the altitude is consistent with an LOA procedure, no entry.
        2. If the altitude is non-standard or not contained within this LOA, a temporary altitude reflecting the cleared altitude.
      2. For aircraft descending to meet an issued crossing restriction, a temporary altitude with the applicable crossing altitude. Exception: ZNY controllers may use hard altitudes instead of temporary altitudes in these circumstances.
      3. For aircraft descending to an assigned altitude, no temporary altitude is used, and the filed/planned altitude is amended to the new cleared/assigned altitude.
      4. No scratchpad, except if specific control instructions that differ from LOA procedures have been issued. In these cases, the alternate instruction must be verbally or textually included as well as included in the scratchpad. Scratchpad entries may include:
        1. Indicated speed restrictions (e.g., “S210”, “S270+”); clients capable of 4-characters remove the "S" if needed (i.i., "270+")
        2. “M” for Mach speed restrictions (e.g., “M81”, “M78+”)
        3. “H” for heading assignments (e.g., “H230”)
        4. “H” and direction for deviations (e.g., “H15L” for 15 degrees left of track)
      5. Ensure the aircraft type and equipment suffix is accurately inputted.
  2. Except for aircraft originating in ZBW or ZNY, controllers must not be required to change or issue routing to aircraft as long as the routing is satisfactory to the first fix in the receiving facility’s area.
    1. For aircraft originating in the transferring facility’s area, a centralized preferred routes database is accessible through both organizations’ websites. Preferred routes as published in our unified database must be used wherever possible, with FAA/FlightAware routes used as a secondary source.
    2. Any direct clearances to points located in the receiving facility’s airspace require the transferring facility to delete the flight plan up to that point.
  3. Each facility has control for beacon code changes on traffic within 10nm of the ZBW/ZNY boundary.
  1. Traffic destined to KJFK and KJFK Satellites routed via the IGN STAR:
    1. May be given direct LOLLY without any additional coordination or flight plan amendment.
    2. Must cross LOLLY at FL200.
    3. ZNY will have control for turns up to 30° right of course and/or direct LENDY 10 nautical miles (NM) of the ZNY/ZBW High boundary.
    4. When ZNY is offline, arrivals via the IGN STAR may be handed off directly to the appropriate N90 sector without pre-coordination. All other items specified above apply.
  2. The IGN STAR is available for aircraft capable of 250+ KIAS only. Other KJFK arrivals must be issued the PWL STAR.
  3. Traffic destined to KDOV via J121 must enter ZNY airspace at or below FL220.
  4. Traffic destined KPHL North Satellites, KWRI, and KWRI Satellites routed via J121 or V139 must enter ZNY airspace at or below 16,000′.
  5. Traffic destined KACY, KACY Satellites, KPHL, and KPHL Satellites at and above FL190 must enter ZNY airspace via:
    1. DNY at FL190.
    2. J121 at FL200 (KACY, KILG and KPHL only). These aircraft may be instructed to cross 35nm NE of MANTA at FL200 or be instructed to descend so as to enter the ZNY “shelf” at FL200.
    3. KPHL arrivals may be cleared direct LVZ from DNY without prior coordination.
    4. Turboprop traffic destined KPHL routed via V268/V308/DRIFT must enter ZNY airspace at or below 16,000'.
  6. Traffic southbound on J6, J75, Q406, Q448, and Q480:
    1. Must enter ZNY airspace at or above FL240.
    2. ZNY will have control for turns up to 30° left or right of course when within 10nm of the ZNY/ZBW high boundary.
    3. ZBW may clear aircraft routed via Q406 and Q448 direct DBABE without coordination.
    4. ZBW may clear aircraft routed via Q480/J6 direct JEFFF without coordination.
    5. ZBW may clear aircraft routed via J75 direct JERSY without coordination.
    6. Traffic destined KBWI and KBWI satellites routed via J75 must enter ZNY airspace in-trail, and either below or in-trail with other traffic routed via J75.
    7. Aircraft destined KBWI/KDCA must be between FL240-FL360.
  7. Traffic destined KIAD and KIAD satellites:
    1. Routed via the HYPER STAR:
      1. Must enter ZNY via KEAVR between FL240-FL360.
      2. ZBW may clear aircraft direct KEAVR without coordination.
      3. ZNY will have control for turns up to 30° left or right of course when within 10nm of the ZNY/ZBW boundary.
    2. Non-RNAV turbojet traffic must be routed via either J49 or J59 PSB PRIVO STAR. These aircraft must enter ZNY at or below FL300.
    3. Turboprop traffic routed via HNK V576 or CFB V423 FQM must enter ZNY airspace at or below FL220.
  8. Traffic destined to KDCA routed via J174 ZIZZI and the DEALE STAR arrival will pass south of ZNY and is a direct handoff for ZDC. When ZDC is offline, DCA traffic may be routed via PATSS NELIE CMK J75 MXE CLIPR STAR and will pass through ZNY. These aircraft enter ZNY between FL240-FL360.
  9. Traffic destined KPIT and KPIT Satellites routed via HNK must cross HNK at FL280.
  10. ZBW may clear aircraft direct MANTA without coordination.
  11. ZBW must route aircraft so as to remain clear of that Special Use Airspace (SUA), shared with ZNY, designated as "hot" as determined by http://sua.faa.gov
ZBW to N90
  1. May clear SHAFF aircraft via direct SAX direct EWR to arrive at SAX between the SAX R-360 and SAX R-060 and be assigned 7,000’.
  2. Must handoff and transfer communications:
    1. At or prior to VALRE for V157 LGA arrivals.
    2. At least 5nm prior to all other arrival fixes.
  3. Must ensure JFK turbojet arrivals via CCC cross CCC (or the CCC R-170) at 12,000’ and 250 knots. May clear aircraft direct ROBER so long as arrivals arrive between CCC and the HTO R-260.
  4. Must ensure JFK arrivals unable 250 knots or greater enter N90 via a preferred route at or below 10,000’. These arrivals must be transferred from PVD TRACON to N90 Islip Area when staffed.
  5. May clear ISP arrivals via SARDI direct CCC between KOPPY and SARDI. These aircraft must cross the SARDI area at 7,000'.
  6. When HPN ILS RWY 16 is in use, ZBW may vector HPN jet arrivals to intercept the localizer or direct FARAN, when the aircraft is on or east of the localizer course.
  7. May clear LGA jet arrivals direct BASYE.
  8. Must clear EWR satellite jet arrivals to 6,000’, when other traffic at that altitude is not a factor.
  1. Traffic departing KACY, KDOV, KWRI, KPHL, and satellites of those airports routed via J55 and J121 requesting FL230 or above must be handed off to ZBW climbing to FL230.
  2. Traffic destined KALB and KSCH:
    1. Turbojets must be routed via LGA LGA055 V487 CANAN ALB and must be instructed to cross LGA at FL240. ZBW will have control for turns up to 45° of left of course at and northeast of LGA. All other traffic:
      1. Routed on or west of J190 must enter ZBW airspace at or below FL240.
      2. Routed east of J190 must be routed via RKA, HNK, and DNY, and enter ZBW airspace at or below 17,000’.
  3. Traffic at or above FL240 destined KBDR, KFRG, KHPN, KHVN, and KOXC routed via HNK or CFB must enter ZBW airspace at or below FL270, descending to FL240.
  4. Traffic destined KBAF, KBDL, KCEF, and KSWF routed via DPK must enter ZBW airspace at FL190.
  5. Traffic landing KHPN routed via the BOUNO STAR must enter ZBW airspace at 17,000’.
  6. Traffic destined to N90 satellites routed via ZBW must enter ZBW airspace as follows:
    1. KISP and satellites at or below 9,000’.
    2. Prop traffic destined KHPN routed via V139 or KPVD satellite airports at or below 11,000’.
  7. Traffic destined to KASH, KMHT, KORH, and Boston North Satellites routed via JFK DPK MAD must cross DPK at or below FL230.
    1. Where possible, traffic destined to Boston North Satellites must be routed via HFD/ORW/WIPOR and the DREEM (RNAV) or GRAYM (conventional) arrivals.
  8. Turbojet traffic destined KBOS:
    1. Must be routed via the ORW or ROBUC (RNAV) STAR.
    2. Must enter ZBW airspace between FL270 and FL240 inclusive. Altitudes inappropriate for direction of flight are approved within this block. ZBW has control for descent 5nm south of NEWES.
    3. ZNY may clear aircraft direct FEXXX intersection without coordination. This change must be reflected in the flight plan.
  9. The ORW and ROBUC procedures apply to turbojet aircraft only. Non-turbojet traffic destined KBOS and satellites must be routed via:
    1. From the N90 area: MERIT ORW WOONS STAR
    2. From all other areas: ORW WOONS STAR
  10. Traffic destined KBDL, KCEF, KBAF, and KORH must be routed via either:
    1. HNK STELA STAR and enter ZBW airspace at or below FL270.
    2. RKA STELA STAR and enter ZBW airspace at or below FL370, descending to FL330.
  11. Traffic destined KPVD routed via RBV J62 must enter ZBW airspace at or below FL270.
  12. Traffic destined KBOS entering via ACK or LFV must enter ZBW airspace pilot discretion descending FL280.
  13. ZNY may clear traffic direct HTO, ACK, PUT, or SARDI without coordination. ZNY may clear traffic at or above 13,000’ routed via CCC or ORW direct to CCC or ORW. In all cases, the routing change must be reflected in the flight plan.
  14. Traffic destined to KSYR from ZNY must be instructed to cross 35nm from SYR at 11,000’ and be handed off directly to SYR TRACON, when available. SYR TRACON or ZBW has control on contact for turns 30 degrees on either side of track.
N90 to ZBW
  1. Must ensure all departures are on course to the first fix depicted in the flight plan unless a heading is specifically coordinated verbally or via text prior to communications transfer.
  2. Must not reduce the IAS of an arrival below 250 kts until the aircraft is within 10nm of the arrival fix (i.e., CCC, VALRE, NOBBI).
  3. May vector TRESA and FILPS arrivals up to 30° south of course within 5nm of the fix.
  4. May vector JFK arrivals up to 30° left or right of course west of the CCC R-170.
  5. May vector HPN/ISP north area arrivals to the right at RICED.
  6. May vector LGA arrivals via V157 VALRE up to 45° right of course, south of VALRE.
  7. May vector LGA arrivals via NOBBI up to 45° right of course, south of NOBBI.
  8. ZBW has control for climb:
    1. BETTE/HAPIE departures cleared to 11,000’, east of V229.
    2. KFRG/KISP departures cleared to 10,000’, east of the CCC/ROBER line.
    3. KJFK GREKI and MERIT departures assigned 17,000’, east of JFK R-010.
    4. Propeller aircraft filed over GREKI, MERIT, and BAYYS assigned 16,000’ east of a CMK-DPK line.
  9. N90 must transfer communications for departures no later than 2 ½ nm prior to the ARTCC/TRACON boundary.
  10. ZBW has control for right turns on MERIT and BAYYS traffic at 13,000’ and above.
  11. N90 must transfer communications for departures no later than 2 ½ nm prior to the ARTCC/TRACON boundary.
Airspace Delegation
Airspace delegations between ZNY and ZBW will be in accordance with Attachment 1.
Attachment 1 – Airspace Delegation [show]


Attachment 2 – ZNY Sector Splits [show]
Two Center Operation (SW/NE split) Two Center Operation (E/W split)
ZNY Center Splits - Two-SW.png ZNY Center Splits - Two-E-W.png

NY_SW_CTR (South and West): Controls PHL TRACON when offline

NY_NE_CTR (North, Central, and East): Controls N90 TRACON when offline

NY_W_CTR (South, West, and North): Controls PHL TRACON when offline

NY_E_CTR (East and Central): Controls N90 TRACON when offline

Three Center Operation Four Center Operation
ZNY Center Splits - Three.png ZNY Center Splits - Four.png

NY_SW_CTR (South and West): Controls PHL TRACON when offline

NY_E_CTR (East and Central): Controls N90 TRACON when offline



NY_S_CTR: Controls PHL TRACON when offline


NY_E_CTR (Central and East): Controls N90 TRACON when offline

Attachment 3 – ZBW Sector Splits [show]
  1. General
    1. When Boston Center is combined, it will be operated as BOS_CTR on frequency 134.700.
    2. Outside of events, Boston Center splits will be coordinated with adjacent facilities through the use of the air traffic control channels. Standard sector splits are shown below.
  2. Altitudes
    1. Unless otherwise defined, high-altitude sectors cover FL240 – FL600. Low-altitude sectors cover the surface to FL239.
  3. Splits:
Two-Way (E/W) Two-Way (N/S)
ZBW Two-Way EW.png ZBW Two-Way NS.png
Three-Way Three-Way (Heavy BOS Arrivals)
ZBW Three-Way.png ZBW Three-Way BOS.png
Three-Way (Heavy JFK Arrivals) Three-Way with High Sector
ZBW Three-Way JFK.png ZBW Three-Way High.png
Three-Way with High Sector (Heavy BOS Arrivals) Three-Way with High Sector (Heavy JFK Arrivals)
ZBW Three-Way High BOS.png ZBW Three-Way High JFK.png
Four-Way Four-Way with High Sector
ZBW Four-Way.png ZBW Four-Way High.png
Attachment 4 – Transfer of Altitude/Routes
ZBW Procedures for N90 Arrivals [show]
NOTE: The “Frequency” column presents the appropriate N90 sector for handoffs. The frequencies are presented in the order of precedence. The bold frequency indicates the most common handoff (as normally sectors are consolidated to this frequency). N90 sometimes combines the entire TRACON to one position. If the entire TRACON is combined, the handoff must be initiated to the consolidated position.
Arrival Route Segment Aircraft Type Waypoint Instructions Handoff Frequency
JFK ROBER or PARCH Turbojet CCC 12,000’ at 250 KIAS 10nm east of CCC 2K 125.70
2G 128.12
Direct ROBER 15nm east of ROBER 12,000’ at 250 KIAS
IGN 250+ IAS LOLLY FL200 LOLLY N34 132.17
N56 125.32
2G 128.12
LOVES Multiple LOVES 6,000’ Boundary 3H 120.05
2K 125.70
2G 128.12
PWL Prop LOVES 6,000’ PWL
JFK Props, FRG, BDR, HVN Multiple Multiple LOVES 6,000’ PWL
LGA NOBBI Prop NOBBI 8,000’ PWL 1V 120.80
EWR and Sats SHAFF FLOSI Multiple CRANK 7,000’ 5nm prior to CRANK 4A 120.15
4P 128.55
V489 COATE EWR props; Sats all types LEMOR 6,000’ Boundary 4S 123.77
4U 127.60
4A 120.15
4P 128.55
HPN Runway 16 in use Any Direct FARAN Join loc. at 4,000’ Boundary 1X 126.50
1V 120.80
VALRE Turbo VALRE 6,000' Boundary
NOBBI Non-Turbo NOBBI 6,000’ Boundary
Via HTO from E Jet HTO 11,000’ Boundary 3B 125.97
3H 120.05
2K 125.70
2G 128.12
RICED Any RICED 9,000’ Boundary
BOUNO Jet DPK 15,000’ at 250 KIAS Boundary 3Z 128.62
3H 120.05
2K 125.70
2G 128.12
SWF Direct TRESA or HUD STAR Jet TRESA 6,000' Boundary 5H 132.75
56 126.80
2G 128.12
FILPS Jet FILPS 7,000' Boundary
ISP J121/V268 HTO SARDI Any SARDI 7,000' Boundary 3H 120.05
2K 125.70
2G 128.12
LOVES 250+ IAS LOVES 6,000' Boundary
NELIE RNAV Boundary 8,000' Boundary 3B 125.97
3H 120.05
2K 125.70
2G 128.12
ZBW Procedures for ZNY Arrivals [show]
Arrival Route Segment Aircraft Type Waypoint Instructions Handoff
PHL North Sats, WRI J121 or V139 Any Boundary AOB 16,000’ Boundary
ACY, PHL, WRI, and Sats DNY (SPUDS) FL190+ HARVA FL190 Boundary
J121 (BRIGS/VCN) FL190+ Boundary FL200 ZNY if open or ZDC
V268/V308/DRIFT Non-jet Boundary AOB 16,000’
DOV J121 Any Boundary AOB FL220 Boundary
AVP LAAYK or LVZ Any Boundary AOB 14,000’ Boundary
BWI / DCA Traffic above FL240 routed via J75 (or J6/Q406/Q448/Q480) Turbojet Boundary FL240-360 Boundary
IAD and Sats HYPER via BAF or ALB Turbo KEAVR FL240-360 Boundary
HYPER via RBV Turbo RBV FL240-360 Boundary
J49 or PRIVO Non-Turbo Boundary AOB FL300 Boundary
HNK V576 or CFB V423 FQM Turboprop Boundary AOB FL220 Boundary
PIT and Sats HNK Any HNK FL280 Boundary
ZNY Procedures for ZBW Arrivals [show]
Arrival Route Segment Aircraft Type Waypoint Instructions Handoff
BOS from ZNY ORW Turbojet Boundary FL240-FL270 inclusive
FL230 from KPHL
WOONS Non-Turbojet Boundary FL230 Boundary
ACK or LFV Any Boundary P/D FL280 Boundary
BOS from N90 ORW Turbojet N/A 11,000’ to 17,000’ 2 ½ nm from ARTCC/N90 boundary
WOONS Non-Turbojet AOB FL210
ASH, MHT, ORH, BOS North Sats JFK, DPK, MAD Any DPK AOB FL230 Boundary
ALB LGA LGA055 V487 CANAN Turbojet LGA FL240 Boundary; ZBW control for turns NE of LGA
On/W of J190 Non-turbojet Boundary AOB FL240 Boundary
E of J190 Non-turbojet Boundary AOB 17,000’ Boundary
PVD RBV J62 Any Boundary AOB FL270 Boundary
BDR, FRG, HPN, HVN, OXC Via HNK or CFB Any Boundary AOB FL270 descending FL240
BAF, BDL, CEF, SWF Via DPK Any Boundary FL190 Boundary
BAF, BDL, CEF, ORH HNK STELA Any Boundary AOB FL270 Boundary
RKA STELA Any AOB FL370, descending FL330
N90 Sats ISP and Sats through ZBW Any Boundary AOB 9,000’ Boundary
KHPN via V139 Prop Boundary AOB 11,000’ Boundary
PVD Sats Any Prop Boundary AOB 11,000’ Boundary
Attachment 5 – Area Airport Listings [show]
ZNY Airports
Area Abbreviation Satellite Airport Codes
Elmira Area ELM ELM, BGM, ITH, SYR
Harrisburg Area MDT MDT, CXY, LNS, MUI, SEG, THV, ZER, N68, N71, N79, N94, 58N, 74N, 9D4
Islip Area ISP ISP, HWV, 23N
Islip Area East ISPE FOK, HTO, MTP, 03NY, 1N2, 21N, 87N
Islip Area North ISPN BDR, HVN, JSD, OXC, SNC, 42B
Kennedy Area JFK JFK, FRG
LaGuardia Area LGA LGA
LaGuardia Area North LGAN DXR, HPN
Liberty Area LIB SWF, POU, MGJ, MSV, NY35, N45, N69, N72, N82, N89, 06N, 20N, 44N, 46N, 5NY5
McGuire Area WRI WRI, NEL, BLM, MJX, N12, N14, N73, N81, N87, NJ20, NJ24, NJ46, NJ59, NJ60, NJ69, NJ72, NJ75, NJ87, 19N, 2N6, 2N8, 3N6, 3N7, 46NJ, 6NJ0
Newark Area EWR EWR
Newark Area North EWRN CDW, FWN, MMU, TEB, N05, N07, 1N7, 12N, 13N, 3N5, 4N1
Newark Area South EWRS LDJ, SMQ, N51, 39N, 47N
Philadelphia Area PHL PHL
Philadelphia Area North PHLN CKZ, DYL, LOM, PNE, PTW, TTN, UKT, N10, N47, 3NJ6, 9N1
Philadelphia Area South PHLS EVY, ILG, MQS, OQN, N57, NJ74, 17N, 58M, 7N7
Wilkes-Barre Area AVP AVP, HZL, MPO, WBW, N13, N30, 70N, 76N, 8N4, 9N3
ZBW Airports
Area Abbreviation Satellite Airport Codes
Albany Area ALB SCH
Boston Area North BOSN BED, BVY, FIT, LWM, 6B6, 9B1
Boston Area South BOSS GHG, OWD, 1B9
Bradley West Area Y90 West BAF, CEF, ORH, PMX, 7B2
Manchester Area East MHTE DAW, PSM, 3B4, 7B3
Manchester Area West MHTW ASH, CON, LCI, 8B1
Providence Area PVD BID, EWB, GON, LZD, SFZ, TAN, UUU, WST, 0B8
Other Airports
Area Abbreviation Satellite Airport Codes
KBWI Satellites BWI W29, KDMW, 2W2, W50, KESN, W48, W42, MD31, KFDK, 0W3, KANP, KMTN, KGAI, KAPG, W18, KFME, KEDG
KDCA Satellites DCA KADW, KCGS, KNDY, KDAA, W00, W32, KVKX, 2W5
KDOV Satellites DOV 0N4, 33N, KGED
KACY Satellites ACY KWWD, N87, KMIV, 26N, KOBI
KPIT Satellites PIT KAGC, KBVI, KBTP, 02G, 5G8, 2G2, 9G1, KFQW, KAFJ, KHLG, KPJC



Change Date Description
NOTE: Change notices 1-3 were archived and are no longer available.
CHG4 1 Aug 2016 MAJOR REVISION. Converted to Wiki format and aligned with real world procedures.
CHG5 15 Feb 2017 Added and revised various general procedures to align more closely with other LOAs; revised IGN STAR procedures; clarified procedure for PHL arrivals routed via MANTA; added new procedure for DCA arrivals when ZDC is offline; added SUA procedure; clarified ZBW-N90 JFK arrival procedure for aircraft unable 250 KIAS; clarified procedure forASH/MHT/ORH arrivals; added SYR procedures; clarified ZBW's control authority on MERIT/BAYYS departures; added ZBW-N90 ISP arrival restriction.
CHG6 12 Sep 2017 Updated speed scratchpads format.
CHG7 23 Dec 2019 Updated ZBW Sector Splits. Added ZBW-N90 SWF arrival restriction. Other minor stylistic changes.

© Copyright 2017 New York ARTCC and Cleveland ARTCC on VATSIM, All Rights Reserved.