The CTAF Self-Announce Call, the Nontowered Pattern Position Report, and the Five-Part Format Every Student Has to Own Before Their First Solo Cross-Country

At a nontowered airport, no controller sequences your arrival - pilots do it for each other through position reports on the Common Traffic Advisory Frequency (CTAF). The self-announce call follows a specific format and a specific sequence of call points, and getting both right is a fundamental skill before any solo cross-country. What follows covers the complete format, the full sequence, the most common mistakes, and what the Aeronautical Information Manual (AIM) and Airman Certification Standards (ACS) actually expect from you.

What Is the CTAF and Where Do I Find It?

The Common Traffic Advisory Frequency (CTAF) is the designated frequency for pilot-to-pilot communication at airports without an operating control tower. Find it on the sectional chart, in the Airport Facility Directory, or in any modern flight planning app.

The CTAF is often a UNICOM frequency - commonly 122.8 or 123.0 MHz. At some airports it is a MULTICOM frequency: 122.9 MHz. The specific frequency matters less than confirming it before you get there. Assuming is not a procedure.

Are CTAF Self-Announce Calls Required by the FAA?

No - and this surprises many students. The FAA does not legally require self-announce calls at nontowered airports. You could fly into an uncontrolled field in radio silence and remain technically within the regulations.

Safe airmanship requires something more. Other pilots cannot see you until they can see you. Without a position report, a pilot on final has no shared awareness of your existence. Self-announce calls exist to create that awareness, and the pilot who skips them because they are technically optional is not the pilot anyone wants to share a pattern with.

What Is the Correct Format for a CTAF Self-Announce Call?

The standard format contains seven elements in this order: airport name - aircraft type - N-number - position - altitude - intentions - airport name again.

A complete call sounds like this:

“Riverside traffic, Cessna one seven two, November four five six seven Alpha, ten miles to the southeast, two thousand five hundred, inbound for landing, Riverside.”

Every element earns its place.

The airport name at the front and back solves a frequency-sharing problem. Multiple airports in the same region may share the same CTAF. If interference cuts off the start of your call, other pilots can still catch the closing airport name and know whether the call applies to them. That structure is functional design, not formality.

Aircraft type before the tail number gives every pilot on frequency immediate performance information. “Cessna one seven two” tells them you’re slow before they’ve even heard your position. They can start building a traffic picture before you finish the call.

A real position - not just “inbound.” Ten miles to the southeast. Five miles northwest of the field. Abeam the water tower. A vague “inbound for landing” tells someone you’re coming but not from which direction or altitude, which means they cannot place you relative to themselves. The purpose of the call is to paint a complete, accurate, instantly-readable picture in another pilot’s head. If it doesn’t do that, it isn’t doing its job.

What Calls Should I Make at Every Point in the Pattern?

There are five standard call points for an arrival. Make all of them.

1. Ten miles out - initial inbound call. At typical training speeds, ten miles is five to six minutes of flight time. That’s enough runway for a pilot on final to land, roll out, and clear before you arrive. Making this call early gives everyone time to sequence.

2. Entering the traffic pattern. The AIM recommends entering on the 45-degree leg to the downwind, and this is where most pilots make their second call. State your position, the runway in use, and your altitude: “Riverside traffic, Cessna four five six seven Alpha, entering left downwind runway two seven, one thousand eight hundred, Riverside.”

3. Turning base. Base leg is a conflict zone. A pilot on a long final who missed your downwind call has no idea you’re there. A departing aircraft climbing through pattern altitude could be turning crosswind exactly where you’re about to be. Call it every time.

4. Turning final. Call it - every time, without exception. Final is where the consequences of a conflict are most severe, and four seconds of words costs nothing.

5. Clear of the runway. This is the most overlooked call. Once you’ve exited the active runway: “Riverside traffic, Cessna four five six seven Alpha, clear of runway two seven, Riverside.” This tells the pilot holding short that the surface is available. It tells the pilot on a one-mile final that the runway is clear. It closes the loop for everyone.

What Calls Are Required Before Departure?

Radio work at a nontowered airport starts before you leave the ground.

