Hi all,I've been having a bear of a time with autoland and have yet to capture a localizer at any airport.I have a feeling my problem is my hard core knowledge of Fly!'s PMDG 777, Dreamfleet's 737, and PSS's 777.I have those procedures ingrained in my head so much I wonder if there is a step that I am missing due to the increased(?) complexity of the PMDG 737NG versus the aformentioned aircraft packages.I've looked through these forums at the other autoland threads and followed them to the letter (albeit, none of them are very detailed).Let's do this the easy way. Can someone lend me a hand with a simple step-by-step write up (push this, push that, do this, do that, DON'T do this, don't push that). Once tested, may be we should add it to the FAQ or make it a sticky.Here's what I've been doing so far:1) Upon advisement of the active approach runway from ATC (whether it be VATSIM or FS9's ATC), I select the runway in the FMC (under DEP/APP) and EXECute. a) This of course marks the approach vector on my PFD. Looks good.2) I'm now following the vectors given to me by ATC (whether live ATC or FS9)3) I have my MCP alt set to the capture alt (so KEWR (Newark, NJ) would be 3000' and I'm flying at that altitute on an intercept vector given to me by ATC.4) I have my HDG HOLD switch engaged to keep this intercept course4) I set NAV1 and NAV2 to the localizer frequency (NAV1 is done for me with the PMDG737NG but I do need to manually set NAV2).5) I engage both A/P (both CMD A and CMD B lit up).6) I engage APP (APP lights up)7) I set my MCP alt for a missed approach (I'm still flying straight & level @ 3000')8) I see an unboxed VOC/LOC and G/S in the PFD9) ... My plane proceeds to glide carefree right past the localizer.... every time... *chuckle*. No turn towards the active or start of any descent. *chuckle* Sorry it just makes me laugh when I think about it in regards to my imagining the tower controller watching my aircraft fly past his runway 15 times in a row. I've tried the following airports: KDEN, KEWR, KJFK, KLAX, KSFO, KLAS, ad nauseumI do try to keep a sense of humor about this considering I'm flying with live traffic. I've reduced myself to flying with AI traffic to keep the VATSIM ATC's from grounding me. Oh the humanity! :+P.S. I would go for a manual landing but I'm currently reduced to keyboard control only (ugly!) until I get myself unpacked and locate my flight yoke & HOTAS. Chandler "CAT III Retard" Lugovsky

Did you forget to set the COURSE window to the intercept course? HummmmmmmmEDIT FOR FUN SAKES: 3000' heading of 089, localizer course is 035, I slow to 170 flap 5 by final approach fix, NAV 1 & 2 always set to FEQ ILS and set intercept course (035) on the MCP course window. I PUSH VOR/LOC which arms by showing white on the PFD untill the aircraft captures localizer. The aircraft captures correctly and I am smiling. AT one dot G/S I select GEAR down, flaps approach ref @ 15 etc, I also now arm APP and push second CMD (which does nothing but ARM untill capture with APP light on button) G/S capture, APP light goes out (This means ACTIVE) G/S on PFD turns green and TMD displays GA and I am slowing to my final approach ref like a happy camper and down I go..... With DUAL Autoland the A/T will disconnect on it's own upon touchdown, if you are single channel you will have to manually turn of A/T, with either landing you will have to manually turn off the A/P.....EDIT 2# lol, Fred is correct but if you set Nav 2, I would assume that Nav 1 was the same?? On the real bird you need to set course intercept, but I think this is not an issue in FS ;( but it should be![h5]Best Wishes,Randy J. Smith [h4]P M D G 7 3 7 NG[/h4] [h3] Realism on the horizon [h5]AMD XP 2200 |MUNCHKIN 512 DDR RAM |ECS[/b ][i] K7S5A MB[/i] |GF2 MX 32 MEG and still runs GOOD!|WIN XP PRO |MITSUBISHI DIAMOND PLUS 91 19"[/h5]

Chandler,I think I have spotted your problem. NAV1 is not autotuned to the runways ILS frequency in the 737NG series. Make sure to set NAV1 to the proper freq, but besides that, your procedure looks good :)

I saw another procedure here in the forums and use it, and it always works: Both radios tuned to the ILS, approaching the ND ILS line at 4000ft on AP A, using HDG or LNAV. When ILS markers become active, I engage LOC. Then I watch the vertical ILS marker, and engage APP just beneath it. Verifying "Single CH" in the PFD, I engage AP B. "Single CH" goes away, and it`s time to arm the autospoilers/autobrake.I have a problem with ILS and some flightplans. If I do not pass through the last waypoint before the destination airport, I don`t receive the ILS, even if I tuned them manually. Found a way to overcome this, working FAST in the FMC, I put the airport into the scratchpad, and paste it over the (ACT) waypoint on the LEGS page.

Oooooooooooooooooh. Interesting.I'll have a shot at it. Clear the skys. Chandler's takin the big iron up again. :(

>Chandler,>>I think I have spotted your problem. NAV1 is not autotuned to>the runways ILS frequency in the 737NG series. Make sure to>set NAV1 to the proper freq, but besides that, your procedure>looks good :)Nailed it! Thanks a lot Fred and everyone else here who provided their wisdom.You were spot on. The FMC does NOT autotune your NAV1 to the ILS localizer frequency. It has to be done manually (both both NAV1 and NAV2).CAT III's a plenty now.-Chan