Abrupt Controller

On Thu, 7 Aug 2008 15:07:57 -0400, "Kobra" wrote:

Where was your readback?


I read it back and just like me he heard what his brain expected to hear:
'unable' when I actually said 'when able' . I wish I thought of that while
I was being reprimanded. I was just too busy flying, being embarrassed and
head scratching trying to figure out how this whole misunderstanding took
place.

I seem to recall that ATC isn't responsible for not correcting
mis-heard readbacks so don't count on that, ever. Now, were it me:

1) File an ASRS form, now.

2) WRT the instruction, I would have thought the prefered method would
have been "aircraft, unable Smyrna." As you mention, "Smyrna
unable" is confusing. In fact, if I read the 7110.65 right, he wasn't
in compliance with the approved terminology in 2-1-18(c):

2-1-18: Operational requests
c. State the word “UNABLE” and, time permitting,
a reason.
PHRASEOLOGY-
UNABLE (requested operation).
and when necessary,
(reason and/or additional instructions.)

3) Never get into an on-air discussion. Just shush and go on to the
next sector. It's not worth the airtime, regardless of what the guy
on the ground is doing. You have better things to be doing, like
flying the aircraft. If you want to get into it later after you
landed, ask for the controller's initials, note the time, and then
call his facility and ask for the supervisor or QA guy. They'll take
the information and pull the tapes.