Hello, I have some annoying problems with rc4.03 at times when trying to fly STARs that begin quite far from the arival's airport. Let's take EGLL: my last waypoint in the plan is LOGAN, so rc4 sees my flight path as: EBBR HELEN COA KEGIT SASKI SUMUM LOGAN EGLL (CRZ FL240). At 80nm I get ATIS, set RWY and punch in the STAR (in this instance they are LAM1Z or LAM3A). After crossing LOGAN I start flying along LAM1Z or LAM3A which is to the north from the flight plan as seen by rc4. Before I get a chance to switch to and request anything from Approach the Center begins to nag me non-stop into flying back on course HGD 180 (or so). There are some other popular destinations where I have the same problem. I fly fs9 with the latest FSUIPC3.98a and corresponding make_runways. I've never tried ticking NOTAMs on arrival though, but I doubt it might give me some more latitude to reach the Approach and request IAP? I understand I could place an additional waypoint closer (60nm<) to the arrival, but that would mess up my flying STARs that begin from the previous waypoints etc. A patch to fix this would be very much appreciated. I wish Center just left me alone after crossing the last waypoint (particularly those distant from the arrival) and Approach took me over as usual when I'm less than 60nm provided that would've been the easiest way to temporarily fix this problem for rc's coder till the next rc's release of v5. Otherwise there's PFE for some important destinations with its own way of handling these situation but I'd prefer to stay with rc4.Thanks,Dirk.

The common points in the STAR to about 30 nm out should be in your flight plan for RC to see. The FMC must agree. This will carry you through to approach where you can elect to fly an IAP for the assigned runway and totally navigate by the FMC terminal procedure if you wish. This is discussed a bit in the latter responses from me on using the FSB planner;http://forum.avsim.net/topic/321137-please-increase-time-delays-between-tellings-off/As your plan stands now RC sees you as flying LOGAN direct EGLL. In this 3A STAR since the heading is straight through LAM put that before EGLL so you have LOGAN LAM EGLL. That looks to be about 35 nm out and you can let RC vector you at the LAM transition (just before) or request an IAP to the assigned runway and follow your FMC path to getting established on final without RC monitoring you movement. In fact, as I look at the intermediate charts where LAM is the first transition common to both, I think you'll need one more waypoint such as created at LAM R275 D11 for your planner to create. This would be roughly common to landing on the East or West runways. This is so RC will not be expecting you to turn direct EGLL from LAM and give it some idea as to where you wish to go. I note in the chart it gives conditions where ATC may require other approaches (Note 8 on the chart I perusing from AIS services.) If landing on the 27's I see the S turn pattern which RC would not know about. Note that comments on the two intermediate approach chart state these are not to be used for radar vectors which means your FMC NAV. For that there are other choices.Whatever you use I recommend you pull up the ILS for the landing runway in your FMC so that it will display on your NAV screen for situational awareness, even if deciding to take vectors.As in the real world ATC dominates, not your FMC. ATC can pull you off a published procedure if need be.Terminal procedures are handled differently in RC5 whenever it gets released.

That was an easy one, how did I forget about LAM! Yes I knew what you said, it's in the tutorial, I should have put LAM in the plan in the first place. Now need to check out some of my other approaches. I know, I was looking at the 'direct to' line from the last waypoint (LOGAN in this case) and trying to find something decent for a common STAR/FltPlan point, whereas I should've just looked at the STAR path and pick one from there.Thanks,Dirk.