Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - Brin Brody

Pages: [1]
1
News / New EC in ZJX!
« on: April 02, 2020, 06:39:38 pm »
Congratulations to Maxine Grooms, the new EC for Jacksonville! Maxine brings great enthusiasm and experience with her, and is eager to continue learning in her new role on the VATSIM network. Maxine also has a strong sense of leadership and can’t wait to expand upon that in her new role. Congratulations Maxine!

2
News / Jacksonville has a new Events Coordinator!
« on: December 15, 2018, 04:44:21 pm »
It is my pleasure to announce Elai Kindler as the new Events Coordinator for Jacksonville. Elai joins us from Anchorage, where he previously served as the Events Coordinator. Elai has some great ideas for some new events, and we are looking forward to seeing them in action. Congrats Elai!

3
News / Jacksonville has a new Webmaster!
« on: November 07, 2018, 04:41:40 pm »
Congratulations to Dillon Marshall, the new WM for Jacksonville! Dillon brings great web development, and ARTCC staff experience with him, and is eager to continue learning in his new role on the VATSIM network. Dillon also has a strong sense of leadership (gained from his experience as the HCF EC, and a mentor there), and he can’t wait to expand upon that in his new role. Congratulations Dillon!

4
News / Position Vacancy: Jacksonville Facilities Engineer
« on: November 01, 2018, 06:29:06 am »
We're building a visionary ARTCC at Jacksonville. To help build this ARTCC, we're seeking a qualified, professional, and motivated individual to fill the role of Facilities Engineer. In the next few months, the individual will play a critical role in revolutionizing Jacksonville's facility files, to provide our controllers with the best experience possible.

Key Responsibilities
- Maintaining an online presence within the facility and on the VATSIM network.
- Attending staff meetings.
- Maintaining and updating sector files for all approved ATC client software, updating at least every other AIRAC cycle.
- Maintaining vATIS configuration files.
- Maintaining POF and alias files.
- Coordinating with adjacent ARTCCs as required, specifically relating to frequency issues.
- Ensuring established SOPs and LOAs are fully represented within sector files and other procedures.
- All other responsibilities which help to accomplish the mission, goals, and vision of ZJX.

Key Requirements
- Have knowledge of VRC, vSTARS, vERAM, and vATIS.
- Possess a high degree of energy and commitment appropriate to the requirements of the position.
- Have no significant disciplinary record.
- Have no history of unprofessional behavior.
- Be in good standing on the VATSIM network.
- Be a home controller at the time of appointment.

To apply, please send your cover letter, resume, and goals/ideas you would accomplish if appointed to atm@zjxartcc.org and datm@zjxartcc.org by November 8, 2018 at 0000z. Qualified applicants will be asked to interview with key ARTCC staff.

5
The Control Room Floor / Descents Between Facilities
« on: September 09, 2018, 06:07:27 am »
Hi, everyone!

I've noticed, recently, a few cases in which various controllers have different opinions on how to keep track of altitudes on aircraft, specifically in the enroute environment. Typically, this will take the form of a controller issuing an aircraft a descent to enter terminal airspace of some kind, descending them to comply with a border-crossing restriction per coordination/LOA, or similar.

I've heard arguments for (and seen) the use of both updating an aircraft's hard (cruise) altitude, or updating an aircraft's temporary altitude.  Please answer the poll, and choose the one you use most for descents

Have an opinion that addresses WHY you use one rather than the other?  Would love to hear it.  Thanks.   :)

6
Anchorage (vZAN) / [APRIL FOOLS] ZAN New Monthly Hour Requirements
« on: March 31, 2018, 09:00:01 pm »
Controllers,

As of April 1, 2018, all controllers will be required to complete 25 hours of ZAN controlling time per month.  Many controllers have proven that they are able to complete their necessary hours in the time allotted, and more.  In order to try and provide more constant service to the pilots of ZAN, we have increased the hour requirement, to ensure staffing.  We are confident that we will be able to provide 24/7 coverage to all users of the Alaska FIR airspace, following this change.  Questions, comments, or concerns should be addressed to the ATM (atm@vzanartcc.net).  If you feel you are unable to complete these new requirements, please contact the ATM NO LATER THAN APRIL 10TH to request an exemption. Thanks for making our ARTCC team great!

