The CTAF Call, the Seven-Element Self-Announce Students Collapse Into Three Words, and the Non-Towered Airport Where Your Radio Is the Only Separation You Get

At a non-towered airport, there is no controller sequencing traffic, issuing pattern entries, or alerting you to conflicts. Your radio is your primary traffic separation tool. A complete, well-timed self-announce call is what keeps other pilots from occupying the same piece of sky you are headed for.

Why Non-Towered Airport Radio Is Different From Towered Flying

Towered airport training builds one specific skill: read back instructions and comply. That is useful, but it is a fundamentally different skill from what non-towered operations require. At a controlled airport, the controller does a significant portion of the separation work. At an uncontrolled airport, every pilot on frequency is doing that work for themselves - and only if they can hear what everyone else is saying.

There is no radar, no scope, no controller watching for conflicts. The Aeronautical Information Manual (AIM), Chapter 4, Section 1 lays out recommended self-announce procedures for non-towered airports. Worth noting: there is no regulatory requirement to transmit at a non-towered airport under Visual Flight Rules. You are not even required to have a radio. But choosing not to transmit - or transmitting incomplete calls - is a serious safety decision with consequences for every other pilot on that frequency.

What Are the Seven Elements of a Proper CTAF Call?

Most pilots compress a self-announce call down to three elements. The missing four are exactly what other pilots need to build an accurate traffic picture. A complete call has seven elements, in this order:

1. Airport name. Lead with the airport, not your call sign. Anyone on frequency needs to know in two words whether this call is relevant to them.

2. Aircraft type. “Cessna 172” tells other pilots what to expect from your approach speeds, descent rate, and pattern size. A Cessna 172 flies a significantly different pattern than a Beechcraft Baron.

3. Call sign. This is what another pilot uses to respond if they need to reach you.

4. Position. Not “inbound.” Where you are relative to the airport, and in which direction. “Ten miles to the southeast” is usable. “Inbound” is not - it gives no scanning reference to the pilot already on downwind.

5. Altitude. Pattern altitude is not universal. Not every pilot flies the same height, and not every airport has the same traffic pattern elevation. Altitude is especially critical when transitioning at or near pattern altitude.

6. Intentions. Landing, touch-and-goes, or overflight are three different traffic scenarios for everyone else on frequency.

7. Airport name again. This is the element most pilots drop, and the AIM specifically recommends it. Radio frequencies overlap and calls from other airports bleed in. Repeating the airport name at the end confirms which field you are calling.

What Does a Complete CTAF Call Sound Like?

A full, correct call looks like this:

“Riverside traffic, Cessna one seventy-two, November four five six seven eight, ten miles southeast, two thousand three hundred, inbound for landing, Riverside.”

That call takes roughly eight seconds. It gives every pilot on frequency everything they need to find you, sequence around you, or get out of your way.

When Should You Make CTAF Calls?

The AIM recommends your first call at ten miles out - not when you see the runway, not when you join the downwind. Early calls give maximum planning time. A pilot about to depart can hold short, let you land, and go. A pilot who hears you for the first time on short final is already making an emergency decision.

After the ten-mile call, transmit at each standard pattern position:

• 45-degree entry to downwind
• Turning downwind
• Turning base
• Turning final
• Clear of the runway (after landing)

That last call is almost universally skipped by student pilots. “Riverside traffic, Cessna four five six seven eight, clear of runway two seven, Riverside” tells every aircraft holding short that the runway is available. Skipping it leaves them waiting for information they will never receive.

Are CTAF Calls Clearances?

No - and this distinction matters. CTAF calls are advisory. You are announcing intentions, not receiving a clearance to do anything. When you hear another pilot call their position, you are receiving information, not a guarantee of their exact location.

Traffic pattern legs are not a fixed size. A pilot flying a wide, stable base leg will be a quarter mile further from the runway than a pilot flying a tight, cramped base. The call gives you a starting point for your scan. Your eyes have to confirm it. See and avoid remains your responsibility, regardless of what the radio tells you.

What Happens When Students Get This Wrong?

