You want us to descend now?

[NW1]

I think AF 1 raises a very good point. Probably best approached from the "how can we sort it" angle than the "how high can we p1ss up against the bog wall" angle.

I rekon the problem has it roots in the increasing prevalence of FMS run profiles. The FMS will ping up a prompt some distance from the computed TOD (about 15nm from memory - I'm personally free of the green godess for a while!!) and it seems de rigeur to ask for descent at that point to reset the alt. alert window and so satisfy the machine, waiting the 2-3mins left in level flight for the A/P to cycle to its vnav profile. So pre-cleared descents have, rightly or wrongly, become the norm. On yer non-FMS jet, you calculate your ideal TOD (using sums), judge R/T traffic load and ask for descent such that you're straight into it. But what price progress?!

So what to do? Well, I can sympathise with the ""descend FLxxx" means just that" school of thought (that's how I'd personally treat it) but it seems that isn't happening. My feeling is that if you ATC chaps/chapesses have a need for a descent, as in AF 1's ""That's that problem sorted". "" scenario above, then "Descend now FLxxx" oughta do it, or if the neck hairs are starting to party then "Due traffic descend now FLxxx" as mentioned above would seem to be clearer. OK OK, it shouldn't be strictly necessary - but surely a syllable or 2 early on is better than frayed nerves later? Also, I think if you ask for descent when the FMS first squeaks, it is only polite to say something along the lines of "Bogbrush123 request descent in 12nms". Helps keep ATC in the loop.

LHR arrivals are another source of confusion. We get this constant descent approach thing rammed down our necks, so if we're on a closing heading with the glide half a dot fly up and we get cleared down to 3000', don't be surprised if we pick a ROD which prevents level-off pre glide capture. If that's not good enough then how about a specified minimum ROD in the clearance, or even "expedite" if you need it. That's the thing - if you need it we'll gladly give it (that's my thinking anyway) but a minor r/t effort early has gotta be better than a bigger effort and frustration later on, no? And low-level altitude capture is still quieter than a mid-air, even to the ears of those weird-beards at HACAN....

But please guys, don't get pissy with us if we ask for confirmation of a descent clearance - the need for us to manage an efficient operation is higher now than ever: even if you consider a syllable or two a waste - it may save the confusion and far greater r/t load of confirmation requests later on which seems to be giving rise to not a little frustration?