Letter of Agreement
Optional Override Title
Rev. 3 - 16 Aug 2024
- Purpose
- 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).
- Scope
- The procedures contained herein must apply unless prior coordination is effected.
- Disclosure
- 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.
1. Purpose
This agreement defines the necessary pre-defined air traffic control procedures and coordination responsibilities between the Virtual New York ARTCC (vZNY) and Boston Virtual ARTCC (BVA).
2. Scope
The procedures contained herein must apply unless prior coordination has been effected.
3. Disclosure
BVA and vZNY 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. BVA and vZNY are not affiliated with the FAA in any manner.
4. General Procedures
- BVA/vZNY ATC must at all times:
- 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.).
- Ensure that all aircraft are at a 1X simulation rate prior to initiating handoff.
- 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.
- 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 10 nm (steady or increasing) or other value specified herein unless greater MIT separation is requested real-time by BVA/vZNY.
- NOTE: Separation of less than 10 nm 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.
- 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.
- Ensure that all conflicts, imminent situations, and MIT separation issues are resolved prior to handoff.
- Ensure the data block is formatted as follows:
- The altitude status (e.g., assigned and/or interim altitudes) will always reflect the actual/cleared status of the aircraft.
- Fourth line data block usage as authorized in the 7110.65, plus the following entries are authorized:
- A## - the aircraft has been approved to step away. The expected return time is indicated by ##.
- NORDO - The aircraft type and equipment suffix must match the aircraft and equipment capability.
- NORDO - the aircraft is unresponsive to multiple handoff attempts and has been messaged to contact the new frequency.
- 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.
- 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.
- 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.
- Each facility has control for beacon code changes on contact.
- KMTP is a ZBW airport (PVD_APP when online). N90 must coordinate with ZBW (or PVD_APP) prior to issuing VOR or GPS RWY 6 Approach to KMTP.
5. ZBW to ZNY
- Traffic southbound on J6, Q75, Q406, Q448, and Q480:
- Must enter ZNY airspace at or above FL240.
- ZNY will have control for turns up to 30° left or right of course when within 10nm of the ZNY/ZBW high boundary.
- ZBW may clear aircraft routed via Q406 and Q448 direct DBABE without coordination.
- ZBW may clear aircraft routed via Q480/J6 direct JEFFF without coordination.
- ZBW may clear aircraft routed via Q75 direct JERSY without coordination.
- Traffic destined to KDCA routed via Q167 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 Q75 MXE CLIPR STAR and will pass through ZNY. These aircraft must enter ZNY between FL240-FL340.
- ZBW may clear aircraft direct MANTA without coordination.
- ZBW must route aircraft to remain clear of that Special Use Airspace, shared with ZNY, that is designated as “hot” as determined by network coordination.
- Turbojet departures from KSWF/SAT routed via LAAYK with requested altitudes at or above 13000 must be transferred to ZNY AOA 13000, climbing to 17000. ZBW may clear aircraft direct LAAYK from north of T216.
6. ZNY TO ZBW
- The ORW and ROBUC procedures apply to turbojet aircraft only. Non-turbojet traffic destined KBOS and satellites must be routed via:
- From the N90 area: MERIT ORW WOONS STAR
- From all other areas: ORW WOONS STAR
- Traffic departing KACY, KDOV, KWRI, KPHL, and satellites of those airports routed via JIMEE WAVEY SHLEP and Q439 requesting FL230 or above must be handed off to ZBW climbing to FL230. ZBW must point-out to ZDC and climb traffic above FL230 as soon as practical.
- Traffic departing KITH requesting AOA FL180 must be transferred at 17000.
- Eastbound aircraft north of ULW may be cleared direct HINGZ. ZBW has control for left turns on these aircraft north of a ULW-HNK line.
- Without coordination, ZNY may clear eastbound traffic direct to:
| Via… | Required Route | May Be Cleared Direct |
|---|---|---|
| ZNY-56 | None | HTO, ACK, PUT |
| ZNY-66 | CCC or ORW AOA 130 | CCC or ORW |
| None | SARDI, RICED, HTO | |
| ZNY-68 | None | HTO |
7. ZBW TO N90
- Must handoff and transfer communications:
- At or prior to VALRE for V157 LGA arrivals.
- At least 5nm prior to all other arrival fixes.
- EWR terminal airspace is considered part of N90 on VATSIM. Traffic crossing the green line shown below, including LEMOR@6000 and CRANK@7000 handoffs, shall be instructed to contact:
- When the airspace is controlled top-down by ZNY: “New York Center”.
- When the airspace is controlled by NY_APP or a sector-specific position using the handoff code ‘N4’: “Newark Approach”.
Attachment 1: Airspace Owned by N90
| Section | Unconditional Airspace |
|---|---|
| D | 17,000' and below |
| E | 19,000' and below |
| F | 19,000' and below |
| G | 17,000' and below |
| L | 14,000' and below |
| Section | Conditional Airspace |
| AA | 20,000' - 21,000' |
Handoffs and Transfer of Communications
- ZBW ARTCC to N90 TRACON:
- At or prior to VALRE for LGA arrivals.
- At least 5 nm prior to all other arrival fixes.
- N90 TRACON to ZBW ARTCC:
- No later than 3 nm prior to the ARTCC/TRACON boundary.
- Ensure aircraft are established on a route or heading to intercept the appropriate route at the proper altitude prior to the departure fix.
Miles In-Trail Restrictions
- From ZBW to N90:
- LGA Arrivals: 10 MIT
- EWR Arrivals: 10 MIT
- JFK Arrivals: 10 MIT
- Aircraft bound to the same destination airport within ZBW or N90 shall be separated by no less than 10 miles (constant or increasing) unless coordinated otherwise.
- Aircraft on the same route segment and at the same altitude (not going to the same airport) shall be separated by no less than 10 miles (constant or increasing) unless coordinated otherwise.
Speed Restrictions
- Arrivals to N90 from ZBW:
- ZBW shall ensure that all aircraft do not exceed 250 knots Indicated Airspeed (IAS) at all arrival fixes. Higher IAS may be approved by N90.
- N90 shall make every effort not to reduce the IAS of an arrival aircraft below 250 knots until the aircraft is within ten (10) miles of the arrival fix without prior coordination with ZBW.
Airspace Owned by N90
| Section | Unconditional |
|---|---|
| D | 17,000' and below |
| E | 19,000' and below |
| F | 19,000' and below |
| G | 17,000' and below |
| L | 14,000' and below |
| Section | Conditional |
| AA | 20,000' - 21,000' |
Routing Procedures
- ZBW to ZNY:
- Traffic southbound on J6, Q75, Q406, Q448, and Q480 must enter ZNY airspace at or above FL240.
- ZNY will have control for turns up to 30° left or right of course when within 10nm of the ZNY/ZBW high boundary.
- ZBW may clear aircraft routed via Q406 and Q448 direct DBABE without coordination.
- ZBW may clear aircraft routed via Q480/J6 direct JEFFF without coordination.
- ZBW may clear aircraft routed via Q75 direct JERSY without coordination.
Center Delegations
- Boston Center
- Has control for climbs east of JFK R-010 on all GREKI and MERIT aircraft assigned 17,000' MSL.
- Shall release DEEZZ Holding Airspace after traffic within the airspace is coordinated with Liberty sector.
- N90 TRACON
- Coordinate for release of DEEZZ Holding Airspace when holding is required.
- Advise Danbury Sector when the Holding Airspace is no longer required and coordinate any traffic exiting the DEEZZ Holding Airspace (area AA in Attachment 1).
Attachment: Satellite Airports
- Attachment 1: Satellite Airports
- LGA Area Satellites:
- DXR, HPN
- JFK Area Satellites:
- FRG
- EWR North Satellites:
- 12N, 1N7, KCDW, 4N1, N05, N07, KMMU, 3N5, KFWN, KTEB, 13N
- EWR South Satellites:
- 47N, KLDJ, 39N, N51, KSMQ
- ISP Satellites:
- HWV, 23N
- LGA Area Satellites: