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

ISP SOP

From New York ARTCC
More actions
New York ARTCC
Standard Operating Procedure — Long Island MacArthur ATCT and TRACON

Rev. 6 — Revised: 2026-06-24

Area at a glance

ICAO Code Airport Name Airspace
KISP Long Island MacArthur C
KBDR Bridgeport/Igor I. Sikorsky D
KHVN Tweed-New Haven D
KOXC Waterbury-Oxford D
KFOK Suffolk County D 
       Uncontrolled Fields
       [Show]


Purpose
This document prescribes the procedures to be utilized for providing air traffic control services at the Long Island Air Traffic Control Tower (ATCT) and any of the positions within the Islip Area of New York TRACON (N90) and the airports it serves. The procedures described herein are supplemental to the New York ARTCC Standard Operating Procedures and FAA Order JO 7110.65.
Distribution
This order is distributed to all New York ARTCC personnel.
Procedural Deviations
Exceptional or unusual requirements may dictate procedural deviations or supplementary procedures to this order. A situation may arise that is not adequately covered herein; in such an event use good judgment to adequately resolve the problem.



Operational Positions

Position Callsign Radio Name Frequency Identifier
Clearance Delivery ISP_DEL Long Island Clearance Delivery 121.850 3F
Ground ISP_GND Long Island Ground 135.300 3D
Tower ISP_TWR Long Island Tower 119.300 3C
ATIS KISP_ATIS 120.720
Position Callsign Radio Name Frequency Identifier
Ground BDR_GND Bridgeport Ground 121.750 3J
Tower BDR_TWR Bridgeport Tower 120.900 3G
ATIS KBDR_ATIS 119.150
Position Callsign Radio Name Frequency Identifier
Ground HVN_GND New Haven Ground 121.700 3Q
Tower HVN_TWR New Haven Tower 124.800 3P
ATIS KHVN_ATIS 133.650
Position Callsign Radio Name Frequency Identifier
Ground OXC_GND Oxford Ground 121.650 3T
Tower OXC_TWR Oxford Tower 118.470 3S
ATIS KOXC_ATIS 132.970
Position Callsign Radio Name Frequency Identifier
Ground FOK_GND Suffolk Ground 121.800 3M
Tower FOK_TWR Suffolk Tower 125.300 3L

Sector Callsign Frequency Identifier Combined Sector
LaGuardia Departure LGA_DEP 120.400 1L Primary Departure
HAARP LGA_V_APP 120.800 1V Primary Approach (LGA_APP when combined)
Final Vector LGA_F_APP 134.900 1F 1V
NYACK LGA_Y_DEP 120.550 1Y 1X (1L if NOBBI is not covered)
EMPYR LGA_D_APP 127.300 1D 1V
NOBBI LGA_X_APP 126.400 1X 1V
Sector Callsign Frequency Identifier Combined Sector
Final Vector JFK_A_APP 132.400 2A 2K
CAMRN JFK_G_APP 128.125 2G 2K
Kennedy Departure JFK_DEP 135.900 2J Primary Departure
ROBER JFK_K_APP 125.700 2K Primary Approach (JFK_APP when combined)
Kennedy Satellite JFK_M_APP 118.400 2M 2K
Sector Callsign Frequency Identifier Combined Sector
Islip ISP_H_APP 134.550 3H Primary TRACON
Calverton ISP_N_APP 120.050 3N 3H
SEALL ISP_R_APP 133.100 3R 3H
VIKKY ISP_O_APP 128.625 3O 3H
LOVES ISP_Z_APP 124.075 3Z 3H
BEADS Low ISP_I_APP 118.950 3I 3H
BEADS High ISP_B_APP 125.975 3B 3H
Sector Callsign Frequency Identifier Combined Sector
Newark Departure EWR_DEP 119.200 4N Primary Departure
Yardley EWR_P_APP 128.550 4P Primary Approach (EWR_APP when combined)
Final Vector 22 EWR_M_APP 125.500 4M 4P
Final Vector 4 EWR_Q_APP 125.500 4Q 4P
North Arrival EWR_A_APP 120.150 4A 4P
MUGZY EWR_U_APP 127.600 4U 4P
ZEEBO EWR_S_APP 123.775 4S 4U
METRO EWR_H_APP 132.800 4H 4U
Sector Callsign Frequency Identifier Combined Sector
East NY_LE_DEP 126.800 5E 5W
West NY_LW_DEP 120.850 5W Primary TRACON (NY_L_APP when combined and covering Catskill)
North NY_LN_DEP 118.175 5T 5W
South NY_LS_DEP 124.750 5S 5W
Catskill SWF_APP 132.750 5H 5W

