This latest update came with a rework of the general aviation callsign system. It’s now far more realistic, adding country specific (callsign prefixes? Is that what they’re called?). The problem with this, however, is that you can no longer create a fully custom callsign. I didn’t have an issue with this, until I realized that I could no longer input an ICAO code for an airline who’s callsign is missing in the callsign menu. If that last sentence confused you, let me give an example.
I was planning a flight from Manila to Phnom Penh in Cambodia with JC International Airlines. It’s a small-ish airline for a small-ish country, so I didn’t expect to find the airline in the callsign menu; I didn’t.
My workaround for this used to be I would go to general aviation and use the ICAO code of the airline followed by the flight number as my callsign. In this case, that would be JCC8661. I can’t do that anymore; I’m required to use a prefix (unless I’m just missing something, please tell me if I am). There’s no prefix that starts with JCC, so I’m forced to either use an incorrect airline callsign, or use an incorrect country code as my callsign.
If this was a one time thing I wouldn’t be bothered, but I like flying to lower demand unusual places, a lot of which are operated by smaller airlines not included in the airline section of the callsign menu.
Is there a work around to this, or should I make a feature request to bring back the ability to create a fully custom callsign?
Edit: I can see why we can’t do fully custom callsigns, so I thought of a workaround for that: