Toggle search
Toggle menu
35
596
3
1.3K
New York ARTCC
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

BGM SOP

From New York ARTCC
More actions
New York ARTCC
Standard Operating Procedure — Binghamton ATCT and BGM TRACON

Rev. 3 — Revised: 2026-06-24

Area at a glance

ICAO Code Airport Name Airspace
KBGM Greater Binghamton Airport D (TRSA) 
       Uncontrolled Fields
       [Show]


Purpose
This document prescribes the procedures to be utilized for providing air traffic control services at Binghamton Air Traffic Control Tower (ATCT) and any of the positions within the Binghamton Terminal Radar Approach Control (TRACON) and the airports it serves. The procedures described herein are supplemental to the New York ARTCC Standard Operating Procedures and FAA Order JO 7110.65.
Distribution
This order is distributed to all New York ARTCC personnel.
Procedural 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.



Operational Positions

Position Callsign Radio Name Frequency Identifier
Clearance Delivery BGM_DEL Binghamton Clearance Delivery 125.050
Ground BGM_GND Binghamton Ground 121.900
Local BGM_TWR Binghamton Tower 119.300 1G
ATIS KBGM_ATIS 128.150
Sector Callsign Frequency Identifier Tag Remarks
Low Approach Radar BGM_L_APP 118.600 1L L Primary TRACON
High Approach Radar BGM_H_APP 127.550 1H H

ATCT

Clearance Delivery

Note

While strict north/south exit point usage is not required at BGM, the guide above may be useful for directing pilots to proper exits for departing the area.

Position Frequency Code
BGM_L_APP 118.600 1L
NY_CTR (Elmira 34) 132.175 C34
NY_CTR (Kennedy 56) 125.325 C56

The table on the right lists the common frequencies used as departure frequency by BGM Clearance Delivery. The first available controller in this list should be handling departures.

Note that this table only serves as a guide. The actual departure frequency has to be determined based on coordination with the other online controllers.

If there is no other controller online that would accept departures from BGM, use UNICOM frequency (122.8).

Routing to certain airports in ZNY and Tier 1 adjoining ARTCCs have been precoordinated through letters of agreement (LOA). These routes have been added to the Preferred Route Database. Follow ZNY PRD usage policy accordingly.

  • The initial altitude for IFR departures of all types is 4,000' whereas higher may be expected in 10 minutes after departure.
  • There is no published departure procedure out of Binghamton. All aircraft must be cleared to their destination via radar vectors to a BGM exit.
PHRASEOLOGY
Cleared to (clearance limit), via radar vectors (exit), then as filed. Maintain 4,000, expect (final altitude) one zero minutes after departure. Departure frequency (frequency), squawk (code).

Binghamton is a Class Delta airport. As BGM is located within a TRSA, VFR departures are assumed to desire flight following and radar services unless they state otherwise in their initial call. See the VFR Operations document for detailed explanation of applicable VFR procedures.

Ground

Departure Sequencing
Exit Gate Exits
North LAMMS, GTOWN, EXTOL, TRAAD, RKA
South CFB, LVZ, DNY, HNK, LAAYK

Aircraft should be sequenced to depart in the following order:

  1. By alternating gate group.
  2. If not the above, then by alternating exit.
  3. If not the above, then by aircraft type largest to smallest.
Runway Ownership and Crossings
  1. Closed runways shall be owned by Ground Control. The only time runways will ever be closed is during events, and closures must be authorized by the TMU. We do not simulate runway closures on VATSIM during standard day-to-day operations.
  2. Transfer of runway ownership, between Ground Control and Local Control, shall be accomplished verbally (or textually).
  3. Ground Control is authorized to cross all active runways with coordination with Local Control.
Intersection Departures and Usable Runway Lengths
  1. Since departures can come from multiple taxiways, the sequencing for intersection departures is a bit more involved as it will require Ground Control to properly push the strip to the tower controller in the correct order.
  2. For intersection departures, state the usable runway distance if that distance is not broadcast in the ATIS. Below is a list of usable runway lengths from common intersections. If the numbers are not divisible to 50, you must round them down to the nearest 50 feet before providing the information to the pilot.
    PHRASEOLOGY
    Runway one zero at alpha, taxi via foxtrot, golf, alpha. Runway one zero at alpha intersection departure, one thousand and seven hundred feet takeoff distance available.
