I can't seem to figure out the correct way to add SID/STAR waypoints to my flight plan. I'm following the LAX-LAS tutorial stickied at the top of this forum, and after I import my flight plan I click on DEP/ARR in the FMC and add SID info. I have to delete and add a waypoint under LEGS but then I'm all good - I have my SID info out of LAX that joins to my flight plan created in FS. Great.

However, then I try to set STAR info for my LAS approach. In the DEP/ARR Index, I see:

<DEP     KLAX    ARR>
            KLAS    ARR>

I click the ARR on the KLAS line, and choose a STAR and a runway (CLARR & 25L). However, when I press EXEC, it deletes half of my flight plan and leaves only the SID data (plus a couple extra waypoints) back in SoCal.

What am I doing wrong? I'm reading through the manual and searching on the CS site and coming up short. What's the proper way to set DEP/ARR info after you've loaded your flight plan?

(and as a bonus question, how do you delete a saved route in the FMC?)

Did you do it with the build in navigation database or with newer AIRAC data? I will do a test and report at weekend but i have AIRAC 0909.

If you do want to enter STARs you'd better enter them manually either using Jeppesen charts or MSFS map. It's much more easier.

That is a relatively short route.  Some procedures are very long and might well eat up much of your route.  Fly from St. Louis to Chicago and you'lll find out that some STARs pretty much start at where you're taking off from.

You can always tweak your route after that and save it as a company route.

The last volume in the documents has a method of creating your own procedures for the FMC, too.

Or, you can create a flight plan that includes your SID and STAR and add your speed and altitude constraints manually.  I think it is more fun to work within the FMC system, though.

KSFO to KLAX is another example. �I am not sure there is a "route" between the SID and the STAR. �I don't think there is anything between the end of the PORTE3 SID and the beginning of the STAR, since AVE is a transition. �If I'm not remembering exactly, this is pretty close. �The point is you will often have a complete route with just your SID and STAR and things will make more sense as far as your FSX flightplan on a long route.

Constraints are easy.

Let's say you want to be at 240 kts and 4000 feet. �On the LEGS page scratchpad you type:

240/4000

and then hit the line select key on the right side of your fix. �It will show in a bigger font to indicate a user input.

If you want to make sure you are above 4000 ft. you type:

240/4000A

if you just want to leave the speed and change the altitude, you can type:

/4000

You can also have very complicated conditional constraints like "fly runway heading to 4000 ft, then blah blah blah." � Good examples are running through the South American legs of the World's 100 Busiest Airports freeware collection.

One thing I have noticed is that the Navigraph constraints are not always honored with the 757. �To make sure, you can just re-enter them manually and for some reason that seems to do the trick. �Chock, Petraeus and I were kicking this around on the AVSIM forum a while back. �Interestingly, I have not noticed problems with the 767, but could be different routes, different AIRACs, maybe they cleaned up the programming... who knows?

I always check the VNAV page to make sure there is one constraint reflected.  If there is nothing there, I have found you cannot count on the constraint being honored.

Vol. 5 of the documentation is very well written and complete for the FMC. �Everything except Vol. 1 is worth biting the bullet and printing out for study and reference.

Does this answer your questions about constraints?

Thanks for the info, guys. I'll give it a whirl.

Hi Tim,
yes. that's much more close... looking to the VNAV pages shows what the plane will do and what not.
So i have to understand the SID/STAR contraints as "calculated" or "advised". Overwriting them (small letters) with my values (lage letters) helps much. Only for route-waypoints (CRZ mode) that dont work for me. But in the manual is a remark to use FLCH for that or type in a new CRZ ALT.
In reality, it is the pilots responsibility to monitor the FMS and AP - So i can work with it for my type of flying: Offline with FSX ATC or online with IVAO or VATSIM. There I can't fly a whole programmed route, especially for the altitudes. But changing the weather to match your plan is a great idea! I think many real world pilots would pay much for that tool in a real plane!!!
So i hope for the next update but still use this gorgeous plane with some small bug's. Thank you for your help and have the right - changed - weather for your approaches!
And vecor: Sorry for our small discussion in your thread. Is your question answered with the remarks above and your test is ok?

vector wrote on Sep 17^th, 2009 at 8:44am:


interesting