Just a question about priorities:

 

I leave Seoul (RKSS), rw 32L, SID ENKA1J. RC gives me an initial altitude of 6000ft then FL160.

Now the SID has altitude restrictions RC4 is not aware of: GILGA below 5000, INCHEON below 9000, ANYANG below 12000.

 

PMDG737NGX's FMC + AP follow these restrictions but since I am instructed by RC to climb to FL120 before reaching GILGA I have RC talking to me in more and more unfriendly language ("Sir, this is the third time ...").

 

How is that handled in real life?

Is ATC allowed to assign a SID but override published alt restrictions?

Do I have to obey ATC or stick to the published STAR?

Others will elaborate further on this but the shortest answer is that you are always to follow ATC (RC in this case) instructions.  Even in the RW that will be the case.  The best way to include your STAR is simply write it into your flight plan.  Checking the NOTAMS  box before starting your flight will cause RC to leave you alone for the last 30 or so nm of your flight so you can closely follow your STAR as regards altitudes and headings.  As I said, others will explain this more clearly.

Is ATC allowed to assign a SID but override published alt restrictions?

Not sure about in other parts of the world, but normally in Australia, the departure controller will say something along the lines of this:

 

"Qatari 901, cancel altitude and speed restrictions, climb to FL180"  ie. Cancel all restrictions on the SID, but follow the waypoints on it.

 

and then later, before handing over to Centre possibly "Qatari 901, cancel SID, track direct 30S 108E"

 

 

Do I have to obey ATC or stick to the published STAR?

In terms of the STAR, ATC here will call you with "STAR clearance" eg. "Qantas 78, expect JULIM 6A arrival for ILS 21, maintain FL390"

 

but more often than not, after the initial descent, they will say: "Qantas 78, cancel STAR, descend and maintain FL100, track direct HAIGH to intercept the localiser runway 21"

 

So, you should always follow the direction of ATC (do what they tell you) however, it is likely if you are at a busy airport, you will have to "dot all the Is and cross all the Ts" when following a SID or STAR.

I'd regard SIDs and STARs as shorthand for ATC instructions. If they issue clearances different from what's stated in the charts - do what they want you to do. (They'll have good reasons not to adhere to their shorthand procedures in that case.)

 

MSFS is the only place where you can make the controllers do what YOU want THEM to do - as indicated in the posts above.

 

A quick and dirty means is not to reply to RC until you've finished flying your procedure - that way they yell at you only once and further misfortune is averted ...

Thanks to all for the clarifications.

Answer is in the manual. If you have altitude restrictions of that nature, open up the "Controller Info" box after you've loaded your flight plan and check "No Altitude Restr":

 

 

 

Now the controller won't pester you when you stay at certain altitudes.

Also, to fly your STAR, once your within 40nm miles of the airport (if you have STAR waypoints further out than that, which I'm sure is common, make sure they're filed in you're flight plan), RC will tell you to expect vectors. After you accept that, you should see an option "Request IAP app" or something like that. Request that, and the controllers will say you're cleared the full approach, and won't bother you again until you're finally handed off to tower.

 

NOTAMs could do the trick too, but that's designed more for when you're in mountainous areas and need some wiggle room with ATC instructions.

Hi metalmike,

indeed, it's in the manual (p108) although it's a bit confusing:

 

"No Altitude Restr

Clearance Delivery will assign an initial altitude, and Departure will keep you climbing. However, some published DPs include altitude restrictions. They may be AOA (at or above), AT, or AOB (at or below) altitude instructions. If you see your DP might cause you to remain level at an altitude for some period or until a certain DME, this is the DP feature to use. Use this checkbox if you do not want the RC controller pestering you for not maintaining a continuous rate of climb to your assigned altitude. There will be no lateral “watch-dogging”, there will be no vertical “watch-dogging” from RC until you are at or beyond 30 miles from the departure field.

 

Alt Restrictions

By far, most DPs are of published routes without any altitude restraints. If your DP contains lateral routes but no altitude instructions, or if you simply wish to join an airway outbound, this is the way to go. Again, Clearance Delivery will assign an initial altitude, and Departure will keep you climbing but in this case, you need adhere to those altitude clearances. Keep it climbing to assigned, do not level off."

 

So, if I understand this correctly, you have to tick "No Altitude restr" if you have altitude restrictions in your SID and "Alt restrictions" if your SID doesn't have altitude restrictions.

So, if I understand this correctly, you have to tick "No Altitude restr" if you have altitude restrictions in your SID and "Alt restrictions" if your SID doesn't have altitude restrictions.

 

Yes. Altitude Restrictions means you want ATC altitude control and the opposite if you don't want them. The default where a SID mode is forced or desired is Altitude Restrictions (from ATC).

 

This is only during the departure phase up to 30 nm out from your departure airport. It also means you do your own navigation where your SID waypoints in that area are in your flight plan. You are expected to line up with your first waypoint outside of that 30 nm.

 

If your first waypoint is within 30 nm RC will assume you are flying a SID and you'll need to pick one of the altitude options. You can also choose one of these SID modes in addition to the no Departure Procedure option if your first waypoint is outside of 30 nm. In this case you only need to line up with the first waypoint outside of 30 nm.

 

NOTAMS has a greater range for altitude flexibility.

 

BTW, the NOTAMS option for arrival does NOT wave the crossing restriction at 40 nm out from destination.

 

For runway specific SIDs or STARs where you do not wish to specify the runways to RC and let RC dynamically assign them, just use common waypoints to all runways in the plan sent to RC. SIDs and STARs are designed for your departure or arrival direction based on airways transition points which you do know in advance from your flight planning.

Hi Ron,

I'm beginning to understand: It's not whether you have alt restrictions in your DP or not, but whether you want RC4 to control your altitudes during the DP.

Thank you.