I have recently been accepted in the IFATC team and after doing a lot of thinking and controlling these past few weeks, I realised that some simple but useful commands could be added in a next update. I was thinking of the following ones:
“Cleared for takeoff runway xx via intersection xx” would be a command that a controller could use if a pilot requests an intersection departure in order to avoid taxiing all the way down the runway. It could be used by both pilots and atc for example when there is not much traffic. The controller could also respond negatively to the pilot and ask him to taxi down all the way, e.g. when there is a traffic on final.
Of course, this could be used if one day we see taxiway names on airports.
The tower controller should be able to give vectoring instructions (speed, altitude and heading) to more easily handle traffic when approach is not present. Simple instructions are needed, especially for speed. Because, when there is only one runway in use for departures and arrivals, the controller would want to maintain separation between arrivals to squeeze in departures. With speed commands, this could be very useful.
It could be nice for the tower controller to give for example the command “line up runway xx behind the landing traffic” so the pilot is ready to line up once the aircraft passes ahead and can result in a major gain of time in heavy traffic situations.
These are only some ideas that I think would definitely help controllers easing up their job.
- “Cleared for takeoff runway xx from next/desired intersection”.
- “Line up runway xx behind next landing aircraft”.
- Possibility of vectoring instructions for the tower controller (to use moderately).