New York ARTCC
ABE SOP
Rev. 3 — 07 May 2020

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

Area at a glance

Operational Positions

Position Callsign Radio Name Frequency Identifier
Clearance Delivery ABE_DEL Allentown Clearance Delivery 124.050 AC
Ground ABE_GND Allentown Ground 121.900 AG
Tower ABE_TWR Allentown Tower 120.500 AL
ATIS KABE_ATIS 126.970
Sector Callsign Frequency Identifier Tag Squawk Remarks
Departure Radar ABE_DEP 124.450 AZ Z 3301 — 3337
Arrival Radar ABE_APP 119.650 AF F 3301 — 3337 Primary TRACON


ATCT

Clearance Delivery

Position Frequency Code
ABE_DEP 124.45 AZ
ABE_APP 119.65 AF
NY_CTR 125.32 N56

The table on the right 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.

If there is no other controller online that would accept departures from ABE, use UNICOM frequency (122.8).

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

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

Allentown is a Class Charlie airport. 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 FJC
Northeast SAX
Southeast ARD, RBV
South PTW
West ETX

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 six at alpha four, taxi via alpha, alpha four. Runway six at alpha four intersection departure, six thousand and fifty feet takeoff distance available.
6 13 24 31
A4 (6,050’) B6 (4,900’) A1 (7,200’) B3 (east) (4,100’)
J (5,250’) B5 (4,200’) E (5,500’) B3 (west) (4,050’)
13/31 (4,700’) 6/24 (3,400’) A3 (4,400’) B4 (3,200’)
B (4,400’) A (3,000’) B (3,100’) A (2,650’)
A3 (3,100’) B4 (2,450’) 13/31 (2,700’) 6/24 (2,200’)
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 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
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 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
Wind Speed Direction Configuration
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.

PHRASEOLOGYFly 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
  1. Class CHARLIE.
  2. The tower owns 2,000' and below within a 5 mile radius of the airport.
Departures
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 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
  1. All aircraft wanting to perform pattern work at ABE, must be assigned left closed traffic.
  2. 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

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

ABE Airspace Delegation.png

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:
    1. Assign Runway 6 on ODD numbered days and Runway 24 on EVEN numbered days.
    2. 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.
    3. If wind/weather conditions are a factor, utilize normal procedures for runway assignment.
  2. Instruct all turbojet aircraft departing Runway 31 to turn right to an initial heading of 360 degrees.
  3. Ensure that ABE departing turbojet aircraft are not turned until the aircraft is at or above 2000 feet.
Letter of Agreement
Allentown TRACON (ABE), Harrisburg TRACON (MDT) & Reading TRACON (RDG)
Rev. 1 — April 7, 2020
Purpose
This agreement prescribes transfer of control procedures, radar handoff procedures, route/altitude assignments, and delegation of airspace between Allentown TRACON (ABE), Harrisburg TRACON (MDT) & Reading TRACON (RDG).
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. Transfer of Control Procedures:
    1. Transfer of control on all aircraft must be accomplished no later than the ABE/MDT or ABE/RDG common boundary.
    2. 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 ABE/MDT or ABE/RDG common boundary. RDG has additional control for turns not greater than 45 degrees for aircraft on V93 only.
    3. 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.
  2. VFR Procedures:
    1. Automated VFR handoffs are optional between facilities. No verbal coordination is required.
    2. It is suggested to inhibit MSAW alerts (vSTARS client) on all targets.
    3. The receiving controller must be responsible for obtaining all pertinent information.
    4. Beacon codes do not need to be changed.
  3. Coordination Procedures:
    1. 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.
  4. Reading TRACON Operations Hours:
    1. During those periods when RDG is not in operation (0000-0600 local time), MDT must provide the services assigned to RDG in this LOA.
ABE TRACON to MDT/RDG TRACON
  1. All aircraft from ABE TRACON to MDT/RDG 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.
  2. Traffic from ABE airspace may be given direct RAV or SEG without coordination.
  3. Traffic from ABE airspace with a destination airport within MDT or RDG TRACON may be given direct without coordination.
MDT/RDG TRACON to ABE TRACON
  1. All aircraft from MDT/RDG 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.
  2. Traffic from MDT/RDG airspace may be given direct ETX, FJC or STW without coordination.
