The controller change process is a great addition to IF, but it could be more effective if the following changes were implemented.
- At the present time, when the announcement is made, and the outgoing controller closes, his status doesn’t change for somewhere around 30-45 seconds. During this time, the new controller is unable to open, as the frequency is shown as still occupied by the outgoing controller.
This status of the controllers frequency seems to be a polled function, that occurs at a very slow rate. This is reasonable to cover short outages that might occur with a controllers internet connection, or maybe even to allow a controller to quickly check something by putting IF in background for a few seconds. But when a controller actively closes a session, that ought to cause an event that propagates to the server, which is immediately sent down to all devices. This would allow the new controller to takeover within a few seconds of of the outgoing controller closing.
- As traffic increases, it sometimes becomes necessary for a controller that was handling tower and ground to release one frequency so another controller can help by splitting the load. Instead of one controller handling both frequencies, you have a separate controller for each frequency. Unfortunately, there is no convenient way to quickly release one frequency. The current active controller has to exit and wait the time described in #1 above before he can come back in with only one frequency, leaving the other frequency open for the new controller.
If the feature described in #1 is implemented above, it would go a long way toward solving this issue. A better approach would be for the current controller to be able to drop one of his frequencies without leaving the controller session at all! He would announce controller change on the frequency he wants to close, then close it, without closing any other open frequencies.