Welcome to Flightinfo.com

  • Register now and join the discussion
  • Friendliest aviation Ccmmunity on the web
  • Modern site for PC's, Phones, Tablets - no 3rd party apps required
  • Ask questions, help others, promote aviation
  • Share the passion for aviation
  • Invite everyone to Flightinfo.com and let's have fun

Reporting Leaving an altitude

Welcome to Flightinfo.com

  • Register now and join the discussion
  • Modern secure site, no 3rd party apps required
  • Invite your friends
  • Share the passion of aviation
  • Friendliest aviation community on the web
The check airman at WN point to an AIM sentence that says it's a required call. I've never done it before and quite frankly never heard anyone else do it until I started here at WN, so who's right?

You might want to re-read your question. You've already answered yourself and even provided the reference.
 
Wow, another thread, peppered with pithy comments from self-righteous, anal-retentive turd-polishers . . what a surprise.

This is clearly an archaic hold-over from non-radar days that needs to be changed. Controllers are not shy about making their annoyance known when this call is made.

Yes, it's in the AIM. So is "words twice" "Mayday" and "Pan Pan". Use sparingly.

TW
 
The check airman at WN point to an AIM sentence that says it's a required call. I've never done it before and quite frankly never heard anyone else do it until I started here at WN, so who's right?

Point to the line about not taxiing faster than a brisk walk and ask them about that.
 
I only call "vacating" after I call "traffic in sight" or most times "tally" just to pi$$ off the civvie pilots and always or at least 63% of the time I finish every call with "over".
 
This requirement comes from another era, when the controllers had a "strip" board in front of them rather than a radar scope and this particular call would prompt him to move your strip from one altitude column on his strip board to the next before he hand you over. It is just one more of the regulations or requirements that have no practical purpose in today's aviation network (thus controllers not caring much if you make such call or not) but because of the slow and painful process that is change in any government agency (the FAA included) these relics continue to be in the books as active requirements and regulations. I'll give you another example, If you are navigating in a fancy modern A/C at 5, 000 feet in a beautiful clear day from Miami to West Palm on an IFR flight plan, witch way do you think the FAA regulations want you to navigate, using your fancy GNSS, IRS, GPS or looking down at the terrain features? Again, a requirement that comes from another era and that no FAA examiner in the cockpit doing a route check will actually enforce.
 
It's pretty much the same thing as reporting the FAF on every approach, entering a hold, leaving a hold; you're supposed to do it, but most don't. I wouldn't worry about it.
 
I'll never understand why people ask questions they already know the answer to.

If that makes me self-righteous and anal retentive in your book, so be it.
 
The greatest skill that a pilot can acquire is headwork. Yes it is a required call, but headwork would dictate whether it should be made. Try making that call to New York during its rush hour.

You can apply this to almost all requirements. Use your head.
 

Latest resources

Back
Top