Attachment 1 – Route Descriptions
From ABE to MDT/RDG [show]
From To Route Via Altitude Restriction
ABE & ABE Sats MDT & MDT Sats V6 / V30 / V39 / V93/ V162 / V276 6,000' or 8,000'
RDG Radar Vectors 4,000'
V93 DUMMR 4,000' or 6,000'; traffic handed off at 6,000' must be descended by RDG prior to adjacent airspace boundaries.
RDG Overflights V93 4,000' or 6,000'; traffic handed off at 6,000' must be descended by RDG prior to adjacent airspace boundaries.
V30 / V39 / V162 4,000'
Direct FLOAT or LRP 4,000'
From MDT/RDG to ABE [show]
From To Route Via Altitude Restriction
MDT & MDT Sats ABE & ABE Sats V6 FJC or V39 ETX 7,000'
Overflights V6 / V30 / V39 / V93 / V162 7,000'
RDG ABE & ABE Sats (except 1N7) ETX 3,000' or 5,000'
1N7 FJC STW 3,000' or 5,000'
Overflights Direct FJC or ETX / V93 / V93 SNOWY 5,000'
Attachment 2 – Area Airport Listings [show]
Area Abbrevation Satellite Airport Codes
Allentown Satellite ABE Sats XLL, N43, N53, 22N, 1N7, N40, N85, 69N, 7N8, 9N1
Harrisburg Satellite Airports MDT Sats CXY, LNS, MUI, THV, ZER, SEG, N68, N71, N76, N79, N94, 9D4
Letter of Agreement
Allentown TRACON (ABE) & New York TRACON (N90)
Rev. 1 — April 7, 2020
Purpose
This agreement prescribes transfer of control procedures, radar handoff procedures, route/altitude assignments, and delegation of airspace between Allentown TRACON (ABE) and New York TRACON (N90).
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. Transfer of Control Procedures:
    1. Transfer of control on all aircraft must be accomplished no later than the ABE/N90 common boundary.
    2. 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 ABE/N90 common boundary.
    3. 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.
  2. VFR Procedures:
    1. Automated VFR handoffs are optional between facilities. No verbal coordination is required.
    2. It is suggested to inhibit MSAW alerts (vSTARS client) on all targets.
    3. The receiving controller must be responsible for obtaining all pertinent information.
    4. Beacon codes do not need to be changed.
  3. Coordination Procedures:
    1. 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.
    2. ABE must coordinate with N90 prior to conducting instrument operations at the following airports:
      • Stroudsburg-Pocono Airport (N53)
      • Blairstown Airport (1N7)
      • Alexandria Airport (N85)
      • Sky Manor (N40)
    3. N90 must coordinate with ABE prior to conducting instrument operations at the following airports:
      • Blairstown Airport (1N7)
      • Aeroflex-Andover (12N)
      • Sky Manor Airport (N40)
ABE TRACON to N90 TRACON
All aircraft from ABE TRACON to N90 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.
N90 TRACON to ABE TRACON
All aircraft from N90 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.
Attachment 1 – Route Descriptions
From ABE to N90 [show]
From To Route Via Altitude Restriction
ABE, ABE Sats, RDG, MDT, CXY & LNS EWR Direct BWZ or PENNS STAR 5,000' or 6,000'
ABE & ABE Sats EWR N Sats
LGA N Sats ( ≥ 210 knots)
STW; N90 has control for a right turn up to a heading of 110 degrees. 5,000'
EWR S Sats
JFK, FRG, ISP, 1N2, MTP, 21N, FOK, HWV, HTO, LGA (< 210 knots)
SBJ 5,000'
LGA N Sats (< 210 knots)
LIB Area, ISP N Sats, BDL Area & New England Airports (east of ALB / BML)
FJC V162 HUO; New England Airports west of ALB / BML must be routed via LHY. 5,000'
From N90 to ABE [show]
From To Route Via Altitude Restriction
EWR & EWR S Sats ABE & ABE Sats ETX, FJC or BUSKY 4,000, 6,000' or 8,000'
Overflights ETX, FJC or BUSKY 4,000, 6,000' or 8,000'
EWR N Sats & LIB Area ABE & ABE Sats FJC 4,000'
Overflights V162 FJC or direct FJC 4,000'
Attachment 2 – Flow Depiction [show]

N90-ABE Flow Depiction.png

