Feedback on ATC Communications and Phraseology Inconsistencies

Hello ATC Team,

I would like to provide some feedback regarding the ATC communications and the phraseology used in Infinite Flight. I understand that consistency is important, but I believe there’s a contradiction in how certain phrases are interpreted by controllers, and this can be quite frustrating for pilots.

Here’s the issue:

When a pilot says “Inbound on the ILS runway XX, it seems understood as the correct phrase to request landing clearance. However, when the pilot then says On final runway XX, which, in essence, is the same meaning (we’re on the final approach), controllers sometimes respond by saying, “You’re already cleared to land, avoid sending unnecessary reports. This suggests that “On final” is not actually incorrect and communicates the same thing.

This creates a contradiction. If On final is considered incorrect, why is it that after stating Inbound on the ILS, repeating On final is seen as unnecessary, and yet still acknowledged as valid information?

What I’m pointing out here reflects real-world aviation communication, where pilots and controllers adapt their terminology based on context. In real-life scenarios, flexibility in phraseology is crucial for effective communication, as both “Inbound” and “On final” essentially convey the same message. The focus on strictly adhering to one phrase in Infinite Flight, therefore, may limit communication efficiency and create unnecessary confusion.

As someone without real-life ATC experience, I do recognize the importance of using clear and precise terminology, but the reality is that, in practice, both phrases communicate the same thing. I feel that the strict adherence to certain phrases, without considering the context, might hinder more efficient communication and frustrate pilots who are simply trying to follow the procedure.

I hope you’ll take this feedback into account and consider a more flexible approach when evaluating phraseology, as the current guidelines seem a bit contradictory in practice.

Thank you for your time and consideration.

Correction ! In this text, I wanted to say specifically that : just to clarify, my concern is not about reporting position after already being cleared to land. My main point is about using “on final” as the initial call to request landing clearance. Some controllers seem to accept it, while others reject it and request “Inbound on ILS” instead. This inconsistency creates confusion because pilots don’t know what to expect. If “on final” is not an acceptable initial call, then there should be a clear guideline stating that. But if it is valid, all controllers should accept it consistently. Mistake of my Part

We send that when the pilot has already called inbound and has been cleared to land. This makes the position report unnecessary, which is why we respond that way.

Some pilots report position as their initial contact with tower. I alongside most controllers don’t mind that, so we just clear them to land as normal.

4 Likes

Since IFS has no “Report establish or Final” it is not close to what in real life or in vatsim reporting on final with a clearance make it unnecessary since ATC knows you’re already in final

To clarify with that reporting position may use if you haven’t have clearance prior to your arrival

If I am wrong let me know that would be a great opportunity to further @CompetitiveDivide320 @Jinco sorry for tagging you folks

2 Likes

Hello!

What Aato said above is correct, and I agree with him. I don’t mind too if a pilot reports “Inbound on the ILS” or “On final” with their initial contact with me, Tower controller. If you do one of the above, I will simply clear you to land. However, if you have already been cleared, and then report position, that would be incorrect and considered as an unnecessary request. The only time I’d accept such a thing is in a pattern scenario. For example, a pilot is flying patterns and, during their fourth circuit, they decide to Full Stop. I already cleared them for the option, but as a courtesy from their side, they say “Callsign is on final runway 05, Full Stop”. In this case, I’d just reply with a “Roger”, acknowledging their “request”, if we want to call it like this.


I have no real-life ATC experience as well, however, I believe that the ATC commands we currently have on Infinite Flight are good enough considering it is a mobile simulator, and some other factors as well. While sometimes a very few commands may sound confusing, or there are still some things missing, for the IF scenario, I’d say every command is clear, and if not, there are enough guides for you to understand everything :)


I’m also sure that with time, there will be plenty of improvements regarding the ATC part of IF, which will definitely improve the quality of the commands (if needed), and increase the variety of what we currently have!

3 Likes

Love the reponse from Jinco above, but adding on: reporting your position after already being cleared to land/option will ping ATC to respond with a flashing orange icon. This needlessly increases Controller workload, which can be detrimental in busy hub operations. Trust me, ATC (Tower) workload can be high when we have to account for runway crossings, clearances, takeoffs, handle any Go-Arounds, monitor approach speeds, etc.

The purpose of announcng inbound vs reporting your position is very different, although I understand the initial confusion.

Calling Inbound

Whether inbound for landing or for touch-and- goes, pilots are expected to use this message because it tells our Tower lads what approach you’ve been cleared by the Approach Controller (ILS/GPS/Visual/Radar Vectors). Although Tower can indeed see this infomation through the ATC UI, this message is certainly more practical and offers more infomation than just your position.

Reporting Position

Reporting your position is primarily done for the reason above, as stated in the User Guide. Otherwise, pilots should avoid reporting their position because it’s simply redundant - ATC has a very clear view of the positions of all aircraft on their frequency.

By the way, the reason why many controllers will reply “Roger” first before sending “you were already cleared to land, avoid unnecessary messages” - is because there’s this big green Roger button on our UI which (for me) I just instinctively press.

This infomation is readily available in the User Guide, which outlines very clearly how to properly communicate with ATC. I don’t see why they should be frustrated.

I hope this sheds more light on this topic, feel free to ask if you have any more questions!

4 Likes

ATC shouldn’t send the “Unnecessary reports” command on initial contact with Tower when a pilot reports their position instead of calling “inbound on the XX” approach.

Although, in a busy airspace, it is does help to say “Inbound on the XX” rather than reporting position, after being cleared by approach, because it saves ATC time. We don’t have to look at the flight strip to see what approach the pilot was cleared for.

The flight strip shows what approach the pilot was cleared for by a Radar controller.

If you are cleared to land, and then report position, Tower can send the “Unnecessary reports” command because it takes up their time to respond with “Roger.” If you’re cleared for an ILS for example, you’re on final on handoff, so saying “I’m on final” could be seen as redundant.

And there’s no way for ATC to ask you to report position currently, if you were curious.

1 Like