Air Traffic Controller Discussion With a Global Perspective
By Owen Catherwood 903683
#40419 Part of the problem which should be solved (or reduced quite a bit) by the multi-repeater setup on sectors is that we as controllers have to set our range towards the center of the sector, but at the same time the range must be set so we can "see" the border of the farthest point from the middle + about 20nm to accept handoffs. Yet when this happens, we also go quite a bit out into other sectors. For example, for Seattle center I set my visibility to about 400nm which just reach the extreme NE and SW corners of the sector. Yet at the same time, due to how the airspace is set, I see a good 200nm of Salt Lake center's airspace. With the repeaters the over-coverage of other sectors can be reduced, while still reaching the far-out sections of the home sector.
By Alejo Ellero 932833
#48175 Few days ago, a supervisor call me ASRC when i was controlling in Argentina, asking me to reduce my visibility range; so I did it, with no complain.

The problem was that I never knew that rule. In my tutorials and manual I´d never seen some topic related to the adjustment of the visiblity range, so it should be very usefull to notify this recomendation by NOTAM.

Thanks for your attention, and sorry for muy english... :D

Alejo.
By Tavis Walters 919400
#83403 My two penneth on ranges is that they should be set with a little judgement with regards to position. Hence:

DEL/GND 10NM
TWR 20NM
APP 40-60NM

CTR or TMA positions need to se their ranges according to the amount of airpace that they control. The same applies to APP. If we can save on bandwidth, it will stop crashes and dlowdowns on the network

Regards

Tavis Walters
S3 Midlands RTS
Vatsim UK
By Ruud op de Weegh 851729
#109055 Hello everybody,
Richard Jenkins 800012 wrote:Controllers,

When logging in please be sure to set the appropriate visibility range for the position you are manning.
General rule:
10-20 nm for DEL/GND
30-50 nm for TWR
100-150 nm for APP/DEP
300-600 nm for CTR

It is a logical thing...sure. But as observer of a Center position I had my range at the same range as a Center controller. It did not take long before some guy asked me to reduce to 40 nm. But how can I observe a Center Controller at this range? So nobody wrote about the observer range. Please advise for which I thank you in advance.
By Aaron Cannata 811277
#109140 Observers range should match the area that they are watching.

When watching a huge CTR/FIR sector, with the new ASRC and VRC you can set up multiple visibility points

.vis
.vis2
.vis3

and space them around your sector file. Be sure to reduce the size of your range from 600nm to that which is appropriate.

Aaron "AX" Cannata
By Ruud op de Weegh 851729
#109666
Aaron Cannata 811277 wrote:Observers range should match the area that they are watching.

When watching a huge CTR/FIR sector, with the new ASRC and VRC you can set up multiple visibility points

.vis
.vis2
.vis3

and space them around your sector file. Be sure to reduce the size of your range from 600nm to that which is appropriate.

Aaron "AX" Cannata

Thanks for your reply, but I am looking for an official VATSIM document about this. As I was ordered to reduce my range to 40nm observing the TNCF FIR I was not able to observe anymore. I use to have my range to max 400nm as observer for the whole FIR as well as for controlling as Center
By Mark Richards 811451
#163129 Fellow Controllers:

Probably time to BUMP this posting again to remind Controllers about checking their range settings.

I had just over two hours online this morning as NZCH_A_CTR but was conducting SUP checks at the same time and asked no fewer than 38 Controllers to reduce their range settings.

What is not mentioned is that OBS (including Instructors, ATMS, etc) should ideally not need more than 300nm range settings.

Reducing range settings really help to reduce bandwidth and therefore cost to the members who provide the servers free of charge for us all to enjoy!

Thanks in advance

Mark
By Joe Caban 844086
#212692 Can we have this stuff posted in a policy section somewhere? I was told the limit for APP was 200 by a member of VATUSA. I had my settings at 160 and was asked to reduce it to 150 on a night where there were a total of 338 members connected to VATSIM. It is obvious that know one really knows where to find this one forum post. If this is the official "policy" I will make sure we have it correctly reflected on our website and training materials.
By Thomas Mathieu 998318
#212694 :oops: I have been guilty before manning an app position with my center settings. I have now setup VRC for each position that I work so I am straight with the vis ranges when I log on :D
By Steve Ogrodowski 876322
#212698
Can we have this stuff posted in a policy section somewhere? I was told the limit for APP was 200 by a member of VATUSA. I had my settings at 160 and was asked to reduce it to 150 on a night where there were a total of 338 members connected to VATSIM. It is obvious that know one really knows where to find this one forum post. If this is the official "policy" I will make sure we have it correctly reflected on our website and training materials.


Maybe that's necessary. It's always just been managed by local facilities. In my five years with ZOB, we have always taught and posted the Radar ranges necessary to control any of our facilities. It's not a policy...it's just a decency thing (to minimize any excess strain on the server) (unless people do consider this Sticky a policy). The only problem with setting a "global" policy is that it can vary from place to place. All you could really do with a Global policy is say "Each Division shall ensure proper radar ranges be utilized by local ATC. Because of all the possible range needs by any given facility, all actual values shall be set by each local facility."

For instance, your APP necessity might be 160-200NM. At any single APP facility here at KZOB, the most you need is 90-100 tops (that's even to have enough lead time to accept handoffs). I would never tell any of our APP controllers that it's okay to have a range higher than 110 miles (I recommend 95 miles anyways).

Not that it matters very much when we only have 340 members online...it gets a lot more important I think upwards of 450 to 500. Consistency, though...we should always pay attention to this. I know that when I switch positions using ASRC I don't always pay attention to it. VRC makes it easier because I can save each profile for each position.
By Daniel Gustin 940540
#212702 Yea I was bumped today after trying to configure my Eurocenter Profile on VRC. Thing calls for 600nm range.........
By Aaron Cannata 811277
#213507 Plus remember there is a bug in the server that Ross Carlson is trying to track down that will sometimes show LAX TWR on the Controllers List on the other side of the world. It's NOT a range issue. It's a bug.
By Mike Evans 822396
#213534 That bug only manifests when the servers split & reconnect.. it's a byproduct of the servers trying to resync with each other.
By Brendan Samson 1070087
#274498 How much bandwidth does a 10 mile vis range compared to a 300 mile vis range use?

How much $$$ does it cost vatsim for a controller with a 50 mile vis range over 1 hour?