VATSIM MINNEAPOLIS ARTCC MINNEAPOLIS TRACON LETTER OF AGREEMENT

Size: px

Start display at page:

Download "VATSIM MINNEAPOLIS ARTCC MINNEAPOLIS TRACON LETTER OF AGREEMENT"

Randolph Ward
5 years ago
Views:

1 VATSIM MINNEAPOLIS ARTCC MINNEAPOLIS TRACON LETTER OF AGREEMENT SUBJECT: TERMINAL AREA CONTROL SERVICE EFFECTIVE: September 1, PURPOSE. This agreement delegates authority and establishes procedures for the control of IFR and Special VFR traffic on the VATSIM network within the terminal area described herein and is supplementary to FAA Order , Air Traffic Control Handbook and VATSIM Network Policies and Procedures. 2. SCOPE. Minneapolis ARTCC (ZMP) delegates to Minneapolis Approach Control (M98) the airspace described in Attachment A for the control of IFR traffic at and below 17,000 ft MSL. 3. RADAR PROCEDURES. Unless otherwise coordinated, the following procedures shall apply: a. Handoffs. Aircraft entering ZMP from M98 airspace shall have at least 5 NM constant or increasing radar separation when radar vectored for the same fix on similar tracks. b. Transfer of control for turns ± 30 degrees from the assigned heading to: (1) M98 shall occur when the arriving/overflight aircraft are within 10 NM of ZMP/M98 boundary providing that M98 make any necessary point outs to other affected control positions. (2) ZMP shall occur when the departing aircraft are at least 25 NM from the MSP VOR or leaving 11,000 feet providing that ZMP make any necessary point outs to other affected control positions. c. M98 shall have control for descent of satellite STAR aircraft within 10 NM of the M98/ZMP boundary, except at AGUDE. M98 shall have control for descent of 7000 MSL satellite STAR aircraft at AGUDE within 10 NM of the M98/ZMP boundary. d. Beacon Code Assignments. Normal beacon codes, as assigned by IDS or ZMP RBCAS, shall be used at all times except when IDS or RBCAS are out of service. e. Departures (1) M98 shall issue enroute clearance provided: (a) Aircraft are cleared at 17,000 feet MSL or below. (b) Departures 6,000 feet MSL and below will be as filed (c) Departures filed 7,000 or 8,000 feet MSP shall be on a heading to clear satellite STAR arrival areas.

2 (2) M98 shall establish departing aircraft filed for 9,000 feet MSL or above in the appropriate ZMP sector, clear of STAR arrival areas on: (a) The appropriate MSP SID, or (b) A heading to join the appropriate SID within 50 miles of the MSP VOR, or (c) For the ROCHESTER SID, when departing Runway 12, a heading to join at or east of FOBUG and prior to CORDY, or (d) For the DARWIN SID from a position at or north of INUNE, direct DWN, or (e) For non-sid qualified aircraft, an assigned heading for a vector to: 1 Enter ZMP airspace east of the GEP STAR on a heading to maintain a track of 350 to 020 magnetic; e.g., Brainerd, Park Rapids, Grand Forks, Duluth, or Winnipeg. 2 Enter ZMP airspace west of the GEP STAR on a heading to maintain a track of 290 to 300 magnetic; e.g. Fargo, Alexandria, Bismarck or Jamestown. 3 Enter ZMP airspace north of the ENCEE STAR on a heading to maintain a track of 265 to 285 magnetic; e.g., Aberdeen, Watertown, or Rapid City. 4 Enter ZMP airspace on a heading to maintain a track of 210 to 240 magnetic; e.g., O'Neill, Sioux Falls, Redwood Falls, Kansas City, Fort Dodge, Mason City, or Des Moines. 5 Enter ZMP airspace east of the KASPR STAR on a heading to maintain a track of 140 to 160 magnetic when filed for 10,000 MSL or above; e.g., Waterloo, Rochester, Dubuque, or Waukon. 6 Enter ZMP airspace south of the WILDD STAR on a heading to maintain a track of 100 to 130 magnetic; e.g., Nodine, Dells, La Crosse, or Madison. 7 Enter ZMP airspace north of the AGUDE STAR on a heading to maintain a track of 040 to 060 magnetic; e.g., Rhinelander, Sault Ste. Marie, Marquette, Iron Mountain, or Eau Claire. (3) Prop aircraft requesting 12,000 feet MSL or higher shall be climbed to or level at 12,000 feet. ZMP shall have control for climb of these aircraft at 25 NM from MSP VOR. (4) M98 departures filed for 5,000 feet MSL or below shall enter ZMP Sector 05 at 5,000 feet MSL and Sectors 08, 09 and 10 at 4,000 feet MSL. f. Arrivals (1) The clearance limit fix for arrivals shall be the destination airport

