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

Extract:LOAs-LGA

From New York ARTCC
More actions
Letter of Agreement
New York TRACON (N90) & LaGuardia Local (LGA)
Rev. 2 - 30 Jul 2015
Purpose
This agreement prescribes transfer of control procedures, radar handoff procedures, route/altitude assignments, and delegation of airspace between New York TRACON (N90) and LaGuardia Local (LGA). 
Cancellation
New York TRACON (N90) and LaGuardia Local (LGA) Letter of Agreement, dated January 2011, is hereby cancelled.
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

Coordination

  • Procedures contained in Letters of Agreement shall apply at all times unless prior verbal (or textual) coordination between facilities has been effected otherwise.

Position Combining/Decombining

  • Coordinate prior to combining/decombining pertinent positions within facilities with any affected controllers.

Conflicting Flows

  • When the facilities to which the LOA pertains must use conflicting traffic flows, they shall do so alternately, governed by traffic volume and delays at each airport or airspace.

LaGuardia Departure Procedures

  • LGA Local shall:
    • Select the runway configuration and notify the N90 TRACON prior to the change. When this selection conflicts with other airports, TRACON has final approval authority for runway configurations.
    • Identify to TRACON the last aircraft that will depart prior to a runway configuration change. Tower shall then obtain a release from TRACON for the first departure in the new configuration.
    • Ensure complete and accurate flight plans for all VFR departures. If the departure will be handled by TRACON, do not radar identify but handoff in a timely fashion.
    • Handoff departing traffic to TRACON after observing a turn towards the assigned climb or heading. Ensure the handoff is accomplished in a timely fashion.
  • LGA Local may:
    • Use heading of 350 instead of 340 when departing runway 31, in the event of strong winds aloft from the East/Northeast. If using heading 350 instead of 340, departures to the East Gate must also use heading 010 instead of 360.
    • Use heading of 055 (LGA# as published) instead of heading 070 when departing runway 4 and landing ILS 13, in the event of strong winds aloft from the North.


LaGuardia Arrival Procedures

  • New York TRACON shall:
    • Use the proper approach indicator (as per the table below) in the aircraft’s scratchpad if the assigned approach differs from the approach advertised in the ATIS.
    • Not turn departures until they reach 1,500'.
Table 1 – Scratchpad entries for approaches to LGA
Approach 4 13 22 31
ILS I4 I13 I22 –
LOC L4 L13 L22 L31
GPS G4 G13 G22 G31
RNP P4 – P22 –
Visual V4 V13 V22 V31
River Visual – 13 – –
Park Visual – – – PPV
VFR Arrivals VFR VFR VFR VFR
Letter of Agreement
Newark TRACON (EWR) & LaGuardia TRACON (LGA)
Rev. 4 - 19 Feb 2021
Purpose
This agreement prescribes transfer of control procedures, radar handoff procedures, route/altitude assignments, and delegation of airspace between Newark TRACON (EWR) and LaGuardia TRACON (LGA).
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.

Introduction

Coordination

    • Procedures contained in Letters of Agreement shall 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.

Conflicting Flows

When the facilities to which the LOA pertains must use conflicting traffic flows, they shall do so alternately, governed by traffic volume and delays at each airport or airspace.

General Procedures

  • EWR area shall allow LGA area departures to exit the northern portion of the LGA West Departure Gate, climbing out of 10,000' with a pointout.
  • Traffic landing within the TRACON airspace should not be climbed to 7,000' on the BREZY route.
  • Faster traffic landing outside of the TRACON airspace departing via the BREZY route may be climbed to 7,000' if its speed is roughly 50+ knots faster than the preceding BREZY departure and there is a risk of it overtaking the other aircraft.
  • For traffic on the CMK R-275 or through the arrival gate:
    • EWR has control for turns not to exceed headings to intercept the TEB ILS RWY 19 localizer from the East, and not to exceed heading 160 from the West of the localizer.
    • EWR has control for descent reference Eastbound traffic, and is responsible for ensuring that conflicts with that traffic are resolved before descending.
  • LGA Area shall provide in-trail spacing of NYACK SAX traffic at 4,000' to ZEEBO. When a significant speed difference exists, SAX traffic ≥ 210 Kts may be handed off to ZEEBO at 5,000'.
  • EWR has control for turns at 5,000' in LGA Area #40 (EWR Area #5) for traffic handed off from LGA to EWR.

EWR East Gate Departures

  • EWR Depart 4L/R:
    • LGA Departing Rwy 13/22 - departures shall be on hdg 040 at 5,000'.
    • LGA Departing Rwy 31 or Rwy 4 w/ headings – vector the departure through the EWR east departure gate, headings of 100 to 150.
  • EWR Depart 22R/L
    • Turboprops shall be on a 040 heading at 5,000'.
    • Jets shall be on a 040 heading at 6,000'.
  • EWR Depart 29 over BAYYS/BDR:
    • Turboprops shall be on a 060 heading at 5,000' unless LGA specifies that they should proceed through the East Departure Gate
  • LGA has control for climb to 10,000' and E/NE turns for East gate departures.
  • VFR aircraft shall be on a 040 heading OR through the East departure gate at 5,500'.
  • If Newark TRACON is offline and LaGuardia Departure is online or covered by another controller, Newark Local shall handoff to LaGuardia Departure:
    • EWR Depart 4L/R or 11: Departures shall be on a left turn to heading 040.
    • EWR Depart 29: Departures shall be on a right turn to heading 060.
    • EWR Departure 22L/R: Departures shall be on a right turn to heading 040.


Special Use Line (SUL)

  • When EWR is 22L/R and LGA is landing ILS 22, ILS 13, LOC 31, or departing Coney climb, Whitestone climb or NTHNS/TNNIS/HOPEA/JUTES:
    • EWR may climb RWY 22 departures to 6,000' along the Special Use Line (SUL).
    • LGA shall remain 1 1/2nm East of SUL from 10,000' to 7,000' and 3nm East of SUL below 7,000'.
  • When EWR is 22L/R, and LGA is same as above and using Maspeth climb or GLDMN departure:
    • EWR may climb RWY 22 departures when 1 1/nm West of SUL from 2,500' to 10,000'.
    • LGA shall remain 1 1/2nm East of SUL from 10,000' to 3,500' and 3nm East of SUL below 3,500’.
  • When EWR is 22 L/R and LGA LND 4, Expressway 31, River 13:
    • EWR may climb RWY 22 departures when 3nm West of SUL from 2,500' to 10,000'.
    • LGA may descend along SUL from 10,000' to 3,500' and shall be 3nm East of SUL below 3,500'.
  • When EWR is landing 22L/R and Departing 29:
    • If there is a departure demand for RWY 22L/R, then EWR Area should coordinate with EWR Tower to advertise the use of both runways for departure on the ATIS and coordinate this with LGA. EWR retains Areas #25 and #26 from 7,000' to 10,000'.
  • If the departure demand for RWY 22L/R will be light, then EWR Area has the option of delegating Areas #25 and #26 from 7,000' to 10,000' to LGA, and any EWR RWY 22 departures will climb only to 6,000' in those areas.
  • When EWR is departing runways 4L/R or 11, LGA may descend along the SUL (LGA Areas #13 and #14) from 10,000' to 4,000' and shall be 3nm east of the SUL below 4,000'.
  • The Newark departure controller may issue a climb above 2,500' when the following conditions have been met:
    • Traffic which may be a factor in the adjacent airspace has been observed on a heading parallel to or diverging from the SUL.
    • The Newark departure is observed diverging from the SUL by at least 15 degrees.


Procedures for when EWR lands 11/29

  • When EWR's primary approach is ILS runway 11, all LGA arrivals being vectored to the ILS runway 4 approach shall be kept at or above 2,700' until turning base leg. In the event of a EWR missed approach that has not established radio contact by the Verrazano Bridge, EWR will point out the aircraft.
  • When EWR utilizes RNAV (GPS) X RWY 29 for overflow traffic, LGA must use LOC 31 and EMPYR delegates Newark Local the airspace depicted in the Newark Local Airspace Delegation.


Procedures when LGA lands ILS runway 13

  • When LGA lands ILS runway 13 and EWR lands runway 22L:
    • EWR shall release areas #19 and #20 (i.e. LGA areas #33 and #34) from 3000-2700 west of TEB and 2700-1800 east of TEB, after coordinating with Teterboro Local.
    • TEB arrivals are in a TIMESHARE with LGA arrivals (i.e. TEB goes into airborne holding while LGA lands and vice versa). Traffic permitting, LGA will provide a gap for TEB arrivals to Rwy 1/6 departures.
    • TEB departures are not affected.
    • EWR intercepts ILS runway 22L at or above 3,000'. LGA intercepts ILS runway 13 at or below 2,000'.
  • When LGA lands ILS runway 13 and EWR lands runway 4L or 11:
    • EWR shall release areas #19 and #20 (i.e. LGA areas #33 and #34) from 3000-2700 west of TEB and 2700-1800 east of TEB, after coordinating with Teterboro Local.
    • Teterboro Local shall restrict runway 1 or 6 departures to 1,700'.
    • TEB may conduct SVFR operations at or below 1,300' in EWR areas #18, #19 and #20 (i.e. LGA areas #22, #23 and #24).
    • Newark Local to restrict departures to climb on heading 040 degrees to 4 DME, then turn left heading 290 degrees, maintain 2,000'
    • EWR SAT Departure may climb the departure to 2,000' when its course diverges from the ILS runway 13 localizer. The departure must remain on a divergent heading or 3nm from the ILS runway 13 localizer until it is clear of ILS runway 13 airspace.
    • TEB arrivals are in a TIMESHARE with EWR departures (i.e. TEB goes into airborne holding while EWR departs and EWR goes into a ground stop while TEB lands).
    • TEB departures are not affected.
    • LGA intercepts ILS runway 13 at or West of TEB at 3,000'. Descent on the glideslope is authorized.
    • EWR East Gate departures are vectored west to gain altitude then are turned back east over top of the LGA ILS runway 13 traffic and handed to LaGuardia Departure.
Letter of Agreement
John F Kennedy TRACON (JFK) & LaGuardia TRACON (LGA)
Rev. 3 - 31 Aug 2021
Purpose
This agreement prescribes transfer of control procedures, radar handoff procedures, route/altitude assignments, and delegation of airspace between John F Kennedy TRACON (JFK) and LaGuardia TRACON (LGA).
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

Coordination

  • Procedures contained in Letters of Agreement must apply at all times unless prior verbal (or textual) coordination between facilities has been effected otherwise.

Position Combining/Decombining

  • Coordinate prior to combining/decombining pertinent positions within facilities with any affected controllers.

Conflicting Flows

  • When the facilities to which the LOA pertains must use conflicting traffic flows, they must do so alternately, governed by traffic volume and delays at each airport or airspace.

Departure Procedures

Departures from/through JFK Area

  • Departures from/ through the JFK Area flight planned through the LGA Area shall be vectored NW bound to pass between Glen Cove and the Throgs Neck Bridge, and shall be at or above 6,000’, 1 1/2nm prior to the JFK/LGA boundary.

Departures from/through LGA Area

  • Departures from/through the LGA Area flight planned through the JFK Area shall be issued direct JFK, to pass between CRI and JFK ILS RWY 22L FAF.
  • JFK Area has control for climb and turns from 140 to 210 not to exceed the gate.
  • DIXIE traffic shall be direct JFK VOR, at or above 5,000’ to maintain 6,000’ , 1 1/2nm prior to the JFK/LGA boundary.
  • WHITE prop traffic shall be direct JFK VOR, at or above 6,000’ to maintain 7,000’, 1 1/2nm prior to the JFK/LGA boundary.
  • WAVEY/SHIPP traffic shall be direct JFK VOR, direct the respective fix (WAVEY, SHIPP), at or above 7,000’ to maintain 8,000’, 1 1/2nm prior to the JFK/LGA boundary.
  • When LGA is using Coney Airspace, LGA WAVEY/SHIPP/DIXIE jet traffic shall be routed via the Coney Climb airspace, WAVEY/SHIPP traffic unrestricted to 8,000’ and DIXIE jet traffic unrestricted to 6,000’. JFK Area has control for climb and turns to the East on contact.

Airspace Delegation

Belmont

Belmont Airspace

  • Under the following conditions, the LGA Area will release “Belmont Airspace” (LGA Area#23/JFK Area #4), after coordination, at and below 3,000’ to the JFK Area:
    • The primary JFK approach is ILS or RNAV (GPS) RWY 22L, or any approach to 22R.
    • LGA Airport is closed to fixed wing aircraft or the LGA Area does not require the use of the Belmont Airspace.

Belmont Extension

Belmont Extension Airspace

  • After coordination, LGA Area may delegate this airspace (JFK Area #30) at and below 3,000’, to JFK Area. The airspace shall be delegated upon request when the following conditions are met:
    • Weather is IFR.
    • JFK is landing instrument approaches to both RWY 22L and 22R.
    • LGA is landing ILS RWY 22 and departing RWY 13 (other than the Flushing Climb).
    • HPN is landing and departing any runway other than RWY 34.
  • LGA shall retain this airspace when landing RWY 22 and departing RWY 31, or when HPN is landing RWY 34.

Coney

Coney Airspace

  • When LGA is departing RWY 13 or 22 and coordinates for CONEY, NTHNS or HOPEA departures, and JFK is:
    • Landing RWYs 4L/R or 22L/R
    • Departing RWYs 4L/R or 22L/R or RWY 13
    • Not landing RWY 13
    • Not landing or departing RWYs 31L/R, JFK Area shall release the following airspace to LGA Area:
      • JFK Area #6/ LGA Area #17 from 1,500’ to 12,000’ (NOTE: 1,500’ to 2,000’ from JFK Tower)
      • JFK Area #7/ LGA Area #16, from 2,500’ to 10,000’
      • JFK Area #8/ LGA Area #15, at 4,000’ and 5,000’

Approaches

JFK ILS 13L Approach

JFK ILS 13L Approach Airspace Delegation

  • LGA will use ILS RWY 13 Approach, depart RWY 4 or 13 and release, with coordination, LGA Areas # 14 and 18/ JFK Areas #9A, 10 and 11, to JFK Area, at 3,000’ and below.

JFK ILS 22L/22R & RNAV 13L

  • Simultaneous use of JFK ILS 22L/R and RNAV 13L when LGA is departing RWY 13 is authorized only when LGA jets and turboprops are on the TNNIS departure and props are on the Flushing Climb.

LGA Localizer RWY 31 or RNAV (GPS) Z RWY 31

LGA Localizer RWY 31 or RNAV (GPS) Z RWY 31 Airspace Delegation

  • When JFK is not on 4s or 22s, JFK Area shall release the following airspace, with coordination, to LGA Area:
    • JFK Area #5A/ LGA Area #26 from 4,000’ to 2,000’; 4,000’ to 3,000’ when FRG ILS 14 is in use
    • JFK Area #5B/ LGA Area #25 from 4,000’ to 1,000’
    • JFK Area #5C/ LGA Area #24 from 3,000’ to 1,000’
  • When LGA is using the LOC RWY 31 approach or RNAV (GPS) Z RWY 31, JFK will not conduct any instrument approach to RWY 13L/R, due to a conflicting missed approach. The JFK Parkway Visual RWY 13L/R approach can be used with the LGA LOC RWY 31 approach.
  • Independent simultaneous instrument approaches to RWYs 31L/R are not authorized.

LGA TNNIS Departures

  • When LGA is using this departure procedure, visual approaches on RWY 22R are not authorized unless the aircraft is East of or established on an instrument approach course (ILS, RNAV).
  • LGA Area controllers shall notify JFK Area controllers when they are using the TNNIS or JUTES Departures.

EWR RNAV (GPS) X RWY29

  • The LGA Area will coordinate the use of the EWR RNAV (GPS) X RWY 29 approach with the JFK Area. The JFK Area will coordinate the use of the EWR RNAV (GPS) X RWY 29 approach with JFK Tower. After coordination, any point outs necessary will be made to EWRT.

Helicopters

  • Helicopters on the Copter RNAV 027 Approach via BANKA and COVIR waypoints shall be pointed out to the EMPYR position prior to the BANKA waypoint.
Letter of Agreement
LaGuardia TRACON (LGA) & Liberty TRACON (LIB)
Rev. 1 - 1 Jan 2011
Purpose
This agreement prescribes transfer of control procedures, radar handoff procedures, route/altitude assignments, and delegation of airspace between LaGuardia TRACON (LGA) and Liberty TRACON (LIB).
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.


LGA

  • LGA shall provide in-trail spacing of LGA and LGAN traffic towards SAX at 8,000' to LIB-N. When a significant speed difference exists, V249 traffic may be handed off at 8,000' and 9,000' to LIBN.
  • LGA shall hand off to LIB-E climbing out of 9,000' for 10,000', 1.5 NM from LGA/LIB boundary. LIBE has control for turns at or above 9,000' not to exceed headings needed to transition the LGA East Gate.
  • LGA prop departures to the West shall be climbing out of 11,000' for 12,000', 1.5nm from the LGA/EWR boundary. LIBW has control for climb to 15,000'.
  • LGA shall hand off to LIBN:
    • HAAYS prop and jet traffic requesting 12,000' to 17,000' - climbing to 12,000'.
    • COATE jet traffic requesting flight levels - climbing to 15,000'.
    • COATE prop traffic requesting flight levels - climbing to 12,000'.
    • COATE props and jet traffic requesting 17,000' and below — climbing to 12,000'.
  • Note: LGA may climb HAAYS and COATE prop traffic to 11,000' for handoff to LIBN when jet traffic at 12,000' is a factor, without coordination. LIBN has control for climb to 12,000' on prop traffic handed off at 11,000'.

LGAN

  • LGAN shall hand off to LIBE climbing out of 10,000' for 11,000', 1.5nm from the LGA/LIB boundary. LIBE has control for turns at or above 10,000' not to exceed headings needed to transition the LGAN East Departure Gate. Aircraft filed for 10,000' may be left at that altitude. LGAN has the option to hand off props requesting above 10,000' to LIB-E at 10,000' without coordination. LIBE has control for climb in LIB Area #30 (LGA Area #41).
  • LGAN has control for turns not to exceed headings needed to transition the departure gate for LIBH departures.

Liberty North (LIBN)

  • LIBN has control for turns not to exceed headings needed to transition the departure gates. LGA departures may be turned beyond 320 track at or above 12,000'.

Liberty East (LIBE)

  • LIBE has control for climb to 12,000' for aircraft climbing to 10,000' from LGA, southwest of the LGA/LENDY boundary line, and to 15,000' Nnortheast of the LGA/LENDY boundary line. LGA has the option to leave props requesting 10,000' and above at 9,000' without coordination. LIBE has control for climb for these aircraft in LGA Area #38 (LIB Area #29).

Liberty South (LIBS)

  • LIBS has control for turns for LGA traffic to enter LIBS airspace south of the DPK R-282.
  • LIBS has control for climb to 12,000' on contact on Coney Climb departures in Liberty Airspace #42 (LGA Airspace #17).

Liberty West (LIBW)

  • LIBW has control for turns not to exceed headings needed to transition the departure gates.
  • When LIBW uses the JFK radar sensor, LGA shall treat PARKE and ELIOT departures as one, with 20 miles in-trail spacing.

Liberty Catskill (LIBH)

  • LIBH has control for turns not to exceed headings needed to transition the Liberty Departure Gate for LIBH arrivals from the LGA Area.
  • LIBH shall ensure aircraft remain on or North of the IGN R-107 to provide a minimum of 3.5nm separation from the edge of the ANDLF holding pattern.
  • When LIBH is using SWF ILS Runway 27 approach, LGA will block 3,000' and below in Airspace Areas 43 and 44, remaining 1.5nm from the boundary line.
  • LIBH may clear aircraft routed IGN V157 VALRE direct to VALRE.
Letter of Agreement
LaGuardia TRACON (LGA) & Islip TRACON (ISP)
Rev. 2 - 14 Jul 2019
Purpose
This agreement prescribes transfer of control procedures, radar handoff procedures, route/altitude assignments, and delegation of airspace between LaGuardia TRACON (LGA) and Islip TRACON (ISP).
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.

LaGuardia Area to Islip Area

  • Departures from LGA Area to ISP Area
    • LGA must vector departures filed below 10,000' through the LGA to ISP Gate (LGA refers to this gate as "ISP Departure Gate") on a track from 060-080, and ensure aircraft are at 7,000' or 8,000' 1.5nm prior to the LGA/ISP boundary.
    • NYACK must vector departures filed below 10,000' through the LGAN to ISP Gate (LGA refers to this gate as "LGAN East Departure Gate") on a track from 060-130, and ensure aircraft are at 7,000' or 9,000' 1.5nm prior to the LGA/ISP boundary.
    • ISP has control for turns not to exceed headings needed to transition the departure gates.
  • ISP VIKKY (3Z) has control on contact of traffic on:
    • CCC R-285 for Northeast-bound turns not to exceed BDR R-218.
    • BDR R-248 for Eastbound turns.
  • ISP SEALL (3R) has control for:
    • Descent to 3,000', 1.5nm west of the boundary for traffic routed CMK V374.
    • Climbs at the line 5nm East of CMK for traffic vectored through the LGAN to ISP Gate at 7,000'
  • LGA Local must APREQ with the LGA Area prior to issuing the Hampton Helicopter Route to departures out of NYC or LGA:
    • The LGA Area must APREQ the route with ISP. LGA must hand off to ISP LOVES (3I) at 3,000'.
    • If the route cannot be approved, the fixed wing route via BDR must be issued.

Islip Area to LaGuardia Area

  • ISP must vector departures from ISP North Area (ISPN) towards CMK, and ensure aircraft are at or above 5,000' for 6,000' on the LGA/ISP boundary.
  • LGAN arrivals at 4,000' via BDR R-288 may be assigned 3,000' without coordination under the following conditions:
    • Prior to LGA accepting a handoff and
    • Only when an in-trail flow at 4,000' is not feasible due to speed differences.
  • Prior to issuing the Hampton Helicopter Route from FOK, HTO or 87N. ISP will APREQ with LGA area. In the event LGA area is unable to approve the route, the standard fixed wing route via BDR must be issued. ISP Area must handoff to LGA NOBBI (1X) at 2,000’.
  • LGA must advise the ISP Area when the HPN RNAV RWY 34 approach is in use and coordinate for either BDR RYMES or BDR DABVE transition. When the BDR DABVE transition is in use, the shoreline routing must be used for non-RNAV equipped aircraft. Termination of BDR DABVE transition must be coordinated between LGA and ISP.
    • ISP Area:
      • Must verbally advise LGA Area of aircraft that will not use the BDR DABVE transition or shoreline for non-RNAV equipped aircraft, as previously coordinated.
      • For BDR DABVE transition, must instruct aircraft to cross DABVE at 3,000' and transfer communications to LGA Area prior to DABVE. LGA Area has control for descent to 2,000' at DABVE.
      • Must instruct non-RNAV equipped aircraft to follow the shoreline and hand-off traffic to the LGA Area at 3,000'. LGA Area has control for descent to 2,000', 2-1/2nm from LGA/ISP boundary.
    • LGA Area:
      • Must clear aircraft to a fix for the appropriate transition.
      • May issue crossing altitudes at fixes other than those noted in the procedure.
      • May vector aircraft off the procedure for separation or sequencing. Instruct aircraft to resume the procedure by issuing a clearance direct to a fix or a heading to intercept the track for the appropriate transition.

LaGuardia Area Airspace Released to Islip Area

  • When the LGA Area releases airspace for CT60 departures, they will release ISP Areas #1 and #2 (Southern half of LGA Areas #46 & #47) from 3,000' and below.
Letter of Agreement
New York TRACON (N90) & Washington ARTCC (ZDC)
Rev. 1 - 27 Jun 2014
Purpose
This agreement prescribes transfer of control procedures, radar handoff procedures, route/altitude assignments, and delegation of airspace between New York TRACON (N90) and Washington ARTCC (ZDC).
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.

Delegation of Authority

Washington Center delegates to New York TRACON authority and responsibility for control of IFR arrival, departure, and tower en route (TEC) aircraft in controlled airspace within the Approach Control area depicted in Attachment 1.

Departure Procedures

  • When New York Center is offline:
    • N90 shall hand off J209 departures to Washington Center climbing to FL240
    • N90 shall hand off J174 departures to Washington Center climbing to FL230

Arrival Procedures

  • Arrivals shall be routed over the arrival fixes depicted on Attachment 2.
  • Arrivals shall have airport clearances provided that:
    • Approach control has not requested that arrivals be cleared to the clearance limit fixes on Attachment 2.
    • Approach control receives a radar handoff on arrivals at or prior to the transfer points.
    • Arrivals are cleared to cross the arrival fixes at the altitudes specified on Attachment 2.
  • N90 may descend and/or vector LGA arrivals via Robbinsville (RBV) when aircraft enters area A or B as depicted on Attachment 1.
  • N90 has control for turns not to exceed 30 degrees left of course on EWR arrivals at Yardley VORTAC (ARD).
  • When holding is necessary for LGA arrivals at RBV VORTAC:
    • N90 shall accept traffic descending to 10,000 feet at KORRY intersection that will hold at 9,000 and 10,000 feet and:
      • Issue holding instructions to the traffic that will be holding at 9,000 feet.
      • Advise ZDC when 10,000 feet is available at RBV VORTAC.
    • ZDC shall issue holding instructions to the traffic that will hold at 10,000 feet and transfer control to N90.
  • When delays are anticipated by N90, coordination shall be initiated in sufficient time to permit ZDC to clear arrivals to the appropriate clearance limit fixes depicted in Attachment 2.

Attachment 1 - New York Approach Control Airspace

       New York Approach Control Airspace
       [Show]

Attachment 2 - N90 Arrival Procedures

       Arrival Procedures
       [Show]
Retrieved from "https://wiki.vzny.org/index.php?title=Extract:LOAs-LGA&oldid=499"