Two Similar Call Signs in the Zone
It is a busy Saturday at a Class D aerodrome with four aircraft inbound. Your registration is G-BXTR; another inbound aircraft is G-BXRT. You transmit: "Golf-Bravo-Xray-Tango-Romeo, eight miles south, two thousand feet, inbound for landing." The controller replies: "Golf-Bravo-Xray-Romeo-Tango, cleared to enter the zone, not above one thousand five hundred feet, report left downwind runway 27." You read the clearance back using your own registration and continue. About 30 seconds later, G-BXRT reads back what sounds like the same clearance. The controller then transmits: "G-BXTR and G-BXRT, I have two aircraft reading back the same clearance - each confirm your position." You are now 6 NM south at 2000 ft, close to the zone boundary. Nothing on your radio has failed; the problem is entirely procedural.
1. Identify where the exchange broke down and set out the radio discipline that would have prevented it.
Read the worked answer
Where it broke down. The call signs differ by one letter, but two separate failures made that fatal: you accepted a clearance addressed to a different aircraft, and your readback did not make it obvious to the controller that the wrong aircraft was answering.
The discipline that prevents it.
- Full registration on the initial call, and again on the readback. ATC may abbreviate only after it has done so first; the pilot should not shorten first. "G-BXTR" and "G-BXRT" sound almost identical in a noisy cockpit, so arguably the pilot should spell out or emphasise the suffix until ATC has confirmed the shortening.
- Listen to the whole transmission before keying the microphone. The call sign is at the start of the instruction and the content follows; a pilot who starts writing after hearing a plausible-sounding prefix hears only what they expect.
- Read back the clearance in full, beginning with the call sign ATC used, then the clearance elements, then your own position. The position is the honest cross-check: a controller hearing "G-BXRT at 6 NM south" immediately knows something does not add up.
- Never assume. If the call sign, the position, or any element does not match what you expect, stop and ask: "Confirm that clearance was for G-BXTR." One extra transmission is cheaper than an airspace infringement.
- Monitor the frequency. The other aircraft's readback of "your" clearance was the cue, and it came 30 seconds after the fact.
2. You are 6 NM south at 2000 ft, close to the boundary, and a clearance to another aircraft is the only thing you have heard. What do you do now, and what are you legally entitled to assume?
Read the worked answer
What you are entitled to assume: nothing. A clearance addressed to another aircraft is not a clearance to you, even if it sounds like it might have been yours. Entering controlled airspace without a clearance is an infringement regardless of what you believed at the time.
Actions, in order.
- Do not enter. Remain clear of the boundary - slow down, orbit if necessary, or hold south of the zone. You have 6 NM, which is several minutes of margin; use it rather than the boundary itself.
- Transmit with the full registration and a position, on a clear frequency break: "Golf-Bravo-Xray-Tango-Romeo, six miles south, 2000 feet, requesting confirmation - I have not received a clearance, say again." State that you have not been cleared. That resolves the ambiguity for the controller in one sentence.
- Expect an explicit clearance and read it back in full, including your position so the two aircraft are unambiguous from then on.
- If the frequency is congested and you cannot get through, remain outside and, if you cannot resolve it, do not force the issue - go around and re-plan.
- After landing, file the report. If a genuine ambiguity has been created, tell the controller; it is a known hazard and worth recording.
Judgement point. The pressure to "just go in" is strongest exactly when the boundary is close and another aircraft is also inbound. The correct answer is to stay outside the zone with altitude and time in hand.
3. Suppose instead that your radio fails completely while inside the zone. What do you do, and how would you interpret the light signals?
Read the worked answer
Radio failure. Continue VFR, squawk 7600, keep a good lookout, and land as soon as practicable at the nearest suitable aerodrome - do not continue the planned flight. If the aerodrome is your destination, join in the normal manner and watch the tower.
The signals that matter, for an aircraft in flight:
- Steady red - give way to other aircraft and continue circling. Do not land: this often means the runway is obstructed.
- Flashing red - aerodrome unsafe, do not land. Leave the circuit; do not attempt to sort it out overhead.
- Steady green - cleared to land. Proceed normally.
- Flashing green - return for landing, to be followed by a steady green at the proper time. It is not a landing clearance, and this is the signal pilots most often misread, because on the ground a flashing green means "cleared to taxi".
- Flashing white - land at this aerodrome and proceed to the apron.
- Alternating red and green - danger, be on the alert.
After landing. Clear the runway, park, and report the radio failure to ATC by telephone. The controller has a flight with no communications in controlled airspace and needs to know you are on the ground and safe. Keep the 7600 squawk until you are clear of the manoeuvring area; do not recycle it while you still need to be seen.