I was wondering if I'm doing something wrong or if there is something funky in FSX... When doing ILS approach to RWY 9L at Philly Intl KPHL, the autopilot brings me in on the right edge of the runway, instead of the runway centerline. It did it in the Airbus and in the 737. I'm going to try another airport (JFK) next, but it seems odd to me. I believe I have the right freq (108.95) for the 9L localizer. I'm using APP mode on the autopilot.

i had the same problem at KSEA on 34R i tried it again and all was fine.

I don't know about KPHL, but a number of localizers are offset in reality and Microsoft modelled these. It's always worth checking the real world information if you're in doubt.

i had a very similar problem at STL when landing today. its not that the headings and courses are different, its that the ILS doesnt even lead to the runway...i was flying the 12L ILS there and flying it down the chute perfectly, but ended up having to pull up quickly after realizing it was leading me to a point somewhere north of the airport, parallel to the path i was supposed to be on. i had to pull up the GPS, and zoom in, and only then did i realize what a complete mess STL is, and i assume its not the only one. ILS's leading everywhere, and only 1 of them leading to a runway (the 12R loc happened to lead to 12L, probably by sheer coincidence)

>i had a very similar problem at STL when landing today. its>not that the headings and courses are different, its that the>ILS doesnt even lead to the runway...i was flying the 12L ILS>there and flying it down the chute perfectly, but ended up>having to pull up quickly after realizing it was leading me to>a point somewhere north of the airport, parallel to the path i>was supposed to be on. i had to pull up the GPS, and zoom in,>and only then did i realize what a complete mess STL is, and i>assume its not the only one. ILS's leading everywhere, and>only 1 of them leading to a runway (the 12R loc happened to>lead to 12L, probably by sheer coincidence)Perhaps you were chasing the LOC/DME (IABW/110.10) associated with 12L. It is located where you describe (north of the airport). There is another one (IFXD/110.55) associated with 30L east of the airport.If you go to Visual Flight Path on the FSX Aircraft pulldown menu you can turn on visual indicators for the ILS.Dial up 108.90 (the Cat II associated with 12L) and you will see that it does indeed drop you onto 12L.Likewise, Dial up 109.70 (the Cat I associated with 12R) and you will see that it does indeed drop you onto 12R.KSTL is a big airport. There ARE a lot of ILS. The ones that are supposed to ALL put you on a runway.And in case something has recently changed, note that the Nav data FSX is built on is a snapshot from February-ish of 2005.-Doug

>I was wondering if I'm doing something wrong or if there is>something funky in FSX... When doing ILS approach to RWY 9L>at Philly Intl KPHL, the autopilot brings me in on the right>edge of the runway, instead of the runway centerline. It did>it in the Airbus and in the 737. I'm going to try another>airport (JFK) next, but it seems odd to me. I believe I have>the right freq (108.95) for the 9L localizer. I'm using APP>mode on the autopilot.I spoke with our data manager about KPHL 9L ILS alignment. Here is a summary:We receive runway placement information in two ways: 1) Center Lat/Lon, length, width and heading. 2) Threshold Lat/Lons, width (typically more accurate).KPHL 9L was received via method 2, and we calculated the length (9487 ft.) and heading (85.45). The associated ILS was received as heading 85.0.The ILS is category 1 - for use with some visibility (2400 feet RVR / 1800 feet RVR with runway TDZ and centerline lites). These do not necessarily line up exactly with runway centerline.Remember that ILS has a course width aspect (it's not just a straight line).As such, we allow for a certain amount of discrepancy with Cat 1 ILS before we start investigating. Cat 2 and Cat 3 ILS we make sure line up exactly.Hope this explanation helps.-Doug