This post is different than others I have searched for or seen about this issue. Let me preface by saying:1) yes, I have and use EditVoicePack2) yes, I have defined many custom callsigns that work admirably in FSX3) yes, my [fltsim.xx] section has atc_airline=Costena defined4) yes, Costena is a valid in my .gvp file.5) Costena works for SOME aircraft, but not others. !!How can it work for some aircraft, but not others? Is there something I am forgetting?Thanks for any help!RhettAMD 3700+ (@2310 mhz), eVGA 7800GT 256 (Guru3D 93.71), ASUS A8N-E, PC Power 510 SLI, 2 GB Corsair XMS 2.5-3-3-8 (1T), WD 250 gig 7200 rpm SATA2, CoolerMaster Praetorian case

It seems to me that it must be something in some of your aircraft.cfg files. I have sometimes stared at a code error forever without recognizing what's the matter. Later, after it's fixed, I can't believe why it took so long for me to see it.Why not delete everything out of the "ATC" section of an errant file, then cut and paste that section from a working file. It won't take long to try that. R-

>It seems to me that it must be something in some of your>aircraft.cfg files. Is it affected by atc_parking? Perhaps atc_parking=RAMP will mean that an airline callsign is never used. But atc_parking=GATE will allow an airline callsign to be spoken. ?RhettAMD 3700+ (@2310 mhz), eVGA 7800GT 256 (Guru3D 93.71), ASUS A8N-E, PC Power 510 SLI, 2 GB Corsair XMS 2.5-3-3-8 (1T), WD 250 gig 7200 rpm SATA2, CoolerMaster Praetorian case

You may have a space or other character before or after the word in the atc_airline= entry in some aircraft.Can you easily identify the aircraft which are not working?Copy the atc_airline= entry from a good aircraft.cfg and past it into the bad aircraft.cfg.I have not tested in FSX, but in FS2004 atc_airline= entries were not case sensitive.