Calling Level at...

[Beechball]

Question...
Is everybody calling level upon reching their assigned cruising altitude without a specific request from ATC to do so? The associated conditons are that you are "Radar Identified" in the climb. ATC has not requested a "Call level at..." from you. Obviously, we're only talking about a RADAR environment here, and you have been identified already. In a non-RADAR environment it's a given. For sure!
I don't report level if I haven't specifically been requested to do so while having been "IDENTIFIED" already. I've never gotten any flack from ATC on this. I don't do this because it's my 2 cents in reducing frequency congestion, especially when ATC is busy. Yes, I am aware that the A.I.P. clearly stipulates the call is required when reaching or vacating the assigned cruising altitude. There's other procedures that are neglected on a daily basis which are listed in the A.I.P. RAC section, and pilots and controllers alike seem comfortable with these details. Some guys call level and some don't. Who's right and who's wrong? A.I.P. notwithstanding...
Some feedback from controllers would be much appreciated.

[twinpratts]

IFR proc. manual says do it... if they didn't want you to, why would it be in there? Besides, most times you get a thank you for calling.
2 cents.

[DragEraser]

It's not required in U.S. airspace. When you call level down there, they're all "...whaa, er, who's calling?". I don't usually call level either, but I've gotten "C-FFFF, check you're level 370." I think he was looking for the level off call.

[Panama Jack]

It is proper Radio Phraseology to do so "Toronto Centre Bugsmasher 1 Flight Level 190," and IMHO, much more appropriate than the terms "Checking in" or "with you."

[Bcn-In-Bnd]

I have talked to atc ywg and atc yyz. They both told me that is not needed BUT THEY dont mind hearing it and like it.

[Beechball]

Panama, I think you're referring to a controller handoff etc... Going over to another freq with somebody new. Then of course you have to report in on freq with altitude. What I'm saying is... Same controller, same freq, same guy who just 8000 ft earlier "RADAR IDENTIFIED" you. He's still watching you as you level off at altitude.

Yes, it's written everywhere for sure, that you make the call. But in everyday life, maybe half the guys at best make this call. I stopped doing it a while back.

[Always Moving]

If you ARE level Right?

If it is not congested I do it all ( reaching AND leaving) my reasoning is...
They can "forget" about me since I am level and they know where I am going and is always good to crosscheck the machines(radar,transponders,etc)

When I am descending I tell them what I am passing and more important (and many times forgotten) the altitude I am going to.


Frecuency permiting

[Beechball]

Bcn In Bnd says YWG and YYZ don't need it. Good enough. The A.I.P. lists it a requirement. Go figure. Always Moving does it as a personal preference.
So far it looks like a requirement on paper but in practice it seems up to the discretion of the individual. These are the kind of opinions I was after.
Thanks.

[b777av8r]

When radar identified and cleared by same controller to change a level...call not required.

When radar identified and given a radar handoff..call required.

When on departure on a SID...call with SID Identifier, current altitude and alititude 'cleared to'.

Under non radar enviornment...call required for all level changes

[Bcn-In-Bnd]

Beechball,
I make this CALL all the time, except in the US OF A.

[turbo-prop]

Also it shows the altimeter is still reading correct. If you call level 190 they look on their screen and confirm 190.

[dctthefield]

Calling level would help to cross-check your altitude and their readout, however, that was already done when you checked in on the frequency in the first place.

My 2 cents... I don't call level, but I do call if leaving an altitude when I was given Pilot's Discretion.

[split s]

I think you are all correct! We all do things differently for sure! The only time I feel like an a$$ is when the controller asks "call level" and then I forget! oops!

[Beechball]

Thanks for all the interesting answers. As illustrated by the replies, certain practices are clearly outlined in print (A.I.P. among other sources) but in day to day activities pilots and controllers both practice some lattitude in the way things are done. My question was born as a result of occaisionally receiving a gruff acknowledgement of my calling level shortly after being "IDENTIFIED". I decided to drop that call lately.
Another example of "By The Book" VS "Real Life"...
Who the hell bothers to switch to 1200 after cancelling IFR 25 miles out, SKY CLR or SCT and field in sight? By the book; 1200 would be the rule after cancelling IFR.

[Always Moving]

I do.

[Disco Stu]

I change the code.

Cancelled with YWG about 70W of YQT enroute to YAG. Did't bother changing the code. Minneapolis centre was apparently looking for me on freq. and contacted me through another airplane, wondering if I was having a problem and needed assistance because I hadn't changed the code.

Hit the 1200 button every time now.

[FamilyGuy]

I'm assuming that what some of you are trying to say is that calling level is not important enough to bother the controller with if he is busy. Right?

Wrong! Frequency congestion should not be the rationale for calling level or not. If it's required - its required. If that sector is consistently that busy that Pilots and controllers are developing unwritten "work-arounds" to make it work, such as reducing/eliminating required R/T, then there is obviously a larger problem that needs addressing.

You should always squawk the appropriate code at the appropriate time, discrete, 1200, 1400 etc.

There are no un-important rules or procedures. They have all been written for a reason. Most times the rules and pros when dealing with ATC come about because of something really bad happening - or nearly happening. I'd just as soon not have to explain my rationale for not doing something required in front of a Judge.

[dxprguy]

I don't consider myself too old... but I have been in the aviation business for about 20 years now initially as a pilot and then for several years as a flight dispatcher. One thing I came to learn is that you should always listen to that little inner voice whether you call it instinct or what I am not sure. I can remember on more than a few occations when I thought I should "read back" something to ATC, or call to confirm US customs was advised or re-checking the TAF or Runway surface condition which was supposed to improve. I guess what I am trying to say is never assume in aviation, the price is to high.

Just my two bits

[control_man]

Calling "level, leaving or passing" is a requirement. Is it done 75% of the time..yes. I agree that freq. conjestion should NOT be the rationale for not making these calls. When it is busy and guys are climbing descending, etc for turb. weather, departure, or arrival it is appreciated. When many factors come into play with workload and you are sitting with only your OWN pair of eyes on the boards, the calls are if anything a check and balance for us. Don't be of the assumption that it is bothersome. It is required, just as we are required to acknowledge it.
Is it done all the time? NO. Does it make me snap? NO. But believe me when I say that I would rather everyone do it than not. Especially in RVSM airspace (which I do work in..not all...but there is some transitional airspace), and I like hearing the calls. Remember RVSM is coming. Make the calls and make them habit. It gives me the warm and fuzzy feeling....

CONTROL_MAN

[Beechball]

Control Man.
Good answer. I'm going back to the call. I hope your answer was based on the conditions I set forth in the original post at the beginning of this thread.