10 34 28 16
B2 (3,350') 10/28 (5,750') B2 (1,600') 10/28 (1,550')
A (1,700') B (5,450') A (3,250') B (1,850')
34/16 (1,350') F (3,850') 34/16 (3,600') F (3,450')
D (2,300') D (5,000')
C (1,150') C (6,150')
Aircraft Movement
  1. As the taxiway system is simple, there are no pre-defined routings.
  2. If there is an imminent conflict between arriving and departing aircraft, hold departures on the ramp until the inbound aircraft is clear of the outbound aircraft.

Tower

Releases

Releases from Binghamton are automatic, unless the BGM TRACON requests individual releases.
Separation
The standard departure separation technique to be used is anticipated radar separation. When wake turbulence is a factor, use timed separation in accordance with FAA Order JO 7110.65 para 3-9-6.
Radar
This tower uses a DBRITE radar only and is not certified for any approach control services. By agreement with Binghamton TRACON, 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. It is imperative that tower controllers observe departing traffic turning towards the assigned heading before handing off. VFR aircraft can and must be radar identified to receive flight following within the tower's airspace, otherwise it is not necessary.
Aircraft Exiting the Runway
Arriving aircraft shall be issued a turn onto one of the taxiways adjacent to the landing runway to ensure the aircraft continues its taxi away from the runway exit. Handoff to Ground Control after the aircraft starts taxiing away from the active runway. Local Control will coordinate with Ground Control, as needed, to determine the traffic flow on the taxiways.

Runway Selection

Wind Speed Direction (°M) Configuration
Depart Land
0-4 Any 34 34
> 4 250-070 34 34
071-249 16 16

Note: Runway 10/28 is available for use at controller discretion if it is operationally advantageous or weather requires it, as well as at pilot request.

IFR aircraft must be given runway heading, unless otherwise coordinated with the departure controller.

PHRASEOLOGY
Fly runway heading, wind (wind), runway (runway), cleared for takeoff.
Runway Heading Altitude
10 Runway Heading 4,000'
28 Runway Heading 4,000'
16 Runway Heading 4,000'
34 Runway Heading 4,000'
Missed Approach Procedures
  1. Missed approaches or go-arounds must fly runway heading or track the localizer until reaching the departure end of the runway, then be issued a heading, unless the controller determines that it would be advantageous to delay or initiate a turn early.
  2. The table to the right indicates the heading and altitude that need to be assigned to a missed approach or go-around prior to release to TRACON frequency.
  3. If the conditions are VMC (Visual Meteorological Conditions), then the Tower may keep the aircraft in the pattern and clear the aircraft for a visual approach in accordance with FAA Order JO 7110.65 para 7-4-3. Use best judgment to determine whether to keep the aircraft in the pattern or not.
Additional Information
  1. Separation must be based on altitude initially during all missed approaches or go-arounds. Prior to issuing a climb to 4,000', interval altitudes such as 3,000' may be utilized to prevent converging targets from losing separation.
  2. In order to prevent increased workload on the TRACON, consider issuing missed approaches or go-arounds speed restrictions in accordance with FAA Order JO 7110.65 para 5-7.
  3. Coordinate with TRACON as soon as possible and hand off when Local Control traffic is not a factor.
  4. Sound judgment must be exercised when dealing with go-arounds or missed approaches. Deviate as necessary from the headings and altitudes listed on the table if using them would compromise safety. (Exercise due caution for terrain and associated MVAs in the vicinity of BGM, which are more impactful at this airport than most in ZNY.)

Airspace

  1. Class DELTA.
  2. The tower owns 4,100' and below within a 5 mile radius of the airport.
Departures
Aircraft should be given the most expeditious way out of the airspace, which should be away from the IFR flow.
Over-flights
Allow overflight aircraft to cross over the numbers of the active runway. Make sure to give traffic advisories as necessary.
Pattern Work
  1. All aircraft wanting to perform pattern work at BGM must be assigned left closed traffic.
  2. All helicopters should be at 500' AGL, props at 1,000' AGL and jets at 1,500' AGL. Adjust these altitudes when necessary to avoid over-flights or IFR traffic flow.

TRACON

Callsign

  1. Whenever a controller handles a departure, they must use the radio name "Binghamton Departure" when referring to themselves on frequency.
  2. Whenever a controller handles an arrival or enroute traffic, they must use the radio name "Binghamton Approach" when referring to themselves on frequency.
  3. If talking to other controllers via land line, refer to yourself as the sector name for which you are controlling.
