Thank you so much, @schyllberg, always for your time and help!
It happened to me with the same controller
1 Like
Hello and good day, @schyllberg and @Jan . I’m sure it’s a bit of a technological process of resetting a server, but just informing you that it appears it shows the controller being active for 18 hours again.
And this is why technology—unfortunately—can be so nice and yet so troublesome, but same controller and same username active for 6 hours “controlling” New York Approach and New York Departure.
Hello @Jan and/or @schyllberg it appears KLAX Tower on TS shows a “stuck” controller for 10 hours. Thank you and the team in advance!
Inactive tower and I am assuming ground controller at KLAX for 24 hours.
Hello and Good Day,
It appears a very responsive ground controller is apparently active now for 21 hours and counting at KJFK.
Active for 3 hours, attempted to contact by other users and no response given. @moderators
I know this is very off-topic, but what software is that?
It’s InfiniteInfo and can be found under ThirdParty.
Thanks so much!
1 Like
In TS, such situations occur frequently, as most of the ATC players are either beginners or practicing how to become standard ATC players.
Thanks for your reply, though I am aware as @schyllberg said earlier in this post: Inactive Controller at KJFK on Training Server - #22 by schyllberg. I was just trying to point it out for a pretty busy station for people who are trying to learn the complex procedures of ATC, though would you, @Zedrist , say it is an extremely ineffective learning environment to be controlling for 18+ hours? In addition to that, in the real world according to the Bureau of Labor Statistics, “Controllers may not work more than 10 straight hours during a shift, which includes required breaks, and must have 9 hours of rest before their next shift.”
Kind of sad that KSEA isn’t staffed more often. Anyways, I was controlling KPDX because it’s not too long of a flight from SFO, though I failed to realize that KSEA shows “active” for 20 hours. @schyllberg @Jan No worries! Obviously I’m aware it’s a server/technology issue, just thought I’d inform.