Choose the right flight simulator ATC callsign for GA, airline and online flying, with setup rules, radio examples and fixes for common errors.
Use the callsign that matches your aircraft and flight plan: a registration for general aviation, or an official airline telephony designator plus flight number for an airline service. In Aviation & Real-World Flying scenarios, enter that same identifier in the simulator or network and say it in full on first contact.
Which ATC callsign format should I choose?
The correct format depends on the type of flight you are simulating.
| Type of flight | Enter or file | Say over the radio |
|---|---|---|
| General aviation | The aircraft registration, normally without spaces or punctuation, such as GABCD or N123AB | “Golf Alpha Bravo Charlie Delta” or, under common US phraseology, “Cessna One Two Three Alpha Bravo” |
| Airline service | The operator's ICAO designator and flight number, such as BAW123 | The official telephony designator and number: “Speedbird One Two Three” |
| Business or charter flight | The registration unless the operator has an assigned ICAO designator | The registration, or the operator's official telephony callsign and flight number |
| Military or special operation | The callsign assigned by the scenario, unit or controller | That assigned callsign, subject to the simulator or network's rules |
Do not confuse an airline's two-letter commercial code with its ATC identity. British Airways flight BA123, for example, may be identified as BAW123 in a flight plan and spoken as “Speedbird One Two Three”. A livery alone does not establish that radio identity.
If there is no official operator callsign, we recommend using the aircraft registration. Also, “November” is the nationality prefix for a US N-registered aircraft; it is not a generic callsign for every light aircraft.
How do I enter and transmit the callsign correctly?
Set one identity before starting the flight, then use it consistently in the aircraft settings, flight plan and every ATC transmission.
- Choose the identity before loading or connecting. Use a registration for a private flight. For an airline flight, choose the correct operator designator, telephony name and flight number.
- Fill the fields according to their labels. A simulator's “airline callsign” field may expect
Speedbird, with123entered separately as the flight number. An “aircraft identification” field may instead expectBAW123. Do not enter the flight number in both places unless the software specifically requires it. - Match the flight plan. The callsign used by ATC should match the identifier attached to the filed or loaded plan. Online controllers see the connection callsign, so a mismatch can produce corrections or confusion.
- Use the full callsign on first contact. Include it with your position and request, then place it at the end of readbacks as local phraseology requires. Our guide to making clear ATC radio calls in a flight simulator covers the rest of the exchange.
- Shorten it only after ATC does. If the controller changes “Golf Alpha Bravo Charlie Delta” to “Golf Charlie Delta”, you may use that shortened form. Airline callsigns are not normally abbreviated. A controller may also require the full identifier when similar callsigns are on frequency.
Microsoft Flight Simulator's built-in ATC derives its spoken identity from the configured aircraft and flight details, not reliably from the selected paint scheme. The exact fields vary between simulator versions, so check how callsign and flight-plan settings feed Microsoft Flight Simulator ATC rather than assuming the livery has configured them.
Heavy and Super are wake-turbulence suffixes, not part of the basic aircraft identification. Use one after the callsign only when the aircraft and applicable procedure require it. “Mayday” is a distress signal, not a callsign.
Why is simulator ATC saying the wrong callsign?
An incorrect spoken callsign usually comes from mismatched fields or a text-to-speech limitation.
- ATC uses the tail number instead of the airline name: the airline callsign or flight-number field is blank, unsupported or was entered after the flight loaded.
- ATC repeats the flight number: the number was included in both the callsign field and the separate flight-number field.
- ATC spells an airline code letter by letter: the simulator cannot map that code to an official telephony designator. Select a recognised callsign from the available list or fall back to the registration.
- The livery and radio callsign disagree: repaint files often change only the aircraft's appearance. Set the ATC identity separately.
- An online controller sees another identifier: the callsign used to connect does not match the flight plan. Correct it using the network's amendment or reconnection procedure.
- An old callsign persists: some simulators do not apply identity changes to an active flight. Set the fields before departure, then reload or reconnect if necessary.
Can I invent a callsign for online ATC?
You may use a fictional callsign only when the online network permits it and its format follows that network's rules. The connection identifier and filed flight plan must still match, and you should not use reserved government, emergency or special-purpose callsigns without an appropriate scenario.
For an airline operation, use the official ICAO operator and telephony designators rather than inventing a spoken airline name. For general aviation, a plausibly formatted registration is usually the cleanest choice. Network procedures differ, so review our practical guidance for flying with live online controllers before connecting.