Add Callsign Suffix Restriction

Features
,
1

I’m sure many of you who strive for realism will empathize with the extreme frustration I feel when I see an improperly used callsign suffix on the expert server, which is supposed to be (and I know it’s not perfect) the epitome of professionalism. I’m proposing, purely for the expert server (and possibly training too seeing as its purpose is to practice realism outside of the expert server) a restriction/mandatory suffix that must be used depending on the aircraft.

The premise is simple: if a user tries to spawn on the expert (or training?) server with a suffix that doesn’t match their selected aircraft (e.g. attempting to spawn in an A380 with suffix “Heavy”, attempting to spawn in a 767 with no suffix at all, or attempting to spawn in a 747 with suffix “Super”) a warning message will appear that informs the user of their mistake and instructs them to change their suffix according to their aircraft (ideally it would tell the user which suffix to use in case they are unfamiliar with the system, as seems to be the case for many pilots on the sim). The sim wouldn’t allow the user to spawn into the “professional” server(s) with an incorrect suffix.

This would increase clarity and reduce confusion for ATC and other pilots, who, similar to real life, would be able to tell instantly the general size of the aircraft they are dealing with without having to check. As a member of several VAs, I often also find myself flying back to back VA flights with different aircraft and forgetting to remove or add a suffix because I didn’t need to change my callsign.

Theoretically, there should be no opposition to this idea; if you want to fly with an unrealistic callsign, you should be flying in the unrealistic server, and if you want to be realistic (fly in the expert server) you should be as realistic as possible. This proposed feature obviously wouldn’t affect the “Flight of x” suffix since those are unique and subjective cases, and pilots would continue to be able to use whatever suffix they want in the casual server. This should be a universally agreed upon idea to everyone who strives for as much realism as possible; I hope you agree with and vote for it!

2 Likes
2

How about instead of a warning that blocks you from spawning in, the sim automatically sets your suffix depending on the aircraft you’re spawning in with? Obviously, they’d be supressed if “Flight of X” was chosen on the callsign.

1 Like
3

Remember suffix are not used for flights outside US but only for the initial contact which is also pretty much rare as radar controllers IRL can easily identify the aircraft with their callsign which consists of letters and number.

4

to be honest thats something i thought of after which does make way more sense, either option is fine to me

1 Like
5

i have heard it used plenty and continuously in comms all over the world, also if we are going to have suffixes at all they should be used right. if you want to get rid of them altogether (which im totally against) thats a separate conversation

1 Like
6

Well atleast in europe and middle east the call sign for most flights are different from their real number instead they are usually given unique numbers and letters to easily identify the aircraft and also the flow of traffic. If you take a look at the live atc for London or Dubai you will get what I’m saying.

7

i get what youre saying but in infinite flight its standardized to the suffix system and there is no need to complicate things further. ifatc are from anywhere and can control anywhere and they need standardized procedures and practices to be able to work as efficiently as possible

8

Well I want to point out that neither of these airports are covered in Live ATC but you should be able to find few clips on yt. I will prefer IF the way it is but as op mentioned the suffix needs to be restricted to the aircraft they intend to fly or not using at all.

1 Like