Hi guys, is it just me or does anyone else out there has issues with ILS on that airport in FS9? It looks like the ILS tracks a "virtual" centerline that is about 1.5 widths to the right between the runway and the first parallel taxiway. At first I thought a 34 knot crosswind would be why but then I tried it with fair weather and got the same. I've flown the POSKY 757-200 many times, this is the first time this occured. Any help would be appreciated.Nick

AFCAD shows a slight off-center deviation on 10R 28L but not as much as you state. There is a one degree difference between the two runway localizers with the 10R28L showing the slight angular offset to the runway centerline.

When you come in for the approach at a 30 degree angle and end up landing 1.5 runway width over I wouldn't say that is insignificant. A major correction way out is needed to compensate for that. I think the best option is to forget about ILS, hand-fly the approach and do a visual.Best,Nick

Are you using the default airport scenery and afcad? I'll overlay it with the scenery and see what I get. Did you add any PAI afcads or use UT2?I only saw with the default AFCAD an offset angle of 1 degree, not 30. Any chance you have set a course error on your VOR course selector (it can happen due to wrong info)?It is normal to merge using heading control at a 30 degree intercept angle until the localizer starts to center, then steer close to the correct course as you merge and engage approach.If the frequencies for the localizer are the same at each end of the runway, due to an FS problem watch your localizer ident since unlike real world both are active in FS. This means you could be picking up the wrong one if far off center. After you verify the ident (audio morse code or ident display on EHSI) and steer to the desired course with heading control centering approx the VOR you can engage approach.Been there, done that (at KMSP) .I'll look at it when I get home.Note that a similar thread for CMH was just started on flightsim FS9 forum apparently with a HUD user.BTW there are some airports where the localizer heading is offset several degrees expecting you to go visual and get on course the last short distance. This is due to terrain and I think LOWI Innsbruck is noted for this. Don't think you'll see this at Cleveland, however.

I am positive that there should be no offset on that runway (Port Columbus Intl.). I am using PAI, but there is no AFCAD associated with CMH. Also I performed the simple test of dialing in the 10R ILS while on the ground on the centerline and indeed it is about 1.5 runway lengths off. I tried correcting it using AFCAD2.21 and did, however I overwrote the default airport and lost all the marker data and another ILS...trying saving it as a separate AFCAD file on the same or higher layer produced no effect...still new at AFCAD. It doesn't look like I'm picking up the wrong ILS. So the issue now is to correct the problem. RegardsNick

I checked the default AFCAD and overlaid it. The other one I have is from UT2. They matched up.I take it your default was the only one showing up when using the open airport - search menu. (For the record, only the base AFCAD and one additional overlay should ever show FS9 being confused if more than two are present.As suspected the navaid list shows both ends of each ILS runway sharing the same ILS frequency. In addition, each ILS property shows backcourse enabled. Chances are you were locked on to the backcourse.Here's the frequencies and IDs for the default:28R IONB 109.1, 28L ICMH 108.7, 10R IAQI 108.7, 10L ICBP 109.1.I would turn off in AFCAD the backcourse enable in the properties for each to see if that has an effect.It should be noted that a localizer part of ILS is just past the far end of the runway while the GS antenna is offset to the side of and a few feet from the threshold. These are shown correct for KCMH. The inbound mag course settings are 99 and 279 and my SimPlates collection does not show back-course published plates so go ahead and turn off the back-course property with AFCAD2 and save it as noted above. Here's how I place additional afcads:On my FS drive, h:, I have H:AFCAD2S folder. Under this I have scenery folder. In this scenery folder I place the afcad bgls. It is important not to have a texture folder here.In my scenery settings in FS I added the AFCAD2S folder fairly high up on priority. Whenever now I place an AF2_xxxx.bgl in H:AFCAD2Sscenery, I start FS and it reindexes the scenery making it effective.Supposedly AFCAD can not modify some objects in the base (unless it has changed with the last upgrade). If your original needs to be restored, I could send you an afcad of the original to be installed as an overlay. The other option is to locate the .bgl file on the CD, I am not sure of which collection, and restore it. WIN XP and WinZip can open .cab files. _____However that should NOT be necessary as noted by the following from the docs:________<<<<<<<<<<<>>>>>>>>>>>So it would seem the stock has not been changed and you need to find, probably in Add-On-Sceneryscenery (default AFCAD2 save location but you can choose your own if you add it as I outlined above) an AF2_KCMH.bgl file and move it elsewhere or delete it if you wish to start over.Any objects that are the same as in the stock FS9 bgl file such as navaids will override the stock objects.Note that in AFCAD the localizer properties list the heading as true. In that area you have to add 6 degrees to get the course setting in mag degrees.Now if indeed it was back-course that you were locked onto, the centerline would give reversed sensing but on center should have been close. The GS would have been a reflection and way off.Hope this helps.www.projectai.com has a link to an AFCAD forum you can browse probably with an FAQ.To get directly to the AFCAD help files without starting AFCAD2, just go to the folder it is in and click the readme.html and it will open up in your browser.

Me again. On the FS forum with a similar thread another poster said he had checked it and it showed a problem. I have the 9.1 patch installed and maybe that corrected the default.

OK, Nick. On the other forum that three message thread had a correction for the headings of two localizers to correct that problem. Look for CMH contained in the subject line.

First of all, thank you for your replies and effort regarding this issue. I think I have corrected the problem. Here it is just for the record:The true heading of the actual runway vs. the ILS were 1.5 degrees different. I am thinking that this is attributed to the fact that FS had a -6 deg. mag. variation for the airport, whereas if you go to Airnav the variation for KCMH is -5 deg. So what I did finally was set the mag. variation to -5 thus for rwy 10R the true heading is 94.210 and the mag. is 99 (per Airnav data). In addition to that I also had to center the ILS on the rwy threshold since it was a little off. That seemed to do it and last night in fact I flew a seemless ILS on rwy 10R. Again, thanks for all your great tips and happy flying!Nick