New York ARTCC
ISP SOP
Rev. 5 — 14 Jul 2019

Bookmarks: TopISP ATCT ( DEL | GND | TWR ) • TRACON

Area at a glance

Operational Positions

Position Callsign Radio Name Frequency Voice Channel
Clearance Delivery ISP_DEL Long Island Clearance Delivery 121.850 ZNY_3F
Ground ISP_GND Long Island Ground 135.300 ZNY_3D
Tower ISP_TWR Long Island Tower 119.300 ZNY_3C
ATIS KISP_ATIS 120.720 KISP_ATIS
Position Callsign Radio Name Frequency Voice Channel
Ground BDR_GND Bridgeport Ground 121.750 ZNY_3J
Tower BDR_TWR Bridgeport Tower 120.900 ZNY_3G
ATIS KBDR_ATIS 119.150 KBDR_ATIS
Position Callsign Radio Name Frequency Voice Channel
Ground HVN_GND New Haven Ground 121.700 ZNY_3Q
Tower HVN_TWR New Haven Tower 124.800 ZNY_3P
ATIS KHVN_ATIS 133.650 KHVN_ATIS
Position Callsign Radio Name Frequency Voice Channel
Ground OXC_GND Oxford Ground 121.650 ZNY_3T
Tower OXC_TWR Oxford Tower 118.470 ZNY_3S
ATIS KOXC_ATIS 132.970 KOXC_ATIS
Position Callsign Radio Name Frequency Voice Channel
Ground FOK_GND Suffolk Ground 121.800 ZNY_3M
Tower FOK_TWR Suffolk Tower 125.300 ZNY_3L
Sector Callsign Frequency Voice Channel Tag Squawk Remarks
JFK Departure NY_KEN_DEP 135.900 ZNY_2J J 1550 — 1577 Primary Departure
CAMRN NY_CAM_APP 128.120 ZNY_2G G 1550 — 1577 Primary Approach
Final Vector NY_KFI_APP 132.400 ZNY_2A A 1550 — 1577
ROBER NY_RBR_APP 125.700 ZNY_2K K 1550 — 1577
JFK Satellite NY_ROS_APP 118.400 ZNY_2S S 1550 — 1577
Sector Callsign Frequency Voice Channel Tag Squawk Remarks
LGA Departure NY_LSO_DEP 120.400 ZNY_1L L 1150 — 1177 Primary Departure
HAARP NY_HRP_APP 120.800 ZNY_1V V 1150 — 1177 Primary Approach
Final Vector NY_LFI_APP 134.950 ZNY_1F F 1150 — 1177
NYACK NY_LNO_DEP 120.550 ZNY_1Y Y 1150 — 1177
EMPYR NY_EMP_APP 127.300 ZNY_1D D 1150 — 1177
NOBBI NY_NBI_APP 126.400 ZNY_1X X 1150 — 1177
Sector Callsign Frequency Voice Channel Tag Squawk Remarks
EWR Departure NY_NWK_DEP 119.200 ZNY_4N N 2350 — 2377 Primary Departure
Yardley NY_ARD_APP 128.550 ZNY_4P P 2350 — 2377 Primary Approach
Final Vector NY_NFI_APP 125.500 ZNY_4Q Q 2350 — 2377
North Arrival NY_NOA_APP 120.150 ZNY_4A A 2350 — 2377
ZEEBO NY_ZBO_APP 123.770 ZNY_4S S 2350 — 2377
METRO NY_MET_APP 132.800 ZNY_4H H 2350 — 2377
MUGZY NY_MGZ_APP 127.600 ZNY_4U U 2350 — 2377
Sector Callsign Frequency Voice Channel Tag Squawk Remarks
Islip NY_ISP_APP 120.050 ZNY_3H H 1640 — 1677 Primary TRACON
Calverton NY_CCC_APP 118.000 ZNY_3E E 1640 — 1677
SEALL NY_SEA_APP 133.100 ZNY_3R R 1640 — 1677
VIKKY NY_VIK_APP 128.620 ZNY_3Z Z 1640 — 1677
LOVES NY_LOV_APP 124.070 ZNY_3I I 1640 — 1677
BEDAS Low NY_BDL_APP 118.950 ZNY_3N N 1640 — 1677
BEADS High NY_BDH_APP 125.970 ZNY_3B B 1640 — 1677
Sector Callsign Frequency Voice Channel Tag Squawk Remarks
East NY_LBE_DEP 126.800 ZNY_56 6 2630 — 2677 Primary
West NY_LBW_DEP 120.850 ZNY_54 4 2630 — 2677
North NY_LBN_DEP 118.170 ZNY_52 2 2630 — 2677
South NY_LBS_DEP 124.750 ZNY_58 8 2630 — 2677
Catskill NY_CSK_APP 132.750 ZNY_5H 9 2630 — 2677


