Extract:LOAs-EWR
From New York ARTCC
More actions
Letter of Agreement
New York TRACON (N90) & Newark Local (EWR)
Rev. 3 - 19 April 2021
- Purpose
- This agreement prescribes transfer of control procedures, radar handoff procedures, route/altitude assignments, and delegation of airspace between New York TRACON (N90) and Newark Local (EWR).
- 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 affected otherwise.
Position Combining/Decombining
- Coordinate prior to combining/decombining pertinent positions within facilities with any affected controllers.
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.
Airspace Delegations
- EWR Local is delegated its airspace from the N90 TRACON and therefore the airspace delegated from N90 depends on the runway configuration
- The airspace delegated to EWR Local can be found in the Airspace Delegation in the Local Control section of the EWR SOP.
Newark Departure Procedures
- EWR Local shall:
- Select the runway configuration and notify the N90 TRACON prior to the change. When this selection conflicts with other airports, N90 TRACON has final approval authority for runway configurations.
- Identify to N90 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.
- Obtain releases for aircraft not using the standard departure runway(s).
- 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.
Newark 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.
- The scratchpad entries for Visual Approaches are used when the approach is not for the arriving runway. If the Visual Approach is being conducted to the standard arriving runway, use "VAA" as the scratchpad entry for a visual approach to the airport, while "VAP" should be used for an aircraft following traffic ahead.
- Not turn departures until they reach 1,500'.
| Approach | 4L | 4R | 22L | 22R | 11 | 29 |
|---|---|---|---|---|---|---|
| ILS | I4L | I4R | I2L | I2R | I11 | – |
| GLS | G4L | G4R | G2L | G2R | G11 | – |
| GPS | R4L | R4R | R2L | R2R | R11 | R29 |
| RNP | – | P4R | P2L | – | – | PY9/PZ9 |
| Visual | 4L | 4R | 22L | 22R | 11 | 29 |
| Bridge Visual | – | – | – | – | – | B29 |
| Stadium Visual | – | – | – | – | – | S29 |
| Circle to Land | – | – | C2L | C2R | C11 | C29 |
| VFR Arrivals | VFR | VFR | VFR | VFR | VFR | VFR |
Letter of Agreement
Newark TRACON (EWR) & Liberty TRACON (LIB)
Rev. 1 - 1 Jan 2021
- Purpose
- This agreement prescribes transfer of control procedures, radar handoff procedures, route/altitude assignments, and delegation of airspace between Newark TRACON (EWR) 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.
General Procedures
- EWR Departure may leave North props requesting 10,000' and above at 9,000' without coordination. Aircraft flight planned below 10,000' will be at 9,000'. LIBN does not have control for climbs for traffic at 9,000'.
- For departures going to South Gate exits, EWR Departure will clear departures direct ELVAE at 6,000'/5,000' and release control for climbs to LIBS. LIBS is still responsible for coordination as required with LGA area and/or LIBW.
- LIBN and LIBW have control for turns of EWR and EWR satellite departures not to exceed headings which transition the respective departure gates.
- LIBW has control for turns on SBJ gate traffic no farther North than the extended centerline of EWR runway 11.
- LIBN may handoff any V249 traffic at 8,000' or 9,000' to METRO if a significant speed difference exists, with a pointout to EWR Departure.
- When EWR Satellite Departure is open EWR/EWR SAT jets may transition the North gate at 9,000' or 10,000', and should be at 10,000' when traffic permits.
- When EWR Satellite Departure is open, LIBN may turn no further East than 5½nm from the Western edge of the North Gate.
- EWR/EWR SAT will provide 20 miles-in-trail departures via ELIOT.
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
Newark TRACON (EWR) & Teterboro Tower (TEB)
Rev. 2 - 1 Mar 2019
- Purpose
- This agreement prescribes transfer of control procedures, radar handoff procedures, route/altitude assignments, and delegation of airspace between Newark TRACON (EWR) and Teterboro Tower (TEB).
- 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
- Class D Airspace:
- The TRACON may allow traffic inside Class D airspace at 2,500 feet MSL without prior coordination, except when the ILS RWY 19 approach is in use.
- EWR RWY 22 arrivals shall cross TEB at or above 2,500' and descend to cross 5nm Southwest between 1,800' and 1,500', except cross TEB at 3,000' when the ILS RWY 19 approach is in use.
- Use of ILS RWY 19 approach: in the event of a missed approach, Teterboro Local will issue control instructions to separate the missed approach aircraft from B757/heavy jet traffic landing RWY 22L/R at EWR and climb the aircraft to 2,000' in the designated airspace.
- Combining positions: each facility shall notify the other prior to combining/decombining positions and specify which position will assume responsibility.
- Runway Configuration: Teterboro Local shall select the runway configuration and notify EWR TRACON prior to changes. When Local's selection conflicts with other airports, EWR TRACON has final authority for runway configuration.
Arrival Procedures
- TRACON Shall:
- Inform Teterboro Local of the first and last aircraft for each approach/runway whenever a change of traffic flow occurs.
- Use the proper approach indicator (as per the table) in the aircraft’s scratchpad before the aircraft is 3nm from TEB Local airspace, if the assigned approach differs from the approach advertised in the ATIS.
- Obtain approval and provide handoff for arrivals approaching from other than the normal transfer point or landing on a non-service runway.
- Advise when Newark (EWR) RWY 22 and/or LaGuardia (LGA) ILS/DME RWY 13 approaches are in use.
- Retain responsibility for separation of TEB IFR arrivals and EWR RWY 4/11 departures and may enter Area B with EWR departure traffic above 1,000'.
- Teterboro Local Shall:
- Advise of changes in the ATIS code and visibility/wind changes not shown in current weather observations.
- Inform of airport conditions, runway acceptance rates, and specify the separation required between successive arrivals.
- Coordinate control instructions affecting traffic under TRACON control (e.g., missed approaches, go-arounds, speed reductions).
- Advise TRACON of the landing runway if a circling approach is being made.
- Enter Area B descending out of 1,500' with VFR traffic landing runways 1 and 6 or climbing to 1,500' departing runways 19 and 24, with appropriate traffic advisories.
- Advise whenever a speed restriction is necessary for arrival aircraft.
- Notify of changes in RVR that may affect traffic under TRACON control.
- Teterboro Local is authorized to clear aircraft for a visual approach as per FAA Order JO 7110.65 and shall advise TRACON when the clearance is issued.
- Coordination: The controller receiving a point-out is responsible for completing all necessary internal coordination.
| Approach | 1 | 6 | 19 | 24 |
|---|---|---|---|---|
| ILS | – | I6 | I19 | – |
| GPS | – | RX6/RY6 | R19 | – |
| RNP | – | P6 | P19 | – |
| Visual | 1 | 6 | 19 | 24 |
| VFR Arrivals | VFR | VFR | VFR | VFR |
Departure Procedures
- Teterboro Local Shall:
- Obtain releases for IFR departures.
- Provide visual separation between traffic on the VOR/DME-B Approach and traffic departing RWY 24.
- Inform TRACON of the departure sequence and ensure its integrity.
- Provide a “rolling call” to Departure position, which may consist of call sign only, per FAA Order JO 7110.65
- Following a runway change, inform of the last aircraft to depart prior to the change and the first after, and obtain release from TRACON.
- When automatic releases are in effect, obtain release for aircraft departing RWY 19. Re-coordinate release off RWY 24 after any RWY 19 departure.
- Depart no more than one (1) more aircraft after automatic releases are canceled if arrival traffic is a factor.
- Check release five (5) minutes before departure on traffic landing at EWR, Linden (LDJ), LGA, MMU, or CDW.
- RWY 19 IFR Departures:
- Request an arrival gap in the EWR RWY 22L/R sequence.
- When Teterboro is IFR, TRACON will provide a gap of no less than 10nm.
- When feasible, arrival gaps are provided behind non-heavy aircraft.
- Teterboro Local ensures standard separation between a RWY 19 departure and aircraft identified in the RWY 22L/R arrival gap.
Attachment 1 – Airspace Allocation and Terminal Entry Points
| Area | Restrictions |
|---|---|
| A |
|
| B |
|
| C |
|
Attachment 2 – Airspace Diagram
TEB Airspace Diagram
Letter of Agreement
Newark TRACON (EWR) & McGuire RAPCON (WRI)
Rev. 1 - 2 Mar 2015
- Purpose
- This agreement prescribes transfer of control procedures, radar handoff procedures, route/altitude assignments, and delegation of airspace between Newark TRACON (EWR) and McGuire RAPCON (WRI).
- 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.
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.
EWR arrivals from WRI airspace
- WRI feeds ARD from RBV V249 METRO at 6,000' on EWR Jet/HPTP arrivals.
- When N90 is unable to accept traffic landing EWR, N90 will delegate that portion of the RBV holding pattern north of V276 (i.e., EWR Area #36, WRI Area #12) at 6,000' to WRI.
- WRI shall affect a radar handoff and transfer communications at least 2½nm from the airspace boundary lines. ARD has control for turns 30 degrees left or right of the inbound course.