I was flying into Mallorca with the PMDG747, I was told to fly heading 95 degrees at 4500ft to intercept the ILS for runway 06L. I did exactly that and intercepted the localizer. The pink triangle (localizer symbol in my primary display) was all the way to the left, and didn't even move. I kept the localizer enabled until the glide slope became level with the plane, I then pressed on "APP." I had 110.90/060 in my NAV radio. I have done this many ILS approaches before. The plane flew level for a minute (pink triangle was still level) and then started moving back up to where it came from, all the while the plane was flying level at 4500ft.What happened there folks?Thanks for any advice/help.When I missed my approach, I asked for vectors to another runway. ATC told me to maintain 6000ft....and I did! but it kept nagging me to maintain 6000ft and wouldn't stop.

So you never were able to capture the localizer? Sounds like you flew past the runway and was picking up the G/S for the opposite runway. Sometimes I have noticed Radar Contact can get put in a tight spot based on your arrival route where if you follow the headings RC gives you to intercept the localizer, you will never get in a position to properly fly the final approach.About ten days ago I flew into Cape Town and the arrival route pretty much had me in a straight heading into the actice runway, but RC said to expect vectors, which makes sense, and then gave me a vector of what would have been a left turn of about 5 degress, but I was about 25 nm from the threshold (I am guessing, I do not remember exactly but it was very far), too far for the localizer and glide slope to be active, so if I had followed the heading RC gave me, I would never have captured the localizer. If what I am describing is the same thing that you experienced, then my advice would be to always have a "sense" of where you are around the airport, so when RC gives you a command to maintain heading until established on the localizer that doesnt jive, you can ignore it and proceed in a direction that will guarntee a successful loc capture.

Hi. Thanks for the response. I did capture the localizer, I had the pink localizer triangle show up on my primary display. RC ATC asked me to intercept it about 30 degrees from the active runway, about 20nm out. I eventually intercepted the glideslope. It's just that my plane never turned to center the localizer and never went down on the glideslope for some reason. Could be a PMDG problem and not exactly RC. But I've done ILS approaches many time before. Not sure what was going on. Any other ideas?

Hi. Thanks for the response. I did capture the localizer, I had the pink localizer triangle show up on my primary display. RC ATC asked me to intercept it about 30 degrees from the active runway, about 20nm out. I eventually intercepted the glideslope. It's just that my plane never turned to center the localizer and never went down on the glideslope for some reason. Could be a PMDG problem and not exactly RC. But I've done ILS approaches many time before. Not sure what was going on. Any other ideas?

So the localizer indicator showed up but Autopilot never changed your heading to track it? That could still sound like my scenario. And I believe their is a limitation in default settings of the PMDG that will prevent the autopilot from following the glideslope prior to capturing the localizer, this however can be turned off in the PMDG settings.Were you flying with the MAP displaying on the ND? THe PMDG 744 has a nice feature that sort of "extends" the runway for about 5nms with a white dotted line that can be used to line yourself up with the runway. Do you recall seeing this and where it was in relation to your plane and the localizer indicator?Also, are you using Navigraph to update your FMS? The PMDG 744's FMC will automatically tune the ILS radio using stored information, not information gathered from FSX. The Navigraphs updates are current to realworld conditions, so you can update your FMS to be up to date, but your airports in FSX are still the old ones and will not reflect the new ILS frequencies, new runway designators, etc.

Make sure you check the LOC ident on your PFD. FS has a problem where the same LOC frequency is used at both ends of the same runway. By default all backcourse transmitters are enabled and you'll pick up the incorrect one unless right on the center line.Like Cras suggested, use the extended runway center line on your ND to see where you are in relation to the runway.You don't state the airport but check to see if you were at or above the transition level. At some airports 6,000 feet would be above and you'll here maintain FL60 instead of 6,000. See the RC manual on this. You'll need to set your altimeter appropriately and don't rely on the "B" key as it is hard coded for 18,000 feet transition level for FAA airports. That can lead to incorrect altitudes.On the PMDG 737NGs I load the IAP (not STAR) from the FMC DEP/ARR page database at the time RC approach makes the assigned runway known. It provides the situational awareness similar to what Cras referred to.I believe the 747 autotunes your ILS. If its database differs from the navaid properties in your scenery for RAW (ILS/LOC) data, you'll have incorrect tuning.As far as the GS remember the GS indicator must be above center at least slightly for you to intercept it and descend on APP. On the PFD you'll see indication when the AP is locked to it.

