Hello fellow members:I am having a repeatable problem when performing an ILS approach to Burbank airport (KBUR) to ILS RWY 8. I use the same autoland procedures as found in tutorial #1 (the NGX performs flawlessly when performing the autoland to Schiphol). The localizer and glide slope are captured, and the aircraft makes a perfect decsent like in tutorial #1 to Amsterdam. However, when the aircraft is about 200' on the approach, the aicraft vears to the left and the autopilot cuts off automatically. Both NAV radios are tuned properly (109.5) and the course selector is set at 76 degrees as per the current chart. Both CMD A and CMD B autopilots are active(again, just like the procedure in tutorial #1). However, what I don't see is LAND 3 annunciated. I don't know what I am doing wrong. Maybe the ILS approach to RWY 8 doesn not support autoland? I'm sure I am doing something wrong or have missed a setting somewhere. I know how to perform manual landings, but I wanted to test out the autoland feature of this aircraft.Here are the specs of my system:Intel Core i7-2600 @ 3.4GHz8GB RAMNvidia GeForce GTX 560 TiWindows 7 Professional 64-bitAll drivers, chipset drivers, etc., are up to dateAll service packs up to dateAdd ons:No yoke or ruddersNot using FSUIPCUsing Logitech Extreme 3D Pro joystick onlyNo add-on aircraft except PMDG 737 NGX (800, 900 series only)SP1cWorld of AI (free ware)Blue Sky Scenery (free ware)Any guidance would be appreciated. Also, since installing SP1c, I have noticed too much "air" noise from the air conditioning system. It is absolutely ear deafining, even when performing the cold and dark procedure at the gate before the engines are started. As soon as ground power is applied, the noise level is very annoying. This was not the case using SP1b. Any clues or work arounds?Other than that, the product is absoultely amazing!!!!Thanking everyone in advance for help.Robert

I checked the FSX files, It doesnt appear to be your fault. The default FSX data for KBUR is kind of messed up. (i am not sure if Real life or FSX data flaw), The ILS is placed ahead of the runway, causing the airplane to "run out" of the localiser before it lands. So the autopilot disconnects. See your FSX map, with ILS display, for a visualisation.Regards.Marcus JianEdit, You may try this fix I just did for the airport sce file.http://www.mediafire...bd72r11u8x6mxg6Basically just repositions the ILS. You can try if your autoland works now.Place into FSX/Addon scenery/scenery folder2nd edit. Im assuming your airport in question is a default fsx one. I dont know if this will conflict with any custom airport scenery you may already have for KBUR.

Hello Marcus:Thanks so much for your research and solution! I'm glad to know that I was performing the proper steps and that it was a problem with FSX. I will download the bgl file and let you know how it works.Regards,Robert Amster

Are you sure it isn't an LLZ approach or offset localizer and the GP is erronous (i.e. should not be there)? Would make more sense....and it is the case! It is a LOC approach (localizer only) to RW08. VGSI = Visual Glide Slope Indicator not aligned with glide path (meaning visual cue is INVALID).http://dtpp.myairpla...-3/00067LY8.PDFNote that such an approach is a NON-PRECISION approach!Best regards,Robin.

The LOC is in front of the runway just like the real approach..

You are not allowed to fly with the autopilot coupled below 977 ft MSL on this approach. Always check the charts before you attempt to fly an instrument procedure.

You are not allowed to fly with the autopilot coupled below 977 ft MSL on this approach. Always check the charts before you attempt to fly an instrument procedure.

And why -you think- isn't he allowed to do that sir?

Are you sure it isn't an LLZ approach or offset localizer and the GP is erronous (i.e. should not be there)? Would make more sense....and it is the case! It is a LOC approach (localizer only) to RW08. VGSI = Visual Glide Slope Indicator not aligned with glide path (meaning visual cue is INVALID).http://dtpp.myairpla...-3/00067LY8.PDFNote that such an approach is a NON-PRECISION approach!Best regards,Robin.

I think you have the wrong chart. There is a valid ILS approach for RWY08 (00067ILZ8.pdf)Best Regards,Bert Van Bulck

And why -you think- isn't he allowed to do that sir?...

Because the approach chart says so http://155.178.201.1...3/00067ILZ8.PDF. As for why the approach chart says so, I'm guessing because the localizer does not work properly below 977ft MSL. Perhaps there's some sort of interference from the NDB beacon which is located at VINEE. It also appears that the localizer is at the approach end of the runway instead of the far end. That would be an obvious reason why autopilot coupled approaches would be illegal here

Because the approach chart says so http://155.178.201.1...3/00067ILZ8.PDF. As for why the approach chart says so, I'm guessing because the localizer does not work properly below 977ft MSL. Perhaps there's some sort of interference from the NDB beacon which is located at VINEE. It also appears that the localizer is at the approach end of the runway instead of the far end. That would be an obvious reason why autopilot coupled approaches would be illegal here

yup, missed the text at the top!Bert Van Bulck

Hmmm, in that case you may disregard my so called "fix", I am not aware of the real procedures for most of the airports. but just you know there isnt anything wrong with your setup or procedures(in engaging autopilot), Though there are many airports around in FSX whose ILS's are misaligned, especially in more remote areas and those without custom scenery. Using those will land you onto the grass. Check with real life charts if necessary. The fsx map can give you the placement of the ILs in the FSX world. Zoom to the closest level and see if the ils feather is in line with the runway line. If i am not wrong one example I can remember offhand is WMKJ. Regards Marcus Jian

The localiser is set up on the approach end, rather than the departure end (interesting choice there...) so as you near it (around the Vinee LMM) you enter the cone of silence for the antenna array. With a loss of localiser signal, it is not possible to complete an autoland - the note indicates that you must handfly after the DA.