mNo edit summary |
m ([email protected] moved page Draft:LOA/LGA ISP to LOA/LGA ISP without leaving a redirect: Publishing Draft to Main) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 7: | Line 7: | ||
}} | }} | ||
=== LaGuardia Area to Islip Area === | |||
*Departures from LGA Area to ISP 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. | ** 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 | ** 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 has control for turns not to exceed headings needed to transition the departure gates. | ||
*ISP VIKKY (3Z) has control on contact of traffic on: | * ISP VIKKY (3Z) has control on contact of traffic on: | ||
**CCC R-285 for Northeast-bound turns not to exceed BDR R-218. | ** CCC R-285 for Northeast-bound turns not to exceed BDR R-218. | ||
**BDR R-248 for Eastbound turns. | ** BDR R-248 for Eastbound turns. | ||
*ISP SEALL (3R) has control for: | * ISP SEALL (3R) has control for: | ||
**Descent to 3,000', 1.5nm west of the boundary for traffic routed CMK V374. | ** 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 | ** 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 | * 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. | * 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 | ** Prior to LGA accepting a handoff and | ||
**Only when an in-trail flow at 4,000' is not feasible due to speed differences. | ** 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’. | * 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. | * 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: | ** 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. | *** 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. | *** 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. | *** 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: | ** LGA Area: | ||
***Must clear aircraft to a fix for the appropriate transition. | *** Must clear aircraft to a fix for the appropriate transition. | ||
***May issue crossing altitudes at fixes other than those noted in the procedure. | *** 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. | *** 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. | * 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. | ||
Latest revision as of 17:53, 30 June 2025
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.
- ISP Area:
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.