Hello,If the ID of an airport is changed (upgraded by the FAA) how do I change it in FS9?Example: 8S5 changed to KLROThanks in advance,Ron SagelNEAR KCHS

The only way I know would be to find the appropriate stock .bgl file, decompile it, make the change, and then recompile it.AFCAD doesn't help - I've tried it and also asked questions about it here. Using AFCAD to change the ID results in both airports appearing.

Please do not attempt to decompile the stock APnnnnnn.bgl file. It holds about 110 airports in addition to your airport.You can make the change - but I've got about 275 airports on my list of those which have changed designators since the FS2004 data was compiled. I'm sure there are a lot I don't know about.It's a detailed procedure to redesignate and airport - and because 8S5 has Instrument Approach Procedures in the database - it's a bit more work than normal.You need AFCAD to manipulate the visuals.NewBGLAnalyze to decompile the stock airport data.BGLComp from the BGLComp SDK on the Microsoft site to create the new .BGL files.EditVoicePack.1. Use EditVoicePack to associate the airport name East Cooper with the KLRO ICAO code - you might have to create the sound - I don't have access to EVP on this computer.2. Open the stock AFCAD and save it after changing the designator.3. Use NewBGLAnalyze to decompile the AP926200.BGL. Copy this file from the SceneryNAMEScenery folder to a working folder to avoid the possibility of messing up the base file.4. Create a file 8S5_Remove.XML by removing everything from the decompiled AP926200.bgl except the base information and the airport header. Set all the remove flags to TRUE.5. Save and compile that .XML file with BGLComp - place the new .BGL file in the SceneryGenericScenery folder.6. Open another copy of the decompiled file. Remove everything except the airport data. Save the file as KLRO_New.XML7. Change the ident to KLRO in the header.8. I would personally remove all the TaxiwayPoint, TaxiwayParking, TaxiwayPath, Apron and ApronEdgeLights from this file - and use AFCAD for creating and manipulating those visual elements - up to you.However, the runway must remain in this file, along with the approaches - RNAV Rwy 17, VOR Rwy 36. For this file I would use text from a decompile by NewBGLAnalyze to keep the Taxiway signs and the CF legs of the approaches. Save and compile the file - place it in the SceneryGenericScenery folder.Both airports will be visible in FS - but 8S5 will have no runways, no aprons, no start locations.Just make danged sure that you do not ever make any changes to the stock 8S5 AFCAD and save them as a new file.

I will also add the way I do it which is very simular to Reggie's post.You must delete the original airport from the FS9 database.Some of the steps are to use the AFCAD program 1st and make the airport exactly how you want it. Once this is done you will not be able to go back and edit the airport with AFCAD. You will also never be able to open the airport with AFCAD and make any changes so do everything first with AFCAD.Now delete the original airport from the database as per the SDK.That requires a airport header and all the delete element statements.This xml compiled to a bgl deletes 19a from the database.<?xml version="1.0" encoding="ISO-8859-1"?> Place the compiled bgl into the SceneryGenericscenery folder.Start a new XML using the same airport header but change the Ident and name to whatever you want.example<?xml version="1.0" encoding="ISO-8859-1"?> note -- use both decompilers and combine the approach data that each leave out. Place the new compiled XML to bgl into the Addon Sceneryscenery folder and set file property attributes to "Read Only". This protects the file from AFCAD so you can't make any changes and save.Never use AFCAD to open the original airport because AFCAD always reads the Apnnnnnnn.bgl and never a new changed name airport. hope this also helps and gives you 2 options to look at.

Hello,Thank you for the detailed response.This is a lot bigger deal to fix than I was aware. Too bad MS made this so difficult.Ron SagelNEAR KCHS

It's not that it's difficult - just detailed.But a LOT of critical elements are tied to the unique computer code which FS used to ID the airport. To make things simplier - FS used the "ICAO" code of the airport - thus changing it is a relatively big deal.PS - Send me a PM - I've got a couple files you can test.