Have a question I am kind of curious about. Let's say we receive the clearance "descend to 10,000' when ready/at pilot's discretion". If we stay at altitude for another 30 miles or so, would you like to hear "XXX leaving FL200 for 10,000" when we commence descent? (Or something along those lines)

Is there any benefit to making this call when in radar coverage for the entire duration of flight?

The benefit would be that it is a required call.

Thanks, found the reference. RAC 8.5.1(b).

Krimson, turn back a page in the AIM to 8.4. Big difference between 'should' and 'shall'. Should report leaving/reaching means it's a good idea, but if radar etc, not mandatory. Difference is when atc requests the info, then it is manditory and becomes a 'shall'.
A28

RAC 8.5.1 (b) wrote: If the phrase “when ready” is used in conjunction with
an altitude clearance or instruction, the change of
altitude may be initiated whenever the pilot wishes. [...]
Pilots are expected to advise ATC when the
altitude change is initiated.

RAC 8.4 wrote:Although the CARs do not specifically direct pilots to report
altitude information to ATC, pilots, if not operating in radar
airspace (i.e. radar-identified by ATC), should report reaching
the altitude to which the flight has been initially cleared. When
climbing or descending en route, pilots should report when
leaving a previously-assigned altitude and when reaching the
assigned altitude.

To me it seems like an unnecessary transmission but I would like to know what is expected and am a bit confused at this point.
I do not hear too many others reporting leaving altitudes, but some also insist on it.

It's clear that for a descent at pilot's discretion, you need to make the call.

As stated, altitude reports are normally a should. So unless specifically requested by ATC you could always omit them and never get violated. However, a more professional attitude would be to do all shoulds unless there is a good reason not to. Personally in a non radar environment I make the calls exactly as recommended in the AIM.

Though I do find it strange that surveillance identified in ADS-B airspace YEG always makes us report reaching.

Correct me if I'm wrong, but the entirety of the AIM is advisory, except where it exactly repeats or parallels what's written in the CARs. If it's not in the CARs then you cant be busted for doing (or not doing) it.

Absolutely correct photofly.

The same goes for the flight training manual and from the ground up. Like the AIM though, it's a good idea to follow the recommendations.

ahramin wrote:
Though I do find it strange that surveillance identified in ADS-B airspace YEG always makes us report reaching.

Probably just a habit for guys used to working in a non-radar environment. I do it often, even on radar identified aircraft. Sometimes its nice to have the tweak of a guy calling level.

As far as the "report leaving" aside from it being required, its again nice for the tweak. I give you lower "when ready" and then move on to other tasks. Not that I forgot about you, but the report at the top of decent allows me to re-evaluate the plan I had for you in the first place.

The only thing I ask is please, for the love, PLEASE don't ask if I heard you when you report leaving and I don't answer. I heard you. . . I promise. And if I didn't, you'll figure that out when you level and can't get ahold of me.

AlbertaBoy wrote:

ahramin wrote:
I heard you. . . I promise. And if I didn't, you'll figure that out when you level and can't get ahold of me.

If you heard me, why can't you click the wee plastic button and say "mmmfff" or breath softly into it, or sigh approvingly, or well, something, anything?

I like it when you respond, it validates my fragile existence.

ahramin wrote:
As stated, altitude reports are normally a should. So unless specifically requested by ATC you could always omit them and never get violated. However, a more professional attitude would be to do all shoulds unless there is a good reason not to. Personally in a non radar environment I make the calls exactly as recommended in the AIM.

.

My experience is that nobody makes routine altitude calls, other than to read back the clearance, of course; in busy airspace like around YVR. The frequency is already busy enough and if everybody added "ABC level at XXX" for everyone of the step downs you would not be able to get a word in edgewise.


The exception as has been noted is the "descend at pilots discretion" situation where you have to tell ATC when you are starting down. However I find sometimes I can put it in during my initial readback. Like " XXX descend pilots discretion to one zero thousand, we will commence descent at SUMPT"

There is no requirement to make a call .... if you're on radar, the controller can see that you're descending.