Warm Regards,
ZAN Staff

7
The Control Room Floor / VATUSA Controller Cooperation - Not Correction
« on: December 08, 2017, 05:37:15 am »
Fellow VATUSA Controllers,

There’s a saying that states “do not walk into someone else’s house and...”  This is typically followed by an action that is socially unacceptable when in someone else’s home; their “airspace”, if you will.

This post references an issue I have seen several times both as a pilot and a controller inside VATUSA.  Some controllers, like myself, love to share their knowledge with other controllers at other ARTCCs, most of the time in an effort to benefit everyone involved.  I find this knowledge sharing to be often helpful, with controllers (doubling as pilots at the time) explaining to me a part of my airspace that I am less than familiar with.  The same applies to control methods or phraseology mistakes/shortcuts.  As a general rule, I have found it is a great idea to either research or discuss their suggestions with your facility staff, in order to maximise controller knowledge and adaptability.

This, by itself, is not the issue.  The issue is with the way some people choose to present this knowledge.  Some feel it necessary to, on an active voice/text frequency, to correct the controller.  They do this in a variety of ways including complaints on frequency or statements such as: “I’m not sure why you’re giving me vectors all the way out here, are you working some large amount of traffic I don’t see or hear?”  Nearly every controller on VATSIM has run into a pilot/controller who thinks they should share their knowledge with you in this way.  It is not only annoying but quite disrespectful to do this on frequency (to both controllers and to ARTCC staff), in addition to disrupting activities on frequency.

Fortunately, on VATSIM, we possess many tools for communication that are not possessed by FAA air traffic controllers in the real world.  These tools include:

  • Feedback pages
  • Chat boxes
  • Websites with direct email links to staff

All three of these tools are easily accessible and can be requested by the pilot to the controller at any time.  Many controllers have their ARTCC feedback page in their controller ATIS.  A link to a staff page is also sometimes found in the same place.  To send a controller a private chat message, .chat CALLSIGN or .msg CALLSIGN MESSAGE are also options.  These methods are private ways to communicate correction and/or instruction to controllers, without disruption or disrespect on frequency.

I certainly appreciate those who come onto the network looking to correct me… I am far from an excellent controller, I might go so far as to say that I’m not even a good one yet.  I am happy, as I’m sure others are, to accept constructive criticism and instruction from those better informed than I am.  It should be at the forefront of everyone in this division’s mind that we are here to serve each other:  Anything we say or do should be to benefit those around us.  Air traffic controllers are responsible for thousands of lives every day…  It obviously takes someone selfless (or crazy) to do the job.

The message here is as follows:
Controller cooperation is always better than controller correction.

As controllers, we should strive to not be the guy that manages to make everyone in a particular ARTCC want to log off when they see you because you have a history of insulting and/or correcting their controllers on frequency.

As staff members, we should strive to explain and reinforce these ideas of cooperation amongst our controllers.  Though you may not realise it, you, as an ATM, DATM, or TA, have the power to shape how your controllers think and act while on the network.  The goal should never be to be “the best ARTCC”, but rather “the best division”. 

But whoever said anything about friendly competition? ;)

I look forward to everyone’s thoughts on this.

8
VATUSA Pilots,

As of late, I have noticed that pilots will, quite frequently, either file or accept routes that they are unable to fly.  While it is common practice for controllers to assign preferred routes to pilots, it is the responsibility of the pilot to determine whether or not they can accept it.  Similarly, software such as simbrief or skyvector provides recommended routeings to pilots.  If you are unable to fly the route provided by this software, please do not file it, and instead, find a route that you are able to fly.  If a controller tries to assign you a route you can't fly, don't be afraid to use the word "unable".  Making this changes before you get off the ground makes it easier for both you and controllers further down the line.

Thanks.

9
Events / Alaskan Tri-Shuttle: Civilian [18 JUN, 22:00z-02:00z]
« on: May 16, 2017, 05:27:02 pm »

Join the Anchorage ARTCC as we bring you the first part of a two-part series of our Alaskan Tri-Shuttle event.  On June 18th, from 22:00z (18:00 EDT) to 02:00z (22:00 EDT), we will be staffing up Ted Stevens Anchorage International, Fairbanks International, and Juneau International to provide full services to you and your passengers.  Fly any aircraft, big or small, to deliver your passengers, and your cargo, where it needs to be when it needs to be there, with some excellent control along the way.



