I thought it was possible to replace the call signs used by default AI traffic (Soar, Landmark, etc.). I tried the following:"Open aircraft.cfg file of any default aircraft and change string editable=0 to editable=1 then open FSEdit, open that aircraft and just type in the field ATC Information -> airline the desired name from airlines.cfg file. For instance for MD-80 you can change Soar to Air Canada. The same for flight number. So next time ATC will call the MD-80 Air Canada."which I got here:http://www.planesimulation.com/tips1/tips1b.htmBut this only changed the call signs used when flying the default aircraft, not the call signs used for default AI traffic.Why doesn't this change the call signs used for default AI traffic (since the AI traffic uses the aircraft that I modified)?-Basil

Hi Basil,Hmmmm, I thought that would do it too. But I never tried. I went the PAI route, and I must say I couldn't be happier. It is a lot of downloading on my poor old 56K MODEM, but it is worth it, believe me. And it is all free; those PAI folks have put lots of work into their project. R-

Hello Basil, I switched out all my default aircraft in FS2002 and now in FS9. No glitches encountered. ATC uses the recognized callsigns I assigned as well as new and matching textures. I never did use FSEdit either. All my changes were done to the aircraft.cfg via WordPad. The airline name goes after atc_airline= and a flight number has to be assigned or ATC will not recognize the name, but will only refer to the aircraft by type/model.atc_airline=Americanatc_flight_number=37Z----------------------------If you haven't already jacked-up your airlines.cfg found at the bottom of the Aircraft folder (Microsoft GamesFlight Simulator 9Aircraft) you can start with this which increases the names available to ATC. Works in FS2002 and FS9. accalls.zip (or for FS9 only (airline_list_2004.zip)) note: EditVoicePack is a necessary tool to install the missing spoken 'sounds' to FS. The freeware utility EditVoicePack will substantially increase available aircraft callsigns, models, types, airports etc. (available for FS2002 and FS9)http://bevelstone.xs4all.nl/FlightSimulator/EditVoicepack/Hope this helps you out. If not, come back and we'll get it figured.

Most of my AI a/c and traffic is GA, for which I use GA_Maker. I do all of my flying in Alaska, so when I started fiddling with AI, I removed all the default flightplans except those too and from Alaska airfields. While I don't doubt that PAI is the cat's meow for those into airliner simulation, I'm content just to modify the existing default aircraft to more realistic call signs. (Well, I've added some AI a/c models and flight plans for Alaska Airlines, and some military AI flying to and from Elmendorf, but if just get the call signs for the default AI to something more realistic, I'll be happy.)-Basil

>Hello Basil,>> I switched out all my default aircraft in FS2002 and now in>FS9. No glitches encountered. ATC uses the recognized>callsigns I assigned as well as new and matching textures. I>never did use FSEdit either. All my changes were done to the>aircraft.cfg via WordPad.>> The airline name goes after atc_airline= and a flight>number has to be assigned or ATC will not recognize the name,>but will only refer to the aircraft by type/model.>>atc_airline=American>atc_flight_number=37Z>----------------------------Well, following the examples I posted, I have for one of the default 747's:atc_airline=JAPAN AIRatc_flight_number=1123>If you haven't already jacked-up your airlines.cfg found at>the bottom of the Aircraft folder (Microsoft GamesFlight>Simulator 9Aircraft) you can start with this which increases>the names available to ATC. Works in FS2002 and FS9. >accalls.zip (or for FS9 only (airline_list_2004.zip)) note:>EditVoicePack is a necessary tool to install the missing>spoken 'sounds' to FS.For what I want to do, I don't think I need this utility. I know the sound for "JAPAN AIR" exists, because I've heard ATC use it when I load up this a/c.But a little light bulb just came on. Do you suppose I need to recompile my AI .bgl file? Nothing in the instructions I had mentioned that, but I can imagine how it might be required. Is it possible that the call sign for AI aircraft is encoded into the compiled BGL for AI? If so, then at the time it read the aircraft.txt file, and parsed the referenced aircraft.cfg files, it would pick up whatever call sign was then assigned that aircraft. If the call sign was later changed, it would not be reflected in the BGL until it was recompiled.I don't know if that's the problem or not, but I'm going to check it out.-Basil

I'm a little slow, so let me make sure I understand this.I have, for example the 3 default textures and 2 addon textures for for the B-777. Can I dump the defaults and then change this:(fltsim.3)title=Boeing 777-300 United Airlinessim=Boeing777-300model=panel=sound=texture=uakb_checklists=Boeing777-300_checkkb_reference=Boeing777-300_refatc_id=N777UAatc_airline=UNITEDatc_flight_number=009atc_heavy=1ui_manufacturer=Boeingui_type=777-300ui_variation=United Airlinesto this:(fltsim.0) <---title=Boeing 777-300 <---sim=Boeing777-300model=panel=sound=texture= <---kb_checklists=Boeing777-300_checkkb_reference=Boeing777-300_refatc_id=N777UAatc_airline=UNITEDatc_flight_number=1123 <--- (seems to be a default #)atc_heavy=1ui_manufacturer=Boeingui_type=777-300ui_variation=United Airlinesand ATC will recognize it as an AI aircraft? (United is already in airlines.cfg)

I have a somewhat similar problem. AI keeps telling me to look for traffid "Baron Baron". Is there any way to get AI to just say "Baron"?Dave Hinson

What does aircraft.cfg say. It should say:(General)atc_type=Beechatc_model=BE58

I have had the time to edit my 737, 747, 777 and MD-83 files and the system works like a charm. (So far.)

Those were the variables I was looking for. Thanks a lot.Dave HinsonMine had: atc_type=Baron atc_model= (blank)