First, I am a happy RC3.x user, have been for some time now, use it for ALL of my flights, without issues.I am curious, in the real world (commercial jet), what is the standard operating procedure for descents ... meaning, with the FMC/MCDU calculating TOD which I guess is the point where you can make the most economical descent in flight idle ... does ATC always "initiate" the descent or does the pilot request descent? To be specific, I am thinking commercial jets, US airspace. I notice in all of my RC3 controlled flights, I am asked to descend a considerable distance in front of the TOD ... whether in a Boeing (PMDG) or Airbus (PSS), usually losing the ability to use the FMC calculated descent profile.Certainly NOT A PROBLEM ... and I never want to cross Bill Stephenson ( 8-)= ) but I am a bit curious. Having been a fan of Just Planes videos for many years, I notice that usually the pilots request descent, at or just before TOD on their ND.When told to start my descent, if I use a descent rate of 1700 FPM I seem to be just about right with ATC and can have a continuous descent without level off .. at least to 10000 feet/40 miles out, but certainly not on the FMC profile. If the answer is IT DEPENDS, then that's fine ... I am just being curious george here. Is 10000'/40 miles a usual ATC rule of thumb?Thanks Scott and JD (and team) for providing me with hours of interesting "flying" ...

funny you should askwhile in memphis last week, doug and i had a long discussion about this. why? because i made a rather significant change to the point at which rc starts your descent. as doug said, paraphrasing, "you listened to a bunch of pilots".since he is the authority, i changed it back, ironically to where it was years ago.in real life, doug, or other controllers, are not concerned about what your fmc - "thingy" says. there are many variables, weather, other traffic, arrival delays, other traffic, how many times he had to call you before you replied, etc.in the end, we both agreed to this statement, "rc doesn't do things because it is easier to program, or means fewer recordings, or because a number of users want it done. we do it the way it is done."that doesn't mean we don't listen for requests for improvements, but sometimes the requester is surprised that the enhancement isn't what he thought it would be. because it is the way it really is.jd

Hi jd,I understand your note, and having followed this forum for some time, understand that the controller really is king of the process (hahahahaha ... Bill S is the enforcer!!!) I will have to check on my next flight if I can refuse the descent instruction (and get my flak vest to ward of Bill S)... and then maybe ask for descent when TOD comes up .. worth a try ... I can't remember off hand if that is an option and I suppose I should look at the manual. I know I have cancelled IFR on occasion just to try out profile descent in an Airbus and Boeing to understand the notion of continuous descent profiles whichI understand are becoming more common ...Again, I suppose there is not really an answer, but still wondering if 40 miles/10000 feet is still pretty much of a standard ... but I guess I am answering my own question huh? ... there really is no standard for the real world ... just "It Depends ...." hahahahaThanks again ... looking forward to the next release!!!!!!

actually in v4, there will be multiple/variable crossing restrictions. they will be higher :-)you cannot refuse the descent clearances. sorry

Really appreciate your comments Paul!Crossing altitudes vary from airport to airport. I'm aware of fields with 110, 120 and 140 xing altitudes. Some LOAs call for differing altitudes dependant on what rwy's in use. There is no single altitude used by everyone.v4 - We're raising your xing altitude from 100, to 110. Higher elevation fields usually call for xing at 150. That won't change. Under varying conditions, your xing restriction will no longer call for the 250kt speed at the gate but per the rules, you need to be at 250kt prior to descending through 100 when your descent clearances come. I'm excited about these particular changes. They'll be fun to test :-)Now, FMCs, MCDUs, fancy/dancy GPSs, EIEIOs, - I have to stand firm here Paul. I as a controller... well, that last thing on my mind is what that thing says. In 24yrs I