Hi,Generally RC4 ATC commands me too early to descents.iFly T/D points are miles away.When ATC insists on descending there is no way and no selection menu offering an alternative or to tell ATC that I want/need to descend later (no menu with "3-PD" or similar).The IAP Approach menu item is offered much later.Following RC4 descend orders in mountaneous areas often ends in too low flight levels and conflicts with mountains.What is your suggestion on how to handle this situation?Best regardsErnst

if the copilot has the comms, you don't get the 3-pd. if the copilot is flying the plane, you don't get the 3-pd. i think there may be a limitation, that the last checkpoint has to be a vor, within 5 miles of the airport, to get the 3-pd.what altitude are you at when you want to see the 3-pd?if you know you are going to be landing in mountainous areas, and you should know this, enable the arrival notams option in rc, so that all descent clearances are "if able..."jd

To get the 3-PD option you must have manual comms. If your first request is denied keep requesting and eventually you should get lucky. My record is 7 requests.

Thank you all for your help!I definitely was in copilot comms mode and in non-manual comms mode.All clear to me now.Thanks again for your immediate help and my best regardsErnst

A word about TOD on many aircraft:These are based on a constant descent approach to destination altitude. RC4 has a crossing restriction of either 11,000 feet (or FL110 above the transition altitude for the area) or 12,000 feet (or FL120) depending on your arrival destination. RC's computed TOD is calculated using the 3-in-1 rule for the difference of your current altitude to the crossing restriction, not the destination airport elevation.For Smith's type (Boeing) FMC's I put a range ring to display on the ND at 40 nm out from destination. I enter a FIX of the airport destination ICAO code and a position entry of /40 in the planning stage of FMC input. If you want your FMC via VNAV to meet the restriction you can:1. If there is already a waypoint on or just before that range ring on your route when you get the RC command for the restriction on your LEGS page make it a hard altitude for that waypoint.2. Create a waypoint of your route by entering a fix with place/bearing or if from a VOR distance/bearing where your route crosses the range ring and then enter the hard altitude when RC issues the restriction.I just use use MCP V/S and observe the descent arcs on the ND to insure they terminate before the range ring.Using the PMDG 737NG series I have found RC's TOD not too far off from the FMC TOD.In addition for varied terrain obstacles take advantage of the RC NOTAMS option to allow altitude flexibility or after being offered vectors by RC select an IAP approach for the assigned runway after you acknowledge the first vector. This lets you follow published STAR procedures to get around terrain in difficult approaches. Neither option though relieves you of the crossing restriction.

A word about TOD on many aircraft:These are based on a constant descent approach to destination altitude. RC4 has a crossing restriction of either 11,000 feet (or FL110 above the transition altitude for the area) or 12,000 feet (or FL120) depending on your arrival destination. RC's computed TOD is calculated using the 3-in-1 rule for the difference of your current altitude to the crossing restriction, not the destination airport elevation.Using the PMDG 737NG series I have found RC's TOD not too far off from the FMC TOD.

Thanks for the tip there Ron. The other day RC told me to descend nearly 80nm from the top of my descent point in the NGX.Just to clarify what you said. Create a waypoint 40nm from the destination airport along the route with a hard crossing restriction of 12000ftThanks

Thanks for the tip there Ron. The other day RC told me to descend nearly 80nm from the top of my descent point in the NGX.Just to clarify what you said. Create a waypoint 40nm from the destination airport along the route with a hard crossing restriction of 12000ftThanks

It might be 11000ft (FL110) dependent on the wind. If you're approaching from the south and landing runway is 300-060 with winds from the north that's called a near-side approach and you need to be slower on approach otherwise you'll not get down quick enough.

Please see pages 49 and 50 in the RCv43 manual for examples of near side and far side crossing restrictions. Since RC assigns runways giving ai patterns first priority your runway can vary since there are many runway/weather conditions that ai respond to. For low headwinds they might accept a mild tailwind. This is a design within FS, not RC.If you enter a 40 nm out waypoint during planning with a hard altitude be prepared to modify that altitude when the crossing restriction is issued since it can vary depending on your arrival direction and the assigned runway as Ray stated.

Hi guys,

 

i have the problem that my RC4.3 wont show me the "3-PD" menue.

 

- "Otto" hand over the com`s back to me before getting descent clearence from center, using kyb.-command about 50miles before TOD.

- "Otto" is not flying the plane, he never does.

- Just to make shure, i also tryed last checkpoint to be a VOR, within 5 miles of the airport.

 

...but ithink i saw this menue entry on an older system i used last year (WinXP), (i never used it because i didnt know what "3-PD" was for), running now on W7 64bit, FSUIPC.

 

 

JG

You will only see 3 - PD if you have the comms, not Otto. Make sure you have pressed the correct keys to switch comms back to you. From memory it's CTRL+SHIFT+K.

 

The last checkpoint being a VOR has no bearing on this.

You will only see 3 - PD if you have the comms, not Otto. Make sure you have pressed the correct keys to switch comms back to you. From memory it's CTRL+SHIFT+K.

 

The last checkpoint being a VOR has no bearing on this.

yes Sir, i made it shure, could it be that i am not allowed giving "Otto" the coms the whole RC session ? (i altered the key for that, i use CTRL+SHIFT+C)

 

...testing now starting RC using WIN XP compatible mode.

 

 

JG

Make sure CTRL+SHIFT+C doesn't conflict with anything in FS. Yes, you can give Otto the comms for the entire flight if you wish. I usually switch over to Otto once I've been cleared for take-off. I ack that then transfer comms to Otto.

 

There's one way to check if he has comms or not. Wait until you get an instruction from ATC and see if he responds. If he doesn't then it means you have comms and leaving things like that will mean you will see 3 - PD when RC instructs you to descend.

There are a couple of negatives with having Otto handle the comms:

 

Firstly, it negates the repeat request on ATC commands if you did not understand one.

 

Secondly, sometimes you may wish to delay an ack to give you the chance to allow you to manipulate the aircraft and have it start conforming to the change before acking. (Don't delay an ack just before crossing a waypoint - RC will not credit it.) RC's controllers can sometimes be impatient. In addition some aircraft in a change might do the opposite briefly from intent and this will trigger the ATC watch-dog to reissue the command. With Otto handling the comms acks are immediate.

 

Just somethings to consider.

...if i switch comms, i always get also audible confirmation who has the comms, i know defenetly who have them. if i dont understand the controler, the pilot who have comms repeat them, so there is no problem understanding if otto have comms, which is also realistic as the PNF is mosty responsible for that. iwould like to have an option, that Otto automaticaly request a PD.

 

...edit: no luck still not working, no PD menue entry before i was commanded decsending or directly after that.

 

what i get is a pilots descretion while reaching FL240, followed with a crossing restriction of 11.000 feet, 20 miles before reaching AML intersection, but i want to have that as initial decsent using the PD menue entry, (best automatical requested from Otto...)

 

Radar Contact 4.3.38.45, is that the very last official version ?

 

 

JG

v4.3.3845 is the current version.

 

What is your cruise altitude? I'm not certain if you get PD on every flight. It might be related to altitude.

 

Try a flight with a cruise level of FL350. You should definitely get a PD with that level.