Extract:LOAs-ISP

Letter of Agreement

New York TRACON (N90) & Long Island Tower (ISP)

Rev. 2 - July 14, 2019

Purpose: This agreement prescribes transfer of control procedures, radar handoff procedures, route/altitude assignments, and delegation of airspace between New York TRACON (N90) and Long Island Tower (ISP).

Cancellation: New York TRACON (N90) and Long Island Tower (ISP) Letter of Agreement, dated Sep 2016, 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

Runway Changes
1. ISP Tower must select the runway configuration and notify the N90 TRACON prior to any change. When this selection conflicts with other airports, TRACON has final approval authority for runway configurations.
2. ISP Tower must identify to N90 TRACON the last aircraft that will depart prior to a runway configuration change. Tower must then obtain a release from TRACON for the first departure in the new configuration.
3. N90 TRACON must identify to ISP Tower the last aircraft that will arrive prior to a runway configuration change.
Missed Approach Procedures
1. ISP Tower is authorized to clear aircraft for a visual approach in accordance with Template:7110 and must advise N90 TRACON when the clearance is issued.
2. Aircraft who are not cleared for a visual approach by ISP Tower, must be coordinated and handed off to N90 TRACON as soon as practicable.
Practice Instrument Approaches
1. N90 TRACON must advise ISP Tower how the approach will terminate (full stop landing, touch and go, missed approach instructions, etc.). This must be accomplished prior to handoff.
2. ISP Tower must advise whether or not it can approve the approach.

Departure Procedures

New York TRACON must:
1. Have control for turns below 1,500' within 30 degrees either side of runway centerline.
2. Notify ISP Tower of overflights that affect departures and issue appropriate restrictions.
3. Issue expected release times when aircraft are held.
Long Island Tower must:
1. Provide separation within their airspace between traffic under their control and departure traffic under TRACON control.
2. Handoff departing traffic to TRACON after observing a turn towards the assigned heading. Ensure the handoff is accomplished in a timely fashion.
3. Ensure complete and accurate flight plans for all VFR departures. If the departure will be handled by TRACON, radar identify and handoff in a timely fashion.
4. Obtain release for aircraft departing from an inactive runway.
5. Obtain release for aircraft whose flight is planned via GAYEL, HAAYS, NEION, COATE, DPK, CCC or V16.
6. Obtain release for aircraft landing at any N90 airport; optimally, within 10 minutes of taxi time.

Arrival Procedures

**Table 1** - Scratch pad entries for different types of approach to ISP
Approach	6	15L	15R	24	33L	33R
ILS	I6	–	–	I24	–	–
LOC	L6	–	–	L24	–	–
GPS	R6	–	R5R	R24	R3L	–
Visual	6	15L	15R	24	33L	33R
VFR Arrivals	VFR	VFR	VFR	VFR	VFR	VFR
Note: Use "VAP" in the scratch pad to indicate that an arrival is visually following traffic to the active runway.

New York TRACON must:
1. Coordinate any approach other than that advertised in the ATIS by using scratchpad entries from Table 1. In VRC, press INSERT text <asel> to set scratch pads where "text" would be one of the entries below. Make sure to use capital letters when inserting scratch pads.
2. Verbally (or textually) obtain approval for use of a runway not designated as active for arrivals. Coordinate each arrival that will approach from a nonstandard transfer point or will land on a non-standard arrival runway. Approval for these approaches may be granted for an individual aircraft, a series of aircraft, or for a specified time frame.
3. Ensure transfer of communications to tower NO later than 6.5NM from the airport.
4. Sequence aircraft to downwind leg outside of the 30 degree cone on either side of the departure corridor of the active active runway or to 6.5NM on final.
Long Island Tower must:
1. Ensure that affected TRACON controllers are aware of the current ATIS code, runways in use, and approach information either by verbal (or textual) or automated coordination.
2. Verbally (or textually) advise of special changes in the airport configuration or weather.
3. Notify TRACON of control instructions which may affect aircraft under TRACON control.
4. Have control for turns and descent for sequencing not to exceed a 6.5NM final, on contact.

Letter of Agreement

John F Kennedy TRACON (JFK) & Islip TRACON (ISP)

Rev. 3 - August 31, 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 Islip TRACON (ISP).

Cancellation: John F Kennedy TRACON (JFK) and Islip TRACON (ISP) Letter of Agreement, dated July 2019, 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.

Departures from/through the ISP Area

Departures from/through the ISP Area flight planned over GAYEL/HAAYS/NEION/COATE/LGA@90, shall be vectored through the JFK/ISP Departure Gate on a track between 260 to 290 degrees.
GAYEL/HAAYS/NEION/COATE/LGA@90 traffic shall be at or above 6,000' to maintain 8,000' 1-1/2NM prior to the ISP/JFK boundary.
JFK Area has control on contact for turns not to exceed headings needed to transition the gate.
Traffic below 6,000' will be pointed out to ROBER.

Single Engine Aircraft from/through the ISP Area

Single engine aircraft from/through the ISP Area flight planned V16, shall be established on V16 and at 6,000' 1-1/2NM prior to the ISP/JFK boundary.
Traffic below 6,000' will be pointed out by ISP to ROBER.

Departures from/through the JFK Area over BDR

Departures from/through the JFK Area flight planned over BDR below 10,000' shall be climbed to 7,000' or 8,000'.
ISP has control for turns not to exceed headings needed to transition the East Departure Gate.

ISP and ISP East Single Engine Arrivals

Use the single engine arrival gate for ISP and ISP East single engine arrivals.
The JFK Area shall hand off these aircraft on a 090° heading at 3000'.

