Calling Level

[Bank Angle]

Can anyone tell me what the official rule is regarding calling level when reaching your assigned altitude in Canada? I have been told by many different pilots, including training captains, that we have to call level in Canada. However, I cannot find the reference anywhere in the CARs or the Canadian AIM. The way I interpret them, we only have to call level if not radar identified or if requested. I know we have to call leaving an assigned altitude if the climb or descend is at our (pilot's) discretion, but again do not believe we have to call level unless requested, as once the climb or descend is started it is expected to be continued at a normal rate until reaching the new altitude. And I know it is not a requirement in the US. Please correct me if I'm wrong, and send me the regulatory reference.

[Jerricho]

The requirement was removed about 18 months ago.

I'll dig up a reference for you ASAP. I know where it is in our ATC MANOPS (which I don't have in front of me at the moment), I'll try and find a CAR reference.

[Jerricho]

Right, I've managed to get MANOPS out, and here's what it and AIM have to say about the matter............

ATC MANOPS 437.2 states:
"You may instruct an aircraft to report:
A: reaching or leaving an altitude
B: passing an altitude during climb or descent"

There is a Note that states:
"437.2 A Note - Pilots of IFR and CVFR flights are not required to report when leaving or reaching an assigned altitude unless instructed to do so
Reference - Altitude Reports RAC 8.4, TC AIM"

Now, looking at the AIM reference RAC 8.4:
"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." (my bolding)

Clear as mud. Radar environment, not required. Non radar, should.

If I may add something to this not related to the question. On departure, ATC requires a passing altitude report to verify your altitude. SOME pilots out there either are not aware of this, or have interpreted RAC 8.4 to preclude the requirement. The reason I mention it is I've lost count of the number of departures I've had call me with "BLAH123, airbore off <RUNWAY>".

If we read on in the AIM:

"On initial contact with ATC, or when changing from one ATC frequency to another, when operating in radar or non-radar airspace, pilots of IFR and CVFR flights should state the assigned cruising altitude and, when applicable, the altitude through which the aircraft is climbing or descending. In order for ATC to use Mode C altitude information for separation purposes, the aircraft Mode C altitude readout must be verified. The Mode C altitude is considered valid if the readout value does not differ from the aircraft reported altitude by more than 200 ft. The readout is considered invalid if the difference is 300 ft or more. Therefore, it is expected that pilot altitude reports, especially during climbs and descents, will be made to the nearest 100-ft increment"

Makes life much easier. Thanks folks.

[kevenv]

Edit: Written and posted while Jerricho was posting.

[invertedattitude]

It's not required, but it still is nice, but if a pilot doesn't it really doesn't matter.

It's not required to report vacating an altitude either when cleared, but in those few cases you're given PD descent sometime before you actually start down, it is not only nice to tell the controller, if you want to avoid being levelled off I would suggest mentioning you're vacating your level, as the controller may not be staring at your particular datatag...

[Jerricho]

Personally, in a radar environment I've always found it a superfluous call, and on a busy frequency it's just an extra call to block another.





Overheard one time on an Approach/Terminal frequency for a dinky little airport just to the west of London, England.

The airport had just had 09L blocked and there were several go-arounds that had to be resequenced. The Intermediate South Director was busier than stink. With all this going on, a rather cheery AAL pilot had reported level at the top of the stack. The Int Director didn't acknowledge, too busy trying to keep everybody in controlled airspace. The AAL pilot waited for a gap in transmissions and reported level again, with the second part of the transmission stepped on. The DIR asked AAL to say again. "Just wanted to let you know we're level at 12!"

The response "Thanks for bloody nothing!".

[Bank Angle]

Thanks Jerricho for your thorough reponse. You basically confirmed my interpretation, and the ATC MANOPS references were a great addition.

[SAR_YQQ]

Good to know guys - thanks for the reference.

I will discontinue my level calls to Centre/Terminal from now on - I will also be sure to pass this on to my future MIFR students.

Huge downfall with military aviation is that we don't follow the CARS and only get these updates when our own regulations are amended. Our GPH204A is ridiculously "organized" and changes are made every quarter or so.

[Jerricho]

We still need them on departure to validate your altitude

(the reason I mention this is for some reason in the last week, I've had several departures I've had to go back and get a passing altitude)