The CTAF Self-Announce, the Phrase the AIM Tells You Not to Say, and the Non-Towered Airport Radio Habit That Creates Confusion Instead of Traffic Awareness
'Any traffic in the area, please advise' is not recommended by the AIM - here's what to say instead and how proper CTAF self-announce calls build real traffic awareness.
“Any traffic in the area, please advise” is one of the most common radio calls at non-towered airports - and one of the least effective. The Aeronautical Information Manual (AIM) specifically flags this phrase as not recommended, not because it sounds wrong, but because it doesn’t accomplish what pilots think it does. Proper CTAF self-announce calls follow a defined structure that builds the traffic picture for everyone, rather than asking others to build it for you.
Why Does “Any Traffic in the Area, Please Advise” Fail?
The phrase puts the burden on every other aircraft in the area to stop what they’re doing and respond. Some pilots can’t - they’re on short final, turning base, or focused on a critical task. The ones who can respond will. The ones who can’t, won’t.
The result is a partial picture. The real danger is interpreting silence as no traffic. A pilot on final who’s too busy to key the mic is still a factor - their silence is not an all-clear. That’s the core problem with the call: it invites a false sense of security.
The AIM addresses this explicitly. The phrase is not forbidden and not illegal. But it is specifically not recommended, and the AIM provides a better alternative.
What Does the AIM Recommend Instead?
The AIM recommends the self-announce procedure - a structured call that gives other pilots exactly what they need without requiring them to respond. At a non-towered airport, pilots are collectively responsible for building the traffic picture. The CTAF is a cooperative system, not a one-way request channel.
At a towered airport, the controller handles sequencing, advisories, and pattern management. You can be a relatively passive participant and still be safe. At a non-towered airport, that job falls on every pilot in the area - including you. Self-announce calls work because they push information outward. Every aircraft on frequency receives your position, intentions, and identity without having to ask.
What Should a Proper CTAF Self-Announce Call Include?
Every self-announce has five elements:
- Airport name (at the beginning)
- Who you are - aircraft type and call sign
- Where you are - position and distance from the field
- What you’re doing - current pattern leg or flight status
- Airport name again (at the end)
The airport name appears twice because multiple uncontrolled airports frequently share the same CTAF frequency. In many areas, a single frequency serves two or three different fields within radio range of each other. A pilot at a different airport needs to know immediately whether your call is relevant to them. The second airport name confirms it and reduces frequency clutter.
A complete call sounds like this:
“Millbrook traffic, Cessna Seven-Two-Three-Four Foxtrot, ten miles to the south, inbound runway two-two, Millbrook.”
That call is roughly eight seconds long. It tells every pilot on frequency who you are, where you are, which runway you’re targeting, and your intention. Anyone within radio range can place you precisely in their mental traffic picture.
When Should You Make CTAF Calls During an Approach?
The AIM recommends self-announce calls at these specific points:
- Ten miles out, when inbound to the field
- Entering the 45 for downwind
- On downwind
- On base
- On final
- Clear of the runway after landing
That’s five or six calls through the full approach and landing sequence. Pilots who trained primarily at towered airports sometimes find this excessive. But at a non-towered airport, there is no radar and no controller. Your position reports are the only traffic picture other pilots have.
How Do You Determine Which Runway to Announce?
Check the wind first. If the field has AWOS (Automated Weather Observation System) or ASOS (Automated Surface Observing System), listen to it before entering the area. If automated weather isn’t available, look for the wind sock once you’re close enough. If neither is available yet, monitor the CTAF - if other pilots are already flying the pattern, note which runway they’re calling.
Once you’ve identified the active runway, it belongs in every call you make. If someone else is approaching from the opposite direction, your runway call alerts them immediately that a conflict may exist. If the pattern is empty, your calls establish the runway for any aircraft that tunes in after you.
What If You Tack “Please Advise” Onto an Otherwise Correct Call?
This is a subtle mistake that’s easy to miss. A pilot makes a fully correct self-announce - aircraft, position, runway, airport name twice - then appends “any traffic, please advise” at the end.
The instinct behind it is understandable. You want confirmation. You want someone to tell you you’re clear to come in. But no pilot on a CTAF can clear you for anything. Even if every aircraft in the area responds and acknowledges your position, that exchange is information - not a clearance to land.
Radio supports situational awareness. It does not replace the requirement to see and avoid, or transfer the judgment call that remains yours alone.
How Do You Handle a Busy CTAF?
Popular non-towered airports - especially fly-in destinations on a weekend morning - can generate real frequency congestion, with pilots stepping on each other and garbled transmissions. In those conditions, frequency discipline matters more, not less.
Keep calls tight and factual. Don’t editorialize, provide weather commentary, or ask questions unless you have no other option. Make your call, listen, and clear the frequency.
One thing that surprises many student pilots: you do not acknowledge other pilots’ self-announce calls unless you have something meaningful to add. If someone calls short final, responding with “roger” just adds noise. What you do is register their position and figure out what it means relative to yours. If you’re on downwind and someone calls short final, you know you have at least a minute before turning base. Absorb it. Act on it. Don’t respond to it.
What Is the Examiner Looking for on Your Checkride?
The Airman Certification Standards (ACS) for the private pilot certificate address radio communications across several tasks, including airport operations and traffic pattern procedures. Examiners want to see three things:
- You understand the CTAF concept and its cooperative nature
- You can make complete, accurate self-announce calls
- You demonstrate actual situational awareness based on what you hear - not just what you transmit
Non-standard phraseology is a red flag. “Any traffic in the area, please advise” is non-standard. So is omitting the airport name. So is vague or ambiguous runway language.
Be specific about your intentions. If you’re doing touch-and-goes, say so - the pilot sequencing in behind you needs to know you’re returning to the pattern, not clearing the runway to taxi in. If you’re landing full stop, say that. The more specific your call, the more useful it is to everyone else on frequency.
Does ADS-B Out Replace CTAF Calls?
No. The logic seems reasonable: if you’re transmitting ADS-B out, you’re visible on every equipped display in the area. But traffic displays have latency built in, and not every aircraft in the pattern has traffic advisory capability. Situational awareness built on listening is also fundamentally different from situational awareness built on watching a screen.
The pilot flying head-outside is going to see you. Your CTAF call tells them which direction to look before they ever check a display. ADS-B out is a surveillance tool. CTAF is a communication tool. They serve different purposes and work best together. Make your calls regardless of what equipment you’re carrying.
What Does a Complete CTAF Arrival Sequence Look Like?
Here’s a full arrival at a non-towered airport called Riverside, winds favoring runway one-niner, flying a Piper Cherokee:
Ten miles out: “Riverside traffic, Cherokee Two-Four-Five-Romeo-Tango, ten miles to the north, inbound runway one-niner, Riverside.”
Entering the 45: “Riverside traffic, Cherokee Two-Four-Five-Romeo-Tango, entering the forty-five for left downwind runway one-niner, Riverside.”
On downwind: “Riverside traffic, Cherokee Two-Four-Five-Romeo-Tango, left downwind runway one-niner, Riverside.”
Turning base: “Riverside traffic, Cherokee Two-Four-Five-Romeo-Tango, left base runway one-niner, Riverside.”
On final: “Riverside traffic, Cherokee Two-Four-Five-Romeo-Tango, final runway one-niner, Riverside.”
Clear of the runway: “Riverside traffic, Cherokee Two-Four-Five-Romeo-Tango, clear of runway one-niner, Riverside.”
Six calls. Each one eight to ten seconds. Over five to eight minutes of flying, your position and intentions are on frequency six times. Anyone within radio range knows exactly where you are through the entire approach.
That’s how you build a traffic picture at a non-towered airport - not by asking for one, but by broadcasting it.
Key Takeaways
- “Any traffic in the area, please advise” is not recommended by the AIM - it produces an incomplete picture and can mislead pilots into treating silence as an all-clear.
- A proper self-announce includes five elements: airport name, aircraft identity, position, intentions, and airport name again at the end.
- The airport name appears twice because multiple airports frequently share the same CTAF frequency.
- The AIM recommends five to six position calls through a full non-towered airport approach and landing sequence.
- ADS-B out does not replace CTAF calls - they are different tools that serve different purposes.
Radio Hangar. Aviation talk, built by pilots. Listen live | More articles