ISP and ISP East Turbo Prop, Twin Engine, and Jet Arrivals

Use the jet, turbo prop and twin engine arrival gate for ISP and ISP East jets, turbo props and twin engine arrivals.
JFK Area shall vector jet, turbo prop and twin engine aircraft through the arrival gate at 4000', on a track between 040° and 085°.
ISP Area has control on contact for turns not to exceed headings necessary to transit the gate.

FRG BEADS departures

The JFK Area will handoff the FRG BEADS departures to the ISP Area through the ISP multi-engine gate at 4000', or if the aircraft departs FRG to the north, towards DPK climbing to 5000'.

JFK Area to LGA North

Traffic from the JFK Area to LGA North airports shall be handed off to LOVES through the ISPN gate direct BDR at 3,000'

JFK/FRG arrivals over DPK

SATELLITE/ROBER has control on contact for turns 30 degrees right of course for all JFK and FRG arrivals routed over DPK from ISP Area.

JFK Southeast Arrivals

The following procedures may be applied for JFK Southeast Arrivals
JFK area shall provide an automated point out of JFK arrivals to the VIKKY position.
Acceptance of the point out constitutes approval for the aircraft to transition JFK Area 24/ ISP Area 16 southwest corner no further northeast than the extended centerline of ISP RWY 33L as low as 9,000'.
ISP is responsible for separation between point out aircraft and other aircraft under ISP control and shall issue restrictions necessary to provide separation from other aircraft within ISP area of Jurisdiction.

ISP Eastbound Departures

The following procedures may be applied for ISP Eastbound Departures
ISP Area shall provide an automated point out of ISP departures to the JFK ROBER position.
Acceptance of the point out constitutes approval for the aircraft to transition JFK Areas 21 (no further south than the Fire Island shore line)/22/23/25, ISP Areas 7/9 (no further south than the Fire Island shore line)/15 and climb to 11,000' after ISP Area coordination with ZBW.
ROBER is responsible for separation between point out aircraft and other aircraft under ROBER control, and shall issue restrictions necessary to provide separation from other aircraft within ROBER area of jurisdiction.
ISP must verbally coordinate with ROBER prior to course reversal in ISP Areas 7/9/15 (JFK Areas 21/22/23/25).

JFK & FRG ROBER Arrivals

The following procedures may be applied to JFK and FRG ROBER arrivals.
JFK area shall provide an automated point out of JFK and FRG arrivals to the ISLIP position
Acceptance of the point out constitutes approval for the aircraft to transition JFK Areas 25, 23, 22 and 21/ ISP Areas 7, 9 and 15 as low as 4,000'.
ISP is responsible for separation between point out aircraft and other aircraft under ISP control and shall issue restrictions necessary to provide separation from other aircraft within ISP area of Jurisdiction.

FRG RNAV (GPS) RWY 32

When the FRG RNAV (GPS) RWY 32 is in use, JFK will determine which of the following procedures they will use to work the FRG arrival traffic through ISP airspace.
Automated Point Out. JFK will initiate an automated point out to ISP when a FRG RNAV (GPS) RWY 32 is inbound. Upon acceptance of the point out, JFK will ensure that the aircraft remains on or west of the FAC. The point out terminates when the aircraft leaves ISP airspace. JFK will make an additional point out in the event of a missed approach.
Conditional Airspace. After coordination, ISP may delegate the Captree Block (ISP Block # 10, JFK Block # 20) to JFK at and below 2,000'. When the Captree Block is delegated to JFK, aircraft established on ISP ILS 6 localizer may not descend below 3,000' until east of the RNAV (GPS) RWY 32 FAC. JFK will coordinate with ISP to return the conditional airspace.

HPN Arrivals Over BOUNO

The following procedures may be applied for HPN arrivals over BOUNO
ISP Area shall provide an automated point out of BOUNO arrivals to the JFK ROBER position.
Acceptance of the point out constitutes approval for the aircraft to transition the JFK Areas 24, eastbound and descend below 11,000'.
ROBER is responsible for separation between point out aircraft and other aircraft under ROBER control, and shall issue restrictions necessary to provide separation from other aircraft within ROBER area of jurisdiction

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

Islip TRACON (ISP) & Liberty TRACON (LIB)

Rev. 2 - July 14, 2019

Purpose: This agreement prescribes transfer of control procedures, radar handoff procedures, route/altitude assignments, and delegation of airspace between Islip TRACON (ISP) and Liberty TRACON (LIB).

Cancellation: Islip TRACON (ISP) and Liberty TRACON (LIB) Letter of Agreement, dated Sep 2016, 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.

Islip Area to Liberty Area

Departures from ISP Area to LIB Area (Does not apply to intra-TRACON flights)
1. ISP must vector aircraft through ISP East Departure Gate on a track from 280 to 330 degrees, and ensure aircraft are level at 10,000' 1.5NM from the Departure Gate.
2. Liberty EAST has control for turns not to exceed the heading required to transition the Departure Gate.

Liberty Area to Islip Area

Arrivals from LIBH (Liberty Catskill) Area to ISP Area
1. ISP (SEALL) has control of descent for arrivals from 5,000' to 4,000', 1.5NM northwest of the ISP/LIB boundary.

OXC Airspace Block

ISP must coordinate with LIB and Y90 for the OXC RNAV (GPS) RWY 18 airspace block at and below 3,000' prior to clearing aircraft for a RNAV (GPS) 18 approach and advise when the block is no longer needed.
After release of OXC Block to ISP, LIBH must separate aircraft from the block boundary by three miles and utilize vertical separation.