Attachment 3 – Area Airport Listings [show]
Area Abbrevation Satellite Airport Codes
Allentown Satellite Airports
Allentown Satellite ABE Sats XLL, N43, N53, 22N, 1N7, N40, N85, 69N, 7N8, 9N1
New York Satellite Airports
Newark Area North Satellites EWR N Sats CDW, FWN, MMU, TEB, N05, 4N1, N07, 12N, 3N5
Newark Area South Satellites EWR S Sats LDJ, SMQ, 39N, 47N, N51
Liberty Area Airports LIB Area MGJ, MSV, POU, SWF, N69, N82, 06N, 44N, 46N
Islip Area North Satellites ISP N Sats OXC, HVN, BDR, SNC
LaGuardia Area North Satellites LGA N Sats HPN, DXR
Bradley Area Airports
Bradley Area BDL Area BAF, BDL, CEF, HFD, IJD, MMK, ORH, 3B0, 4B8, 4B9, 7B2, 7B6, 7B9, MA68
New England Airports
New England Airports (east of ALB / BML) N/A ACK, BED, BID, BOS, BVY, FIT, EWB, GON, LWM, HYA, MVY, OQU, OWD, PVD, PYM, UUU, WST
Attachment 4 – Airspace Delegation [show]
Letter of Agreement
Philadelphia TRACON (PHL) & Allentown TRACON (ABE)
Rev. 2 — April 7, 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).
Cancellation
Philadelphia TRACON (PHL) and Allentown TRACON (ABE) Letter of Agreement, dated January 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.
General Procedures
  1. Transfer of Control Procedures:
    1. Transfer of control on all aircraft must be accomplished no later than the PHL/ABE common boundary.
    2. 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.
    3. 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.
  2. VFR Procedures:
    1. Automated VFR handoffs are optional between facilities. No verbal coordination is required.
    2. It is suggested to inhibit MSAW alerts (vSTARS client) on all targets.
    3. The receiving controller must be responsible for obtaining all pertinent information.
    4. Beacon codes do not need to be changed.
  3. Coordination Procedures:
    1. 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.
    2. PHL must coordinate with ABE prior to conducting instrument operations at the following airports:
      • Quakertown Airport (UKT)
      • Pennridge Airport (CKZ)
    3. 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 [show]
Area Abbrevation 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 [show]
Letter of Agreement
Allentown TRACON (ABE) & New York ARTCC (ZNY)
Rev. 1 — April 7, 2020
Purpose
This agreement prescribes transfer of control procedures, radar handoff procedures, route/altitude assignments, and delegation of airspace between Allentown TRACON (ABE) and New York ARTCC (ZNY).
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. Minimum radar separation between aircraft, when transfer of control is accomplished, must be at least five (5) nautical miles constant or increasing.
  2. All handoffs and transfer of communications must be accomplished prior to reaching the transfer of control points (TCP) depicted on Attachment 2 and 3, unless prior coordination is accomplished.
Arrival Control
  1. ZNY must clear arrivals as follows:
    1. MIP117R KRAZE or MIP direct KRAZE: cross KRAZE at 9,000'
    2. SNOWY: cross SNOWY at 9,000'
    3. DUMMR: cross DUMMR at 9,000'
    4. SLATT: cross V232 at 9,000'
  2. ZNY must ensure that arrival aircraft are cleared via the routes depicted on Attachment 2, prior to transfer of control to ABE, unless prior coordination is accomplished.
  3. Upon transfer of communications, ABE has control to clear arrival aircraft direct FJC or ETX.
  4. The route FJC V6 SBJ V232 is restricted to non-jet aircraft with indicated airspeeds less than 210 knots (KIAS), originating south of V232, and landing KLGA, KJFK, KFRG, KISP, KMTP, KHWV, KFOK & KHTO.
  5. The route PSB V6 FJC ARD V276 ZIGGI KJFK is restricted to non-jet aircraft, capable of 210 KIAS or greater, landing KJFK that have departed from KCLE, KCMH or KPIT.
Departure Control
  1. ABE must clear departure aircraft to altitudes within the approach control area prior to a ZNY handoff.
  2. Aircraft requesting altitude/flight level above the initial clearance altitude must be informed by ABE to expect further clearance to requested altitude/flight level 10 minutes after departure.
  3. Departure aircraft must be established on, or assigned headings to join/intercept assigned routes as described below and depicted on Attachment 3 prior to their crossing ABE lateral airspace boundary, unless prior coordination is accomplished:
    1. Northbound Reading (KRDG) departures must be cleared via DUMMR V93 LVZ.
    2. ABE must clear departure traffic routed over LRP via ETX or FLOAT intersection, direct LRP.
    3. ZNY92 (Pottstown Sector) must notify ABE when Philadelphia arrival traffic is holding at SPUDS intersection.
    4. When notified by ZNY of holding at SPUDS, ABE must clear departure traffic routed over LRP via ETX direct LRP.
  4. Regardless of which facility requests an altitude or route change that will affect additional sectors in the adjacent facilities' airspace, each facility must be responsible to complete all necessary internal coordination.


Attachment 1 – Delegated Airspace [show]

ABE Airspace Delegation.png

Attachment 2 – Arrival Routes [show]

ABE ZNY LOA ARR ROUTES.png

Attachment 3 – Departure Routes [show]

ABE ZNY LOA DEP ROUTES.png


Departure and Approach


Appendix

Changelog

Change Date Description
CHG1 1 Feb 2008 Initial release
CHG2 1 Jun 2013 General document review, minor editing and update
CHG3 07 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.