Hi friends,after three failed landings at KSEA i decided to post.Coming from KSLC in a beautiful trip i have been vectored to rwy 16L but in all three attempts my aircraft couldn't firmly keep on the localizer and i had to start a missed approach procedure.Later i checked file r.txt and...KSEA,11900,150,16L,180,110.3KSEA,9425,150,16R,180,111.7KSEA,9425,150,34L,360,111.7KSEA,11900,150,34R,360,110.3while approach course should be 161

magnetic variation probably accounts for the heading differences

Hi JD,had same problem in some other approaches and usually they have been solved just editing r.txt; is that because i decided to edit that file once more. Anyway three wrong approaches are too much ;-)Can you please tell me if ILS freq are correct (same for both direction of the rwy)?ThanksLuigi

Luigi,If you edit the runways file your approach will be 17 degrees off.Seattle has a magnetic variation of -17 degrees in FS, so with a runway heading of 180 TRUE, that's 163 degrees which is correct for 16L/R, not including annual rate of change. So thew runways file is correct having 180/360 as the headings.Your aircraft not keeping on the localizer is an FS autopilot/air file/aircraft.cfg issue and not an RC issue. The AP in FS2K2 is pretty bad, especially in APR mode.As for all the real runway information as of 20 March 2003:http://www.airnav.com/airport/KSEAThe real world approach course is 159 degrees magnetic for 16L/R and 339 magnetic, including annual rate of change.It is quite common to have the same ILS frequency on both ends of a runway.16L - 110.3, 34R - 110.316R - 111.7, 34L - 111.7

Scott,thanks a lot for posting.It was Dreamfleet 737 turn and usually (just landed a KLSC coming from KSFO using same bird) localizer interception work quite fine.Will try again...cheersLuigi ;-)

Hi Luigi,>my aircraft couldn't firmly>keep on the localizerYour autopilot doesn't know if the localizer frequency is correct or not, or if the localizer heading is correct or not. The autopilot's job is to lock onto the signal you have tuned in and follow it. If your plane won't track the localizer, I doubt it has anything to do with the localizer itself...it's most likely something to do with your plane/panel. I've flown into KSEA dozens of times and have not detected any problems with the localizers. Try the same approach with a different plane/panel and see if you get different results.Sid