ATCT

Clearance Delivery

Exit Gate Exit Scratchpad Radial
West SBJ SBJ
BIGGY** BIG SBJ 237
LANNA** LAN PTW 059
PARKE** PAR BWZ 250
ZIMMZ** ZIM RNAV only
ELIOT** ELI SAX 252
NEWEL** NWL SAX 264
BWZ** BWZ
North SAX SAX
COATE COA SAX 311
NEION NEI LGA 322
HAAYS HAY HUO 145
GAYEL GAY DPK 320
HUO HUO
CMK CMK
East GREKI GRE CMK 057
SOARS** SOA CMK 057
MERIT MER LGA 055
BDR BDR
ISP East CCC CCC
MAD MAD
HTO HTO
BEADS BEA HTO 236
South DPK DPK
JFK JFK
WHITE WHI COL 204


Notes
  1. While it is recommended that aircraft be rerouted to comply with turbojet and props only departure gates, it is not required.
  2. ELIOT is authorized for all aircraft types, but restricted to a final alitude of 14,000 or 16,000
  3. NEWEL is authorized for jet aircraft requesting a final altitude of FL180 and above.
  4. ZIMMZ is authorized for all aircraft types but restricted to a final altitude of FL180 and above.
  5. "** Satellites Only Exit (ISPN, ISPE)" means departures from the following airports cannot be assigned those exits: KISP, KHWV, 23N
Position Frequency Code
ISP_H_APP 134.550 3H
JFK_G_APP 128.125 2G
NY_CTR 125.325 N56

The table 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).

Airway Join
L453 BEADS V139 SHERL BLUUU Y488 HOBOH PAEPR L453
L454 BEADS V139 SHERL OWENZ L454
L455 BEADS V139 SHERL OWENZ L455
L456 BEADS V139 SHERL BLUUU Y492 SQUAD DARUX L456
L457 BEADS V139 SHERL OWENZ L457
L459 BEADS V139 SHERL OWENZ L459
L461 BEADS V139 SHERL BLUUU Y487 KINGG KINER L461
L462 BEADS V139 SHERL BLUUU Y487 ISLES KAYYT L462
J6 BEADS V139 SARDI RBV Q430 SAAME J6
J37 GREKI JUDDS ALB J37
J48 BEADS V139 SARDI RBV Q430 BYRDD J48
J60 COATE Q436 DGRAF J49 PSB J60
J64 COATE Q436 DGRAF J49 PSB EWC J64
J75 South: BEADS V139 SARDI RBV Q430 COPES J75
J79 South: WHITE J209 VILLS J79
J80 South: BEADS V139 SARDI RBV Q430 AIR J80
J95 GAYEL J95
J174 BEADS EMJAY J174
J209 WHITE J209
J222 North: GREKI JUDDS CAM
J223 NEION J223
J230 BEADS V139 SARDI RBV J230
Q42 BEADS V139 SARDI RBV Q430 SAAME BRNAN Q42
Q75 North: GREKI Q75
South: BEADS V139 SARDI RBV Q430 COPES Q75
Q430 BEADS V139 SARDI RBV Q430
Q436 COATE Q436
Q480 South: BEADS V139 SARDI RBV Q430 BEETS Q480
Q818 GAYEL Q818
Y483/Y487/Y488/
Y489/Y490/Y492 		BEADS V139 SHERL BLUUU Y4##
Filed Exit Amendment
ACK HTO V46 ACK
BOUNO BEADS V139 SHERL
BYRDD BEADS V139 SARDI RBV Q430 BYRDD
CYN WHITE CYN
EMJAY BEADS EMJAY
ETX SAX V249 SBJ V30 ETX
FJC SAX V249 SBJ V6 FJC
GEDIC BEADS V139 SHERL GEDIC
HFD MERIT HFD
HOFFI BEADS
IGN BDR PWL
JOANI J79 WHITE J209 VILLS J79
JUDDS GREKI JUDDS
LAURN BEADS V139 SARDI RBV
LINND BEADS V139 SHERL LINND
LLUND GREKI
MARIO MERIT
NEWES MERIT
OWENZ BEADS V139 SHERL OWENZ
PACER MERIT
PNE BEADS V139 SARDI RBV PNE
PUT MERIT HFD PUT
RAALF MERIT
SARDI BEADS V139 SARDI
SHERL BEADS V139 SHERL
STW SAX
VILLS J209 WHITE J209

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.

