@David Were you thinking of http://forum.avsim.net/topic/336155-magnetic-variation-updates-for-fs9-and-fsx/ ? Cheers, Brian

Isn't there a fix for that? If I'm not mistaking I once saw a link here to the fix...it could have been a post from Ryan I think...? Cheers,David DD

Ye and that STICKY is here: http://forum.avsim.net/topic/336155-magnetic-variation-updates-for-fs9-and-fsx// Leffe

Ye and that STICKY is here: http://forum.avsim.n...or-fs9-and-fsx/ / Leffe

Bingo, that's the one Leffe!Thanks, David DD

I have run the Flight 1 Registry Repair Tool several times over the past several weeks and it has made no difference in my issue. From what I remember it corrects situations where the plane is landing in the grass beside the runway as opposed to landing on the runway but left or right of the centerline. Michael Cubine

You're right - my mistake.

its happened to me several times esppecially jfk runway 13r it missin it by a miles not even close, got the right number in on the radios andof course numbe as well, this definitelyu seem to be a bug, hopefullly pmd will ome out with some fix for us.

Is there a way to know which airports this issue will be experienced at? It would be nice to not to have to test the airfield's ILS before each flight... Also, any insight if PMDG has logged this as a bug/issue? Thanks,Sam Kharey

I know this has been discussed before, but I was wondering if there was a resolution or at least acknowledgment that there is a known issue (or perhaps I'm doing something wrong): At some airports, I find the aircraft does not track towards the runway on an ILS approach. Recently, I tried ILS13 @ CYQR. Both NAV radios were tuned to the ILS frequency, I set course 135 on C and F/O MCP and the FD led me substantially to the right of the runway. Note the "auto-set FSX course" feature is enabled in my settings. Autoland also abandons the approach part way down... Is it a requirement that I get the magnetic variation BGL that's a sticky on these forums? Thanks folks,Sam Kharey

I had the same problem. The fix for me was to turn off the auto-CRS feature. John

Thats more of a mythical fix than an actual working fix in my experience. I have run into this offset localizer issue on a few airports with a working registry. Running the registry repair tool didnt fix it for me. YMMV

You have to do more than just run the registry repair tool, you need to also delete the Facilities and SceneryIndexes folders and let FSX rebuild it.I was having some of the same issues at one time described here and following Ryans post that includes complete directions besides just running the Reg Repair tool fixed the issue for me. In fact, I had a private discussion with Michael Cubine and tried the same airports he was having issue with and it worked perfectly on my rig. Of course this wont fix any runways that actually have an offset localizer on purpose.Sean Campbell

I did a small investigation of this a few days ago.(i didnt check the forums for this issue before).I found out for my case(ils offset at certain airports), it was due to the difference in the "world" magnetic declination and the "airport" local magnetic declination. Then there is the heading information provided up the updated real world airac, but we keep this out of the picture because it doesnt affect ILS tracking. Marcus Jian

You are not quite correct! An offset approach means "exactly" that. In that the approach is "not" physically in line with the runway. There are many examples the nearest to me is LIMJ Genova Sestri. The rwy heading is 290 but the ILS offset is 287. This is to avoid flying directly over the port.If you think there is a discrepancy the first thing you need to do is study the approach plates for said airport. If the ILS approach is clearly in-line then you need to modify the afcad file as there are a number of airports that do have mistakes.

You are not quite correct! An offset approach means "exactly" that. In that the approach is "not" physically in line with the runway. There are many examples the nearest to me is LIMJ Genova Sestri. The rwy heading is 290 but the ILS offset is 287. This is to avoid flying directly over the port.If you think there is a discrepancy the first thing you need to do is study the approach plates for said airport. If the ILS approach is clearly in-line then you need to modify the afcad file as there are a number of airports that do have mistakes.

What I referred to is not an offset approach. I would know the difference between both situations. For that airport(s), the 737 tracks the runway with an offset. But if you were to look at the localiser needle/star, its also off by a few dots. Repeating this ils with the default 737, and it tracks the ils perfectly in the centre, and in this case, its straight towards the runway(no offset). If you were talking about a deliberate ils offset, when tracking it successfully, your localiser needle would be right in the centre, not 'off by a few dots' in this case. In this thread, the problem isnt differentiating between normal parallel ILS and offset ILS like what you mentioned, its about whether the 737NGX is able to track an ILS accurately such that the needle is right in the middle. (doesnt matter where the ils is pointing). I can even have a localiser right in the middle of the ocean and get the 737 to fly an approach into the water, but if the mag dec between that area and the ILS is different, the default course you set will cause the plane to be 'off' the beam. There isnt a need for approach plates for this one. One airport which I encountered this is KPAE, runway 16R. Default FSX airport, using 2010 Magnetic Dec Data. No/little winds(as a control). The ILS is not an intended offset one. Zoom in on the FSX map if you wish to verify. For me the needle doesnt track exactly. (PMDG settings use auto set FSX course). Not sure if everyone would have this problem. If you do not use auto course, note that for the needle to be exactly centred, your course setting would not be the same as the direction your headed towards(or ILS heading). Regards.Marcus Jian (i'm not criticizing the 737NGX, its due to inaccuracies in multiple different datas in FSX that could be causing this)

OK gents, still a little confused -- here's what I've done and I still see this problem at CYYJ ILS27: - I've run the Flight1 reg-fix tool- I've replaced my old magDec.bgl (or whatever) from the one linked in the sticky on these forums- I've turned off the "Auto-tune FSX course" in the PMDG FMC- I try to fly ILS 27 @ CYYJ, I put in the CRS exactly what's listed in the FSX map...- (I have not deleted the Facilities or SceneryIndex folders for them to rebuild as suggested, though) ... still no cigar. Flying to the right of the runway... I don't think there's a deliberate offset on this approach?Anyone spot what I'm doing wrong? Thanks,Sam Kharey

It's the airport, definatly has a problem. Im just glad it wasn't "0/0' weather :-)

Guys, this has nothing to do with the NGX. If there is a problem with default FSX Airport AFCAD then your going to experience this problem. Obviously Microsoft messed this airport up and the fix is at the link below. All ILS Runway information is stored in the AFCAD's for either the Default FSX airport, or Payware sceneries have their own updated AFCAD's. So in order to make CYYJ work correctly you need the updated AFCAD below or its never gonna work. If you have these problems at other airports as well, try going to AVSIM Files section and look for an updated AFCAD for that particular airport. There are many available and they are free. http://library.avsim...=ftp&DLID=95997

This file is compatible and 100 percent compliant with FSX ONLY. ========================= This bgl file fixes the ILS Localizer and Glideslope Transmitters for CYYJ. FSX inadvertently misplaced the Localizer to the rightside of the runway.CYYJ is not a offset ILS type ApproachNo other changes have been made to the airport

Gents, thank you for helping to investigate. Thanks for confirming the problem and proposing the solution. Sam Kharey

Guys, this has nothing to do with the NGX. If there is a problem with default FSX Airport AFCAD then your going to experience this problem. Obviously Microsoft messed this airport up and the fix is at the link below. All ILS Runway information is stored in the AFCAD's for either the Default FSX airport, or Payware sceneries have their own updated AFCAD's.

With all due respect Paul, I think it does affect the NGX. I flew into RW 25L at KLAS in the iFly737 and the FMC indicated the NAV1 freq was 111.75, Course 255. I set the NAV 1 and NAV 2 frequencies to 111.75. When I enabled the APP, the course heading automatically changed from 000 to 255 and the aircraft landed on the runway dead center. I flew the 737NGX and the FMC indicated the NAV1 freq was 111.75, Course 255. But, when I enabled the APP, the course heading changed to 257 and the aircraft was positioned for landing on RW 25L on the right side of the runway. With the APP enabled, I was unable to change the freq to 255 to get back on course. So it is strange to me that the FMC reads one thing and the course heading on the aircraft panel reads 257 on the PMDG737NGX. I used the latest Navigraph cycles. I found the same thing happened when trying to land on RW 25R with both aircrafts. I hope there will be a fix in SP1. Best regards,Jim Young