PREFERRED ROUTINGS

PANC-PAJN:
 NOEND3 NOEND YAK J451 SSR

PANC-PAFA:
 CAWIN LIBER2 

PAFA-PANC:
 PUYVO2 PUYVO KROTO3 

PAFA-PAJN:
 RDFLG2 RDFLG J502 SSR

PAJN-PAFA:
 JNU5 SSR J502 RDFLG HRDNG2

PAJN-PANC:
 ASORT2 ASORT JOH WITTI2 



See you in the skies!

10

The Anchorage ARTCC is pleased to announce Arctic Entry, our Friday Night Ops event. Join us on August 11th 2017 from 2345-0400 (1545 AKDT, 1945 EDT). Come help us make Anchorage International (PANC) the busiest it’s ever been!

Please file the below routes:

PANC-PAFA
   CAWIN LIBER2 (RNAV)
   ANC8 BGQ V438 FAI (Non RNAV or low altitude – 10,000 min)

PAFA-PANC
   PUYVO2 PUYVO TKA TAGER8 (RNAV)
   MKNLY1 TKA TAGER8 (Non RNAV or low altitude – 10,000 min)

PANC-PAJN
   ANC8 JOH J501 YAK J541 SSR

PAJN-PANC
   ASORT2 J541 YAK J501 JOH WITTI2 (RNAV)
        ASORT2 J541 YAK J501 JOH YESKA6

PANC arrivals from the US and Canadian west coast as well as southeast
Alaska – Plan this final route segment:
   YAK J501 JOH WITTI2 (RNAV)
        YAK J501 JOH YESKA6
   

The event includes a Friday Night OPS on the evening of the 11th ONLY.  It previously contained a tour of the Anchorage ARTCC on the following Saturday, but having lost its status as a live event, no longer includes this.

11
Events / Crossfire: Anchorage-Vancouver
« on: March 23, 2017, 08:35:28 am »

The Anchorage ARTCC and Vancouver FIR invite you to come join us for an evening of flying along the beautiful British Columbian and southern Alaska coastline. The Anchorage ARTCC and Vancouver FIR will provide ATC service for this crossfire event starting at 23:00 Zulu on Saturday April 29th. See you there!
 
Preferred routing:
Northbound – YVR9  QQ  YZT J523 YZP J501 JOH   
Southbound – JOH J501 YZP J523 YZT WHSLR4
 
Scenery options:
Orbx Southern Alaska and Pacific Northwest available at https://orbxdirect.com/
CYVR by FSDreamTeam available at http://www.fsdreamteam.com/

12
Hi, everyone!

I'm currently training for C1, so I will be able to begin controlling Anchorage Center positions...  In my training, I found this:

https://web.archive.org/web/20100620051252/http://www.vatusa.net/training/tiki-index.php?page=c1_issuing_altitude_and_crossing_instructions

Part of the C1 old VATUSA Training resources, at the bottom of the page, it teaches 2 different formulas to decide how many miles from the airport an aircraft should begin their descent.  Though many center controllers, I'm sure, "eyeball it", as it's simply easier, for those of us who might like to follow the numbers,
I've tried to make it a little easier, with some JavaScript:

https://jsfiddle.net/gx9w3jks/

When you enter this web page, it will present you with a series of dialogs asking you to enter various pieces of information that will be required to find the number of miles from the airport that you need to begin descending your aircraft by.

I tried to make this as user-friendly as possible, but if anyone knows of a better place to host this piece of JavaScript to increase that, please let me know.  I will begin working on an executable version using Visual Basic, which will be released soon.  I also welcome any and all suggestions you guys might have.  Thanks.

13
General Discussion / VATSPY Anchorage ARTCC Code
« on: November 04, 2016, 04:12:28 pm »
Hi everyone,

I recently downloaded VATSPY and have begun to use it.  I've gotten it all set up to have PANC as the airport it watches, however I can't seem to find the ARTCC code for the Anchorage ARTCC.  Does anyone have the code that I can plug into it to be able to see all arrivals and departures?  Currently I'm stuck with the default, Boston ARTCC.  Thanks.


-Brin Brody (BT)

Pages: [1]