MUI SOP: Difference between revisions

From New York ARTCC
No edit summary
m (fix: CWT link)
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{SOPHeader
{{SOPHeader
|Facility=MUI
|Facility=Muir Army Airfield (MUI)
|Version=2
|Version=2
}}
}}
Line 134: Line 134:
</div>
</div>


[[File:ExitGateDiagram-MDT.png|550px]]
[[File:ExitGateDiagram-MDT.png|450px]]




Line 176: Line 176:
|-|LOA Routes=
|-|LOA Routes=


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.
Routing to certain airports in ZNY, ZDC and ZBW ARTCCs is pre-coordinated through [[LOA|letters of agreement (LOA)]]. These routes have been added to the [[PRD|Preferred Route Database (PRD)]].




Line 250: Line 250:


; Separation
; 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 [https://www.faa.gov/documentLibrary/media/Order/JO_7110.126A.pdf FAA JO 7110.126A].
: The standard departure separation technique to be used is anticipated radar separation. When wake turbulence is a factor, use timed separation in accordance with {{ExtLink_CWT}}.


; Radar (RACD)
; Radar (RACD)
Line 345: Line 345:
== TRACON ==
== TRACON ==


TRACON services for Muir are provided by '''Harrisburg TRACON'''.
TRACON services for Muir are provided by '''[[MDT_SOP|Harrisburg TRACON]]'''.
 
== Appendix ==

Latest revision as of 03:41, 13 January 2026

New York ARTCC
Standard Operating Procedure — Muir Army Airfield (MUI)

Rev. 2 — Revised: 2026-01-13

Area at a glance

ICAO Code Airport Name Airspace
KMUI Muir Army Airfield D
Purpose
This document prescribes the procedures to be utilized for providing air traffic control services at Muir Army Airfield 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

Ground MUI_GND Muir Ground 121.625 HQ
Tower MUI_TWR Muir Tower 126.200 HP

Sector Callsign Frequency Identifier Combined Sector
Harrisburg (HAR) MDT_SW_APP 124.100 HK Primary TRACON
Lancaster (LRP) MDT_SE_APP 126.450 HS
Ravine (RAV) MDT_N_APP 118.250 HG
Reading RDG_APP 125.150 RX Covered by MDT TRACON 0000-0600 local time

Notes:

  • When RDG_APP is not staffed, MDT TRACON may provide top-down services at RDG regardless of local time.
  • When splitting MDT TRACON, split into HAR & LRP sectors first.

ATCT

Clearance Delivery

Exit Gate Exit Scratchpad
North (N) GAAPP GAA
SEG SEG
Northeast (NE) ETX ETX
LVZ LVZ
FJC FJC
East (E) LRP LRP
PTW PTW
ARD ARD
Southeast (SE) DQO DQO
Southwest (SW) HAR HAR
BRNAN BRN
JST JST
VINSE VIN
THS THS
SCAPE SCA
GRAMO GRA
MRB MRB
EMI EMI
Northwest (NW) MCMAN MCM
PSB PSB


Notes
  1. While strict exit direction points are not required at MUI, the guide above may come in handy for directing pilots to proper exits for departing the area.
  2. KIACK is only a valid exit of preceded by GAAPP. The route must therefore read GAAPP KIACK...
  3. MCMAN is used for aircraft routed via V33/J64/Q62.
Position Frequency Code
MDT_N_APP 118.250 HG
MDT_SE_APP 126.450 HS
MDT_APP 124.100 HK
NY_CTR 125.325 N56

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

If there is no other controller online that would accept departures from MUI, use MUI CTAF (126.200).
Notes
  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 Muir. All aircraft must be cleared to their destination via radar vectors to an MUI exit.

Muir is a Class D 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 GAAPP, SEG
Northeast ETX, LVZ, FJC
East LRP, PTW, ARD
Southeast DQO
Southwest HAR, BRNAN, JST, VINSE, THS, SCAPE, GRAMO, MRB, EMI
Northwest MCMAN, PSB

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 possible, 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

Tower Procedures

Releases
Muir Tower will request individual releases from MDT TRACON for all IFR departures, unless previously coordinated.
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.126B.
Radar (RACD)
This tower uses a DBRITE radar only and is not certified for any approach control services. By agreement with Harrisburg 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 Depart Land
0-4 Any 7 7
>4 340-159 7 7
160-339 25 25
Departure Heading

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
7 Runway heading 3,000’
25 Runway heading 3,000’
Missed Approach Procedures
  1. 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.
  2. 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 § 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 used 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.
  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 Delta. The tower owns 3,000’ and below within a 4 mile radius of the airport. The tower also owns below 3,000’ up to 6 miles from the airport along the runway 7/25 extended centerline, which laterally extends 1.5 miles on each side.
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 MDT TRACON 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.
Overflights
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 MUI must be assigned left closed traffic for runway 25 and right closed traffic for runway 7.
All props should be at 1,500’ and jets at 2,000’. Adjust these altitudes when necessary to avoid overflights or IFR traffic flow.

TRACON

TRACON services for Muir are provided by Harrisburg TRACON.