Going to upload landing at LTBA 35R on YT, so you can compare. Lj. Prodanovic

HiI cannot see the video as you removed it... but.... am I correct that your only issue is that the runway is a few hundred metres off? And that the navdata shows it "should be there"? If so.. Have you installed an AFCAD for that airport? Maybe you need to install a new one. I had a problem as I described for VIDP... and corrected it with a user AFCAD from Avsim. Paul

It can be scenery issue. There is great freeware LTBA scenery at avsim library, so I do not see reason to use default one or some bad afcad. Lj. Prodanovic

Here it is:

http://www.youtube.com/watch?v=nyCTVuuG9MM

It's low quality (my upload speed is very bad), but it's readable. Both nav radios tuned at 111.3, both course selectors at 355 (but, AP forced it to 354), APP activated, both APs ON Landing config: flaps 40 (but I recommend 30 for standard app like this), Vref 128, speedbrake armed, gear down. Standard weather Scenery - freeware LTBA scenery from avsim library. Lj. Prodanovic

Not sure what happened.. But I had that happen when I landed in Phoenix last night.. :/All looked swell until right to the last minute.. Not sure why though. I've done severalperfect autolands at other airports, so I know it doesn't happen all the time.

Here it is: It's low quality (my upload speed is very bad), but it's readable. Both nav radios tuned at 111.3, both course selectors at 355 (but, AP forced it to 354), APP activated, both APs ON Landing config: flaps 40 (but I recommend 30 for standard app like this), Vref 128, speedbrake armed, gear down. Standard weather Scenery - freeware LTBA scenery from avsim library. Lj. Prodanovic

Sorry for delay, here is my video also. I recommend to watch in HD format :).

While approaching LTBA 36R the localizer bug captured 100feet before touchdown. Airplane is PMDG 737NGX and same problem in PMDG 747-400X also. I didn't try MD-11X. My config is; Both nav radios tuned at 111.3, both course selectors at 355 (oops... they were automatically changed to 357 ????), I'm not sure that the APP activated, as you'll see on video I'm strugling to press APP for light go on, F/O APs ON. Landing config: flaps 40, Vref 149, speedbrake armed, gear down. Standard (windy) weather. Scenery - Default LTBA Thank you for your attention and effort. I'm going to watch your video.... Regards.

Ok, as far I can see, airport ILS equipment is good, something is wrong with airplane. First of all, runway heading is not 357 so, AP should not force that course. At your videoclip, I cannot see both AP ON, just one. FMA shows LNAV and G/S, so you fly in some RNP mode with simulated Glideslope (or real one but without Localiser captured... huhh I'm confused here)... Localizer is NOT captured and that's why you are not in rwy course. That what you are flying is NOT ILS my friend :) You armed VOR/LOC but never captured it, so its still ARMED on your video (look at FMA, middle column, white letters) Are you sure you selected ILS35R, not RNP, or RNAV 35R or something other? EDIT: I watched video once again: VOR/LOC became active few feet befor touch down. So, my suggestions are:1. Make sure your frequencies and courses are correct (for LTBA 35R it should be 111.3 on both radios, and 354* on both course selectors)2.When you entering in ILS, first ARM VOR/LOC.3. Make sure VOR/LOC mode become ACTIVE (watch your FMA). FMA is the ONLY reference what AP/AT modes are active, lights on MCP buttons are not reliable!4. Make sure rnp symbology disappeared on PFD, and ILS symbology are active.5. Click on APP button, and make sure that both GS and LOC are ACTIVE, not just armed.6. Engage both Auto pilots7. When you get LAND3 mark at PFD, you are good8. Keep monitor your instruments Lj. Prodanovic

If you have the setting "Auto Tune FSX OBS" on (I forget the exact wording), what you enter into the CRS windows won't matter, it's going to try to read the FSX BGL and set it to the actual course automatically. We'll look at this and make sure it's actually working right - I have seen it land off to the right at KLAS for instance when using the FSDT version - not sure why it's doing that.If you turn that option off and play with the course though you should be able to get it to land correctly if it isn't with it on.

