This just started recently as far as I can remember. I haven't flown the 737 for a while and now the plane when in LNAV flys at an angle to the flt path of the FMC. Even when I set up for a landing just using the LOC and APP, the craft does not line up with the runway.I'm including a couple of screen shots to show the problem.Hope someone can help me here in getting this worked out.Jim Dow

Hey Jim, Can't really help you with the app since you only show a outside shot of whats going on. As for your flight pics, well looks like to me you have some strong cross winds @ LVL 290 with the plane compensating as it should. As for the magenta line on the ND - its not prefect in the sim but the plane appears to be flying correctly. In the bottom right shot your LNAV appears to just been re-engaged? (Green box around LNAV on the FMA) yet it's on the 'selected' course. Also in the shot you have 5 miles set on the ND display which exaggerates the discrepancy. The shot on the left the plane is already starting to turn correctly and the top left shot you have MAP PLAN which is not used for flying per se but to cycle through the route visually. Do another flight and post pics of your app and be detailed on how you are flying the aircraft so we can see whats going on.

Thanks Randy for your comments. I will do another flight with better pictures and comments as to what is going on.As to the cross-wind thought, the arrow in the upper left corner of the ND shows wind direction as the course and speed readout is 205/35. So shouldn't the plane be tracking toward the wind instead of with the wind? As I mentiond before, this was not occurring before in thenumerous flights I have done in the 737 even with srong winds. The diamond always tracked the magenta line exactly in the middle.Next flight test will be without wind to see if that has an effect. I'll post sometime today.Jim Dow

I set up a new flight now at NZCH on RWY 02, no wind and FMC programmed for a flight to NZWN.The problem begins right here at the beginning as it seems the compass heading is way off.I'm lined up and the heading should read 020 +/- but reads 037. I have the MCP HDG set at 037just to show what is being displayed. As you can see, the aircraft is not lined up properly on the ND.This occurrs throughout the flight and as dipicted in the 1st posting, the ILS is way off as well.I haven't attempted this with another aircraft yet but will do so to see if it shows a similar problem.If anyone has an answer I would love to hear it and fix it.Thanks, Jim DowThe actual HDG of RWY 02 is 017, so my hdg is off by 20*. This also appeared to be the case with another aircraft.So the problem seems to be with FS9.

Edited November 22, 201015 yr by ilovetofly

Hello there, just my 2 cents worth, dont forget magnetic variation which NZ has extremes and that headings are ref to magnetic north and Rwy,s are ref to True North. Hope this helps, Cheers Dave. :(

Dave,I understand your point, but approach hdgs are magnetic I believe. So while the RWY designation is 020, the magnetic heading is 017, if I'm correct. But this does not explain why I have a skewed aircraft in relation to the runway. Just to test, I set up a flight at KSAN on RWY 27 and the plane is again not lined up on the runway in the ND. So there is some other problem.BTW, before the Mods get to you, this forum requires full names on all posts. You have been warned! Thanks,Jim Dow

Well I fixed the problem. I don't know why it occurred, but this is what I did. Thinking it may be caused by a scenery, I unchecked the first 15 at the top of the list. Went back to FS and set up a flight and, lo & behold, everything lined up perfectly. Now to locate the offending scenery, right? Clicked on the first 5, reset the flight and everything was OK. Did the same with the next 5, still no problem, last 5 and STILL no problem. Did a flight and everything was A-OK.So I don't know which or what caused the problem, but all is fine now.Jim Dow

I had this exact problem too some months ago.I ran FSX and FS2004 on the same computer and thought maybe that was the problem. I uninstalled both FS2004 and FSX. I then reinstalled FS2004 and it's been running fine since.Don't know what to tell you. I was hoping someone knows so I can put FSX back on the computer...John Floyd

I had this exact problem too some months ago.I ran FSX and FS2004 on the same computer and thought maybe that was the problem. I uninstalled both FS2004 and FSX. I then reinstalled FS2004 and it's been running fine since.Don't know what to tell you. I was hoping someone knows so I can put FSX back on the computer...John Floyd

John,On reading some previous posts about this issue, some commented that it was an AFCAD or scenery causing the problem. Also, PMDG noted a problem due to a registry issue causing the ND to display improperly. But this may apply only to the FS9 version. While I don't have FSX installed, many have both versions on the same computer as well as on the same drive, others put them on different drives.Why not reinstall FSX and see if the problem persists, and if so, due a search here for some of the solutions. Jim D.

Some tracking issues, particularly where FS9 and FSX were installed (even if one was removed) caused registry errors to access the incorrect mag declaration files. In these instances it was fixed by this free utility "FSX/FS9 Registry Repair Tool (36KB)" from Flight One:http://www.flight1.com/view.asp?page=libraryCurrent FSUIPCs, and they should be updated, now use as first choice the registry for your FS path.The main required upgrade is with full documentation is here;http://www.schiratti.com/dowson.htmlwith an interim upgrade here:http://forum.simflight.com/topic/66139-updated-modules-18th-november-2010/