Hi,When I use SIDs and STARS (which accounts for most cases), I'd NOTAM the departure and arrival airports so that ATC will allow me to perform the procedures without "deviating" off route.Problem is, that some arrivals start before the point where centre hands me off to arrival, so ATC expects me to follow a leg that goes directly from the last waypoint to the airport. Obviously , when I start preforming the STAR, I'm getting yelled at for deviating.Is there any way to circumvent this, or am I going about it the wrong way?

you're going to have to follow the flight plan as loaded and any directions given by the controlleronce inside approach airspace, you can request an iap approach, and fly whatever approach you want.jd

Most STARS even those that are different based on assigned runway have common waypoints based on arrival direction. Build those waypoints into your flight plan so RC center will follow them until vectors start under approach at which point you can elect to do an IAP approach.

Hmm..so what's the point of an arrival NOTAM then?

Arrival NOTAMs are mainly for the vertical profile when flying into mountainous terrain. Laterally, it also allows you to deviate off the plan for terrain.Subs

That's what I thought Subs. Apparently it does NOT allow me to deviate for terrain, STAR or any other reason if I'm beyond arrivals control radius. Once I'm in, I can ask for an IAP approach and "suppress" ATC whether or not I had NOTAMed it. Isn't that the case?I was looking for a way to suppress ATC lateral guidance past the last waypoint, as you would with a terminal procedure.Apparently that's impossible without "cheating". JD, perhaps you should consider a "STAR" option once one had passed the last waypoint. If it's too late for this version, then maybe for the next...

arrival notam only applies in approach airspaceif you want to fly where you want to fly in approach airspace, then ask for an iap approach once you you are in approach airspacearrival notams, is so that arrival doesn't fly you into a mountain. it is up to you to maintain clearance over the terrain. all of approaches descent clearances will be "when feasible...."and watchdog altitude will be turned off.heading watchdog is still on, when notams is onjd

I think we are confused about your meaning of "last waypoint". The US airspace is simpler to explain.If you look at STARS in the US, they can start over a 100 nm from destination which still falls within enroute center jurisdiction. These early STAR waypoints up to about 30 nm from destination should be included in your flightplan so RC will follow the early portion of the STAR. As you get to about forty miles to destination center will hand you over to approach and a bit closer you will be vectored to line you up for an approach or at this time you can elect to do an IAP. So RC does route you via the STAR in your filed plan.You will see many STARS in the US where even before the final waypoint you might see the comment "expect vectors to . . ." in their description. It is not unusual for ATC to start vectoring you before the final waypoint of a STAR to accommodate traffic flow for the active runways in use but this will occur somewhat toward the end of s STAR.Summarizing, it is only the final points of a STAR where you might start flying your own procedure if you elect it.Here's a real world filing from KORD to KMSP:KORD BAE EAU8 KMSP.This is a common "northern" route from Chicago to Minneapolis. The STAR selected transition actually begins at BAE not too far from Chicago (Badger, WI I believe). It then takes you at heading 307 175 nm to EAU (Eau Claire, WI); 37 nm at heading 281 to TWINZ intersection; heading 255 toward ZASKY at 32nm where on the way you will be broken out for vectors. (ZASKY is only 9 nm from KMSP so you will be vectored before reaching it.) The point is for this transition the entire length is 243 nm for the BAE.EAU8 STAR legs, of which slightly more than 211 will be handled by ATC center following your filed plan. There should be no deviations unless you request a direct-to and it is granted. In this case the STAR is the entire filed flight plan. FYI the filed altitude was at FL320.Therefore it would not be realistic for RC to "drop the STAR" so far out as you suggest.Now if you are trying to use a STAR from an FMC database, don't use that one but use the STAR from your flight planner database application. Export that in FS9.pln format and also a format for your FMC to import. That way RC and your FMC will share the same waypoints until vectors start.Hope this helps you understand the synchronization between ARTCC ("center") and TRACOM ("approach").

Thanks for the detailed reply Ron!It's indeed a tricky situation. I'll follow your advice then and put in the common procedure points as a part of the plan.Full marks for your fine support as well, it does not go unnoticed :)//Michael