On approach to 16L at KSEA the glide slope was indicating right on however the VASI lights are showing me high. My error was I forgot to set the Baro on the altimeter. It was set at 29.92 and should have been at 30.1. I am curious why the glide slope was not showing me high. Is it tied to the altimeter in some way or is there an additional way I screwed up in addition to the Baro setting?Thanks for any comments. I hope the attached photo helps.Tom Hibben

The G/S and VASI are not coincident (not the same path; check out the notes on the approach plate if you've got it). The BARO settings would have no effect on this as you're comparing angular deviation and elevation deviation. Not the same thing.

So why was the glide slope reading correctly yet I was coming in high? I really knew there was no connection to the baro but I mentioned it just in case.Thanks,Tom Hibben

I see that you have G/P, not G/S annunciated. The 3 degree G/S should have you close to the VASI. I've never flown a jet that had the G/P option. Maybe that's not giving you a 3 degree angle. Maybe try looking at your legs page to see what it would give. I'd turn on the G/S rather than using the G/P.

Matt,I think I recall from the tutorial flight that you set the ILS freq's into both nav radios even though you are trying to do a RNAV autoland. Obviously I was probably doing something wrong.Thanks, will keep looking,Tom Hibben

I have had the same problem a couple of times. The G/P (glide path) and the G/S (glide slope) are not the same thing. The G/P is a vnav thing while the G/S is the ILS slope. I have had trouble activating the G/S sometimes. On occasion I was forced to change to alt hold mode and then press app, first then was I able to arm the G/S.

Manfred,Thanks for the info. I will try it again and see what happens. I wonder if this is a bug or the way it works.Maybe I should put it in a bug report and see what is said.Thanks,Tom Hibben

On approach to 16L at KSEA the glide slope was indicating right on however the VASI lights are showing me high. My error was I forgot to set the Baro on the altimeter. It was set at 29.92 and should have been at 30.1. I am curious why the glide slope was not showing me high. Is it tied to the altimeter in some way or is there an additional way I screwed up in addition to the Baro setting? Thanks for any comments. I hope the attached photo helps. Tom Hibben

The screenshot shows you're conducting an IAN approach, not ILS. While an ILS approach will actually work fine with the alimeter set wrong (because of the land based component), IAN requires the alimeter to be set correctly. It isn't, hence your high approach. You're in IAN mode because the ILS isn't tuned, most likely because you used the frequency on the approach page shown by the CDU which happens to be different to what's in FSX.

Jordan,Thanks. I was still in IAN approach. The one positive was I was able to take control and land and make the last turnoff... grinThanks all of you for the help,Tom Hibben