Correlated aircrafts gets uncorrelated between controllers

[Even Rognlien]

Using correlation mode C

Why do we often have to correlate aircrafts that already are correlated by other controllers and have a squawk code? Is that realistic or is it a bug?

 

I have also noticed that when I'm mentoring for my APP student and he correlates an uncorrelated aircraft and give him a squawk, the tag is still uncorrelated on my own screen. Have I misunderstood how the correlation system works, or..?

[Michael Pike]

Are you sure the other controller has the radar and flight plan correlated? If they are using Mode S, it could be correlated that way. I would focus on looking for why it is not correlated on your scope. Make sure the [Mod - Happy Thoughts]R field ([Mod - Happy Thoughts]igned squawk code) is present in the list the aircraft appears in and look at the tag you expect to be correlated - is the code the same? I sometimes find the code the pilot has set is slightly different from the one [Mod - Happy Thoughts]igned.

 

If you manually correlate a blip with a flight-plan that has no [Mod - Happy Thoughts]igned code, using the drop down "correlate" function, that only works on the local scope obviously.

[Stephan Boerner 945550]

Correlation (and uncorrelation) happens only on your PC. The servers do not support it.

 

The only way another controller can influence your correlation is for example if you are using C correlation and he does not or does not require unique squawks, and therefore he does not correct incorrectly set squawks. Your ES does not know if he uses Easy Mode or if he manually correlated an aircraft. If it's a match on your ES, then it is correlated. If not, it's not, so you can never see if a student correlates an aircraft, unless you connect into his ES via proxy.