In the real world certain SIDS and STARS can carry out for hundreds of miles. With V4, SIDS aren't really a problem because you can choose between altitude restrictions or no restrictions. With STARS, however, you can't choose that. It seems like every time I fly a STAR in V4, RC gives me my initial descent clearance after the FMS's computed TOD. The manual says you can request a descent at PD but I never see that option when approaching my TOD during a flight. Is V5 going to be more flexible with the flight setup for programming these kinds of parameters?

if the co pilot is on the comms, you won't get the option for a pd request for the initial descenti'm not going to try to keep up with sids and stars. those for the planner.tell my why sids are a problem? if you want to fly them without altitude restrictions, you choose one.if you want to fly the sid, but let the controller give you the altitudes, you choose the otherstars end when you contact approach. if your planner has the star in the .pln, you can fly it. you don't like the point of initial descent? can't make 100% of the people happy with this point. it's either late, or early, but never right.not that the fmc is always right either. it is the controller who gets to say, not the fmcbut fly the plan, keep the comms, pd the initial request, just make sure you make your crossing restriction.then if you want to fly a specific approach, ask for an iapi think this scenario is covered in one of the tutorials. if it isn't, i'll make sure there is a tutorial for it in v5.jd

I didn't have the copilot on the comms and I still didn't get the option for a descent at PD. I took him off the comms at like 200nm out.there isn't a problem with the SIDS. I was just mentioning the SIDS because SIDS and STARS can carry out for hundreds of miles. i was thinking about having an option (or window) to open up that lets you see all of the waypoints in your flight plan and put altitude restrictions under each of them. So if ATC clears you as filed or clears you for a STAR, you can do your own descent and follow the altitude restrictions of the star. As long as you tagged a restriction under each waypoint of the STAR, ATC won't yell at you for being off your altitude.the controller does get the final say but not every single time you fly. If a STAR is part of your flight plan and you're cleared for it, you can follow the altitude restrictions according to that STAR....meaning descend without needing permission from ATC. RC doesn't need a database of SIDS and STARS like an FMS does. I read through the manual and the tutorials. I just can't ever seem to fly a STAR as published. I usually just keep requesting for a lower altitude so I can let the FMC fly the STAR and meet each restriction without getting yelled at. Its not realistic doing it that way though. Ending the STAR when contacting approach isn't a big deal. Thats more normal then anything I would think.

make a log, instructions pinned at the top of the forum. duplicate the lack of pd for initial descent clearance, and i'll take a look at itjd

I sent you another log the other day where I had a CTD going from KATL to MYNN. Did you get it?

that had the lack of pd from initial clearance?jd

I think the one I sent had a crash to desktop somewhere near the TOD. I tried to duplicate it the following day. The second one, same flight, didn't CTD but it didn't give me a PD descent option. I didn't send that one yet. I'll send the second one to you now.

turn off pilot autoreply, and you will see the optionjd

I'm confusing Pilot Autoreply and Copilot handling the radios. Thats why I'm not getting it. Maybe thats an idea for version 5....be able to turn autoreply on and off while your flying instead of before loading RC.

i'm confused. why not turn auto-reply off, ack the responses until you hand the comms over to the co-pilot.you will still need to be handling the comms, when the initial descent clearance is givendj