3 (2) Conventional STARs. Speeds between 250 and 320 knots, if assigned, do not require coordination. (3) All turbojet and turboprop aircraft shall be routed via STAR routings. The appropriate crossing altitude restriction shall be issued as follows: (a) MSP Arrivals: STAR ROUTING (Turbojets) (Turboprops) EAU Arrival X TWINZ at X TWINZ at 9000 WILDD Arrival (ATC Assigned) X BITLR at KASPR Arrival X DELZY at TWOLF Arrival X TRGET at SKETR Arrival X SHONN at X SHONN at 9000 GEP Arrival (b) Satellite Arrivals: STAR ROUTING X GEP at (RWY 30L/R) X OLLEE at (All other rwys) (Turbojets) X OLLEE at 9000 (Turboprops) TWOLF Arrival X TRGET at 8000 X TRGET at 7000 AGUDE ARRIVAL X AGUDE at 8000 X AGUDE at 7000 ENCEE Arrival X RIXIE at 8000 X RIXIE at 7000 GEP Arrival X OLLEE at 8000 X OLLEE at 7000 (MSP Landing RWY 17) X OLLEE at 5000 or as coordinated (c) RNAV Arrivals (Turboprops NA) STAR ROUTING (MSP Land 12) (MSP Land 30) MUSCL Arrival Descend via, 12L Descend via, 30R KKILR Arrival Descend via, 12R Descend via, 30L BLUEM Arrival Descend via, 12R Descend via, 30L NITZR Arrival Descend via, 12R Descend via, 30L TORGY Arrival Descend via, 12R Descend via, 30L BAINY Arrival Descend via, 12L Descend via, 30R - 3 -

4 (4) STP arrivals routed over BITLR shall be assigned direct GEP and cross BITLR at 6,000 ft. (5) Except when landing Runway 35, ZMP shall provide MSP Approach with a minimum of 5 miles in trail or staggered spacing along the BLUEM/NITZR arrivals. For purposes of this restriction the BLUEM and NITZR arrivals shall be considered as one arrival. (6) All piston engine aircraft terminating in M98 airspace, regardless of altitude, shall enter M98 airspace from ZMP at 4,000 or 5,000 feet MSL as coordinated. (7) M98 will accept a reasonable number of aircraft to accommodate ZMP to recover from an unanticipated, drastic reduction in the arrival rate. These aircraft may be redirected as coordinated by M98 out the departure gates for holding or rerouting by ZMP. (8) All aircraft arriving MSP on any RNAV STAR must be on published speeds prior entering M98 unless otherwise coordinated. g. STC departures landing M98 airports shall enter M98 airspace at 5,000 feet MSL. When Runways other than 12L/R are in use, turbojet and turboprop aircraft departing STC and landing MSP shall be on a STAR arrival at the appropriate altitude. h. MKT departures landing M98 satellite airports shall enter M98 airspace at 5,000 ft. MSL direct destination. i. ZMP shall have control for descent to 10,000 feet MSL on aircraft exiting M98 airspace and landing RST airspace when the aircraft are 25 NM from MSP. j. Aircraft landing OEO, RNH, or RGK from the east (through Sector 5) shall be level at, or descending to, 4,000 feet MSL and M98 shall have control for descent and turns, up to 30 degrees either side of course, when aircraft are within10 NM of the M98 boundary. k. Aircraft landing STC or MKT shall enter ZMP airspace level at 4,000 feet MSL. ZMP shall have control for descent and turns, up to 30 degrees either side of course, when the aircraft are 25 NM from the MSP VOR. l. Aircraft landing STC filed at or above 14,000 ft. MSL shall enter M98 airspace level at 14,000 feet MSL. m. Overflight aircraft that will transit M98 airspace shall be on course and at the correct altitude for direction of flight, unless otherwise coordinated. n. During any time period in which ZMP assumes Rochester Approach Controls (RST) airspace, unless otherwise coordinated, all turboprop aircraft routed via the KASPR STAR shall cross the DELZY intersection at 9,000 feet MSL and all piston engine aircraft terminating in M98 airspace shall exit RST airspace at 4,000 feet MSL

