Extract:LOAs-BGM: Difference between revisions
From New York ARTCC
More actions
m 1 revision imported: Template migration from wiki-dev |
Sync from wiki.nyartcc.org (production) — src rev 2026-03-30T05:25:06Z |
||
| Line 1: | Line 1: | ||
<tabber> | <tabber> | ||
|-|LOA with ZNY= | |||
|-|ELM= | {{:LOA/BGM ZNY}} | ||
|-|LOA with N90= | |||
{{:LOA/BGM N90}} | |||
|-|LOA with ELM= | |||
{{:LOA/BGM ELM}} | {{:LOA/BGM ELM}} | ||
|-|LOA with AVP= | |||
|-|AVP= | {{:LOA/AVP BGM}} | ||
{{:LOA/ | |||
</tabber> | </tabber> | ||
Latest revision as of 00:54, 24 June 2026
Letter of Agreement
Binghamton TRACON (BGM) & New York Center (ZNY)
Rev. 1 – June 26, 2021
- Purpose
- This agreement prescribes transfer of control procedures, radar handoff procedures, route/altitude assignments, and delegation of airspace between Binghamton TRACON (BGM) and New York Center (ZNY).
- 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.
- General Procedures
- Transfer of Control Procedures:
- Minimum radar separation between aircraft, when transfer of control is accomplished, shall be at least five (5) miles constant or increasing.
- Assume control of aircraft at time of communications transfer for turns of 45 degrees or less.
- VFR Procedures:
- Automated VFR handoffs are optional between facilities. No verbal coordination is required.
- At facilities that do not automatically inhibit MSAW, the receiving controller shall inhibit the MSAW function.
- The receiving controller shall be responsible for obtaining all pertinent information.
- Upon completion of a handoff, the aircraft may enter the receiving facility's airspace on the transferring facility's beacon code.
- Coordination Procedures:
- Traffic restrictions shall be applied when delays exceed or are anticipated to exceed 15 minutes. Adequate advance notice must be given to avoid or minimize airborne delays.
- The Tower shall advise the Center of the identity of the aircraft at the highest holding altitude being used at the holding fixes.
- RNAV (GPS)-A Approach to N27:
- ZNY must verbally coordinate the approach with BGM.
- ZNY will clear aircraft via the approach.
- ZNY will initiate a radar handoff, if the handoff is not accomplished within 5 miles of the BGM boundary ZNY will terminate the aircraft's radar service and turn the aircraft over to BGM.
Attachment 1 — Approach Control Area Delegated Airspace
Attachment 2 — Arrival Procedures
Attachment 3 — Departure Procedures
Letter of Agreement
Binghamton TRACON (BGM) & New York TRACON (N90)
Rev. 1 – June 28, 2021
- Purpose
- This agreement prescribes transfer of control procedures, radar handoff procedures, route/altitude assignments, and delegation of airspace between Binghamton TRACON (BGM) and New York TRACON (N90).
- 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.
- General Procedures
Aircraft shall be cleared to destination airport via routes and altitudes depicted on Attachment #1 landing within N90 Liberty Area airspace. All other destination airports will be pre-coordinated.
- Transfer of Control Procedures:
- Transfer points are 5nm from the boundary.
- Coordination and Handoff Procedures:
- Traffic restrictions shall be applied when delays exceed or are anticipated to exceed 15 minutes. Adequate advance notice must be given to avoid or minimize airborne delays.
- BGM shall forward a KERRI estimate for aircraft via V167 KERRI at 5000'.
- BGM must provide a minimum of 4-miles radar separation between aircraft handed off to N90.
- N90 must provide a minimum of 5-miles radar separation between aircraft handed off to BGM.
Attachment 1 — Tower Enroute Chart and Route Description and Procedures
Letter of Agreement
Binghamton TRACON (BGM) & Elmira TRACON (ELM)
Rev. 1 – June 30, 2021
- Purpose
- This agreement prescribes transfer of control procedures, radar handoff procedures, route/altitude assignments, and delegation of airspace between Binghamton TRACON (BGM) and Elmira TRACON (ELM).
- 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.
- Procedures
- Radar Procedures:
- Airport clearances shall be issued via direct ULW and CFB or airways to ULW and CFB. Aircraft landing at Elmira Airport shall be descending to or level at 6,000 feet or level at 4,000 feet; aircraft landing at Ithaca Airport shall be descending to or level at 6,000. Aircraft landing at Binghamton or Tri-Cities Airports shall be descending to or level at 7,000 feet or level at 5,000 feet.
- For aircraft landing at Binghamton and Tri-Cities Airports, or Elmira and Ithaca Airports, the receiving controller shall have control for descent and turns not to exceed forty-five (45) degrees.
- Transfer points shall be the ELM/BGM boundary, see attachments 1 and 2.
- Ithaca Approaches:
- Elmira TRACON shall inform Binghamton TRACON of the approach procedure in use at Ithaca Airport.
- Upon request and traffic permitting, Binghamton TRACON will delegate to Elmira TRACON authority and responsibility with Area "L" (Attachment 2) or control of IFR aircraft into Ithaca Airport. Binghamton TRACON will block the appropriate airspace until Elmira TRACON calls Area "L" clear. Non-radar ILS approaches into Ithaca Airport will be subject to approval by Binghamton TRACON.
- VFR Procedures:
- Automated VFR handoffs are optional between facilities. No verbal coordination is required.
- At facilities that do not automatically inhibit MSAW, the receiving controller shall inhibit the MSAW function.
- The receiving controller shall be responsible for obtaining all pertinent information.
- Upon completion of a handoff, the aircraft may enter the receiving facility's airspace on the transferring facility's beacon code.
- Coordination Procedures:
- Traffic restrictions shall be applied when delays exceed or are anticipated to exceed 15 minutes. Adequate advance notice must be given to avoid or minimize airborne delays.
Attachment 1 — From BGM to ELM
Attachment 1 — From ELM to BGM
Attachment 2 — Area "L" Procedures
Letter of Agreement
Wilkes Barre TRACON (AVP) & Binghamton TRACON (BGM)
Rev. 1 – August 15, 2020
- Purpose
- This agreement prescribes transfer of control procedures, radar handoff procedures, route/altitude assignments, and delegation of airspace between Wilkes Barre TRACON (AVP) and Binghamton TRACON (BGM).
- 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.
- Procedures
- All aircraft must be cleared to the destination airport via the routes and altitudes described in Attachment 1. Routes and altitudes other than those depicted in this LOA must be on an APREQ basis.
- Traffic may be vectored 45 degrees left or right of course by the receiving facility upon communications transfer.
- Transfer of control and communications points must be five (5) miles from the boundary for traffic entering either facility's airspace at 8000 feet or below.
- Traffic inbound to Binghamton airspace or landing ITH from Section E airspace (as depicted on Attachment 2) will be handed off to BGM at the AVP-BGM 8000 feet boundary descending to 9000 feet. Binghamton has control for descent in Section E.
- Traffic departing BGM landing PHL must be assigned 8,000 feet as a final cruise altitude.
- Traffic departing BGM landing PHL must be routed via LVZ V29 PTW.
- Traffic landing Newark must be routed via direct LVZ V613 BWZ302 BWZ EWR.
- Traffic landing Newark Satellites must be routed via direct LVZ V226 MUGZY STW direct (TEB, MMU, CDW, FWN, 4N1, N07, 12N, 1N7).
- Aircraft routed over the LVZ VOR may be cleared direct without prior coordination.
- Aircraft routed direct DNY VOR must be at 7000 feet.
- BGM has control for descent for aircraft landing N27.
- Traffic landing 47N, LDJ, 39N, N51 and SMQ must be routed via DIRECT LVZ..FJC..SBJ DESTINATION.
- VFR Procedures
- Automated VFR handoffs are optional between facilities. No verbal coordination is required.
- It is suggested to inhibit MSAW alerts (vSTARS client) on all targets.
- The receiving controller must be responsible for obtaining all pertinent information.
- Upon completion of a handoff, the aircraft may enter the receiving facility's airspace on the transferring facility's beacon code.
Attachment 1 — Route Descriptions
Attachment 2 — Wilkes-Barre Approach Control Boundary