SCHEDULE (ZLC HOSTED)


The following is a general timeline complete with deadlines and expectations for the ZLC EC.




NOTES:

  • All events and EC actions will be in compliance with the VATUSA Event Division Policy.
  • The EC will check/respond to emails and will check the VATUSA General Staff and Events threads in the VATUSA forums once every 24hrs.
  • It is advised to not schedule an event during or near an AIRAC update due to data conflicts between pilots and the ATC.
  • Do not schedule events on major holidays or on the day of an AIRAC update (+/- 1 day)
  • Active promotion to ZLC ATC about upcoming events is highly encouraged but with caution to not become obsessive is advised.
  • Controllers are expected to be in the ZLC Discord no later than 15min prior to event time or else they forfeit their position and lose their merit.
  • The following schedule will be relevant to each Event Date, minus a specified number of days.
  • Dates will be formatted in DDMMMYYYY time frame. Example: 2DEC2014
  • Time will be represented primarily in Mountain Time as 24hrs time. The Zulu time (and date if it is a different date from the Mountain Time/Date) will be in parenthesis. Duration of event will be shown as well. Example: 14DEC2017 1900MT (15DEC 0200z). Duration: 4hrs.
    • When booking an event near a daylight savings time shift, take into account the change in zulu time. Generally that means:
      • NOV-MAR = GMT-7
      • MAR-NOV = GMT-6
  • ACE Team members participating in an event must be provided with the following resources as soon as a support request is made:
    • ZLC Resource Center log-in credentials.
      • Username: ZLC_SUPPORT_USER
        • The password must be changed to ThankYou4YourHelp! prior to making an ACE Team request.
        • The password must be chaned to Inactive4Now by the end of the next day after an event.
        • To change the password, go to this link and enter the new password. Do not require the user to change the PW on next login.
    • Link to “ACE Team Quick Brief” CBT
      • Link to edit the CBT can be found here and is for ZLC management and ZLC EC eyes only.
    • Discord Server Invite (http://discord.gg/wXBw9Da)




General Ops Schedule/Deadlines

EVENT-90 Days

  • Event draft submission to DATM for approval. Include in the email:
    • Title of event
    • Date and time of event (Including duration)
    • Summary of idea
    • Minimum required positions to be staffed
    • Preferred positions to be staffed



EVENT-70 Days

  • Event Banner submission to DATM for approval. Include in the email:
    • Event Banner in VATUSA aspect ratio standard
    • Event text (including exact format of body and subject line info)
    • Event signup (google form) URL



EVENT-60 Days

  • Create Holding fixes and alias commands. Work with DATM for help. Submit to DATM the holding fix info and alias command. DATM will place the new alias commands into the alias file.
  • Create a “DUPLICATE” off of the ZLC EVENT HOLD TRACKING “DON’T TOUCH” page for this event. Place it to the left in order of events.
  • Event submission to VATUSA calendar.
  • Post event to ZLC/VATUSA Events page
  • Send out emails to ZLC members and visitors inviting them to sign up via the google form.
  • Post the following details to the RC main page, or have the DATM do it. Place this about 8 lines below the “LATEST CHANGE” post. You can also click “Edit” this page to get the formatting codes for this:

UPCOMING EVENTS
NAME: FAKE EVENT CROSSFIRE
DATE: 29DEC2018
TIME: 23:59z-04:00z
PILOT DETAILS:

  • Join ZLC as we do things and stuff like takeoff clearances and PDCs and be all cool and things.
  • Bring your planes and Hot Pockets
  • More stuff.

ATC DETAILS:

  • Don’t Let the Dots Touch
  • Check (link) for more information
  • Sign up here: (link)
  • Whatever else

CRITICAL POSITIONS

  • S56 Stockton <member name who has signed up for it>
  • S56 Lake <member name who has signed up for it>
  • S56 Final <member name who has signed up for it>
  • C33 <member name who has signed up for it>
  • C17 <member name who has signed up for it>
  • SLC TWR <member name who has signed up for it>
  • SLC GND <member name who has signed up for it>

OTHER POSITIONS

  • S56 Gunnison <member name who has signed up for it>
  • C32 <member name who has signed up for it>
  • PVU TWR <member name who has signed up for it>
  • OGD GND <member name who has signed up for it>

ROUTING:

  • KSLC-KDEN
    • RNAV
      • .DENR RUGGD1 PERTY KAMPR LONGZ1
    • Non-RNAV (or doesn’t have new STARS)
      • .DENNR SLC4 OCS MBW RAMMS7
  • The following temporary commands are to be used for the up coming “Cross The Pond (SFO Arrivals) 2020” event.
  • To execute the command, press Keyboard Enter or ASEL.
SyntaxDescriptionExample
3 letter arrival airport RChanges the routing of the selected aircraft to the preferred RNAV event routing.(in the above briefing)
3 letter arrival airport NRChanges the routing of the selected aircraft to the preferred Non-RNAV (or doesn’t have the new STARS) event routing.(in the above briefing)
.THOLD FIX Altitude to hold at EFC TimeWill issue a private message simulating a CPDLC message for holding instructions for fixes listed below..THOLDOCS FL240 0120

HOLDING FIXES

  • RIW
    • Hold northwest on the 280 radial.
      • 25 mile legs.
      • Left turns.
  • OCS
    • Hold northwest on the 280 radial.
      • 25 mile legs.
      • Left turns.




EVENT-30 Days

  • If the minimum and preferred positions are not yet filled, send out another email notification advising that the event will be considered for cancellation if the appropriate positions are not filled within 10 days.
  • If pilot participation is expected to be low (very rare)- Post event to the following media outlets:



EVENT-20 Days

  • If you do not have all of your signups by now, submit an ACE team request.
  • This may serve as the “No-Go” point as well.





EVENT-14 Days

  • FNO’s and Crossfires ONLY: If you do not have all of your signups including ACE team cancel the event.
  • Send out event reminder to ZLC Members and visitors
  • If all required positions are not filled, make mention of the required positions still needing filled and a note that the event will be canceled in 4 days if not filled.
  • Start actively promoting the event in Discord.




EVENT-10 Days
Go or No-Go?

  • If all required positions are not filled by this date, cancel the event and move no further than this line.
  • Send ATC support request to neighboring facilities: ZMPZDVZLAZOAZSE
  • Schedule a 5 day warning, 6 hour warning and “at time of event” warning on ZLC FB Event Page.



EVENT-5 Days

  • Send an event reminder to the invited VAs.
  • Ensure the 5 day warning post was posted and verify the next scheduled posts are still scheduled.



EVENT-30min

  • Be in Discord ready to answer questions
  • Have event briefing ready (METAR, TAF, OPS, last min changes, etc…)



EVENT-10min

  • Give event brief



EVENT-5min

  • Release controllers to their respective channels.



EVENT-0sec

  • All controllers Prime their frequency and the event officially starts.

PREFERRED ROUTES

  • As soon as you are aware of the event that we should support or are hosting:
    • Reach out to the hosting ARTCC and see what routes they will want from KSLC to their featured airports. In the same email, send them our desired routing into KSLC. (We won’t worry about other fields)
    • Once received their preferred routes, tie them into our standard departures routes and create a preferred routing list.
    • Create the routing alias files with the following format example along with the RC post.
    • Send the routing alias and RC post to the ZLC DATM for approval and posting.
    • The ZLC will then add it to the alias file and post the RC post as appropriate.

;SPECIAL EVENT COMMANDS

KFAT RNAV
.FATR .AM RTE DEZRT1 MVA FRA NTELL

KFAT Non-RNAV
.FATNR .AM RTE SLC4 TCH J56 MVA FRA ALTTA9

KRNO RNAV
.RNOR .AM RTE DEZRT1 BAM MYBAD MYBAD2

KRNO Non-RNAV
.RNONR .AM RTE SLC4 LCU J94 FMG



;RC POST DESCRIBING THE COMMANDS

  • The following temporary commands are to be used for the up coming “Let’s Go to Fresno”
  • To execute the command, press Keyboard Enter or ASEL.
SyntaxDescriptionExample
3 letter arrival airport RChanges the routing of the selected aircraft to the preferred RNAV event routing..FATR
3 letter arrival airport NRChanges the routing of the selected aircraft to the preferred Non-RNAV event routing..FATNR

TIME CONVERSIONS

When needed, utilize this site for your time conversions if it is easier www.thetimezoneconverter.com

10MAR2019 07:00z – 03NOV2019 06:59z

UTC (ZULU)MT (12hr format)MT (24hr format)Auckland (24hr format)
1:007:00 PM19:0013:00
2:008:00 PM20:0014:00
3:009:00 PM21:0015:00
4:0010:00 PM22:0016:00
5:0011:00 PM23:0017:00
6:0012:00 AM0:0018:00
7:001:00 AM1:0019:00
8:002:00 AM2:0020:00
9:003:00 AM3:0021:00
10:004:00 AM4:0022:00
11:005:00 AM5:0023:00
12:006:00 AM6:000:00
13:007:00 AM7:001:00
14:008:00 AM8:002:00
15:009:00 AM9:003:00
16:0010:00 AM10:004:00
17:0011:00 AM11:005:00
18:0012:00 PM12:006:00
19:001:00 PM13:007:00
20:002:00 PM14:008:00
21:003:00 PM15:009:00
22:004:00 PM16:0010:00
23:005:00 PM17:0011:00
0:006:00 PM18:0012:00

03NOV2019 07:00z – 08MAR2020 06:59z

UTC (ZULU)MT (12hr format)MT (24hr format)Auckland (24hr format)
1:006:00 PM18:0012:00
2:007:00 PM19:0013:00
3:008:00 PM20:0014:00
4:009:00 PM21:0015:00
5:0010:00 PM22:0016:00
6:0011:00 PM23:0017:00
7:0012:00 AM0:0018:00
8:001:00 AM1:0019:00
9:002:00 AM2:0020:00
10:003:00 AM3:0021:00
11:004:00 AM4:0022:00
12:005:00 AM5:0023:00
13:006:00 AM6:000:00
14:007:00 AM7:001:00
15:008:00 AM8:002:00
16:009:00 AM9:003:00
17:0010:00 AM10:004:00
18:0011:00 AM11:005:00
19:0012:00 PM12:006:00
20:001:00 PM13:007:00
21:002:00 PM14:008:00
22:003:00 PM15:009:00
23:004:00 PM16:0010:00
0:005:00 PM17:0011:00

08MAR2020 07:00z – 01NOV2020 06:59z

UTC (ZULU)MT (12hr format)MT (24hr format)Auckland (24hr format)
1:007:00 PM19:0013:00
2:008:00 PM20:0014:00
3:009:00 PM21:0015:00
4:0010:00 PM22:0016:00
5:0011:00 PM23:0017:00
6:0012:00 AM0:0018:00
7:001:00 AM1:0019:00
8:002:00 AM2:0020:00
9:003:00 AM3:0021:00
10:004:00 AM4:0022:00
11:005:00 AM5:0023:00
12:006:00 AM6:000:00
13:007:00 AM7:001:00
14:008:00 AM8:002:00
15:009:00 AM9:003:00
16:0010:00 AM10:004:00
17:0011:00 AM11:005:00
18:0012:00 PM12:006:00
19:001:00 PM13:007:00
20:002:00 PM14:008:00
21:003:00 PM15:009:00
22:004:00 PM16:0010:00
23:005:00 PM17:0011:00
0:006:00 PM18:0012:00