Thanks for the responses. I have attached a sketch to this post which shows what I think was my path, unfortunately I did not record the flight nor was I paying much attention to my situational awareness during approach, so I may be wrong.Ok, I am very much confused about how FSX/RC/PMDG ILS frequencies/data.Where does Radar Contact get its localizer altitude/frequency information from?Where does FSX get its localizer altitude/frequency information from?Where does PMDG get its localizer altitute/frequency information from?I guess I am trying to understand who depends on what or which governs over the others?The ILS frequency and course for runway 06L for Mallorca shown by RC was the same as that shown on FSX. I inputed those numbers, manually, into my PMDG Nav/Rad button on my FMC. I assume, and correct me if I am wrong, that RC takes these numbers from FSX. But where does PMDG take these numbers from if I used its automatic feature to obtain the ILS frequency/course?I know this is a silly question, but I always press "B" to adjust my Q&H. How can I do it manually on the PMDG747? (slightly off-topic, but might as well ask anyways. ;))What is the range of a localizer for interception?If I deviate from RC to capture a localizer when it is giving me bad data, how I can shut RC up so that they wouldn't terminate my flight?One thing that I forgot to mention is that I was supposed to fly at FL410 but requested FL310. My aircraft alert system was going off the hook with many planes just whizzing right past me at FL310. How could RC allow stuff like that to happen?Thanks.

Radar Contact gets is ILS nav freq from the Sim itself, while PMDGs FMC uses a database which can be updated using the Navigraph service. Using this service will assure your FMS is up to date with real world procedures, runways, and ILS frequencies, but in no way updates the actual airports in FSX, you need to download AFCAD updates for that, which is why if you update your FMC you will see say, KORD having RWY 28, but the default FSX scenery has this runway as the old 27L.Now second off, the ILS radio in the PMDG 744 is controlled only through the FMC, it seems like you already know this, but just making sure. You do not need to do it manually, but when you input your destination runway into the FMC, it will "queue" up the ILS freq. and it will activate it when you are close to the airport. You can tune it sooner by just clicking on the softkey next to the ILS line in the FMC it capture that data, then press the soft key again to put make it active. The ILS frequency, Indentifier, inbound course, and DME if applicable, will display on the PFD right above the artificial horizon.As far as capturing a localizer, it seems in FSX you can get a signal about 25 nms out, and a G/S signal around maybe 18 nm out or closer. I am guessing here as I am not sure, but you will be able to pick up the localizer first, and the G/S needle will stay level. If this is the case, DO NOT activate approach mode. It could cause problems. Only activate VOR/LOC mode for the A/P to track the localizer. Only arm approach when you have an active G/S (where it is sitting at the top of the indicator.)

RC does not terminate your services unless requested but you'll hear a lot of noise.What bad data was RC giving you? If you want altitude flexibility in departure and arrival altitudes before your flight on the RC controller page select NOTAMS. You must still adhere to the crossing restriction just before you enter the approach zone about 40 nm out. If you wish to navigate approach on your own inside of 35 nm out after acknowledging the first vector request an IAP to the runway suggested (especially as RC looks at AI arrivals first) or a runway of your choice.FS aircraft avionics respond to the frequencies built into the scenery, not what is in the FMC database. RC's localizer/GS frequencies come from your scenery database. Be sure you have makerwys.exe version 4.41 or better installed in your FSX folder. In the pinned link for both FSUIPC and makerwys you'll see makerwys in the FS9 section but it is for both versions.RC does attempt to steer aircraft at you altitude around you if you have Interact With AI checked in the RC options. This will also enable RC traffic calls on the comm when you check AI chatter in the options. In general you don't want Prerecorded AI Chatter enabled. If AI are approaching you at some extreme angles, or if they are climbing through your altitude, RC may not divert them.If you have RVMS checked on the RC Controller Page RC will alter your cruise altitude to comply. Unfortunately AI does not follow these rules in FS9 and not to my knowledge in FSX. See http://www.jdtllc.com/FAQ.htm#1 . The RC manual should explain about RVSM.I have the PMDG 737NG series. See if there is an option in the 747 to select TCAS alert altitude range.

If I deviate from RC to capture a localizer when it is giving me bad data, how I can shut RC up so that they wouldn't terminate my flight?One thing that I forgot to mention is that I was supposed to fly at FL410 but requested FL310. My aircraft alert system was going off the hook with many planes just whizzing right past me at FL310. How could RC allow stuff like that to happen?Thanks.