ATCT

Clearance Delivery

Position Frequency Code
NY_ISP_APP 120.05 3H
NY_CAM_APP 128.12 2G
NY_CTR 125.32 B4

The table on the right lists the common frequencies used as departure frequency by ISP 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 ISP, use UNICOM frequency (122.8).

Routing to certain airports in ZNY, ZDC and ZBW ARTCCs is precoordinated through letters of agreement (LOA). These routes have been added to the Preferred Route Database. Therefore, PRD must be referenced for all departures.

The initial altitude for IFR departures of all types is 3,000’. Some intra-TRACON flights have initial altitudes that are non-standard.

ISP4climbs.png

The only departure procedure for ISP is the LONGI# Departure (pronounced Long Island (Version #), such as Long Island Seven). You may also see it abbreviated as ISP#. It should always be assigned, unless the pilot indicates not possessing charts, in which case no departure procedure should be assigned and the pilot should be cleared to their destination via radar vectors to a proper ISP exit.

Because this departure procedure does not have published altitude restrictions, the phrase "Maintain (initial altitude)" must be included in the IFR clearance, as explained in FAA Order JO 7110.65 para 4-3-2.

PHRASEOLOGYCleared to (clearance limit), Long Island (version #) Departure, radar vectors (exit); then as filed. Maintain (initial altitude), expect (final altitude) one zero minutes after departure...

ISP is located inside Long Island Class Charlie Airspace. All VFR traffic must be issued a discrete squawk code.

See the VFR Operations document for detailed explanation of applicable VFR procedures.


Ground

Departure Sequencing
Exit Gate Exits
North COATE, NEION, HAAYS, GAYEL, SAX, HUO, CMK
East GREKI, MERIT, BDR
West LANNA, SBJ
South DPK, JFK, WHITE
ISP East MAD, CCC, HTO, BEADS, SARDI

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.
    PHRASEOLOGYRunway one fife right at bravo one, taxi via charlie, bravo, bravo one. Runway one fife right at bravo one intersection departure, four thousand and fifty feet available.
6 33L 24 15R
A (7,000’) B4 (5,150’) D (7,000’) W (5,150’)
A1 (6,000’) B3 (2,900’) 15L/33R (5,400’) B1 (4,050’)
W (4,950’) 15R/33L (4,500’) B2 (3,050’)
B (2,900’) B (4,000’)
Aircraft Movement
  1. As the taxiway system is simple, there are no pre-defined routings.
  2. Since there are no parallel taxiways, you may use each taxiway as a two-way road whereby aircraft may be taxied in the opposite direction on the same taxiway at the same time. When you do this, ensure that both aircraft are told to watch out for the other. This procedure is only available to single engine props during daylight hours as they are narrow enough to be able to fit two abreast.
  3. When the above is not available, hold departures on the ramp until the inbound aircraft is clear of the outbound aircraft. You may use conditional taxi instructions to accomplish this.

Tower

Releases
Releases from Islip are automatic unless:
  1. N90 requests individual releases
  2. The aircraft's flight is planned via GAYEL, HAAYS, NEION, COATE, DPK, CCC or V16
  3. The aircraft is going to another airport in the N90 TRACON
  4. The aircraft is departing an inactive runway
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 N90, 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 (normal operations)
Wind Speed Direction Configuration
Depart Land
0-4 Any 24 24
> 4 000-119 6 6
120-199 15L/R 15L/R
200-289 24 24
290-359 33L/R 33L/R
Notes
  1. Aircraft weighing more than 48,000lbs must not land, depart, taxi, or hold on runway 15L/33R.
  2. If possible, approve a pilot's request for a different runway, if it is more advantageous than the active runway.
Departure Heading
  • For IFR traffic that is flying the published departure procedure (LONGI#), do not assign a heading (this will override the departure procedure); instead, instruct the pilot to fly the procedure.
PHRASEOLOGYFly the Long Island (version #) departure, wind (wind), runway (runway), cleared for takeoff.
  • Aircraft not flying the standard departure procedure must be assigned runway heading, unless otherwise coordinated with the departure controller.
PHRASEOLOGYFly runway heading, wind (wind), runway (runway), cleared for takeoff.
Landing Runway Hold Short Runway Available Landing Distance
6 15R / 33L 4,200'
33R 6 / 24 3,000’
Land and Hold Short Operations
  1. Land and Hold Short Operations (LAHSO) may only be conducted for the runways specified in the table to the right.
  2. LAHSO is only authorized when there exits at least 3 miles of visibility and 1,000' ceiling, and no wind shear has been reported.
Missed Approach Procedures
  1. Missed approaches or go-arounds must be instructed to fly runway heading and be issued an altitude of 2,000' prior to release to the TRACON frequency.
  2. 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 judgement to determine whether to keep the aircraft in the pattern or not.
Additional Information
  1. In order to prevent increased workload on Departure Control, consider issuing missed approaches or go-arounds speed restrictions in accordance with FAA Order JO 7110.65.
  2. Unless the aircraft is kept in the pattern, coordinate with Departure Control as soon as possible and hand off when Local Control traffic is not a factor.
  3. Sound judgment must be exercised when dealing with go-arounds or missed approaches. Deviate as necessary from the following headings and altitudes if using them would compromise safety.
Airspace
  1. Class CHARLIE.
  2. The tower owns 1,500' and below within an 5 mile radius of the airport.
Departures
  1. All departures whose destinations are in the N90 TRACON should remain on the ground until an approval has been received from the destination tower that they are able to accept the aircraft into their airspace.
  2. Aircraft should be given the most expeditious way out of the airspace, which should be away from the IFR flow.
Flight Following
All aircraft should remain on the tower frequency unless the route of flight will or may impede the operations of N90 while operating inside the tower's delegated portion of the Class Charlie, or the aircraft will leave the tower's delegated portion of the Class Charlie.
Over-flights
Allow overflight aircraft to cross over the numbers of the active runway. Make sure to give traffic advisories as necessary.
Pattern Work
Use the following as a guide for pilots wanting to perform pattern work at ISP.
Runway Direction
6 Left
15L Left
15R Right
24 Right
33L Left
33R Right
NOTE: All props should be at 1,000’ and jets at 1,500’. Adjust these altitudes when necessary to avoid over-flights or normal IFR traffic flow.


TRACON

Callsign
  1. ISP TRACON positions are part of New York TRACON (N90).
  2. Each N90 Area except Islip has primary Approach and Departure sectors; Islip has a primary TRACON sector.
  3. Whenever a controller handles a departure, they shall use the radio name “New York Departure” when referring to themselves on frequency.
  4. Whenever a controller handles an arrival or enroute traffic, they shall use the radio name “New York Approach” when referring to themselves on frequency.
  5. 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 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.
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 shall 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.
Approval Requests (APREQs) for N90 Airports
Traffic departing from N90 Islip Area airports and landing at LGA, HPN, JFK, EWR, or TEB must be APREQ'd with both the area controlling the airport of intended landing as well as the control tower (or in case of events, the TMU).

The following are recommended procedures and shall only be used when traffic, weather, and workload permit their use.

  1. Islip Procedures
    1. Islip Turbojet departures should not be vectored off the DP until above 2,000'.
    2. Islip area arrival and enroute turbine aircraft should be kept as high as possible for as long as possible.
  2. Bridgeport Procedures
    1. Vector Runway 24 Jet departures left along Long Island Sound, then east of Bridgeport to exit fix.
    2. Vector Runway 29 Jet departures west of the General Electric Heliport (CT41), prior to turning right.
From Through To Route Altitude Hand-off Frequency Type
From ISP Area to N90 TRACON Areas
ISP, ISPE, ISPN LGA V475 40 1V 120.8 All
ISPE LGA INOFO TOMYE HEXEF (APREQ) 20 1V 120.8 Heli
ISP, ISPE, ISPN LGAN BDR R-288 40 1X 126.4 All
ISP, ISPE, ISPN LGAN EWR, EWRS V623 (CMK R-275 SAX R-060) 60 1Y 120.55 All
ISP, ISPE, ISPN LGAN LIBN GAYEL, HAYYS, NEION, COATE (Radar Vectors toward CMK) 60 1Y 120.55 <210kts
ISPN LGAN LIBW ELIOT, NEWEL, ZIMMZ, PARKE, LANNA, SAX, BIGGY (Radar Vectors towards CMK) 60 1Y 120.55 All
ISPN LGAN LIBH HUO (Radar Vectors towards CMK) 60 1Y 120.55 All
ISP, ISPE, ISPN LIBE GREKI, MERIT, BAYYS, BDR, SOARS
Gate track 280-330
100 56 126.8 All
ISP, ISPE, ISPN JFK GAYEL, HAAYS, NEION, COATE
Gate track 260-290
80 2J 135.9 >210kts
ISP, ISPE, ISPN JFK LIBS V16 DIXIE 60 2J 135.9 Singles, Twin
V16 (APREQ) 60 2J 135.9 Singles, Twin
ISP JFK DPK 30 2K 125.7 All
ISPE, ISPN JFK, FRG DPK 030-040 2J 125.7 All
From ISP Area to Center/Other
ISP ZBW HTO 100 135.8 All
ISP, ISPE ZBW BEADS 080-100 135.8 All
ISP, ISPN ZBW V39, V91, V487 070-090 128.1 All
ISP, ISPE, ISPN ZNY SARDI 60 128.3 All
ISP, ISPE PVD PVD HTO 050-090 Per LOA All
ISPN PVD PVD MAD 050-090 Per LOA All
ISPN Y90 Y90 MAD 050-090 123.95 All
V3, HFD, V419 050-090 123.95 All
BDR V229 050-090 123.95 All
BDR Vicinity D to BDL, BAF, CEF 050-090 123.95 All
ANGLR, SORRY (APREQ, Fix Est Required) 30 127.8 Heli
OXC Y90 ZBW JUDDS 50 123.95 All
Through N90 TRACON ISP Area
LGA ISPN Y90 BDR R-248 BDR 50 3Z 128.62 Heli
TROGS, COVVE, KINKK (APREQ) 30 3I 124.07 Heli
BDR
Gate track 060-080
070-080 3R 133.1 All
LGA ISPN JFK, FRG BDR CCC DPK 50 3Z 128.62 All Non RNAV
WRENN PUGGS CCC 50 3Z 128.62 All RNAV
LGAN ISPN JFK, FRG BREZY CMK V374 DENNA BDR V44 DPK 50 3I 124.07 All
LGAN ISPN CMK V419, V3 (APREQ) 50 3I 124.07 All
CMK BETHA HTO BEADS 070-090 3I 124.07 All
CMK
Gate track 060-130
070-090 3R 133.1 All
JFK ISPN BDR
Gate track 040-080
070-080 3R 133.1 All
JFK ISPN LGAN BDR R-288 30 3I 124.07 All
JFK ISPN LGAN, EWR, EWRS V623 (CMK R-275 SAX R-060) 30 3I 124.07 All
FRG (South) ISPN CCC BEADS SWL (APREQ)
Multi engine Gate
40 3H 120.05 Jets
FRG (North) ISPN CCC BEADS SWL (APREQ) DPK 50 3H 120.05 Jets
Area Airport List
Area Airport Codes
LGA LGA
LGAN HPN, DXR
JFK JFK, FRG
EWR EWR
EWRN TEB, MMU, CDW, FWN, 12N, 13N, 4N1, N05, N07, 1N7, 3N5
EWRS 47N, 39N, N51, SMQ, LDJ
ISP ISP, HWV, 23N
ISPE FOK, HTO, MTP, 03NY, 1N2, 21N, 87N
ISPN BDR, HVN, JSD, OXC, SNC, 42B
LIBH SWF, POU, MGJ, 44N, 46N, N69, N82, 06N, MSV, 20N, N89
From Through To Route Altitude Hand-off Frequency Type
From Inside N90 TRACON Areas
LGA ISP CCC R-285 50 3Z 128.62 All
LGA ISP, ISPN, ISPE BDR R-248 BDR 50 3Z 129.62 All
LGA ISPN BDR R-248 BDR (APREQ) 30 3I 124.07 Heli
LGA ISPE LEAHA HEXEF TOMYE (APREQ) 30 3I 124.07 Heli
LGA ISP BDR CCC (APREQ) 50 3I 124.07 All Non RNAV
LGA ISP WRENN PUGGS CCC 50 3I 124.07 All RNAV
LGAN ISP JFK, FRG BREZY CMK V374 CMK DENNA BDR CCC 50 3I 124.07 All
LGAN ISP, ISPN, ISPE CMK V374 50 3I 124.07 All
LGAN ISPN RYMES BDR (APREQ) 50 3I 124.07 Heli
JFK ISPE Gate track 090 30 3H 120.05 Single
Arrival
Gate track 040-085
40 3H 120.05 Jets, Turbo, Twin
JFK ISPN B229 BDR 30 3I 124.07 All
LIBH ISP, ISPE, ISPN, JFK LOVES 50 3R 133.1 All
From Outside N90 TRACON Areas
ZBW ISP SARDI 70 3H 120.05 All
ZBW ISPE RICED 70 3B 125.97 All
ZBW ISPE LGAN HTO 110 3B 125.97 Jets
RICED 070-090 3B 125.97 Props
DPK 150 3Z 128.62 All
ZBW ISPE ISPN RICED 070-090 3B 125.97 All
HOFFI 110 3B 125.97 All
ZBW ISPE PVD RICED 070-110 3B 125.97 All
ZBW ISPN LOVES 60 3R 133.1 All
ZBW ISPN ISPE, JFK LOVES 60 3R 133.1 Props
PVD ISPE V16 CREAM 040-080 3B 125.97 All
HTO 060-080 3B 125.97 All
HTO 40 3N 118.95 All
PVD ISP BOROS 100 3B 125.97 Jets
PVD ISPE JFK CCC, HTO 40 3B 125.97 Props
HTO 060-100 3B 125.97 All
PVD ISPE ZBW, ZNY HTO 060-100 3B 125.97 Props
Y90 ISPN SEALL, YALER 40 3I 124.07 All
Y90 ISPN EWR SEALL V188 60 3R 133.1 Props
Y90 ISPN LGAN MAD 060-080 3Z 128.62 Props
Y90 ISPN LGA V229 40 3I 124.07 Heli
Y90 ISPN BEADS MAD BEADS 080-100 3Z 128.62 Props
Area Airport List
Area Airport Codes
LGA LGA
LGAN HPN, DXR
JFK JFK, FRG
EWR EWR
EWRN TEB, MMU, CDW, FWN, 12N, 13N, 4N1, N05, N07, 1N7, 3N5
EWRS 47N, 39N, N51, SMQ, LDJ
ISP ISP, HWV, 23N
ISPE FOK, HTO, MTP, 03NY, 1N2, 21N, 87N
ISPN BDR, HVN, JSD, OXC, SNC, 42B
LIBH SWF, POU, MGJ, 44N, 46N, N69, N82, 06N, MSV, 20N, N89
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
  1. 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.
  2. Missed Approach Procedures
    1. ISP Tower is authorized to clear aircraft for a visual approach in accordance with FAA Order JO 7110.65 para 7-4-3 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.
  3. 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
  1. 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.
  2. 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.
  1. 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.
  2. 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. 2 — July 14, 2019
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 Jan 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.
Kennedy Area to Islip Area
Islip Area to Kennedy Area
Kennedy Area Airspace Released to Islip Area
  1. ROBER Airspace for ISP Eastbound Departures
    1. This procedure must only apply if coordination has been effected between the ISP Area, JFK Area, and ZBW ARTCC.
    2. Once the necessary coordination has been accomplished, the ISP Area can climb eastbound departures to 11,000’ within JFK blocks #21 (no further south than the Fire Island shoreline), #22, #23, and #25. This corresponds to ISP blocks #7, #9 (no further south then the Fire Island shoreline), and #15.
      • JFK Area (ROBER) is responsible for separation between coordinated ISP departures and other aircraft under ROBER control.
      • ISP Area must verbally coordinate with JFK Area (ROBER) prior to course reversal in the blocks aforementioned.
Letter of Agreement
LaGuardia TRACON (LGA) & Islip TRACON (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 LaGuardia TRACON (LGA) and Islip TRACON (ISP).
Cancellation
LaGuardia TRACON (LGA) and Islip TRACON (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.
LaGuardia Area to Islip Area
  1. Departures from LGA Area to ISP Area
    1. 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 degrees, and ensure aircraft are at 7,000' or 8,000' 1.5NM prior to the LGA/ISP boundary.
    2. LGAN 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 degrees, and ensure aircraft are at 7,000' or 9,000' 1.5NM prior to the LGA/ISP boundary.
    3. ISP has control for turns not to exceed headings needed to transition the departure gates.
  2. ISP VIKKY position (3Z) has control on contact of traffic on:
    1. CCC R-285 for northeast-bound turns not to exceed BDR R-218.
    2. BDR R-248 for eastbound turns.
  3. ISP SEALL position (3R) has control for:
    1. Descent to 3,000', 1.5NM west of the boundary for traffic routed CMK V374.
    2. Climbs at the line 5NM east of CMK for traffic vectored through the LGAN to ISP Gate at 7,000'
  4. LGA Tower 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 the ISP LOVES position (3I) at 3,000'.
    Note: If the route cannot be approved, the fixed wing route via BDR must be issued.
Islip Area to LaGuardia Area
  1. 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.
  2. LGAN arrivals at 4,000' via BDR R-288 may be assigned 3,000' without coordination under the following conditions:
    1. Prior to LGA accepting a handoff and
    2. Only when an in-trail flow at 4,000' is not feasible due to speed differences.
  3. 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 the LGA Area, NOBBI position (1X) at 2,000’.
  4. 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.
    1. ISP Area:
      1. 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.
      2. 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.
      3. 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/2 NM from LGA/ISP boundary.
    2. LGA Area:
      1. Must clear aircraft to a fix for the appropriate transition.
      2. May issue crossing altitudes at fixes other than those noted in the procedure.
      3. 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
  1. 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
  1. 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
  1. 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.
  2. After release of OXC Block to ISP, LIBH must separate aircraft from the block boundary by three miles and utilize vertical separation.


Departure and Approach


Appendix

Changelog

Change Date Description
CHG1 24 Aug 2003 Initial release.
CHG2 11 Aug 2011 MAJOR REVISION. See a full list of updates on the ZNY ARTCC forum.
CHG3 9 Mar 2017 Converted to Wiki format.
CHG4 26 Feb 2018 Updated departure frequencies to the correct frequency for NY CAM APP - 128.12, also changed NY_KND_CTR to NY_CTR to avoid confusion.
CHG5 14 Jul 2019 Removed all references to runway 10/28. Updated "Common Amendments" section. Updated N90 - ISP ATCT LOA to include arrival scratchpad entries. Other minor stylistic changes.