Posted in FSX gen. forum but no replies:Hi. I just finnished an unsuccesful flight (overshot the rwy) to KSEA. I was vectored to 34L and not being that experienced yet, i realized too late that the vasi lights were showing all four white and that the localizer glide slope i was tracking was incorrect. The result was touch down at least 1 third of the way down a not too long rwy. and i just couldn't make it to a stop at the end. I was flying a PMDG 747-400 by the way. I have just recently installed ORBX FTX PNW. but i havent read of any affects on KSEA. Anybody had similar experience or knowledge of this?

Posted in FSX gen. forum but no replies:Hi. I just finnished an unsuccesful flight (overshot the rwy) to KSEA. I was vectored to 34L and not being that experienced yet, i realized too late that the vasi lights were showing all four white and that the localizer glide slope i was tracking was incorrect. The result was touch down at least 1 third of the way down a not too long rwy. and i just couldn't make it to a stop at the end. I was flying a PMDG 747-400 by the way. I have just recently installed ORBX FTX PNW. but i havent read of any affects on KSEA. Anybody had similar experience or knowledge of this?

I don't think the problem is caused by the aircraft. If you followed the ILS you shouldn't have to worry about the VASI light. At least until you've disconnected the autoland (autopilot). If you are not used to landing manually just use the autopilot until 500 feet AGL and make a manual landing then.

I'm still learning to fly the 747 so i'm working on last 100ft. above before AP disconnect at the moment and then gradually work back from there(200ft then 300ft. etc) so by 100ft. i'm in trouble. You are right, it isn't the aircraft. I think it must be a afcad problem.

I'm still learning to fly the 747 so i'm working on last 100ft. above before AP disconnect at the moment and then gradually work back from there(200ft then 300ft. etc) so by 100ft. i'm in trouble. You are right, it isn't the aircraft. I think it must be a afcad problem.

So you should be able to change it yourself, programs like Airport Design Editor are very handy for changing the frequencies etc.

So you should be able to change it yourself, programs like Airport Design Editor are very handy for changing the frequencies etc.

Yes i just got this advice on another forum, so will investigate. Thanks Devinci.

Keep in mind KSEA added a runway last year, out of date charts and navdata will have incorrect runway numbering.

wanabflyerI installed that ORBX FTX PNW several months ago. The first landing that I made there was in a CS 752 on 34L which I believe is the new runway at KSEA (default FSX were 34L and 34R but they are now 34C and 34R with PNW installed). Anyway, I landed about halfway down the runway. This was an ILS approach and CS "autoland". I don't land on 34L anymore. I have never tried 16R. Since I am my own accomadating ATC I land on 34R. It must have something to do with ORBX addon.Michael Cubine

wanabflyerI installed that ORBX FTX PNW several months ago. The first landing that I made there was in a CS 752 on 34L which I believe is the new runway at KSEA (default FSX were 34L and 34R but they are now 34C and 34R with PNW installed). Anyway, I landed about halfway down the runway. This was an ILS approach and CS "autoland". I don't land on 34L anymore. I have never tried 16R. Since I am my own accomadating ATC I land on 34R. It must have something to do with ORBX addon.Michael Cubine

That is my experience and like yourself i now switch to 34R untill i can fix the problem.