VFR Radio Calls and Position Reports

Building the call: the four fixed parts

Every initial VFR call opens with who you are calling, the station's callsign, then who you are, your own aircraft callsign, then where you are, your position and, where it matters, your level or altitude, and closes with what you want, a request or a piece of information such as your intentions for joining.

Once contact is established, later calls in the exchange can drop the first element, and your own callsign can shorten to an abbreviated form once the station has used that form first. Reinventing the full callsign every time is not wrong, just unnecessary once the shorter form has been offered.

• Station called: who you are speaking to
• Own callsign: who you are
• Position, and level where relevant: where you are
• Request or intention: what you want

Position reports and calls in the circuit

A position report carries fixed content in a fixed order: your callsign, your position, described relative to a known point or a circuit leg, your level or altitude, and, where the situation calls for it, your next intention. At a controlled aerodrome that content sits inside a longer sequence of expected calls: a request to join, an acknowledgement of the join instruction, then a report at each point the aerodrome expects, typically downwind, then base or final.

The joining call itself has to state your position and intention clearly enough that the controller can place you in the pattern immediately, for instance overhead before descending, or joining downwind directly. Leaving out the level in a joining call is one of the most common incomplete calls, because the controller needs it to sequence you against other traffic sharing the same piece of airspace, not only to know where you are laterally.

Readability and the words that are not interchangeable

The readability scale runs from 1 to 5: 1 is unreadable, 2 is readable now and then, 3 is readable but with difficulty, 4 is readable, and 5 is perfectly readable. A pilot reporting readability 3 is telling the controller that the message is getting through but that a repeat or a frequency check may soon be needed, not that the transmission has failed.

Three words cause most of the confusion in this subject, and each has exactly one meaning. ROGER confirms only that you received the controller's last transmission; it agrees to nothing and answers no question. AFFIRM means yes, and its opposite, NEGATIVE, means no. WILCO means you understood the instruction and will comply with it, so it belongs only where you are actually committing to an action. Answering a yes or no question with roger, or acknowledging an instruction with affirm, both sound plausible and are both wrong, which is exactly why the exam sets them as distractors.