Before taxiing onto the runway, announce your departure: “Riverside traffic, Cessna four five six seven Alpha, departing runway two seven, northbound departure, Riverside.”

If you need to back-taxi - meaning you must taxi down the runway itself to reach the far threshold before takeoff - call that specifically and early. Back-taxiing puts you on the active runway facing opposite to approach traffic. Any pilot on short final who didn’t hear your call faces an unexpected conflict. Make the call clearly before you roll onto the runway.

What Are the Most Common CTAF Mistakes Pilots Make?

“Any traffic in the area, please advise.” Stop saying this. The AIM explicitly states this phrase is not a recognized self-announce call and contributes unnecessary frequency congestion. Make your own position call. Other traffic will respond or you’ll hear their calls as they happen. Asking for advisories instead of announcing yourself wastes time and frequency.

Calling only one leg of the pattern. The calls work together as a system. A student doing practice landings who calls downwind and then goes quiet, or starts calling final without ever calling base, breaks the picture for everyone else. Make all five calls.

Omitting aircraft type. “Four five six seven Alpha turning final” tells no one anything useful. Aircraft type is not optional - it tells other pilots your approximate speed and performance before they even process your position.

Mumbling the airport name. The airport name is arguably the most critical element of the call. Traffic at a neighboring airport on the same frequency needs to hear it clearly to know whether your call applies to them. Enunciate it deliberately, both times.

Transmitting without listening first. Three seconds of monitoring before keying the mic, every time. Someone may be mid-transmission. Stepping on another call turns both transmissions into noise - and neither pilot will know it happened.

What Does the ACS Expect on the Checkride?

The ACS for the private pilot certificate evaluates radio communications as part of every applicable task. Examiners are not grading vocal confidence - they are looking for situational awareness. Did you call at the right points? Did your calls contain accurate position information? Did you identify your intentions? Did you listen? Did you sequence with other traffic?

Students who trained primarily at towered airports are typically excellent with ATC communication but have rarely needed to self-announce, because they simply haven’t needed to at home. When the checkride routes to a nontowered airport, calls come out incomplete or at the wrong times.

The fix is deliberate practice before you need it. Tune a nearby CTAF and listen for ten minutes of live traffic. You will learn more from actual calls - both correct and incorrect - than from any amount of reading. Use what you hear to calibrate your standard.

Does Pattern Direction Matter in My Radio Calls?

Yes - significantly. Most traffic patterns use left-hand turns, but some runways designate a right-hand pattern due to terrain, noise abatement, obstacles, or mixed operations.

“Entering left downwind runway two seven” and “entering right downwind runway two seven” place you on completely opposite sides of the runway. A pilot already in the pattern needs that information to know whether you’re behind them or converging. Left or right is not an optional detail.

The standard traffic pattern altitude at a nontowered airport is 1,000 feet above airport elevation, unless local procedures specify otherwise. If your reported altitude doesn’t match what other traffic is reporting, notice it and resolve the discrepancy before descending into the pattern.

Why This All Matters

A nontowered airport is a self-organizing system with no radar, no controller, and no one sequencing arrivals. It functions because pilots communicate, listen, and follow shared conventions. When one pilot communicates poorly or not at all, every other pilot in that pattern is flying with an incomplete picture - and an incomplete picture at a busy uncontrolled field on a clear Saturday is exactly the scenario that produces midair collisions.

Call early. Call completely. Give positions other pilots can visualize. Listen more than you transmit. Build a mental model of everyone in the pattern, update it with each new call, and let that model drive your spacing and sequencing decisions.

AIM section 4-1-9 covers the self-announce format and recommended call points in full if you want the source material.

Key Takeaways

• CTAF self-announce calls are not legally required but are expected practice and essential for safety at nontowered airports
• The complete format is: airport name - aircraft type - N-number - position - altitude - intentions - airport name
• Make five calls per arrival: ten miles out, entering downwind, turning base, turning final, and clear of the runway
• Departure calls start before you taxi onto the runway; back-taxi operations require their own specific call
• “Any traffic please advise” is explicitly called out in the AIM as incorrect - never use it
• Pattern direction (left or right) is a required element of every pattern position report, not an optional detail