Yes, I've done that. The AIRAC files that I downloaded did that for me! My wpNavAPT.txt looks just like yours now. I thought I had the latest AIRAC cycle before but apparently I didn't, I've been formatting my hard drive back and forth so I keep forgetting what changes I've made and when...Anyway, updating my wpNavAPT.txt didn't solve the problem, autoland is still not able to run on the centerline. It takes me down perfectly but at 40 feet it starts turning, always to the left. That turn results in me not landing on the straight, so when I touch the ground the aircrafts rolls off the runway to the right, really annoying.Can

Ok so do I, I use it to descend until I capture the glideslope?What are the alternatives? Using V/S mode is a bit risky in my opinion as it doesn't stop at the altitude entered in the MCP

Well Oscar,I'm out of ideas. I'm also not really sure what you're trying to accomplish. Even with an "autoland" you still have to ensure the throttles are at idle and you have to engage reverse thrust so it really can't be that much of an imposition for you to steer the plane after landing. I am not having the problem you seem to be having because I always hand fly the approach and landing.I know you mentioned Category III approaches earlier but even in a CAT III approach the pilot is still required to see the runway or he/she has to divert to the alternate. Maybe you have unrealistic expectations of the PIC panel?That said, there's also a tendency for the aircraft to hunt for the localizer after touchdown. I've seen it a few times at runway 25R at KLAX. (Simflyer's scenery) The aircraft veers hard to the right and only stops when the autopilot bar is disconnected.

Oscar,Just so I am clear on this, are you saying that when descending using the V/S mode it will not capture and level off at the altitude set in the MCP window? That is not right. It should always capture the selected altitude and never fly through it. If yours is doing that then something is wrong somewhere.Kevin in CYOW

Hmm, I've noticed one thing as I have practiced landings this morning. The autopilot follows the ILS really good, it actually indicates I'm about a dot to the right but it does nothing to correct it and that's good because I am on the localizer.Anyway, if I disconnect the autopilot when it announces 100ft and then do nothing the aircraft lands nicely on the runway, about

Yes that is what I'm saying!From the 767 panel operation & system manual:"An important note about VERT SPD is that unlike the FL CH mode (that will fly you TO a selected altitude) the VERT SPD mode allows the pilot to fly AWAY from the selected altitude. This means you can make the plan climb or descend regardless of the target altitude in the MCP."Isn't that what we're talkning about here?

Ok! I'm out of ideas aswell...Actually the problem is smaller now, I can let the autopilot fly the aircraft down to 100ft, then just disconnect the autopilot and land manually. I could probably do this at CATII conditions aswell.The only thing that bothers me is that there seems to be some kind of problem with the autoland. And you don't want to get up in the air with an aircraft that doesn't work as at should! :)Anyway, thanks a lot for your help and ideas. Your fast replies has been highly appreciated. Cheers!

Hi OscarThere are two things here being confused.What the PIC Team was referring to, if you aren't descending/climbing TOWARDS the MCP ALT, you will never level off. Example:You are at 5000 ft, MCP ALT is set to 3000 ft. You now engage V/S and select a climb of 2000 fpm. The plane will climb until it stalls, as it is climbing away from the MCP ALT.Now if you are climbing/descending to your MCP ALT, you will level off eventually. Example: You are at 10000 ft and descending. MCP ALT is set to 3000 ft. If you press V/S and select a sink rate of 2000 fpm you will descend to 3000ft and ALT HOLD will engage once at that level.Hope this cleared up the V/S system for you!Regards,Mark

It sure did... Thanks! :)

OscarP,For what it's worth, I just did a flight from EKCH to ESSA and landed in absolutely white-out conditions without problems. In fact I had more difficulty finding taxiway Yankee and Gate 3 than I had lining up on the center line.

LOL!!I bet you were a (the) Continental flight? I was Scandinavian 614! Departed a few minutes before you at Kastrup and landed a few minutes before. Hehe, I know the visibility at Arlanda was terrible. Glad you made it though, but something is still strange with my AP.Cheers captain!

Yes, I was the Continental 763.

>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.0000000124 >Arlanda ESSA01L10830007 59.637256 >17.913225109.9000700124 >>The second line refers to 01L specifically. I interpret it >as follows: >>ESSA01L - the specific runway >10830 - runway length in feet >007 - runway heading >59.637256 - Latitude >17.913225 - Longitude >109.90 - ILS frequency >>124 - runway elevation >>>Perhaps 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. I'm now certain you're right... The 008 value in the Facility Information must be causing my problem! I tried three landings at EKCH, and nailed em. Then I tried a landing at ESSA runway 26, nailed it aswell. But when trying 01L at Arlanda the problem is back!In my wpNavAPT.txt the heading for runway 26 is 254, and when looking at Facility information it shows heading 254 for runway 26 aswell. Probably that is why the autoland nails the landings.http://members.chello.se/oscar/Edit.jpgToo bad I don't know how to change the "facility info heading", it's not done in AFCAD, that I (think) know!

As far as I know, the "facility Info" is hard coded in FS2002, you will have to change the 767 PIC Navdata to match the facility info.

Ok but runway 01R/19L has been added by Swedflights scenery and it has been added to the "facility info" as well, that is strange... Maybe it's coded in the scenery in some way?