| Position | Callsign | Radio Name | Frequency | Identifier |
|---|---|---|---|---|
| Clearance Delivery | WRI_DEL | McGuire Clearance Delivery | 135.200 | |
| Ground Control | WRI_GND | McGuire Ground | 121.800 | 1G |
| Local Control | WRI_TWR | McGuire Tower | 118.650 | 1L |
| ATIS | KWRI_ATIS | 127.100 |
Rev. 9 — Revised: 2025-02-06
Area at a glance
| ICAO Code | Airport Name | Airspace |
|---|---|---|
| KWRI | McGuire Air Force Base | D |
| KNEL | Naval Air Engineering Station Lakehurst | D |
| ICAO Code | Airport Name | Airspace |
|---|---|---|
| KBLM | Monmouth Executive | G |
| KMJX | Ocean County | G |
| N12 | Lakewood | G |
| N14 | Flying W | G |
| N73 | Red Lion | G |
| N81 | Hammonton | G |
| NJ20 | Coyle Field | G |
| NJ24 | Warren Grove Range | G |
| NJ46 | Mar Bar L Farms | G |
| NJ59 | Ekdahl | G |
| NJ60 | Cuddihy Landing Strip | G |
| NJ69 | Ideal Air Strip | G |
| NJ72 | Hop Brook Farm | G |
| NJ75 | Werner | G |
| N87 | Trenton-Robinsville | G |
| 19N | Camden County | G |
| 2N6 | Redwing | G |
| 2N8 | Marlboro | G |
| 3N6 | Old Bridge | G |
| 3N7 | Pemberton | G |
| 46NJ | Real Acres | G |
| 6NJ0 | Lentine South | G |
- Purpose
- This document prescribes the procedures to be utilized for providing air traffic control services at McGuire AFB Air Traffic Control Tower (ATCT) and McGuire Radar Approach Control Facility (RAPCON). 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 | NEL_GND | Lakehurst Ground | 118.375 | |
| Local Control | NEL_TWR | Lakehurst Tower | 127.770 | MH |
| Sector | Callsign | Frequency | Identifier | Combined Sector |
|---|---|---|---|---|
| McGuire Approach | WRI_APP | 126.475 | MY | Primary TRACON |
ATCT
Clearance Delivery
| Exit Gate | Exit | Scratchpad | Radial / SID |
|---|---|---|---|
| West (W) | ARD | ARD | |
| NAGGS | NAG | NAGGS# only | |
| North (N) | RBV | RNV | |
| East (E) | DIXIE | DIX | RBV 122 |
| MANTA | MAN | MANTA# only | |
| South (S) | CYN | CYN | |
| LEEAH | LEE | THMAS# only |
Notes
- Most of the departures out of KWRI start with a SID. These SIDs have transitions that are outside KWRI airspace (e.g. EMI, AIR, MRB, etc.) Refer to the IFR Departures section to learn more about these transitions.
- Exit fixes that are shown in grey can only be used for KWRI departures and they are only acceptable if used as transitions from the proper SID.
| Position | Frequency | Code |
|---|---|---|
| WRI_APP | 126.475 | MY |
| NY_CTR (Kennedy) | 125.325 | N56 |
This table lists the common departure frequencies for WRI Clearance Delivery. In general, the first controller in this list will handle 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 WRI, use WRI CTAF (118.650).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.
| SID | Initial altitude |
|---|---|
| MANTA# | 6,000’ |
| NAGGS# | 6,000’ |
| THMAS# | 8,000’ |
- The chart to the right lists the initial altitudes for the SIDs at WRI. Some intra-RAPCON flights also have initial altitudes that are non-standard.
- All SIDs out of WRI contain published crossing restrictions. Therefore, the phrase "Climb via SID" must be included in the IFR clearance.
- Most IFR departures from WRI start with a SID. If the pilot files a route that does not start with a SID, recommend an amendment that would start with the proper SID.
- Use the tabs below to access information about various departure procedures and their climbs.
The MANTA# RNAV Departure is the standard departure procedure for departures to the east and northeast. The picture below shows the initial climb for each runway. There are no transitions on this SID.
The primary objective of the MANTA# is to keep the WRI departure traffic separated from other ZNY traffic including arrivals to JFK. The primary purpose of the climbs is to keep the WRI departure traffic separated from the restricted area R-5001 to the east of WRI airport.
Cleared to (clearance limit), MANTA (number) departure, then as filed. Climb via SID...
The NAGGS# RNAV Departure is the standard departure procedure for RNAV departures to the west and north. The picture below shows the initial climb for each runway. There are no transitions on this SID.
The primary objective of the NAGGS# is to keep the WRI departure traffic separated from other traffic flying through the Philadelphia airspace. The primary purpose of the climbs is to keep the WRI departure traffic separated from the restricted area R-5001 to the east of WRI airport.
Cleared to (clearance limit), NAGGS (number) departure, then as filed. Climb via SID...
The THMAS# RNAV Departure is the standard departure procedure for RNAV departures to the south. The picture on the right shows the initial climb for each runway. There are no transitions on this SID.
The primary objective of the THMAS# is to keep the WRI departure traffic separated from other ZNY and ZDC traffic. The primary purpose of the climbs is to keep the WRI departure traffic separated from the restricted area R-5001 to the east of WRI airport.
Cleared to (clearance limit), THMAS (number) departure, then as filed. Climb via SID...
- WRI is located inside McGuire Class Delta Airspace. All VFR traffic must establish two-way radio communications.
- See the VFR Operations document for detailed explanation of applicable VFR procedures.
Ground Control
- Departure Sequencing
| Exit Gate | Exits |
|---|---|
| West | ARD, NAGGS |
| North | RBV |
| East | DIXIE, MANTA |
| South | CYN, LEEAH |
- Aircraft should be sequenced to depart in the following order:
- By alternating gate group.
- If not the above, then by alternating exit.
- If not the above, then by aircraft type largest to smallest.
- Coordinate with Local at the beginning of a shift if departures will “monitor” or “contact.” Also ensure to coordinate how Local would like the departure sequence forwarded.
- Before switching departing aircraft to Tower frequency, ensure the aircraft is aware of their number for takeoff. This is important for engine start and warm up times.
- 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.
- Taxi Routes
- As the taxiway system is simple, there are no pre-defined routings.
- Intersection Departures and Usable Runway Lengths
- Tower controllers may initiate/authorize intersection takeoffs. The measured distance from the intersection to the runway end will not be issued to aircraft unless specifically requested. The distance remaining, rounded down to the nearest 50', from each intersection where takeoff is authorized is as follows.
| 24 | 6 | 18 |
|---|---|---|
| B (2,100') | B (7,900') | L (6,150') |
| C (7,200') | C (2,800') |
Local Control
- Releases
- Releases from McGuire are automatic unless WRI RAPCON 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 JO 7110.126A.
- Radar (RACD)
- This tower is equipped with a Remote ARTS Color Display (RACD) and is LRAC (Limited Radar Approach Control) certified. By agreement with WRI RAPCON, this tower shall NOT radar identify departing aircraft and shall instruct IFR departures, and VFR departures requesting flight following 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.
| Wind Speed (kts) | Direction | Depart | Land |
|---|---|---|---|
| 0-4 | Any | 6, 36 | 6 |
| 5-15 | 330-149 | 6 | 6 |
| 150-329 | 24 | 24 | |
| >15 | 030-119 | 6 | 6 |
| 120-209 | 18 | 18 | |
| 210-299 | 24 | 24 | |
| 300-029 | 36 | 36 |
- For IFR traffic that is flying a published SID, do not assign a heading (this will override the climb); instead, simply clear them for takeoff.
Cactus123, wind 330 at 10, runway 36, cleared for takeoff.
- For IFR traffic that is not flying a SID, departure heading will be runway heading.
Missed Approach Procedures
| Runway | Heading | Altitude |
|---|---|---|
| 6 | Runway | 2,000' |
| 18 | 220 | 2,000' |
| 24 | Runway | 2,000' |
| 36 | Runway | 2,000' |
- 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.
- 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 RAPCON frequency.
Additional Information
- In order to prevent increased workload on the RAPCON, consider issuing missed approaches or go-arounds speed restrictions.
- Coordinate with RAPCON 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 headings and altitudes listed on the table if using them would compromise safety.
- Airspace
- Class DELTA. The tower owns 2,600' and below within an 5 mile radius of the airport.
- Radar
- This tower is LRAC (Limited Radar Approach Control) certified.
- Departures
- All departures whose destination is NEL should remain on the ground until approval has been received from the destination tower (or from WRI RAPCON) that they are able to accept the aircraft into their airspace.
- Flight Following
- All aircraft should remain on the tower frequency unless the route of flight will or may impede the operations of WRI RAPCON 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.
- Pattern Work
- Use the following as a guide for pilots wanting to perform pattern work at WRI. All helicopters should be at 600’, light aircraft at 800', and jets at 1,600’. Aircraft in the overhead should be at 2,100'. Simultaneous pattern work at both runways is not allowed
| Runway | Direction |
|---|---|
| 6 | Left |
| 18 | Right |
| 24 | Right |
| 36 | Left |
RAPCON
- 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-RAPCON) or five miles (RAPCON-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.
- Restricted Areas R-5001 and R-5002
- Restricted Area R-5001 is approximately 1 mile east of McGuire airport and approximately 4 miles west of Lakehurst airport. Restrictions are as follows:
- From surface to 4,000' only during 06:00 to 23:30 local time.
- From 4,000' to 8,000' during daytime of Fridays, Saturdays and Sundays.
- Restricted Area R-5002 is approximately 4 miles south of CYN, and includes the airspace above NJ24 airport. Restrictions are as follows:
- Area A: From surface to but not including 14,000' during daytime.
- Area B: From 1,000' to but not including 14,000' during daytime.
- Area C: From surface to 3,000' during daytime.
- Area D: From surface to 4,000' during daytime.
- Area E: From 3,500' to but not including 14,000' during daytime.
- Area F: From 14,000' to but not including FL200 during daytime.
| Block | Unconditional | Conditional |
|---|---|---|
| 1 | 2,000' and below | |
| 2 | 6,000’ and below | |
| 3 | 5,000’ and below | |
| 4 | 8,000’ and below | |
| 5 | 3,000' and below | |
| 6 | 3,000' and below | |
| 7 | 3,000’ and below | |
| 8 | 2,000’ and below | |
| 9 | 6,000’ and below | |
| 10 | 6,000’ and below | |
| 11 | 7,000’ and below | |
| 12 | 5,000’ and below | 6,000’ and below when released by EWR per LOA. |
| 13 | 3,000’ and below | |
| 14 | None | Handoff accepted from EWR at 6,000’ and below. |
| 15 | 2,000’ and below |
From WRI Area to N90 TRACON Areas
| Through | To | Route | Altitude | Hand-off | Frequency | Type |
|---|---|---|---|---|---|---|
| ARD | EWR | DIXIE V276 RBV | 060 | 4P | 128.55 | Jets |
| 050 | 4P | 128.55 | Props | |||
| METRO | EWR | DIXIE V276 RBV V249 METRO | 040 | 4H | 132.80 | EWR SATS |
| EMP | LGA | RBV V123 NANCI | 080 | 1D | 127.30 | Jets |
| MET | 040 | 4H | 132.80 | Props | ||
| MET | HPN/DXR | ZIGGI V276 RBV V249 SAX V39 BREZY | 050 | 4H | 123.80 | LGA SATS |
| CAM | JFK / JFK SATS | RBV V276 ZIGGI | 050 | 2G | 128.12 | |
| CAM | ISP / ISP SATS | RBV V276 ZIGGI | 050 | 2G | 128.12 | |
| PHL / PHL SATS | CYN V312 OOD | 050 | 6V | 119.75 | PHL on East Ops | |
| 6S | 133.87 | PHL on West Ops | ||||
| MET | PNE | RBV V276 ARD | 040 | 4H | 123.80 |
From WRI Area to ACY TRACON Areas
| Through | To | Route | Altitude | Hand-off | Frequency | Type |
|---|---|---|---|---|---|---|
| ACY | DIXIE V229 | 040 | 124.60 | |||
| ACY | DIXIE V16 VCN | 060 | 124.60 | OVERFLIGHTS ONLY |
| From / Through | To | Route | Altitude | Type |
|---|---|---|---|---|
| ARD | WRI/NEL | HAR# STAR / NAGGS CYN | 050 | All |
| ACY | WRI/NEL | SIE# STAR / PANZE ZIGGI | 060 | All |
- Purpose
- This agreement prescribes transfer of control procedures, radar handoff procedures, route/altitude assignments, and delegation of airspace between Newark TRACON (EWR) and McGuire RAPCON (WRI).
- 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.
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.
EWR arrivals from WRI airspace
- WRI feeds ARD from RBV V249 METRO at 6,000' on EWR Jet/HPTP arrivals.
- When N90 is unable to accept traffic landing EWR, N90 will delegate that portion of the RBV holding pattern north of V276 (i.e., EWR Area #36, WRI Area #12) at 6,000' to WRI.
- WRI shall affect a radar handoff and transfer communications at least 2½nm from the airspace boundary lines. ARD has control for turns 30 degrees left or right of the inbound course.
- Purpose
- This agreement prescribes transfer of control procedures, radar handoff procedures, route/altitude assignments, and delegation of airspace between Philadelphia TRACON (PHL) and McGuire RAPCON (WRI).
- 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
- 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.
WRI RAPCON Departure Procedures
- WRI traffic direct ARD shall remain in WRI airspace until approval request (APREQ) has been requested from and approved by PHL TRACON.
- WRI shall handoff traffic on the PTW# or MXE# crossing WHITZ at 5,000' or between WHITZ and NAGGS climbing to 6,000'.
- WRI shall handoff traffic not on PTW# or MXE# which is direct NAGGS, crossing WHITZ at 5,000' or between WHITZ and NAGGS climbing to 6,000'. Traffic direct NAGGS at lower altitudes should be on an APREQ basis.
WRI RAPCON Arrival Procedures
- PHL shall handoff traffic on the HAR# arrival to WRI crossing NAGGS at 5,000'.
- WRI has control on contact for turns 30 degrees left or right of the inbound course.
- Purpose
- This agreement prescribes transfer of control procedures, radar handoff procedures, route/altitude assignments, and delegation of airspace between McGuire RAPCON (WRI) and Atlantic City TRACON (ACY).
- 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
- 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.
- WRI RAPCON Arrival Procedures
- ACY shall handoff WRI arrivals on the SIE# STAR crossing PANZE at 6,000'


