Greetings,What would cause the following problem?Coming in for an ILS landing and have Glide Slope active. As I look at the runway I am off to the left, but on all guages I am on target, including GPS. Is this my bad, or guages, AFCAD or scenery?PaxBradley MitchellHM KLAX ASVA www.nwva.org

Hi Bradley,It all depends on which approach you are talking about. There are some notable MSFS errors such as the ILS into (I believe) 28L for KPDX which is really off, there are offset approaches though but their angle will be off of runway heading... not just sidestepped a little. If you have gyro drift enabled and your gyro heading is way off your compass it can also cause this behaviour.

I cheked my settings and Gyro drift is not enabled. This is happening when approaching 22R KJFK using a new scenery and AFCAD. The add-on scenery is "kjfkv2.zip" by William Morgan. It has all RW active. When I am lined up on Gyro the plane is way off to left left.I have seen this happen to me on other ILS Approaches,at other airports. I am just trying to figure out if I am doing something wrong.

FS9 has some ILS approaches that are just plain wrong. At least one of them at my home airport, Port Columbus INternational KCMH, is similar to what you described: Follow the ILS, and you'll land on the roof of the terminal building.

If you have AFCAD installed, try loading the airport into AFCAD and look at the runway and ILs posiitons. Note that AFCAD reports the runway centerpoint, not the ends, but you can get a good idea by zooming in and using the position from the mouse pointer.Then compare those positions to those availble at airnav.com and see if they agree. Also turn on NAVAID display in AFCAD and look at where the ILS LOC feather is in relation to the runway.Looking KJFK 22R this is what I see:http://forums.avsim.net/user_files/146721.jpgNote that the Localizer is offset to the left. Comparing the runway and LOC positions with AirNav, I found that the default locations were right on. I also note that the localizer course is offset 2.5 degrees, and the runway heading in AFCAD is 210.7, while the localizer is set to 208.7. So the localizer is going to bring you at a slight angle to the offset threshold. exactly what we see here, in APP:http://forums.avsim.net/user_files/146722.jpgAbove the DH you have to pick up the runway visually and then fly yourself into correct position. So, at least the default AFCAD appears to be correct.scott s..

I don't see how gyro drift would affect the ILS. The bars will line up correctly regardless of how far the gyro drifts as it's just reading the strength of the frequencies the Localizer and glideslope trasmit, 2 frequencies for each.----------------------------------------------------------------John MorganReal World: KGEG, UND Aerospace Spokane Satillite, Private ASEL 141.2 hrs, 314 landings, 46 inst. apprs.Virtual: MSFS 2004"There is a feeling about an airport that no other piece of ground can have. No matter what the name of the country on whose land it lies, an airport is a place you can see and touch that leads to a reality that can only be thought and felt." - The Bridge Across Forever: A Love Story by Richard Bach

>I don't see how gyro drift would affect the ILS. The bars>will line up correctly regardless of how far the gyro drifts>as it's just reading the strength of the frequencies the>Localizer and glideslope trasmit, 2 frequencies for each.>>---------------------------------------------------------------->John MorganIn real life the gyro drift won't make a bit of difference but in FS this is tied to the autopilot so if you have any drift in your gyro setting the aircraft won't track the VOR/GPS/ILS accurately. If you don't believe me set your realism setting for gyro drift, then set the DG for 30 degrees off either way and try to track a Nav signal with the autopilot.

I guess it's been a while since I didn't manually track an ILS on FS. I'll have to check it out. I just never recalled anything about gyro drift affecting any of that in my real world flight training, so I was wondering what was up. Thanks.----------------------------------------------------------------John MorganReal World: KGEG, UND Aerospace Spokane Satillite, Private ASEL 141.2 hrs, 314 landings, 46 inst. apprs.Virtual: MSFS 2004"There is a feeling about an airport that no other piece of ground can have. No matter what the name of the country on whose land it lies, an airport is a place you can see and touch that leads to a reality that can only be thought and felt." - The Bridge Across Forever: A Love Story by Richard Bach

I actually found out about it when doing some beta testing. The gyro didn't autocalibrate with the "d" key like the default gauge and we started having all these posts about autopilot tracking problems and ILS tracking offset... tracked it down to the gyro and same thing happens with one of the default gyros if it is not calibrated. I know in real life you can track an ILS with a vacuum failure if you are using a rate based autopilot.