HVN SOP

New York ARTCC

Standard Operating Procedure — Tweed-New Haven Airport (HVN)

Rev. 6 — Revised: 2026-01-13

Area at a glance

ICAO Code	Airport Name	Airspace
KHVN	Tweed-New Haven	D

Purpose

This document prescribes the procedures to be utilized for providing air traffic control services at New Haven Air Traffic Control Tower (ATCT). 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
Ground Control	HVN_GND	New Haven Ground	121.700	3Q
Local Control	HVN_TWR	New Haven Tower	124.800	3P
AtIS	KHVN_ATIS		133.650

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
Calverton	ISP_N_APP	120.050	3N	Primary TRACON (ISP_APP if combined)
Islip	ISP_H_APP	134.550	3H	3N
SEALL	ISP_R_APP	133.100	3R	3N
VIKKY	ISP_O_APP	128.625	3O	3N
LOVES	ISP_Z_APP	124.075	3Z	3N
BEADS Low	ISP_I_APP	118.950	3I	3N
BEADS High	ISP_B_APP	125.975	3B	3N

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	SBJ237
	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	COL204

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.

Position	Frequency	Code
ISP_Z_APP	124.075	3Z
ISP_APP	120.050	3N
JFK_K_APP	125.700	2K
NY_CTR	125.325	N56

The table lists the common frequencies used as departure frequency by FOK 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.

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 pre-coordinated through letters of agreement (LOA). These routes have been added to the Preferred Route Database (PRD). Therefore, PRD must be referenced for all departures.

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

BHAVN#

The only departure procedure for HVN is the BHAVN# Departure (pronounced Bridgehaven (Version #), such as Bridgehaven One). 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 HVN 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 § 4-3-2.

PHRASEOLOGY
CLEARED TO (clearance limit), Bridgehaven (version #) DEPARTURE, RADAR VECTORS (exit); THEN AS FILED. MAINTAIN (initial altitude), EXPECT (final altitude) ONE ZERO MINUTES AFTER DEPARTURE...

New Haven is a Class Delta airport. All VFR traffic must maintain two-way radio communication. 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, SOARS, BDR
West	BIGGY, LANNA, PARKE, ZIMMZ, ELIOT, NEWEL, BWZ, 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

• 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.
• Transfer of runway ownership, between Ground Control and Local Control, shall be accomplished verbally (or textually).
• Ground Control is authorized to cross all active runways with coordination with Local Control.

Aircraft Movement

• As the taxiway system is simple, there are no pre-defined routings.
• 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.
• 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.

Intersection Departures and Usable Runway Lengths

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

PHRASEOLOGY
RUNWAY (number) AT (taxiway designator), TAXI VIA (instructions). RUNWAY (number) AT (taxiway designator) INTERSECTION DEPARTURE (remaining length) FEET AVAILABLE.

EXAMPLE
"Runway two zero at foxtrot, taxi via foxtrot. Runway two zero at foxtrot intersection departure, four thousand nine hundred fifty feet available."

2	20
B (4750')	F (4950')
E (3350')

Local Control

Tower Procedures

Releases

• Releases from New Haven are requested per aircraft, unless N90 permits blanket releases.
• In order to depart New Haven under an IFR flight plan, TRACON must issue a release for departure. 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. Only use timed separation if the pilot requests it.

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 must 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

Wind Speed	Direction	Depart	Land
Any	Any (IMC)	2	2
Any	Any (VMC)	20	20

• For IFR traffic that is flying the published departure procedure (BHAVN#), do not assign a heading (this will override the departure procedure); instead, instruct the pilot to fly the procedure.

PHRASEOLOGY
Fly the Bridgehaven (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.

PHRASEOLOGY
Fly runway heading, wind (wind), runway (runway), cleared for takeoff.

Missed Approach Procedures

• Missed approaches or go-arounds must be instructed to fly the published missed approach procedure prior to release to the TRACON frequency.
• 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

• 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.
• 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.
• 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 DELTA.
• The tower owns 1,500' and below within an 4.5 mile radius of the airport from heading 360 clockwise to heading 260, and 6.5 mile radius from heading 261 clockwise to heading 359.

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.

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 Delta, or the aircraft will leave the tower's delegated portion of the Class Delta.

Over-flights

Allow the aircraft to cross over the numbers of the active runway. Make sure to give traffic advisories to both aircraft.

Pattern Work

Runway	Direction
2	Left
20	Left

Use the following as a guide for pilots wanting to perform pattern work at FOK.

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

TRACON services for New Haven are provided by the ISP sector of N90 TRACON.