LC/GC/CD Tracking once dropped

[Kyle Sanders 2]

Some of our local controllers like to use vERAM when working TWR and below.

I have noticed that when GND is the one that assigns the beacon code (during clearance delivery or some other time while the aircraft is still on the ground) and DEP terminates the track later on, it defaults back to GND tracking them.

Is there a way to create an exception that won't allow GND or DEL positions to track the target once it is dropped by someone else?

[Ross Carlson 189]

Is the GND controller using a suitably-low vis range?

[Kyle Sanders 2]

20 miles. Should he take it lower?

[Ross Carlson 189]

It sounds like what's happening is the DEP controller is dropping track while the aircraft is still within GND's vis range, and GND then auto-tracks the aircraft. If GND sets the vis range to something less, like 5 NM, such that the aircraft is out of range when DEP drops track, the issue shouldn't happen.

I'll take a look at the code, since this shouldn't be happening anyway. If the aircraft is tracked by another position, it should make the aircraft no longer eligible for auto-acquisition in ERAM. You probably are running into a bug that's been there since the start, and it just hasn't been encountered because most people don't use vERAM for GND. 

[Kyle Sanders 2]

Haha... a large portion of ZLC are now using it at the lower levels, as it works just fine for those positions and it gets them ready to use it comfortably in the enroute environment. We are developing our vSTARS facilities and will be offering that as well soon.

We will have them reduce the visibility range until this can be checked out in your code. Thanks! 🙂