LONGI#

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 Order JO 7110.65 para 4-3-2

PHRASEOLOGY
Cleared 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 Class Charlie VFR Operations

Operation Departure Runway Direction Departure Instructions Altitude Departure Frequency
VFR w/ Flight Following (Jets mandatory FF) All All Fly runway heading 2,000' 120.050 (NY Departure)
VFR w/o Flight Following All All Fly runway heading 1,400' 119.300 (Long Island Tower)

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

PHRASEOLOGY- ON DEPARTURE (departure instructions), MAINTAIN VFR AT OR BELOW (altitude), DEPARTURE FREQUENCY (frequency), SQUAWK (code).

Ground

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

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.
  3. PHRASEOLOGY
    Runway 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

  1. Releases from Islip are automatic for aircraft departing through BEADS
  2. Any aircraft not departing through BEADS must be issued a release for departure by TRACON. Departure restrictions such as release times and clearance void times are necessary to separate departures from other traffic in the airspace or to regulate the departure flow. Through land line communications, tower will obtain a release from TRACON for a specific flight after which tower can then issue departure instructions and takeoff clearance.
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 § 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 that will not be receiving flight following after they exit the inner 5NM radius of the Class Charlie will be radar identified by Local Control. For VFR aircraft receiving continuous flight following after departure, Local Control will handoff to TRACON who will perform the radar identification.
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#), there is no need to restate the initial heading or departure procedure.
PHRASEOLOGY — 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.
PHRASEOLOGY — Fly 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 § 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

  • Class CHARLIE.
  • The tower owns 1,500' and below within a 5 mile radius of the airport.
Departures
  • 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.
  • Aircraft should be given the most expeditious way out of the airspace, which should be away from the IFR flow.
  • Aircraft looking for flight following beyond the inner 5NM radius will be radar identified by the TRACON.
  • Aircraft looking to terminate radar services beyond the inner 5NM radius will be radar identified by Local Control.
  • Once outside the inner boundary, aircraft flying at or below 1,400' should be told "RADAR SERVICES TERMINATED, FREQUENCY CHANGE APPROVED, SQUAWK VFR."
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).

Area Unconditional Conditional
1 5,000'-4,000'
2 9,000'-4,000'
3 9,000' and below
4 10,000' and below
5 2,000' and below
6 5,000' and below
7 8,000' and below
8 6,000'-4,000'
9 4,000' and below
10 3,000' and below 2,000' and below (JFK LOA)
11 2,500' and below / 14,000' Note: IFR aircraft must operate within this airspace at or below 2,000'
12 11,000' and below
13 9,000' and below
14 14,000' and below
15 6,000' and below
16 14,000'-11,000' and 8,000' and below
17 6,000' and below
18 8,000' and below
19 6,000' and below
20 5,000' and below / 7,000' and 9,000'


Notes:

  • This map is a good reference tool for enroute traffic with cruise altitudes within the ceiling of the ISP sector's airspace
  • For higher level enroute traffic, and any departures transitioning through the LGA and JFK sectors of N90, or center airspace, the Departure Chart is a better reference tool

}}

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.
  1. 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 LIBE GREKI, SOARS, MERIT
ISP East Departure Gate track 280-330 		100 56 (LIBE) 126.8 All
ISP, ISPE, ISPN LIBE BDR
ISP East Departure Gate track 280-330 		100 56 (LIBE) 126.8 Cruise >= 110
ISP, ISPE, ISPN JFK LIBE COATE, NEION, HAAYS, GAYEL
ISP to JFK Gate track 260-290 		080 2J (KEN) 135.9 Speed >= 210 kts
ISP, ISPE, ISPN LGAN LIBN, LIBH COATE, NEION, HAAYS, HUO, GAYEL
Vector towards CMK 		060 1Y (LNO) 120.55 Speed < 210 kts
ISP, ISPE, ISPN LGAN BDR R-288
 040 1X (NOBBI) 126.4 All