5 o. Knock-It-Off OPD Procedures: (1) From time to time, winds and other meteorological conditions can make it necessary to discontinue the Optimum Profile Descents (OPD) on the RNAV STARs so as to manage the arriving streams more effectively. (2) When MSP is landing 4, 22, 17, 17/22 or anytime either facility has an operational necessity to discontinue the Optimum Profile Descent portion of the STAR, ZMP must: (a) On the MUSCL arrival: Cross BAYKS at and maintain 120. (b) On the KKILR arrival: Cross HUGGI at and maintain 110. (c) On the BLUEM arrival: Cross HHAMR at and maintain 100. (d) On the NITZR arrival: Cross WRSAW at and maintain 110. (e) On the TORGY arrival: Cross OFSON at and maintain 110. (f) On the BAINY arrival: Cross LUCCY at and maintain 110. (g) Cross the M98 boundary at the published speeds of 280kts unless otherwise coordinated. (3) Coordination must be accomplished by M98 OS/CIC/TMU and ZMP TMU. (4) M98/ZMP may invoke Knock It Off OPD procedures at individual gates regardless of runway configuration when operational necessity dictates. EXAMPLE- Knock It Off procedures in effect for meteorological conditions at MSP. 4. MIDNIGHT OPERATIONS: When coordinated (between the hours of 2230 and 0530 local): a. ZMP shall clear all traffic landing at airports within M98 as follows: (1) Direct to the destination airport. (2) Via pilot discretion descent to 10,000 feet to all aircraft at altitudes at and above 10,000 feet. (3) Arrivals at and below 10,000 feet shall remain at altitude. (4) ZMP shall assign all aircraft entering M98 airspace frequency (MSP_R_APP) b. M98 shall: (1) Clear departure aircraft via the first fix in the route. (2) Point out departures to any affected Center position. (3) Climb turboprops/props to 17,000 feet, or lower altitude if requested. 5. ATTACHMENTS - 5 -

6 Attachment "A" ZMP Area/Sector Map and Frequencies. Attachment "B" SIDs. Attachment C STARs. Shane A. VanHoven Air Traffic Manager VATSIM Minneapolis ARTCC Vacant Deputy Air Traffic Manager VATSIM Minneapolis ARTCC - 6 -

7 ATTACHMENT A ZMP Area/Sector Map and Frequencies - 7 -

8 ATTACHMENT B SIDs - 8 -

9 ATTACHMENT C Conventional STARs - 9 -

VATUSA PHOENIX TRACON and VATUSA PHOENIX ATCT LETTER OF AGREEMENT. SUBJECT: Interfacility Coordination Procedures

VATUSA PHOENIX TRACON and VATUSA PHOENIX ATCT LETTER OF AGREEMENT EFFECTIVE: 01/08/08 SUBJECT: Interfacility Coordination Procedures 1. PURPOSE. This Letter of Agreement establishes procedures for coordinating