Vacating altitudes

[ksu_aviator]

http://www.faa.gov/library/manuals/aviation/instrument_procedures_handbook/media/CH 03a.pdf

Page 19 has the information you obviously need to brush up on.

 

[Hook 'Em Horns]

As someone already said, it probably will never be an issue unless you are involved in an incident and whther or not you reported vacating an altitude is deemed to be a factor.

I can't find in 5-3-3 where it states you should not make the report if you think it will add to frequency congestion.

 

[avbug]

KSU,

You just chat yourself up a storm, block the frequencies, look for traffic with your radio and report your altitude every three feet, it it makes you feel better.

I'm very familiar with the information. You go ahead and cite the regulation that requires these reports, while you're at it. Can you find such a regulation?

I'd love to crack a book, but I'm in the MIDDLE OF THE DESERT some distance from the middle of nowhere...and can only assure you that I'll sleep better in my compound knowing you're out there somewhere reporting every little altitude change.

Safety first, courtesy second, or even a distant third. Or in your own case, blind obedience to obscurity, and be-all damned with the rest, right? Ever hear of common sense?

One should report altitude changes when one can, when the frequency isn't congested, and when it's not patently clear that you're changing altitudes.

Where's your basis in writing from an authoritative source that ATC fears and distrusts Mode C? Still looking for that one. You're wrong, of course, but it was a good effort.

 

[DC8 Flyer]

KSU

While I agree with you, advisory is required any time you change assigned altitudes, this quote

Do not draw a horizontal line through an
altitude being vacated until after the aircraft has
reported or is observed (valid Mode C) leaving the
altitude.

from the ATC handbook kind of disproves your point about ATC not trusting Mode C.

 

[Booker]

While I agree with you, advisory is required any time you change assigned altitudes, this quote from the ATC handbook kind of disproves your point about ATC not trusting Mode C.

Hey dude; what's up? I don't know about any of that, but my FOM says I have to make "vacation" reports, nothing optional about it. And who am I to disobey the FOM?

This one time back at our old job, we got a PD descent on the captain's leg. I made an advisory vacating call to FLO approach (I think), and the ensuing cockpit conversation was thus:

Captain: "Is that a required report?"

Me: "No. Are you a check airman?"

OK, well, that's what I should have said. You know how some of those guys were.

Shoot me a PM sometime.

 

[ksu_aviator]

KSU,

You just chat yourself up a storm, block the frequencies, look for traffic with your radio and report your altitude every three feet, it it makes you feel better.

I'm very familiar with the information. You go ahead and cite the regulation that requires these reports, while you're at it. Can you find such a regulation?

I'd love to crack a book, but I'm in the MIDDLE OF THE DESERT some distance from the middle of nowhere...and can only assure you that I'll sleep better in my compound knowing you're out there somewhere reporting every little altitude change.

Safety first, courtesy second, or even a distant third. Or in your own case, blind obedience to obscurity, and be-all danged with the rest, right? Ever hear of common sense?

One should report altitude changes when one can, when the frequency isn't congested, and when it's not patently clear that you're changing altitudes.

Where's your basis in writing from an authoritative source that ATC fears and distrusts Mode C? Still looking for that one. You're wrong, of course, but it was a good effort.

If Mode C is so reliable, why would we ever check in with our altitude? If it was reliable, than all we would need to do is call in with our call sign...right?

I've never heard a frequency so congested that I couldn't get in a 1 second radio call for vacating an altitude.

BTW...learn how to read, I posted exactly where the implied distrust of Mode C is. If you don't like it, too bad, you are just wrong....again.

 

[ksu_aviator]

KSU

While I agree with you, advisory is required any time you change assigned altitudes, this quote



from the ATC handbook kind of disproves your point about ATC not trusting Mode C.

Read the whole thing above.

 

[avbug]

I've never heard a frequency so congested that I couldn't get in a 1 second radio call for vacating an altitude.

You may be forgiven for and need not apologize for your inexperience.

BTW...learn how to read, I posted exactly where the implied distrust of Mode C is. If you don't like it, too bad, you are just wrong....again.

You make wild assumptions, but see what you wish....and cannot in any way show any evidence, implied or otherwise, that the "FAA does not trust Mode C."

Especially as it is the FAA that mandates it. You're a smart one.

 

[Say Again Over]

It does not state anywhere in the 7110.65 that aircraft must state their assigned altitude on every freq check in. The first Center sector checks the mode C. It seems all American pilots report altitude climbing, decending, level, on every check in. Only about half the foreingers do. It sounds odd when you only hear "Boston Center AZA692". I insisted they had to state their altitude, but looked it up and cannot find it.
by zbwmy

From 7110.65

5-2-18. ALTITUDE CONFIRMATION- MODE C
Request a pilot to confirm assigned altitude on initial contact unless:
NOTE-
For the purpose of this paragraph, "initial contact" means a pilot's first radio contact with each sector/position.
a. The pilot states the assigned altitude, or
b. You assign a new altitude to a climbing or a descending aircraft, or
c. The Mode C readout is valid and indicates that the aircraft is established at the assigned altitude, or
d. TERMINAL. The aircraft was transferred to you from another sector/position within your facility (intrafacility).

zbwmy, is this what you were looking for?

 

[avbug]

Request a pilot to confirm assigned altitude on initial contact unless: ...The Mode C readout is valid and indicates that the aircraft is established at the assigned altitude...

Golly gee whiz, miss martha! Does this mean that the FAA might just have a smidgen of confidence in Mode C, rather than being in mortal fear of it's deep-seeded pitfalls as KSU might have us believe? Who'da thunk it?

Stop the presses! Maybe, just maybe, the ATC system doesn't rely upon it so heavily in error after all! Is it possible?

 

[districtpilot]

Since when does a vacating altitude report mean verbalizing the altitude you are leaving. If I am at 10,000 and ATC asked me to descend to 8,000. Then I would say "8000 1234Foxtrot".

 

[A Squared]

Since when does a vacating altitude report mean verbalizing the altitude you are leaving. If I am at 10,000 and ATC asked me to descend to 8,000. Then I would say "8000 1234Foxtrot".

Uhhh, right, and at most, the controller might assume from that ambiguous transmission that you had received the clearence to descend to 8000.

Even if you had used correct phraseology, and said, "descend to 8000 1234foxtrot. the controller would still only know that you had received the clearence.

I know that you're coming late to the party and all, but jeeze, the underlying basis of this entire discussion is that the controller *may not* assume that you have vacated an altitude until you specifically say that you have vacated that altitude, or he has confirmed that you have vacated the altitude. Reading back the new altitude clearence, does absolutely nothing as far as comumincating that you are in fact vacating your current altitude.


I would encourage you to go to Avweb and read the columns by Don Brown. He explains very clearly why sloppy, incorrect and incomplete radio calls make the controllers life harder. He even addresses the question at hand and explains in detail why the vacating call *is* important to controllers and why it should *not* be skipped for brevity, and how in fact skipping it *causes* more frequency congestion.

 

[districtpilot]

I respectively disagree, if a controller issues a clearance that is to be complied with I would assume that a readback of the altitude cleared to and my tail number is proof that I as the pilot have received and will comply with the new clearance. Same with vectors, if I am given a vector say 270 a repeat of that vector plus my tail number to me indicates that I understand and will comply with the new vector. I would not say in my readback that I am now turning to 270.

 

[time builder]

Here's one:
Yesterday, my student and I were decending into Socal. They cleared us for a STAR about 20 miles from the first VOR. A little while later, we reach the first point of descent on the STAR, and my student starts to descend without a radio call. "Let them know you're leaving 8000," I said. He did, and they told him to stay at 8000.

Hence, we acknowledged a clearance, but that didn't mean we could descend without letting the controller know, especially where we didn't reach a point of descent until several minutes after the clearance was recieved.

 

[Booker]

A little while later, we reach the first point of descent on the STAR, and my student starts to descend without a radio call. "Let them know you're leaving 8000," I said. He did, and they told him to stay at 8000.

Just to clarify, you must have been issued a "descend via" clearance, right?