ISP, ISPE, ISPN LGAN CMK
Vector towards CMK 		040 1X (NOBBI) 126.4 All
ISP, ISPE, ISPN LGA HTO NESSI LGA 040 1V (HRP) 120.8 All
ISPE, ISPN LGAN SAX, BWZ, SBJ, NEWEL, ELIOT, ZIMMZ, PARKE, LANNA, BIGGY
Vector towards CMK 		060 1Y (LNO) 120.55 All
ISP JFK SAX
ISP to JFK Gate Track 260-290 		060 2J (KEN) 135.9 All
ISP, ISPE, ISPN JFK V16 060 2J (KEN) 135.9 All
ISP, ISPE, ISPN JFK DPK (not V16) 030 2K (ROBER) 125.7 All
ISP, ISPE, ISPN JFK LIBS WHITE, JFK
ISP to JFK Gate Track 260-290 		030 2K (ROBER) 125.7 All
ISP, ISPE, ISPN LIBH Northbound: V33, V44, V91, V487 AOB 050 5H (CSK) 132.75 Cruise <= 050
From ISP Area to Y90 (BDL) or PVD TRACONs
ISP, ISPE, ISPN PVD Eastbound: V16, V34, V46, V139, V188, V268, V308, V374, V451, V475 AOB 090 PA (PVD) 123.67 Cruise <= 100
ISP, ISPE, ISPN BDL Eastbound: V1, V3, V99, V229, V419 AOB 090 BB (BDL) 123.95 Cruise <= 100
From ISP Area to Center
ISP, ISPE, ISPN ZBW Northbound: V33, V44, V91, V487 060-100 B17 (ACK Area) 133.45 Cruise >= 060
ISP, ISPE, ISPN ZBW BEADS, Westbound: V139, V268, V308 080-100 B17 (ACK Area) 133.45 All
ISP, ISPE, ISPN ZBW BDR, MAD, HTO 080-100 B17 (ACK Area) 133.45 Cruise >= 110
Transitioning STARs through ISP Area
ZBW ISP LGAN BOUNO# 040 1X (NOBBI) 126.4 All
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, JPX, 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, JPX, 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 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.
  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. 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

  1. 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.
  2. 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.
  3. JFK Area has control on contact for turns not to exceed headings needed to transition the gate.
  4. Traffic below 6,000' will be pointed out to ROBER.

Single Engine Aircraft from/through the ISP Area

  1. 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.
  2. Traffic below 6,000' will be pointed out by ISP to ROBER.

Departures from/through the JFK Area over BDR

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

ISP and ISP East Single Engine Arrivals

  1. Use the single engine arrival gate for ISP and ISP East single engine arrivals.
  2. 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

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

FRG BEADS departures

  1. 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

  1. 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

  1. 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

  1. The following procedures may be applied for JFK Southeast Arrivals
  2. JFK area shall provide an automated point out of JFK arrivals to the VIKKY position.
  3. 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'.
  4. 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

  1. The following procedures may be applied for ISP Eastbound Departures
  2. ISP Area shall provide an automated point out of ISP departures to the JFK ROBER position.
  3. 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.
  4. 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.
  5. 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

  1. The following procedures may be applied to JFK and FRG ROBER arrivals.
  2. JFK area shall provide an automated point out of JFK and FRG arrivals to the ISLIP position
  3. 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'.
  4. 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

  1. 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.
  2. 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.
  3. 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

  1. The following procedures may be applied for HPN arrivals over BOUNO
  2. ISP Area shall provide an automated point out of BOUNO arrivals to the JFK ROBER position.
  3. Acceptance of the point out constitutes approval for the aircraft to transition the JFK Areas 24, eastbound and descend below 11,000'.
  4. 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

  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.
CHG6 22 May 2020 Amended the IFR Squawk Code Range.
CHG7 17 November 2020 Update IFR releases information for tower. Added neighboring TRACONs guide. Updated "Departure Chart." Updated "Common Amendments" table. SARDI was removed as a valid exit, aircraft must be routed via BEADS V139 SARDI instead.
CHG8 19 May 2023 Updated VFR procedures.
CHG9 XX YYY 2023 Update identifier for East Hampton airport from KHTO to KJPX.
Retrieved from "https://wiki.vzny.org/index.php?title=ISP_SOP&oldid=1519"