NCAA PPL Communications study materials
NCAA PPL Communications study resources

Similar Callsigns on Approach

NCAA PPL Communications · Put your knowledge to work in context.

All case studies

Similar Callsigns on Approach

You are N123AB, a Cessna 172 on a busy approach frequency, level at 4,500 feet. N123CB, a similar Cessna, is also on frequency. Approach issues: “N123AB, descend and maintain 3,000, cleared ILS Runway 27 approach.” N123CB immediately replies: “Descending to 3,000, cleared ILS Runway 27, N123CB.” The controller does not correct the readback and turns to another aircraft. You see N123CB begin a descent ahead and to your left. You have not received a descent clearance, and your assigned altitude remains 4,500. The frequency is congested, and a handoff is likely within a minute. You must decide what to do now, what to say, and how to prevent the similar-callsign trap from becoming a traffic conflict.

1. What is occurring and why is this a high-risk communication error?

Read the worked answer

N123CB has answered a clearance addressed to N123AB and is descending without its own clearance. The controller did not correct the wrong callsign in the readback, so the frequency now contains a latent conflict: ATC may believe N123AB is descending, while N123AB remains at 4,500 and N123CB descends. Similar callsigns, a congested frequency, and expectation bias make this likely. The risk is an altitude bust or traffic conflict, especially if other aircraft are at 3,000 or 4,500. It is a classic hearback/readback error: the wrong aircraft heard its own call sign because the suffixes are close.

2. What should you, N123AB, do immediately and what transmission should you make?

Read the worked answer

Maintain 4,500 feet and do not descend. Immediately call approach with your full callsign: “Approach, N123AB, level 4,500. I did not receive a descent clearance. N123CB read back my clearance and is descending. Confirm clearance for N123AB.” This separates the two aircraft verbally and alerts ATC to the wrong readback. Keep monitoring the frequency and watch N123CB. If ATC does not respond, continue at your assigned altitude and, if a traffic advisory system is available, use it; do not take evasive action unless a collision threat is imminent. Do not switch frequencies until the confusion is resolved.

3. What defenses reduce similar-callsign errors on both sides?

Read the worked answer

Use full callsigns on every transmission when similar callsigns are on frequency-especially initial call, readback, and final call. ATC should also use full callsigns and avoid abbreviating when suffixes are similar. Pilots should read back the callsign at the end, listen for the complete call, and challenge any clearance that seems intended for another aircraft. Use sterile cockpit during approach, reduce non-essential conversation, and ask “say again” or “confirm for N123AB” if unsure. Expectation bias-hearing what you expect-is powerful; slow down and verify the callsign before acting.