I did a flight in the LD 767 from KSFO to KPDX. My flightplan had a SID but no STAR. The last waypoint was KPDX. This was initially not visible in the LD 767 FMC so I inserted it later manually. When I reached the latest waypoint before KPDX I was told I was getting of course and was given a vector 90 degress away from the planned leg. This vector was never changed by RC and as soon as I turned towards KPDX I was told to turn to the given vector again.

Hi,Without sight of a flightplan it's impossible to determine what went wrong if indeed something did. You can always see your current waypoint in the RC menu so that should give you a clue as to what it expects of you. If the arrival airport is the current waypoint then it suggests you were being vectored for an approach and landing.Were you flying RC headings or was the FMC controlling things?Cheers,

sounds like you missed your crossing restriction, maybe. how far from kpdx were you?jd

>Hi,>>Without sight of a flightplan it's impossible to determine>what went wrong if indeed something did. You can always see>your current waypoint in the RC menu so that should give you a>clue as to what it expects of you. If the arrival airport is>the current waypoint then it suggests you were being vectored>for an approach and landing.>>Were you flying RC headings or was the FMC controlling>things?>My current waypoint in RC was stated as number/50/0 and 50 was the crazy vector RC gave me, while 320 was the heading directly towards KPDX. When I first was given this vector I flew it for a long while using heading select. Before that FMC and RC was in agreement about what I should fly.

Strange waypoint. Can you supply your flightplan? As JD say's it could be the crossing restriction being missed. Did you hear "You're missed your crossing restriction".Cheers,

>Strange waypoint. Can you supply your flightplan? As JD say's>it could be the crossing restriction being missed. Did you>hear "You're missed your crossing restriction".>No not what I can remember but I might have missed that. What does this 'missed your crossing restriction' mean?

how far from kpdx were you?

A crossing restriction is a specified altitude to be at by a certain distance typically 30 miles or less from the time of the command. It is usually required to be reached at 40 nm from the destination. There may also be a speed restriction as well announced or implied. If not at the commanded level you will be given delay vectors until you reach the required altitude at which point you will be vectored back on course. For the US/FAA airports, be sure you have switched back your altimeter pressure setting from standard 29.92 to the surface pressure you were given when told to descend below FL180 (18,000 feet), the transition altitude for FAA areas. Your co-pilot will say "altimeter check" as a reminder and ATC will give the altitude in feet instead of FL when surface pressure should be your altimeter reference. I make it a habit in the FIX page putting a 40 nm range ring around the destination. See your FMC manual. You can then use your ND descent trend arcs to guide your start and rate of descent if RC grants a pilots discretion start of descent or you request it. The trend arcs should end just before the range ring. If your VNAV legs agree, then you can stick with it, otherwise use FLCHG and V/S on your MCP to control your descent rate. If there are any steep descents into KPDX due to terrain delaying descent be prepared to use speed brakes if necessary to meet quick altitude loss while meeting the 250 knot IAS below 10,000 feet here and 210 knots or below within about 30 nm of the airport which is regarded as the approach pattern zone.As usual I must state that ATC rules, not your FMC. Know how to use the FMC and MCP to accommodate ATC requests for headings, airspeed control, and altitude changes.Your FMC flight plan should include your destination airport. You can elect an expected runway but change it later in your FMC as approach tells you what to expect. Occasionally the runway might be changed during the initial approach due to AI action occurring so be aware how to change this in your FMC.Did you notice exported to your FS9 plan a waypoint based on a place/bearing/distance title, not an actual waypoint name? I'm not sure what the 50/0 was. You might want to zip up your FS9 plan and attach it to a reply here.

>sounds like you missed your crossing restriction, maybe. how>far from kpdx were you?>I think I was more than 100 nm from KPDX when I was given this vector. My last waypoint before KPDX was called LMT.

that's not a downwind leg then. maybe you were getting held. maybe you missed a checkpoint.jd

>that's not a downwind leg then. maybe you were getting held.>maybe you missed a checkpoint.>No no and I did this flight again with a somewhat changed flightplan (with a STAR) and again RC4 does not behave as it used to be. I never is told to descend and I was later given a strange vector which was written as<>6724m/45deg/0

you have a checkpoint in your .pln that is 0 degrees lat and 0 degrees long, i bet.jd

>you have a checkpoint in your .pln that is 0 degrees lat and>0 degrees long, i bet.>No not according to the plan seen on the kneeboard. But when I load the plan into RC4 i see this informationKSFO to @39000 (Alt1- , Alt2-) / SASLY.REBAS.SAWNA.RBL.BONVL.REEDI. *RVSMHere I miss the destination which I can see if I load other plans. But why won't RC4 see the destination airport? The flightplan was created with FSBuild 2.2.

let's see the .pln file, that you load into rc. copy and paste the contents hereif the .pln is bad, bad things are going to happen.jd

KSFO to KPDX@39000 (Alt1- , Alt2-) / SASLY.REBAS.SAWNA.RBL.BONVL.REEDI. *RVSMis what I got in RC4.2.3831 building your route in FSB 2.3 with exporting to FS9 set.I suggest you download from the www.fsbuild.com web site that AIRAC version which includes updated SIDS and STARS, then just to make certain after executing the AIRAC installation zip open FSB and go to Options, NAVDATA, Create FSBuild2 NAVDATA Indexes. You can update FSB to (no charge) 2.3 from your account at simmarket.com. Instructions are on the FSB forum linked from the FSB web site. When you log in to simmarket with the login you used for the download and get I think your history, the 2.3 upgrade should show. I don't quite recall but it is not quite straight forward.Do the upgrade BEFORE installing the new AIRAC.I've attached the .pln file I created.I hope this helps.