I think the PIC767 panel is the best around, I love to fly it and I would love to be a master at doing that. I though I was pretty good but after tonight

I'm not sure how you descended from 10000 to 4000 but at 10000 set the MCP to 4000 then engage FL CH. The aircraft will not descend below the set MCP alt. The light will show prior to reaching your target alt {4000} and level off to it. Be sure to check your current altimeter and most likely you did not reset it?? The localizer problem is one that many I know have. So it's better to hand fly her in like the real pilots do :].Best Wishes,Randy J. [email protected]" A little learning is a dangerous thing"AMD XP 2100 |MUNCHKIN 512 DDR RAM |ECS[/b ] K7S5A MB |[b]GF3 64 MEG |WIN XP PRO |MITSUBISHI DIAMOND PLUS 91 19"

Thanks for the answers!Ok, that's what I did. At least I entered 4000 in the MCP. Where do I engage FL CH? About the localizer problem. Please don't tell me it isn't possible to solve?!? What if the weather only allows a CATIII landing, what am I supposed to do then?

Are you using the default NavData?Which airport and runway are you trying to land on?You actually enter 4,000 ft in the ALT or altitude window, which is part of the MCP or Mode Control Panel then press the FL CH button.I suggest a thorough reading of the excellent 767 PIC Panel Operations Manual, paying special attention to pages 46 to 51.

I'm using the latest AIRAC from the NAVData page by Richard Stefan along with some SIDs/STARs/APPs downloaded from there. Last night I tried to land at RJAA but I've experienced the same problem with ESSA and KEWR. Those are the only airports I've flewn to...I entered 4000 in the MCP, and thought it would stop the descend at that ALT, the descend was started by the VNAV so the FL CH was never engaged. FL CH button is on the MCP aswell, right? I've never understood it's function, now I read through the manual again and understand that I need to start using the FL CH function.I have actally read the excellent manual before but I must have missed that part.Anyway, I still have the localizer problem. Is there anything to do about it?

>I'm using the latest AIRAC from the NAVData page by Richard >Stefan along with some a STAR downloaded from there. What is your speed on approach? How may autopilots are you engaging?I'm sure someone will correct me but I usually aim to intercept the localizer at no more than 210 knots with flaps properly configured. When the glideslope is one notch above my altitude, I reduce speed to 180 kts using the Airpseed Select knob and engage APP. I maintain 180 kts until the outer marker, then drop landing gear, go full flaps and reduce to landing speed. Using this technique I have no problems landing at any properly equipped runway. >Last night I tried to land at RJAA but I've experienced the >same problem with ESSA and KEWR. Those are the only airports >I've flewn to... >Ok, using the same data, I've landed recently at ESSA (SwedFlight Pro scenery) and KEWR (Simflyers scenery) and I had no problems.>I entered 4000 in the MCP, and thought it would stop the >descend at that ALT, the descend was started by the VNAV so >the FL CH was never engaged. >From page 46 of the manual about FL CH mode; "Selection of this mode will never cause the plane to fly away from the target altitude. The plane will always fly to the target altitude. ">FL CH button is on the MCP aswell, right? I've never >understood it's function... I have read the excellent manual >but I must have missed that part. The FL CH button is right below the LNAV and VNAV buttons.

Thanks, I've tried a few approaches now and I think I'm certain it wont fly below cleared altitude before intercepting with the glideslop next time. I've started using the FL CH.I usually try to intercept the localizer at 190kts with an "angel of intercept" below 30 degrees. When pasing OM I usually have three autopilots engaged in order to autoland. But the autoland, as I wrote in the last post, doesn't work properly. Or am I doing something wrong here??

Randy,Weird... I have never had any problems with the LOC mode. None whatsoever. My take on it is that it's accurate and perfectly functional. Wonder what might be causing some people these reported problems...Tero

The only things I can think of are the following:(1) You're flying the approach too fast so the autopilot does not get a chance to stabilize. According to Robert Randazzo's Aircraft Operating Manual for 767-200/300:"Autoland Target Speeds: The speed at which the Autoland/Autothrottle approach is flown. Equal to 25REF + 5 or 30REF + 5 knots, regardless of wind conditions. The Autothrottle corrects for normal wind gust conditions through the airspeed and acceleration sensing system."I'm assuming you know how to find the appropriate REF speeds for your flap settings on the APPROACH REF page of the 767 FMC.(2) You need to check your landing runway information in advance and make sure the CRS (course) setting in the NAV 1 radio is the same as the listed runway heading. Its possible that they don't correspond and will cause you to veer off the correct heading. You should also rotate your heading selector on the MCP to the CRS heading, although this is usually done automatically.

