The CTAF Self-Announce, the Six-Part Call Every Pilot Gets Half Right, and the Non-Towered Pattern Where Radio Discipline Actually Saves Lives
Learn the complete six-part CTAF self-announce call structure that keeps pilots safe at non-towered airports, including when to call and what to say.
The CTAF self-announce call is how pilots at non-towered airports build a shared traffic picture - and most pilots only get it half right. A complete call follows a six-part structure defined in the Aeronautical Information Manual (AIM): airport name, aircraft type, N-number, position, altitude, intentions, and airport name again. Getting all six parts right is the difference between adding information to the frequency and adding noise.
What Makes a Non-Towered Airport Different
A non-towered airport (sometimes called an uncontrolled airport) is any field without an operating control tower - including towered airports when the tower closes for the night. The vast majority of airports in the United States have no tower at all. Cross-country general aviation flying will take you to these fields.
At a towered airport, ATC builds the sequence and issues clearances. Your radio call confirms you received an instruction. At a non-towered airport, no one manages the sequence. Every pilot in the pattern is a co-sequencer, and the radio is how you collectively build a shared picture of who is where. That’s a fundamentally different job for the radio - you’re not communicating with a controller, you’re communicating with other pilots.
Where Do You Find the CTAF Frequency?
The CTAF frequency appears in the airport data block on your sectional chart, marked in magenta for uncontrolled fields. It also appears in the Chart Supplement (which older pilots still call the Airport Facility Directory, or AFD). Look it up before you’re in the air. Dialing in frequencies while flying the 45-degree entry is a task-management problem you don’t need.
At most non-towered airports, the CTAF also serves as the unicom frequency - the same channel handles both traffic advisories and communication with the fixed base operator on the ground. Keep non-critical FBO conversations brief. Traffic calls take priority.
What Are the Six Parts of a CTAF Call?
The AIM-recommended format contains these elements, in order:
- Airport name
- Aircraft type
- Aircraft identification (N-number or callsign)
- Position
- Altitude
- Intentions
- Airport name again
The airport name appears at the start and end - a “sandwich” structure - so anyone scanning multiple frequencies or half-listening knows immediately whether the call is relevant to them. Near busy regions where multiple fields share adjacent airspace, this framing makes a crowded CTAF manageable.
A complete call sounds like this:
“Millbrook traffic, Cessna one seven two, November four five six seven Foxtrot, three miles to the northeast, one thousand eight hundred feet, inbound for landing, full stop, runway two four, Millbrook.”
Compare that to what many student pilots actually transmit:
“Millbrook traffic, Cessna inbound, Millbrook.”
That call tells other pilots a Cessna exists somewhere in the universe. They don’t know the tail number to look for, how far out you are, your altitude, or which runway you intend to use. You’ve used frequency time without adding useful information.
When Should You Make Each Call?
The AIM recommends your first inbound call at approximately 10 miles out. That gives everyone in the pattern time to fit you into the sequence before you arrive. The full call sequence for a standard inbound arrival:
- 10 miles out - initial call, full six-part format
- Entering the 45-degree for downwind - position call (or announce straight-in if applicable)
- Turning downwind - position call
- Turning base - position call
- Turning final - position call
- Clear of the runway after landing - call that you’re off the runway
That last call matters more than most pilots realize. It tells the traffic behind you that the runway is clear and they do not need to go around.
If you’re departing from the ramp, make a call when ready to taxi and another from the hold-short line before takeoff. The ground calls catch the pilot who just turned final and hasn’t heard you yet - they hear your transmission and know something is about to enter the runway they’re planning to land on.
Do You Have to Make These Calls?
CTAF calls at non-towered airports are recommended by the FAA, not legally mandated in the same way that readbacks at a Class Delta airport are required. But the AIM’s recommendation at a non-towered field is effectively required by reality - you have no other way to keep other pilots informed.
The Airman Certification Standards (ACS) for the private pilot certificate includes radio communication as an evaluated task. During a practical test at a non-towered airport, the examiner is watching to see that you understand what your radio calls are doing, not just that you can produce sounds on a frequency. That means sequencing yourself correctly, making complete calls, and demonstrating active traffic awareness. A vague call followed by no apparent awareness of other traffic will generate a conversation you don’t want to have with your examiner.
Why Should You Always Include Altitude?
Many pilots drop the altitude component once they get comfortable with the format. The reasoning is understandable - if you’re in the pattern, everyone’s at pattern altitude. But aircraft transiting through the area at a different altitude need that information. A pilot overflying the field at 2,500 feet needs to know you’re at pattern altitude on the downwind leg. Your altitude call answers that question without anyone having to ask.
Why Is “Any Traffic, Please Advise” Discouraged?
The AIM specifically states that “any traffic, please advise” is not recommended. The reason matters more than the rule itself.
When you broadcast “any traffic, please advise,” you’re asking every aircraft in the area to key up simultaneously. If three aircraft are in the pattern, all three may transmit at once. The result is a wall of noise - nothing intelligible gets through. Worse, the phrase creates a false sense that if nobody responds, the pattern is clear. It isn’t. The pilot on a tight base may be too busy to respond. An ultralight running the river may not have a radio at all. Silence is not safety at a non-towered airport.
The correct approach is a self-announce call. You broadcast to the pattern; you don’t ask the pattern to speak to you.
How Do You Handle Conflicts in the Pattern?
If you’re on downwind and hear another aircraft announce they’re turning final for the same runway, don’t wait and hope. Make your position call, listen, and look. If you can’t establish visual contact and aren’t confident you can sequence safely behind them, extend your downwind and announce it:
“Millbrook traffic, Cessna four five six seven Foxtrot, extending downwind, runway two four, will follow traffic on final, Millbrook.”
That call is information. It’s useful to every aircraft in the area and reduces uncertainty for everyone simultaneously.
What Is the Overfly Technique?
When arriving at an unfamiliar non-towered airport, one option is to overfly the field before entering the pattern. Fly over at an altitude above the traffic pattern, look at the wind indicators and segmented circle, and get a visual scan of any existing traffic. While doing this, monitor the CTAF actively. You’re building your situational picture from both sources at once.
This isn’t a requirement - it’s a technique. It pairs well with starting to monitor the CTAF before you’re 10 miles out, not just at the 10-mile mark. Build the picture early and update it continuously.
What About Flight Service Stations on CTAF Frequencies?
At some airports, a flight service station (FSS) is associated with the CTAF. An FSS can provide weather information, wind observations, and a summary of traffic they’ve heard on the frequency. But they are not ATC - they are not separating you from anything. They’re an information provider. The pilot in command makes every traffic decision.
Key Takeaways
- The complete CTAF call has seven elements: airport name, aircraft type, N-number, position, altitude, intentions, and airport name again - in that order.
- Start listening to the CTAF before 10 miles out and make your first call at approximately 10 miles.
- Make calls at every phase: initial call, entering the 45°, turning downwind, turning base, turning final, and clear of the runway after landing.
- “Any traffic, please advise” is not recommended by the AIM - it asks everyone to key up simultaneously and creates false reassurance from silence.
- Always include your altitude, even in the pattern. Aircraft transiting through at different altitudes need that information.
- The goal is not format perfection - it’s giving other pilots who you are, where you are, and what you’re doing.
Radio Hangar. Aviation talk, built by pilots. Listen live | More articles