Most of the time RC4 will completely ignore any STARs you give it just before the final approach, and instead line you up with the runway the way it wants you to. Is there a way to get RC4 to actually let you use the STARs without yelling at you for trying to follow the procedure?

RC4 knows nothing about STAR or SID so once you are handed off to the approach controller he will vector you to the runway designated. Remember you can only request IAP approach when within 40 miles of destination.

 

If you'd rather fly your star and full approach just request IAP on the RC4 menu and he will leave you alone until 5 miles from touchdown then hand you off to tower for landing clearance.

Here is a method I use to sync RC's .pln file with the database of an FMC using an AIRAC updatable planner and FMC. It is based on FSBuild 2.4 but may be applicable to other planners. This coordinates STARS between RC and navigation instrument databases especially prior to approach since STARS can commence a long distance from from destination. For runweay specific STARS just use the common waypoints for all runways.

 

fsb tips and update.pdf

 

As stated, select the IAP approach instead of acknowledging the first vector when approach assigns the runway. Select the IAP for the suggested runway as RC determines since it takes ai into account if present which may not agree with predicted weather.

 

The altitude suggested by RC when issuing the IAP is the merge altitude for final.

 

You should have the STAR and IAP charts for the airport handy to provide obstruction details and special instructions.

 

 

Drink a bottle of vodka and you won't care ^_^  I do this on almost all my flights :excl:

I have to agree this is a real PITA for arrivals.

Nearly every time ATC starts giving me approach vectors way too late for me to switch to IAP and fly a proper STAR.

SIDS are a piece of cake though but I guess you just have to get used to being vectored for finals.

It is not uncommon for STARs to be departed from to resolve traffic conflicts.

 

If you wish to ignore RC's runway dynamic runway assignments as determined by weather and first priority ai patterns and preflight assign your departing and/or arrival runways you can on the RC controller page assign those. Then include the STAR or SID waypoints in the .pln file sent to RC.

 

Be sure your planner and FMC terminal procedure databases are synced with an AIRAC update if you have that capability. This is covered in the .pdf I mentioned in this thread.

I have to agree this is a real PITA for arrivals.

Nearly every time ATC starts giving me approach vectors way too late for me to switch to IAP and fly a proper STAR.

SIDS are a piece of cake though but I guess you just have to get used to being vectored for finals.

If the STAR begins more then 40 nm out from your destination, just make sure to include that waypoints in your flightplan and you will be able to fly the STAR from the beginning. When you are within 40 nm and RC switches you to Approach, you just ask for an IAP approach and you will be able to continue the STAR.

If the STAR begins more then 40 nm out from your destination, just make sure to include that waypoints in your flightplan and you will be able to fly the STAR from the beginning. When you are within 40 nm and RC switches you to Approach, you just ask for an IAP approach and you will be able to continue the STAR.

 

Fair enough, but that's assuming you know which runway ATC will allocate to you on arrival.

The NOTAMs option is rather a cheat here, but if you still enable it, you're free to fly your STAR from even 70 nm out.

Fair enough, but that's assuming you know which runway ATC will allocate to you on arrival.

If your STAR is runway specific just include common waypoints in the plan sent to RC.