ELM SOP

New York ARTCC

Standard Operating Procedure — ELM

Rev. 4 — Revised: 2024-11-13

Area at a glance

ICAO Code	Airport Name	Airspace
KELM	Elmira Corning Regional Airport	D
KITH	Ithaca Tompkins Regional Airport	D

Uncontrolled Fields [Show]

ICAO Code	Airport Name	Airspace	Area
KPEO	Penn Yan	G	ELMN (North)
N03	Cortland County	G	ELMN
N38	Grand Canyon State	G	ELMS (South)

File:TraconOverview-ELM.png

Purpose

This document prescribes the procedures to be utilized for providing air traffic control services at tElmira Air Traffic Control Tower (ATCT) and any of the positions within the Elmira Terminal Radar Approach Control (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

Ground	ELM_GND	Elmira Ground	121.950	EG
Tower	ELM_TWR	Elmira Tower	121.100	EL
ATIS	KELM_ATIS		125.475

Ground	ITH_GND	Ithaca Ground	121.800	EJ
Tower	ITH_TWR	Ithaca Tower	119.600	EH
ATIS	KITH_ATIS		125.175

Sector	Callsign	Frequency	Identifier	Combined Sector
North	ELM_N_APP	124.300	EN
South	ELM_S_APP	128.425	ES	Primary TRACON

ATCT

Clearance Delivery

Exit Gate	Exit	Scratchpad
North	FJC	FJC
Northeast	SAX	SAX
Southeast	ARD	ARD
	RBV	RBV
South	PTW	PTW
West	ETX	ETX

Notes

While strict exit direction points are not required at ABE, the guide above may come in handy for directing pilots to proper exits for departing the area.

Position	Frequency	Code
ABE_DEP	124.450	AZ
ABE_APP	119.650	AF
NY_CTR	125.325	N56

The table lists the common frequencies used as departure frequency by ABE Clearance Delivery. The first available controller in this list should be handling departures. If both ABE_DEP and ABE_APP sectors are online, assign ABE_APP frequency for all departing aircraft requesting altitudes at or below 3,000 feet and assign ABE_DEP frequency for all departing aircraft requesting to climb above 3,000 feet.

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.

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.

Notes

• The initial altitude for IFR departures of all types is 3,000’ whereas higher may be expected in 10 minutes after departure.
• There is no published departure procedure out of Allentown. All aircraft must be cleared to their destination via radar vectors to an ABE exit.

ABE Class Charlie VFR Operations

Operation	Departure Runway	Direction	Departure Instructions	Altitude	Departure Frequency
VFR w/ or w/o Flight Following (at or below 3000') )	All	All	Fly runway heading	3000'	119.650 (Allentown Departure)
VFR w/ or w/o Flight Following (above 3000)	All	All	Fly runway heading	3000'	124.450 (Allentown Departure)

Allentown is a Class Charlie airport. All VFR traffic must be issued a discrete squawk code.

VFR at or below 3000'

PHRASEOLOGY
On departure (departure instructions), maintain VFR at or below (altitude), Departure frequency (frequency), Squawk (code).

VFR above 3000'

PHRASEOLOGY
On departure (departure instructions), maintain (altitude) until advised, Departure frequency (frequency), Squawk (code).

Ground

Departure Sequencing

Exit Gate	Exits
North	FJC
Northeast	SAX
Southeast	ARD,RBV
South	PTW
West	ETX

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

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.

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.

   PHRASEOLOGY
   RUNWAY SIX AT ALPHA FOUR, TAXI VIA LEFT ON ALPHA, ALPHA FOUR. RUNWAY SIX AT ALPHA FOUR INTERSECTION DEPARTURE, SIX THOUSAND FIFTY FEET AVAILABLE

6	13	24	31
A4 (6050')	B6 (4900')	A1 (7200')	B3 (east) (4100')
J (5250')	B5 (4200')	E (5500')	B3 (west) (4050')
13/31 (4700')	6/24 (3400')	A3 (4400')	B4 (3200')
B (4400')	A (3000’)	B (3100')	A (2650')
A3 (3100')	B4 (2450')	13/31 (2700')	6/24 (2200')

Tower

Tower Procedures

Releases

Releases from Allentown are automatic unless the ABE TRACON requests individual releases.

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 (RACD)

This tower uses a DBRITE radar only and is not certified for any approach control services. By agreement with Allentown TRACON, 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 will be radar identified by the TRACON.

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

Wind Speed (kts)	Direction (°M)	Depart	Land
0-4	Any	6	6
>4	010-100	6	6
	101-180	13	13
	181-289	24	24
	290-009	31	31

Note

If runway 13/31 is in use, but the aircraft needs the longer runway, use runway 6/24 that is best aligned with the wind.

IFR aircraft must be given runway heading, unless otherwise coordinated with the departure controller.

PHRASEOLOGY
FLY RUNWAY HEADING, WIND (wind), RUNWAY (runway), CLEARED FOR TAKEOFF.

Runway	Heading	Altitude
6	060	3,000’
13	270	3,000'
24	240	3,000’
31	310	3,000’

Missed Approach Procedures

1. Missed approaches or go-arounds must fly runway heading or track the localizer until reaching the departure end of the runway, then be issued a heading, unless the controller determines that it would be advantageous to delay or initiate a turn early.
2. The table to the right indicates the heading and altitude that need to be assigned to a missed approach or go-around prior to release to TRACON frequency.
3. 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. Separation must be based on altitude initially during all missed approaches or go-arounds. Prior to issuing a climb to 3,000’, interval altitudes such as 2,000’ may be utilized to prevent converging targets from losing separation.
2. In order to prevent increased workload on the TRACON, consider issuing missed approaches or go-arounds speed restrictions in accordance with FAA Order JO 7110.65.
3. Coordinate with TRACON as soon as possible and hand off when Local Control traffic is not a factor.
4. Sound judgment must be exercised when dealing with go-arounds or missed approaches. Deviate as necessary from the headings and altitudes listed on the table if using them would compromise safety.

Airspace

• Class Charlie.
• The tower owns 2,000' and below within a 5 mile radius of the airport.

Departures

• All VFR departures will fly runway heading unless otherwise coordinated with the TRACON.
• Local Control will handoff aircraft to the TRACON to be radar identified.
• All aircraft will receive radar services provided by the TRACON until they exit the Class Charlie airspace. The TRACON will radar identify VFR departures and then, when applicable, terminate their radar services if they do not intend on receiving flight following.

Flight Following

All aircraft should remain on the tower frequency unless the route of flight will or may impede the operations of ABE TRACON 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

• All aircraft wanting to perform pattern work at ABE, must be assigned left closed traffic.
• All props should be at 1,500’ and jets at 2,000’. Adjust these altitudes when necessary to avoid over-flights or IFR traffic flow.

TRACON

General

General Information

Callsign

1. Whenever a controller handles a departure, they must use the radio name “Allentown Departure” when referring to themselves on frequency.
2. Whenever a controller handles an arrival or enroute traffic, they must use the radio name “Allentown Approach” when referring to themselves on frequency.
3. 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 must apply at all times unless prior verbal (or textual) coordination between facilities has been affected otherwise.

Position Combining/De-combining

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

Noise Abatement

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

1. The following procedures apply between the hours of 2130 and 0630 local, when the wind is less than 3 knots and there is no ceiling less than 1000 feet:

• Assign Runway 6 on ODD numbered days and Runway 24 on EVEN numbered days.
• Pilots requesting other than the assigned preferential runway must be advised that the runway assignment is “for noise abatement purposes”. If the pilot insists on departing from other than the preferential runway, honor the pilot's request.
• If wind/weather conditions are a factor, utilize normal procedures for runway assignment.

1. Instruct all turbojet aircraft departing Runway 31 to turn right to an initial heading of 360 degrees.
2. Ensure that ABE departing turbojet aircraft are not turned until the aircraft is at or above 2000 feet.

LOA/ABE MDT RDG

LOA/N90 ABE

Letter of Agreement

Philadelphia TRACON (PHL) & Allentown TRACON (ABE)

Rev. 2 - 7 Apr 2020

Purpose

This agreement prescribes transfer of control procedures, radar handoff procedures, route/altitude assignments, and delegation of airspace between Philadelphia TRACON (PHL) and Allentown TRACON (ABE).

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

• Transfer of Control Procedures:
  • Transfer of control on all aircraft must be accomplished no later than the PHL/ABE common boundary.
  • Completion of radar handoff and transfer of communications constitutes authorization for descents and to turn aircraft up to thirty (30) degrees within 10 miles of the PHL/ABE common boundary. PHL has additional control for turns greater than 30 degrees if the amended track will shorten the distance to leave ABE airspace.
  • If a beacon code is not compatible on handoff, the receiving facility may change the beacon code when in contact with the aircraft, without coordination.
• VFR Procedures:
  • Automated VFR handoffs are optional between facilities. No verbal coordination is required.
  • The receiving controller must be responsible for obtaining all pertinent information.
  • Beacon codes do not need to be changed.
• Coordination Procedures:
  • Regardless of which facility requests an altitude or route change, which will affect additional sectors in the adjacent facility's area, each facility must be responsible to complete all necessary internal coordination, e.g., the ABE controller must be responsible for coordination with all appropriate ABE sectors.
  • PHL must coordinate with ABE prior to conducting instrument operations at the following airports:
    • Quakertown Airport (UKT)
    • Pennridge Airport (CKZ)
  • ABE must coordinate with PHL prior to conducting instrument operations at the following airports:
    • Butter Valley Golf Port (7N8)
    • Sky Manor Airport (N40)
    • Vansant Airport (9N1)

PHL TRACON to ABE TRACON

• All aircraft from PHL TRACON to ABE TRACON must be cleared to the destination airport via the routes and altitudes described in Attachment 1. Routes and altitudes other than those depicted in this LOA must be on an APREQ basis.

ABE TRACON to PHL TRACON

• All aircraft from ABE TRACON to PHL TRACON must be cleared to the destination airport via the routes and altitudes described in Attachment 1. Routes and altitudes other than those depicted in this LOA must be on an APREQ basis.

Attachment 1 – Route Descriptions

From PHL to ABE [Show]

From	To	Route Via	Altitude Restriction
PHL & PHL Sats (except ARD Area)	ABE & ABE Sats	Direct FJC; traffic must remain east of the V29 protected airspace.	4,000'; ABE has control for descent to 3,000' for ABE arrivals.
	Overflights	PTW V29 ETX	8,000'
ARD Area	ABE & ABE Sats	Direct FJC or ETX	4,000'
	Overflights	PTW V29 ETX	8,000'

From ABE to PHL [Show]

From	To	Route Via	Altitude Restriction
ABE & ABE Sats	PHL & PHL Sats (except ARD Area)	Direct PTW; traffic must remain west of SPUDS.	Jets: 7,000'
			Turboprops: 5,000'
		ETX V29 PTW	Piston engine: 4,000'
	ARD Area	Direct ARD or MAZIE; traffic must remain between ETX and FJC.	5,000'
	Overflights	ETX V29 PTW	6,000'

Attachment 2 - Area Airport Listings

Area Airport Listings [Show]

Area	Abbreviation	Satellite Airport Codes
Allentown Satellite Airports
Allentown Satellite	ABE Sats	XLL, N43, N53, 22N, 1N7, N40, N85, 69N, 7N8, 9N1
Philadelphia Satellite Airports
Philadelphia Satellite	PHL Sats	DYL, PNE, TTN, UKT, 3NJ6, EVY, ILG, PTW, N10, N47, N57, MQS, LOM, CKZ, OQN, 7N7, 17N
Yardley Area	ARD Area	DYL, PNE, TTN, UKT, 3NJ6

Attachment 3 - Airspace Delegation

Airspace Delegation [Show]

Area	Sector	Altitude
A	ABE DR ABE AR	080/040 030/SFC
B	PHL NORTH ARRIVAL PHL POTTSTOWN RDG	080/070 060 050/SFC
C	ABE DR RDG	080/050 040/SFC
D	PHL NORTH ARRIVAL PHL POTTSTOWN RDG	080/070 060 050/SFC
E	PHL NORTH HIGH DEPARTURE PHL NORTH ARRIVAL PHL POTTSTOWN	130/090 080/070 060/SFC
F	PHL NORTH ARRIVAL PHL POTTSTOWN	090/070 060/SFC
G	PHL NORTH HIGH DEPARTURE PHL NORTH ARRIVAL PHL POTTSTOWN	130/110 100/070 060/SFC
H	PHL NORTH HIGH DEPARTURE PHL YARDLEY PHL POTTSTOWN	130/070 060/050 040/SFC
I	PHL NORTH HIGH DEPARTURE PHL YARDLEY	130/070 060/SFC
J	N90 METRO PHL YARDLEY	090/050 040/SFC
K	N90 METRO ABE DR ABE AR	090/060 050/040 030/SFC

LOA/ZNY ABE

Departure and Approach

Appendix

Changelog

Change	Date Published	Description
CHG1	1 Feb 2008	Initial release.
CHG2	1 Jun 2013	General document review, minor editing and update
CHG3	8 May 2020	MAJOR REVISION. Converted to Wiki format. Updated ABE TRACON Operational Positions (new primary position). Updated airspace delegation maps. Added new LOAs with neighboring facilities.
CHG4	Mar 2023	Updated VFR procedures
CHG5	9 Oct 2023	Updated Position Codes
CHG6	5 Sep 2024	Added Departure Flow Diagram
CHG7	28 Oct 2024	Converted to new Wiki format