I would like to change the way ATC refers to my various aircraft to be more in line with the real world. There are currently two things wrong with ALL of my non-airline aircraft callsigns:1. FSX has all ATC communications always using the entire, cumbersome registration letter-number-letters string: "November 6645 Charlie." Based on my real-world experiences as an instrument-rated Commercial pilot, this is NOT how things are done. If I'm flying N6645C, my initial call for clearance would be "Podunk Ground, Baron 6645 Charlie, instruments to to Boston Logan, clearance." The initial "N" would never be used except by ATC when reading the clearance to me, and they have to do that because the clearance is a legal "document." On all subsequent calls to Ground, Tower, Departure, Centers, Approach (etc. etc.), my callsign would INVARIABLY be shortened to "Baron 45C" except in the EXTREMELY rare situation where ANOTHER "45C" was on the same frequency at the exact same time- I have heard this ONCE in 46 years of flying- and even then the initial "N" was not used- it was "Listen up: Baron 6645 Charlie, descend and maintain 7,000. Bonanza 9845 Charlie, contact Denver Approach on 126.75." Not a "November" in sight. 2. ATC always prefaces every call with the manufacturer's name. For example (using the above fictitious registration numbers just to illustrate), my 172 is "Cessna November 6645 Charlie" and my Citation is also "Cessna November 6645 Charlie" because it is, in fact, made by Cessna. In the real world, my 172 would, indeed, be called "Cessna 6645 Charlie" and "Cessna 45C" (see #1 above) but my Citation would be called "Citation 6645 Charlie."I just installed the Carenado PA-32R-301 Saratoga, and it's driving me nuts to hear ATC (and "myself") on the radio continually blathering out "Piper November 2855 Kilo" when in fact it should be "Saratoga 55 Kilo."Patting myself on the back in advance for my legendary ingenuity, I edited the aircraft.cfg file to add the lines "atc_airline=Saratoga" and "atc_flight_number=55K" because I have been able to fix the callsigns on other aircraft (the MAAM-SIM DC3's) this way. Unfortunately and inexplicably, this hack didn't work on the Carenado PA-32R-301 file even though I added the lines in the separate sections for all 4 versions of the aircraft. So I have concluded that somewhere else in the file these options are disabled, or at least not explicitly enabled.Does anyone know how I can begin to troubleshoot why I can't fix the callsigns in the Carenado aircraft.cfg file using atc_airline= and atc_flight_number= as I have successfully done with other aircraft? Are there prerequisites to these lines having any effect? A "switch," perhaps, where I need to change a zero to a one or whatever?

ahah another person annoyed by this...I'm a controller and we do use "N12345" but mostly its the aircraft type then the numbers/letters after the N like you said.As far as FSX goes, for some reason I've noticed the entry in the CFG does not equate to the callsign used in game ????So in the aircraft selection screen you click on the paint you want, click details, and then in the tail number, just put the callsign, WITHOUT the N. For instance, we have a local C172 at work, N738JX. So in FSX I put the tail number as 738JX. That way the FS ATC always says "Cessna 738JX....."

ahah another person annoyed by this...

Yup. Thanks for the company!

I'm a controller and we do use "N12345" but mostly its the aircraft type then the numbers/letters after the N like you said.

OK, so you're saying that N12345 would be (for example, if it was a C172) "Cessna 12345" and not "Cessna 345?" Honestly, I only hear the full set of numbers when there's a problem, i.e. multiple a/c with similar last-3's, or when one of us has fubared something... in which case we WILL hear "CITATION NOVEMBER 12345, HOW DO YOU HEAR THIS FREQUENCY?????" (translation: how did you get a waiver to fly instruments in jets when you are obviously deaf as well as blind AND stupid?) but after that it'll be back to the same old "Citation 345, continue approach, follow the Piper Cub on 10 mile final at 12:00 o'clock and 2 miles..." (ROFL)

So in the aircraft selection screen you click on the paint you want, click details, and then in the tail number, just put the callsign, WITHOUT the N. For instance, we have a local C172 at work, N738JX. So in FSX I put the tail number as 738JX. That way the FS ATC always says "Cessna 738JX....."

OK, thanks for the tip, but that still doesn't address ATC's insistence on calling my Baron "Beechcraft [NnnnXX]" instead of "Baron [NnnnXX]," it just eliminates the leading N......but thanks for the empathy and tips. Half a problem solved is better than none... :(

OK, thanks for the tip, but that still doesn't address ATC's insistence on calling my Baron "Beechcraft [NnnnXX]" instead of "Baron [NnnnXX]," it just eliminates the leading N......but thanks for the empathy and tips. Half a problem solved is better than none... :(

Try editing your Baron Config file under the [General] Section for the following linesas follows:atc_type = Baronatc_model = You will however, need the word "Baron" in your voice file, if you use editvoicepack you should be fine.

OK, so you're saying that N12345 would be (for example, if it was a C172) "Cessna 12345" and not "Cessna 345?" Honestly, I only hear the full set of numbers when there's a problem, i.e. multiple a/c with similar last-3's, or when one of us has fubared something... in which case we WILL hear "CITATION NOVEMBER 12345, HOW DO YOU HEAR THIS FREQUENCY?????" (translation: how did you get a waiver to fly instruments in jets when you are obviously deaf as well as blind AND stupid?) but after that it'll be back to the same old "Citation 345, continue approach, follow the Piper Cub on 10 mile final at 12:00 o'clock and 2 miles..." (ROFL)

If a pilot calls me while I'm working approach and says "Duluth approach, Cirrus 233CA, with you 30 E, atis A, inbound duluth." I will say initially: "Cirrus 233CA, DLH app, sqk 0321 and ident."Any subsequent transmissions I will use "Cirrus 3CA." If an acft calls me as "November 233CA," I will reply the same on the first transmission. I may eventually say "November 233CA, say aircraft type" and then proceed to call them as {aircraft type} {last 3 digits}Additionally, I could use "November 3CA." Instead of "Cirrus 3CA."About your Citation following a Cub, lol, I've heard fellow controllers to tell a Cirrus to slow down, following an F16, 3 oclock, 3 miles haha