The loc issue is a strange one. Now I did an approach to rwunway 01l at ESSA, everything seemed ok and I was line up properly with the localizer and followed the glidslope down.Then a few seconds before pasing over the runway threshold instruments showed me being one dot to the right of the loclizer, that resulted in the autoland starting turning and therfore missing the runway...Ok, I could follow the loc/gs until 1000ft AGL and then disconnect and land manually, but what if it is a CATIII landing, then I'm screwed... Besides I haven't practised landing manually that much so I can't say I make it 10 times out of 10 yet. Therefor having a working autoland would be really nice!

Ok, the speeds are correct! I tried to intercept with 10 degrees at 190 knots, went fine and it stabilized on the loc. Then all of a sudden it indicated one dot to the right, about 15-20 seconds before touchdown.Actually the CRS setting on NAV 1 showed 008, that is wrong. The correct direction according to my charts is 007. I'll try to land with 007 and let you know!Thanks for helping!

Oscar,Sorry I can not help you with your Localiser problems, I have never had any problems with CATIII except when the crosswind is strong.Don't worry about not being 10/10 on your manual landings. Keep practicing over and over, eventually you will become a pro - or at least satisfactory at landing like the rest of us.My suggestion is that you ARM Approach mode but disengage both the MCP and the Autothrottle, then all you have to do is follow the flight director in. If the weather is TRULY CATIII, then just pretend that YOU ARE NOT CATIII certified, and head for your alternate.Ian Elchitz CYWG

In FS2002, the CRS heading for runway 1L is 008, so what you're seeing is correct. Make sure that both the heading selector and the CRS heading both read 008.ANd I disagree that there's anything wrong with the Autoland function. I rarely use it but it has worked perfectly whenever I've used it.

Here are a few PICs. This landing actually went a bit better but it started turning left a few seconds before touchdown.http://members.chello.se/oscar/1.jpgStabilized on loc/gs with autoland engaged...http://members.chello.se/oscar/2.jpgRunway staight ahead, still stabilzed on loc/gs.http://members.chello.se/oscar/3.jpg40ft from ground, no longer on the stabil.http://members.chello.se/oscar/4.jpgAircraft starts turning left which drives me off the runway when hitting the ground...http://members.chello.se/oscar/5.jpgAfter hitting the ground, now manually trying to stear it to the centerline...What concerns me is picture number three, to me it looks like I'm straight above the centerline but according to the autopilot I'm not, disconnecting the autopilot at that time would probably take me down on the centerline but if I want to use autoland I wont land on the line, why??!By the way I can see I forgot to arm the autobrake on this landing! :)

I figured out your problem. Is it the default scenery you're using?The runway course headings in FS2002 are fixed at the time the program was created back in 2001. On the other hand, the NAVDATA is real world based on DAFIF information. Consequently what you are seeing is the variance between the real world NavData and the fixed settings in FS2002.At ESSA, FS2002 shows the runway heading for 01L as 008. In the Navdata - the wpNavAPT.txt file specifically - the runway heading is shown as 007.To correct the problem you will have to open the wpNavAPT.txt file in the FMCWP/Navdata/ folder and search for the following lines:Arlanda ESSA01R08227007 59.626178 17.950978000.0000000124Arlanda ESSA01L10830007 59.637256 17.913225109.9000700124The second line refers to 01L specifically. I interpret it as follows:ESSA01L - the specific runway10830 - runway length in feet007 - runway heading59.637256 - Latitude17.913225 - Longitude109.90 - ILS frequency124 - runway elevationPerhaps you should email Richard Stephan, who prepares the NavData, and ask him how to exactly interpret the data on each line. You can go to MapView in FS2002, look up the information for each runway and make the changes as appropriate. Please back up your NavData files since I will not take any responsibilities for any screwups.BTW, I just did a short night flight from ENGM to ESSA and I had no problems. I even stressed the autopilot by doing the TRS 2M approach to 01L and I nailed it with no problems while using the SwedFlight Pro scenery for ESSA.