Sorry if this has been mentioned in the manual, I have three questions:1. Will RC 4 issues shortcut instructions? e.g. "fly heading 120 and join XXX north of XXX".2. Besides the crossing restrictions during approach, will RC 4 (randomly) issues any other types of restrictions? I mean, is there only one restriction that you will have during the whole flight?3. Can I request hold myself?all in all, I just want to practice my FMC skill by instantly respond to any restrictions... it will be fun, is that possible?Thanks!

1) no, but you can request direct any checkpoint in your flightplan2) doug? i'm not sure i understand.3) turn holding on, on the options page. default is weather. you can also choose offjd

Thanks for answering, for number 3, actually I mean can I request hold at anytime I want when I am enroute? (instead of being issued). just for training purpose I think....for 2, restriction like "slow down to xxx knots", "cross xxx at xxx, xxx knots" (other than crossing restriction)Thanks

#2 - I think I know what you're looking for. Including random clearances and/or restrictions has been on my mind for some time now and already have some details on "the list". They include m-speed restrictions, random altitude changes, random routing changes (to a point further along in your flight plan) etc.If you want to give me specifics or other ideas, I'll add them.Something like this isn't as easy as it looks when you think it through. Each category must include a user option to deny the clearance, request an alternate clearance to the amended etc. That can get very complicated respect to coding.I don't know. It's interesting though . Keep this in mind too... rw ATC is inheritantly, boring :) . Enroute flight is normally like watching paint dry. From my perspective as a controller, that's a good thing! No surprises :) .

For slower aircraft at larger airports (think type of aircraft declared on Options page) and type of AI around on approach/final, might an occasional ATC request to expedite landing and getting off the runway quickly be appropriate?In other words advise a higher IAS to the outer marker at which point I understand aircraft performance configuration limits then dominates. Make sense? I've been following that practice anyway when I observe aircraft behind and in front to keep decent seperation.Just a little more variety. It happened to me VFR in a real world incident where tower advised a regional jet was following me in my PA28-180 and I elected to do a crosswind runway well within tolerance which tower greatfully accepted. This was a medium size airport KRST in Rochester, MN.I've also observed breakouts occasionally at KMSP where heavies were creeping up on regional jets, the regional doing the breakout. It is not quite the same as a go-around in that vectoring is immediate especially on parallel ops.Just something for immersion to keep one on their toes. I know trailing aircraft are now controlled by RC4 but it still should be allowed to occasionally happen (but not repeatedly in the same instance).Food for thought?