Hi Folks I flew(?) the KDEN--KLAX flight in Fred's tutorial, 1st try, and I didn't think it went too bad for the first shot. I never completed the flight because the aircraft cruised right over the LAX runway at approx 2000 feet. I suspect I failed miserably in exactly following Fred's instructions for the Approach and Landing phases. As a result, as a start at least, I have two questions: (1) How do I activate the Radar Altimeter? It hung at 200 all the way. (2) When I enable 'AP B' to engage the 2nd autopilot will the 'AP A' autopilot indicator extinguish? It does so I assume only one AP works at a time. (It is different than the multiple PS13 autopilots) Thanks for any help.Regards

Are you tuning in both NAV radios? You have till about 800AGL to active it so make sure you have the navs tuned correctly.Both CMD lights will stay illuminated, only the APP button once active will extinguish. [h4]Best Wishes,Randy J. Smithhttp://img.villagephotos.com/p/2003-8/196432/winglets_lg.jpg [h3] 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"[/h3]

(1) How do I activate the Radar Altimeter? It hung at 200 all the way.That is your decision height bug, not the radar altimeter. The numbers you see in digits in the center lower part of the PFD is the actual radar altimeter.(2) When I enable 'AP B' to engage the 2nd autopilot will the 'AP A' autopilot indicator extinguish?No, this will only happen is you have NOT pressed the LOC button to set up localizer/Glideslope cature.If you forget to tune the second radio as Randy suggests in his post, it will tell you that you have not done so with a FMC message about radio disagree.If you are finding that pressing the CMD A/CMD B buttons is toggling between which is active, it is because you are still in HDG SEL or LNAV modes instead of localizer capture/glideslope capture. These will appear in white text under the current modes then switch to green when active.You know you are doing it right when the PFD shows Single Channel prior to setting the other CMD button. This is simply warning you that you are only running with one of the autopilots for the landing.I suspect based on your overflight, you did everything right except pressing the LOC button on the MCP ;)Ray

I'd just like to re-interate the tune both NAV radios part. Also, make sure to press the button that looks like <-> when you tune your nav radios, as that makes the aux frequency the main one. And make sure to press the LOC and/or APP buttons =)

The nice thing is that the FMC/ND will tell you if you mess up the radios, but it really can't help if you forgot the APP button cause it doesn't know you want to land until you press it :-lolRay(btw Fred:, any way you can publish it in something other then MS Word? (perhaps a RTF format that will load in the stripped down Wordpad?)(edit because it is Friday and I am MCP brain dead! Thats the APP button, not the (doesn't exist LOC button)!!!)

>(btw Fred:, any way you can publish it in something other then>MS Word? (perhaps a RTF format that will load in the stripped>down Wordpad?)Yes, I think I can whip up a PDF version. I didn't think I could when I published my tutorial, but I now know I can, courtesy of OpenOffice =) I will consider re-uploading my tutorial in PDF format.If there is enough of an outcry perhaps I will ;-)

I think you may also be able to do it online through Adobe's web based stuff. It probably will take your word doc as input and spit out a pdf. I'd do it for you, but I'm rather backlevelled with Version 4 and don't use it enough to pay them more money to upgrade.https://createpdf.adobe.com/index.pl/843723...837?BP=IE&v=AHPGive it a try, first 5 are free...Ray

Thanks for the link Ray!

Thanks Randy, Ray and Fred, You hit the nail on the head. I DID forget to click on the LOC switch. Even though I read the Tutorial several times I find that once you try a flight, and goof, I pay much closer attention to the DETAILS of the tutorial. Also a second reading of the Operators Manual gives further enlightenment. Yet the crux of problem solving is a combination of reading material and excellent help from you folks. One thing I still do not see is the RADAR ALTIMETER readout but I guess one has to have the aircraft all powered up and, right now, mine is sitting at Meigs (FS2002) powered only by the fact that the Cessna default is Power-ON. Haven't tried the 737NG in FS2004 yet but that time will come. Time for another go at Fred's Tutorial and see how I do this time. Practice, Practice and more Practice. Sounds like my old cello teacher but that's the name of the game. Thanks men. Probably will be back again.Regards

Hi Ray, Yes, the APP button. My two Nav radios were tuned to 109.90 and this was indicated on the ND. I thought I hit the APP button but may not have because I was looking for the LOC button. So many things were going on at that time, following the recipe while in-flight, I'm not exactly sure what I did. Another attempt will make life easier.Thanks Ray

Pictures are worth a thousand words at times ;)http://forums.avsim.net/user_files/35267.jpgSee the number 11 in yellow on the bottom part of the display?That is your radar altimeter reading. The NG is sitting 11 feet off the ground (this will vary a bit based on gross weight).See the Radio 200 in green?This is the height for the Radio minimums callout, also known as the DH (decision height).http://forums.avsim.net/user_files/35268.jpgSee the dial on the upper left? Use this to control the actual height for this callout (generally where you are going to abort due to runway not in sight or carry through on the landing.)Ray

Hi again Ray, I'll be darned and more so. Unless I missed it again, I took an hour or so and just went through the complete Operations Manual and saw no reference to RA indications. I'll just have to go through it again. I did find out that the DH can be set on the EFIS panel. The DH control is very similar to that in PS1. I'm not sure how long it would have taken me to notice those numbers in that location on the PFD. Yes you are a correct. A picture is worth ......Thanks.Regards

>Thanks for the link Ray!Fred, in case you need it. I've got Acrobat 5 here. Just send over the document to my e-mail address and I'll spit you back out a PDF.I'll do it whenever I see it in my inbox.Hope that helps.-Chandler

"That is your radar altimeter reading. The NG is sitting 11 feet off the ground"Please note.... On the real aircraft, "11" feet would mean that the aircraft was still in the air. Hopefully this will be fixed in SU2 ;-) The RA readout is normally white, but changes to amber when the aircraft goes through the selected Decision Height (DH). It returns to white either when the DH alert is manually reset, the aircraft climbs to 75 feet above the DH or when the aircraft lands.The readout is designed to show zero when the main gear touches the runway with the aircraft in a normal flare attitude. When the nose wheel is on the runway, the aircraft is no longer flared, so shows a height readout of around minus 4 feet (-4).Cheers.Ian.

Hi FolksI flew(?) the KDEN--KLAX flight in Fred's tutorial, 1st try, and I didn't think it went too bad for the first shot. I never completed the flight because the aircraft cruised right over the LAX the flight because the aircraft cruised right over the LAX I read some references to Fred's tutorial - but did not find from where i can copy it.Thanks for any info.Werner Angerer