Hakan, You are flying in LNAV mode. This is the reason for the behaviour you see. You need to capture the LOC sooner. As this is a straight in approach the aircraft might have difficulties capturing the LOC. Use HDG SEL and steer towards the LOC needle at final approach and you should see a nice capture and autoland. The APP mode is armed for LOC/VOR and active for G/S. Once G/S and VOR/LOC are armed or active you cannot press APP anymore. Only way to get out of this is to do a G/A or disconnect the AFDS completely. Hope it helps,

During the flight on MCP: F/D:on (L/R), A/T: Arm, VNAV: on, LNAV: on and CMD A or B : on. I've never turn on both the CMD's. According to the aiport chart, 11nm before the runway (ILS signal) I'm pressing the APP. When the plane catch a ILS signal and start to glide sloping VNAV and LNAV lights goes off, just SPEED and APP stay on. So I can reduce the speed as referred by FMC. Is this procedure wrong? Could you please explain what the "RNP" is? Thanks.

FMA is the ONLY reference what AP/AT modes are active, lights on MCP buttons are not reliable! I made screenshot from your videoclip. Look, LNAV light is OFF, but at FMA (FMA is that thing I framed with blue color), LNAV is still active! When you press APP, and capture LOC and glide, you can engage both APs (and you should do that), and at screenshot, only one is engaged. That red circle at the botom of the PFD is NPS Deviation Scale ( I called it RNP symbology because I forgot real name, but in fact it is RNP symbology). Basic about RNP:http://en.wikipedia.org/wiki/Required_navigation_performance Lj. Prodanovic

During the flight on MCP: F/D:on (L/R), A/T: Arm, VNAV: on, LNAV: on and CMD A or B : on. I've never turn on both the CMD's.

All is correctly set up for A/T and A/P operations. If you want a full AUTOLAND you need to activate both A/Ps. This can only be done after APP is selected (or something to that effect). If the button on the MCP is lit it means that you can deselect that mode.

According to the aiport chart, 11nm before the runway (ILS signal) I'm pressing the APP. When the plane catch a ILS signal and start to glide sloping VNAV and LNAV lights goes off, just SPEED and APP stay on. So I can reduce the speed as referred by FMC. Is this procedure wrong?

The procedure is not wrong but you need to understand what the plane is trying to do. The buttons on the MCP will not really tell you what mode the plane is in. You need to look at the FMA for that. Top of the PFD. In your case you are on MCP SPD speed mode, LNAV lateral mode (which is what screws up your landing) and G?S for vertical mode (which is correct for a ILS approach) Read my previous post again and see if you understand what I am trying to say. Hope it helps,

If you have the setting "Auto Tune FSX OBS" on (I forget the exact wording), what you enter into the CRS windows won't matter, it's going to try to read the FSX BGL and set it to the actual course automatically. We'll look at this and make sure it's actually working right - I have seen it land off to the right at KLAS for instance when using the FSDT version - not sure why it's doing that. If you turn that option off and play with the course though you should be able to get it to land correctly if it isn't with it on.

Thank you. I am going to check that.

Hakan, You are flying in LNAV mode. This is the reason for the behaviour you see. You need to capture the LOC sooner. As this is a straight in approach the aircraft might have difficulties capturing the LOC. Use HDG SEL and steer towards the LOC needle at final approach and you should see a nice capture and autoland. The APP mode is armed for LOC/VOR and active for G/S. Once G/S and VOR/LOC are armed or active you cannot press APP anymore. Only way to get out of this is to do a G/A or disconnect the AFDS completely. Hope it helps,

Thanks. As far as I understand, I should turn off the LNAV before glide sloping or pressing the APP button.

You do not have to turn off LNAV (I like to use HDG SEL standard 30 degree entry for LOC capture), but whatever mode you use, when VOR/LOC mod become active, all other lateral modes automatically go OFF. There are problems sometimes when you do "strait-in" approach, because you fly parallel with localizer,so you are not on intercept course and autopilot cannot capture it. Lj. Prodanovic

As far as I understand, I should turn off the LNAV before glide sloping or pressing the APP button.

No. You need to manipulate the aircraft to intercept the localizer LOC. In this case being a straight in approach I would select HDG SEL and turn the aircraft towards the LOC diamond. That is the white diamond under your attitude indicator on the PFD. This way the aircraft will be able to sense and capture the LOC and the FMA should chaneg from HDG SEL to LOC. Once you see VOR/LOC and G/S you are set up for the ILS approach. I see Lj. Prodanovic beat me to give you same advise. :)