Consider a composite scenario drawn from real patterns of error. A student on their first solo cross-country has been talking to controllers the entire route. Twenty miles from their destination, approach drops them with “frequency change approved.” They dial up the CTAF and immediately key the mic - without listening first. They step on an existing transmission without realizing it. They call “ten miles inbound” without specifying a direction. They enter on a straight-in to runway 27, which is occupied by an aircraft already turning base from the left downwind, also for runway 27.

Neither pilot heard the other’s call cleanly. The conflict was resolved only when the other aircraft caught it visually on final and went around. Luck is not a procedure.

The correct sequence when arriving at an unfamiliar non-towered airport:

1. Twenty miles out: tune the CTAF
2. Listen for 15 seconds before transmitting - build a picture of existing traffic
3. At ten miles: make a complete seven-element call
4. Continue listening and making calls at each pattern position
5. At every turn: clear the airspace ahead before committing to the turn

How Do You Handle Frequency Congestion?

At a busy non-towered airport on a fly-in weekend or a summer afternoon, multiple aircraft will attempt to transmit simultaneously. When two transmissions overlap, they cancel out. The result is a squeal, a garbled mess, or silence. This is called a simultaneous transmission, and it is more dangerous than silence because it creates the illusion of information when no information actually got through.

If you suspect your transmission was stepped on, wait a moment and transmit again. If you hear a squeal when you key up, pause, let the frequency clear, then go. Always listen before you transmit.

One phrase worth addressing specifically: “Any traffic in the area, please advise.” The AIM discourages this call. It was more common in earlier practice and some instructors still teach it, but the AIM removed it from recommended phraseology because it generates frequency clutter without adding safety. Traffic already in the area should already be making position calls. Leave this phrase out.

What Are the Most Common CTAF Radio Mistakes?

Mistake 1: The stripped-down call. “Riverside traffic, one seventy-two, inbound.” Missing the call sign, position direction, altitude, and closing airport name. It sounds like a radio call but gives the traffic picture almost nothing to work with.

Correct: “Riverside traffic, Cessna one seventy-two, November four five six seven eight, ten miles southeast, two thousand five hundred, inbound for landing, Riverside.”

Mistake 2: Omitting the runway. At an airport with more than one active runway, “turning base” is meaningless. “Left base runway two seven” tells other pilots exactly where to look.

Mistake 3: Straight-in without announcing it. A straight-in approach is not wrong - it is sometimes the most efficient and safest option. But it intersects normal pattern legs from an unexpected direction. “Riverside traffic, Cessna four five six seven eight, straight-in final runway two seven, three miles, Riverside” tells the aircraft on downwind that you are not following normal sequencing so they can plan accordingly.

Mistake 4: No clear-of-runway call. Every aircraft holding short is waiting for that transmission.

How Do You Find the CTAF Frequency?

Every non-towered airport publishes its CTAF in the chart supplement. On a sectional chart, look for a small “C” inside a circle near the airport symbol.

• Most non-towered airports use a UNICOM, with 122.8 MHz being the most common frequency
• Some airports share a CTAF with a nearby approach control
• Remote airports may use multicom on 122.9 MHz

Know the frequency before you leave the ramp. Dialing it in at ten miles while simultaneously building a traffic picture is not a good use of heads-down time.

What About Pilot-Controlled Lighting?

Most non-towered airports have pilot-controlled lighting (PCL) - runway lights activated by clicking the mic on the CTAF. The chart supplement lists the procedure for each airport:

• 3 clicks: low intensity
• 5 clicks: medium intensity
• 7 clicks: high intensity

Lights typically time out after approximately 30 seconds. Look up the procedure for your destination before departure. Searching the chart supplement on short final in the dark is not a viable workflow.

Key Takeaways

• A complete CTAF self-announce has seven elements: airport name, aircraft type, call sign, position (direction and distance), altitude, intentions, and airport name again
• Your first call should be at ten miles out - not when you enter the pattern
• CTAF calls are advisory, not clearances - see and avoid remains your responsibility at all times
• The clear-of-runway call after landing tells holding aircraft it is safe to depart - do not skip it
• “Any traffic in the area, please advise” is discouraged by the AIM - leave it out
• Always listen before you key up - simultaneous transmissions cancel each other and create the illusion of information when none got through