Toggle menu
7
505
3
1.1K
New York ARTCC
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

POU SOP

From New York ARTCC
Revision as of 00:01, 27 March 2026 by Admin (talk | contribs) (1 revision imported: Template migration from wiki-dev )
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
New York ARTCC
Standard Operating Procedure — POU

Rev. 7 — Revised: 2026-03-27

Area at a glance

ICAO Code Airport Name Airspace
KPOU Dutchess County D
Purpose
This document prescribes the procedures to be utilized for providing air traffic control services at the Allentown Air Traffic Control Tower (ATCT) and any of the positions within the Allentown TRACON 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
Ground POU_GND Dutchess County Ground 121.800 5D
Tower POU_TWR Dutches County Tower 124.000 5C
ATIS KPOU_ATIS 126.750

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
North / Northeast IGN IGN
PWL PWL
STUBY STU PWL 055
HIDAL HID PWL 021
East HFD HFD
LOVES LOV PWL 172
BRISS BRI PWL 111
MOONI MOO IGN 107
South / Southeast COL COL
VALRE VAL IGN 203
WHITE WHI COL 204
Southwest SBJ SBJ
LANNA LAN SBJ 274
BIGGY BIG SBJ 237
COATE COA HUO 207
West / Northwest HUO HUO
HNK HNK
WEARD WEA HUO 019


Notes
  1. HUO, COATE, VALRE, HIDAL, BRISS and LOVES can only be used for tower enroute control (TEC) routes at or below 5,000'.
  2. HFD can only be used for traffic with cruise altitude of 9,000' or below.
  3. WHITE can only be used for traffic with cruise altitude of 10,000' or above.
Position Frequency Code
SWF_APP 132.750 59
NY_CTR 125.325 N56

The table lists the common frequencies used as departure frequency by POU 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
J6 North: STUBY V487 CANAN V130 ALB J6 Q75
South: LANNA V405 PTW V143 LRP J6
J37 STUBY V487 CANAN V130 ALB J37
J42 North: PWL V34 MOONI V58 HFD J42
South: WHITE J209 CYN J150 OOD J42
J48 LANNA J48
J60 WEARD V167 HNK J49 PSB J60
J70 WEARD V106 LHY V93 LVZ J70
J75 North: PWL V34 MOONI V58 JUDDS J75
South: BIGGY J75
J77 North: PWL V106 BAF J77
South: LANNA J48 PTW J77
J79 East: PWL V34 MOONI V91 CCC HOFFI J79
South: WHITE J209 VILLS J79
J80 North: PWL V106 BAF J77
South: LANNA V30 ETX J80
J95 WEARD V167 HNK CFB J95
J106 WEARD V106 LHY V93 LVZ J106
J146 WEARD LAAYK LVZ V106 DIANO MIP J146
J209 WHITE J209
J222 North: STUBY V487 CAM J222
South: (next airway)
J223 WEARD…CORDS J132
J225 PWL V34 MOONI V167 PVD J225
Filed Exit Amendment
ALB PWL PWL
ARD BIGGY
BAF PWL BAF
BDL PWL BDL
BDR PWL BDR
COL WHITE
CTR PWL CTR
DNY WEARD DNY
ETX LANNA ETX
FJC LANNA FJC
HVN PWL HVN
JOANI WHITE
LAURN WHITE
MAD PWL MAD
PUT PWL PUT
RBV West: BIGGY RBV
South: WHITE RBV
SAX COATE
STW COATE STW

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. Therefore, PRD must be referenced for all departures.

The initial altitude for IFR departures is 3000'.

DUCHS#

DUCHS# Departure (pronounced Dutchess (Version #), such as Dutchess Eight) is the standard departure procedure for POU departures. 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 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.

Ground Control