Coordination
Procedures contained in Letters of Agreement must apply at all times unless prior verbal (or textual) coordination between facilities has been affected otherwise.
Position Combining/Decombining
Coordinate prior to combining/decombining pertinent positions within facilities with any affected controllers.
Point Outs
When using an automated point out, verbal (or textual) approval must be obtained before an aircraft may enter another controller's airspace. An automated point out not accompanied by a verbal or textual description does NOT constitute a valid point out.
Separation Minima
Minimum radar separation between aircraft must be at least three miles (intra-TRACON) or five miles (TRACON-Center) constant or increasing when transfer of control is accomplished. Other factors such as wake turbulence separation and miles-in-trail requirements may increase this minimum.
Conflicting Flows
When the facilities for which the LOA pertains to must use conflicting traffic flows, they shall do so alternately, governed by traffic volume and delays at each airport or airspace.

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
  1. Transfer of Control Procedures:
    1. Minimum radar separation between aircraft, when transfer of control is accomplished, shall be at least five (5) miles constant or increasing.
    2. Assume control of aircraft at time of communications transfer for turns of 45 degrees or less.
  2. VFR Procedures:
    1. Automated VFR handoffs are optional between facilities. No verbal coordination is required.
    2. At facilities that do not automatically inhibit MSAW, the receiving controller shall inhibit the MSAW function.
    3. The receiving controller shall be responsible for obtaining all pertinent information.
    4. Upon completion of a handoff, the aircraft may enter the receiving facility's airspace on the transferring facility's beacon code.
  3. Coordination Procedures:
    1. 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.
    2. The Tower shall advise the Center of the identity of the aircraft at the highest holding altitude being used at the holding fixes.
    3. RNAV (GPS)-A Approach to N27:
      1. ZNY must verbally coordinate the approach with BGM.
      2. ZNY will clear aircraft via the approach.
      3. 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
       [Show]

       Attachment 2 — Arrival Procedures
       [Show]

       Attachment 3 — Departure Procedures
       [Show]
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.

  1. Transfer of Control Procedures:
    1. Transfer points are 5nm from the boundary.
  2. Coordination and Handoff Procedures:
    1. 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.
    2. BGM shall forward a KERRI estimate for aircraft via V167 KERRI at 5000'.
    3. BGM must provide a minimum of 4-miles radar separation between aircraft handed off to N90.
    4. 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
       [Show]
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
  1. Radar Procedures:
    1. 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.
    2. 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.
    3. Transfer points shall be the ELM/BGM boundary, see attachments 1 and 2.
  2. Ithaca Approaches:
    1. Elmira TRACON shall inform Binghamton TRACON of the approach procedure in use at Ithaca Airport.
    2. 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.
  3. VFR Procedures:
    1. Automated VFR handoffs are optional between facilities. No verbal coordination is required.
    2. At facilities that do not automatically inhibit MSAW, the receiving controller shall inhibit the MSAW function.
    3. The receiving controller shall be responsible for obtaining all pertinent information.
    4. Upon completion of a handoff, the aircraft may enter the receiving facility's airspace on the transferring facility's beacon code.
  4. Coordination Procedures:
    1. 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
       [Show]

       Attachment 1 — From ELM to BGM
       [Show]

       Attachment 2 — Area "L" Procedures
       [Show]
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
  1. 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.
  2. Traffic may be vectored 45 degrees left or right of course by the receiving facility upon communications transfer.
  3. 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.
  4. 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.
  5. Traffic departing BGM landing PHL must be assigned 8,000 feet as a final cruise altitude.
  6. Traffic departing BGM landing PHL must be routed via LVZ V29 PTW.
  7. Traffic landing Newark must be routed via direct LVZ V613 BWZ302 BWZ EWR.
  8. Traffic landing Newark Satellites must be routed via direct LVZ V226 MUGZY STW direct (TEB, MMU, CDW, FWN, 4N1, N07, 12N, 1N7).
  9. Aircraft routed over the LVZ VOR may be cleared direct without prior coordination.
  10. Aircraft routed direct DNY VOR must be at 7000 feet.
  11. BGM has control for descent for aircraft landing N27.
  12. Traffic landing 47N, LDJ, 39N, N51 and SMQ must be routed via DIRECT LVZ..FJC..SBJ DESTINATION.
VFR Procedures
  1. Automated VFR handoffs are optional between facilities. No verbal coordination is required.
  2. It is suggested to inhibit MSAW alerts (vSTARS client) on all targets.
  3. The receiving controller must be responsible for obtaining all pertinent information.
  4. 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
       [Show]

       Attachment 2 — Wilkes-Barre Approach Control Boundary
       [Show]

Airspace Sectorization

Retrieved from "https://wiki.vzny.org/index.php?title=BGM_SOP&oldid=1517"