When to acknowledge ATC

On Fri, 06 May 2005 16:50:22 GMT, George Patterson
wrote:

Jose wrote:

No. As you said, Class B airspace requires ATC to tell you you are
cleared into it. You need to hear "Cleared through the Bravo airspace"
or somesuch.

The last clearance I got from New York ran something like "November 3162 Kebec,
climb to 2500 feet, heading 355, stay west of the river, report at the Hudson
tunnel."

When I've asked for a Bravo clearance, and they have to check with
another controller, they'll sometimes come back with something like
the above... Just directions that would be take me into the Bravo
without the explicit 'cleared into the bravo'. I'll usually read
those back with 'understand cleared into the bravo' appended to the
end so there is no mistaking things.

aw

On 5 May 2005 14:21:41 -0700, "Andrew"
wrote:

ATC says "radar contact, 20 miles south of XYZ, proceed on course". Do
you acknowledge this transmission? Do they want read back for everything, or should
we shut up as much as possible?

The best thing to do is click your transmitter twice.

And in deference to Dudley, I'm going to put a smiley here.

00000000000000000000000000000000000000000000000000 00

Sorry, but I just couldn't do it.

Mike Weller

wrote in message
On 5 May 2005 14:21:41 -0700, "Andrew"
wrote:

ATC says "radar contact, 20 miles south of XYZ, proceed on course". Do
you acknowledge this transmission? Do they want read back for everything,
or should
we shut up as much as possible?

The best thing to do is click your transmitter twice.

Where did you hear that? ATC does that. But there's only one of them on
the freq. Pilots shouldn't. ATC requires a verbal response.

moo

I was told under no uncertain terms by ATC one day that "Double clicking is
*NOT* an acknowledgement." On the below, ATC is not only giving information
("radar contact"), but relaying instructions ("proceed on course").
Instructions require not only acknowledgement, but readback: "Proceeding on
course, 45Q."

As far as altimeter settings, if you don't acknowledge, ATC doesn't whether
or not you heard them. If you don't read them back, they don't know whether
or not you heard them correctly. "29.92, 45Q."


wrote in message
news:1115361381.ba8215193ce4b7d4faa4002afd3225cc@o nlynews...
On 5 May 2005 14:21:41 -0700, "Andrew"
wrote:

ATC says "radar contact, 20 miles south of XYZ, proceed on course". Do
you acknowledge this transmission? Do they want read back for everything,
or should
we shut up as much as possible?

The best thing to do is click your transmitter twice.

And in deference to Dudley, I'm going to put a smiley here.

00000000000000000000000000000000000000000000000000 00

Sorry, but I just couldn't do it.

Mike Weller

"Andrew" wrote in message
oups.com...

ATC says "radar contact, 20 miles south of XYZ, proceed on course". Do
you acknowledge this transmission? How about when ATC says "altimeter
setting 2992" on your first contact after a handoff? Does this require
acknowledgement?


If you don't acknowledge them they're going to be repeated.


In the past, I've acknowledged such things if the controller was not
busy. But I've heard all kinds. Some people read back the altimeter
setting. I've even heard people reading back the "radar contact"
message. I feel that this is a waste of bandwidth. However, I don't
know what ATC prefers. Do they want read back for everything, or should
we shut up as much as possible?


I read back control instructions; routes, headings altitudes, etc.
Everything else is just acknowledged.

For me it depends on the situation and what I've been hearing
on frequency. I will most always acknowledge with something ..
it tells them I'm still with them. If they're up to their hind ends in
alligators .. then a quick acknowledgement of the last 3 letters
of my N number or just a "thanks". If I'm hearing them chit chatting
indicating they're bored silly then I might stretch it out to include "good
morning,
how's things going for you this morning"....


"Andrew" wrote in message
oups.com...
ATC says "radar contact, 20 miles south of XYZ, proceed on course". Do
you acknowledge this transmission? How about when ATC says "altimeter
setting 2992" on your first contact after a handoff? Does this require
acknowledgement?

In the past, I've acknowledged such things if the controller was not
busy. But I've heard all kinds. Some people read back the altimeter
setting. I've even heard people reading back the "radar contact"
message. I feel that this is a waste of bandwidth. However, I don't
know what ATC prefers. Do they want read back for everything, or should
we shut up as much as possible?

In article .com, Andrew wrote:
ATC says "radar contact, 20 miles south of XYZ, proceed on course". Do
you acknowledge this transmission?

Yes, but only with my callsign (abbreviated when applicable).

How about when ATC says "altimeter
setting 2992" on your first contact after a handoff? Does this require
acknowledgement?

And a readback. You want to know that both you and the controller are
working off the same altimeter setting or Bad Stuff may happen. My
readback is pretty short ('two niner niner two, november four one
bravo')

--
Dylan Smith, Castletown, Isle of Man
Flying: http://www.dylansmith.net
Frontier Elite Universe: http://www.alioth.net
"Maintain thine airspeed, lest the ground come up and smite thee"

Andrew wrote:

ATC says "radar contact, 20 miles south of XYZ, proceed on course". Do
you acknowledge this transmission? How about when ATC says "altimeter
setting 2992" on your first contact after a handoff? Does this require
acknowledgement?

In the past, I've acknowledged such things if the controller was not
busy. But I've heard all kinds. Some people read back the altimeter
setting. I've even heard people reading back the "radar contact"
message. I feel that this is a waste of bandwidth. However, I don't
know what ATC prefers. Do they want read back for everything, or should
we shut up as much as possible?

I don't read back "ident" instructions, I just press the button. I
acknowledge everything else. Things like altimeter and such I just use the
(shortened) tail number. Anything that's an instruction I read back.

--
Frank....H

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Sorry about my last post, Steve. It's directed towards you, not
Ron.

BL.
- --
Brad Littlejohn | Email:
Unix Systems Administrator, |
Web + NewsMaster, BOFH.. Smeghead! | http://www.sbcglobal.net/~tyketto
PGP: 1024D/E319F0BF 6980 AAD6 7329 E9E6 D569 F620 C819 199A E319 F0BF

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFCfoRMyBkZmuMZ8L8RAsibAJ9IXbqKZDFYnPR4MdKEIe kWAjPfBACggbpZ
uWWXkFydqHkC1HG1LkpKqPk=
=9rb2
-----END PGP SIGNATURE-----