Departure Sequencing
Exit Gate Exits
North / Northeast HIDAL, STUBY, IGN, PWL
East BRISS, HFD, LOVES
South / Southeast COL, VALRE, WHITE
Southwest BIGGY, COATE, LANNA, SBJ
West / Northwest HNK, HUO, WEARD

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.
Taxi Routes
  1. As the taxiway system is simple, there are no predefined 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.

Local Control

Tower Procedures

Releases

Releases from Dutchess County are on a per aircraft request basis unless blanket release is coordinated.
Separation
The standard departure separation technique to be used is anticipated radar separation. Only use timed separation if the pilot requests it.
Radar (RACD)
  1. This tower uses a DBRITE display and is NOT certified for any approach operations.
  2. This tower shall NOT radar identify departing IFR aircraft and shall instruct a departing aircraft to contact Departure Control once they appear to be clear of any traffic. It is imperative that tower controllers observe departing traffic turning towards the assigned climb or heading before handing off.
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 Depart Land
0-4 Any 6 6
5-15 330-149 6 6
150-329 24 24
>15 015-059 6, 33 6, 33
060-149 6, 15 6, 15
150-194 15, 24 15, 24
195-329 24, 33 24, 33
330-014 33, 6 33, 6

Departure Heading (IFR)

  • For IFR traffic that is flying a published climb, do not assign a heading (this will override the climb); instead, instruct the pilot to fly the departure procedure..
PHRASEOLOGY
Fly the DUCHS# departure, wind (wind), Runway (runway), cleared for takeoff.
  • For IFR traffic that is not flying a published climb, departure heading will be based on the table.
Runway Heading
6 Runway Heading
15 Left turn to 360
24 Runway Heading
33 290
Missed Approach
  • Missed approaches or go-arounds shall fly runway heading or track the localizer until reaching the departure end of the runway, then be issued a heading in accordance with the table below unless the controller determines that it would be advantageous to delay or initiate a turn early.
Runway Heading Altitude
6 060 2800’
15 060 2800'
24 040 2900’
33 040 2900’
  • Separation must be based on altitude initially during all missed approaches or go-arounds. Prior to issuing a climb to 2900’, interval altitudes such as 1900’ may be utilized to prevent converging targets from losing separation.
  • 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.
  • 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.
  • The following table indicates the heading and altitude that need to be assigned to a missed approach or go-around prior to release to Departure Control frequency.

VFR Procedures

Airspace

  • Class Class Delta.
  • The tower owns 2700' and below within a 4 mile radius of the airport.
Radar
  • This Tower uses a DBRITE display and is NOT certified for approach operations
  • Tower MAY radar identify aircraft if necessary for identification and separation/sequencing in the Class D
Departures
All departures whose destinations are SWF should remain on the ground until an approval has been received from the destination tower (or from N90 TRACON) that they are able to accept the aircraft into their airspace.
Pattern Work
  • The direction of the pattern work for all runways is LEFT.
  • All helicopters should be at 1200', props should be at 1200’ and jets at 2000’.
  • Simultaneous pattern work at both runways is not allowed.
  • Caution: Rwy 6 extended centerline crosses Rwy 27 final approach course for SWF. Do not allow aircraft to fly wide patterns. Also, be aware of arrivals and departures at SWF and issue appropriate traffic advisories when applicable.

TRACON

TRACON services for Dutchess County are provided by CSK sector of N90 TRACON (LIBH).

Appendix

Changelog

Change   Date Published   Description
CHG1 24 Aug 2003 Initial release.
CHG2 13 Jul 2004 Final Release.
CHG3 16 Feb 2006 Updated Radar Positions and Area Airport Notes pages
CHG4 22 Nov 2011 Significant Revision: updated airspace, procedures, for all positions/areas.
CHG5 18 Apr 2018 MAJOR REVISION. Converted to Wiki format. Airspace delegation and video map diagrams were updated.
CHG6 22 May 2020 Amended the IFR Squawk Code Range. Updated POU_GND frequency.
CHG7 27 Feb 2023 Updated CSK callsign
CHG8 4 NOV 2024 Converted to new Wiki format