Congrats, Odinn! Thanks for stepping up.

Pilot Brief Available here: https://goo.gl/dyQuHH

All pilots,

FNOverly Cooked Turkey is tomorrow night. A few reminders to consider prior to flying this event:

• Please look over the pilot briefing provided above.
• Have updated scenery that includes Runway 11/29. This can just be an AFCAD. Having this runway will allow us to double our arrival rates into the airport. Please indicate if you have updated scenery in your remarks, and if you would like, on initial contact indicate that you have 11. (Arrivals from the south only)
• PDC's will be issued to all CPDLC capable aircraft. If you do not receive a PDC, or are not CPDLC capable, please call delivery for your voice clearance. (You will most likely need an amended route if you're CPDLC capable and you didn't get a PDC)
  
• It is VERY important that on initial contact with the first approach controller and ground controller that you have the current ATIS info.

ZKC looks forward to seeing you tomorrow night!

Brian,
Welcome to VATUSA!
I sent you instructions and additional information about getting started through the support ticket, you filed earlier today.

First off, if have stated something that has already been brought up, just let me know because of the rapid responses to this thread. I personally don't really believe in the N/E/S/W idea. It serves a purpose, yes, but also there are much more sector splits in sophisticated TRACONS that can't be described with just directions. For example, how would you describe many of the Satellite sectors. If east Satellite of St. Louis has a STARS id of "Z" how would you even go about describing that in a controllers call sign. Along with Center, I think having actual numeral sector Id's is the best policy. Here at ZKC, we take multiple real sectors, combine them into one, and take one of the ID's (Picture Below). If I were to just make my call sign KC_W_CTR there is no way a pilot would know where that sector begins and ends. The ATIS maker is still probably the best tool we can use to get the information to the pilots. If they don't use the ATIS maker info. that's on the pilot. As stated above by someone, how does a pilot know how to find the right frequency in an event? I think the use of a pilot briefing is the best way. If you click Here, you can see that we have laid out all of the possible staffed positions for a particular FNO, and their frequencies. I know this doesn't actually provide a visual of the airspace split but it's a starting point. Each ARTCC could provide a Pilot airspace visual on their website, but who says every pilot will go there and search for such information.

Thoughts?

Center splits for FL240 and below:

Congrats Clifford!

Congrats, Russell!