The above is the only reference I can find from 7110.65. And the sample dialogue in that Order contains very few aircraft readback examples. I wouldn't say that there's a lot to go by.
I wasn't using that reference as a source for appropriate pilot readbacks. What I meant was that the examples are used to demonstrate appropriate phraseology for controllers. The examples are fully equal to the other text in the document. In fact, you might argue they have a higher priority. The examples demonstrate what the authors consider to be proper technique. The paragraph texts attempts to generalize from the specifics.
<<it just makes sense and eliminates much confusion in transmissions.>>
In the end, that's a matter of judgement. The AIM authors apparently didn't have a strong preference, other than callups.
<<When you are having a dialoque with ATC...even after numerous transmissions...they always use your call sign first.>>
Of course. They're calling
you!
<<It adds a burden to the controller to have to figure out who is making the transmission.>>
Sometimes, but in that dialog, each person was waiting for the other to respond, so there was no confusion.
I hear conversations between ATC and aircraft where the call sign is left out of all subsequent calls and there is no confusion.
Had the position of the call sign been very important, the AIM authors would have stated so explicitly. The only time they do is on callups, where the identify of the caller isn't obvious. When a controller initiates a conversation with an aircraft, the identity of the other party is pretty clear and the call sign at the end merely confirms it.
You call the examples inconsistent, but they are consistent with the above interpretation. My theory explains the data, yours does not. When theory does not match the data, do you change the theory or get rid of the data?
