Skip to content
View in the app

A better way to browse. Learn more.

The Drone Talk Hub - The Ultimate Drone Community Hub

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (?) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Radio Communication Procedures and Phraseology

FAA ACS — Task V.A: Radio Communications Procedures

Before anything else in this lesson: Part 107 does not require a remote pilot to carry or use two-way radio equipment. Nothing here describes a piece of mandatory gear. What this lesson does cover is standard aviation radio phraseology — the structured, standardized way pilots communicate position and intentions over the radio — because understanding it lets a remote pilot who chooses to monitor aviation frequencies (the subject of the next lesson) actually make sense of what they're hearing, directly supporting the right-of-way and no-interference obligations built across this module.

0Part 107 radio equipage regulations
26Phonetic alphabet letters
V.AACS Task
107.37Right-of-way rule this supports

Part 107 does not mandate radio equipment

This point is worth stating plainly and directly: there is no numbered Part 107 regulation requiring a small UAS or its remote pilot to carry, install, or operate two-way radio equipment. A remote pilot can fly fully compliant Part 107 missions for an entire career without ever transmitting on an aviation frequency. This is genuinely different from some other categories of aviation, and it's an easy point to get backward if you're coming into this course with any assumption that "pilot" automatically implies "radio-equipped."

So why does ACS Task V.A test radio phraseology at all?

Radio phraseology knowledge is tested because of what it enables, not because a radio is required gear. A remote pilot who understands standard phraseology can monitor a relevant aviation frequency (most commonly the CTAF frequency covered in the next lesson) and actually extract useful information from what they hear — another aircraft's position, direction, and intentions — supporting the situational awareness that 14 CFR 107.37's right-of-way rule and 14 CFR 107.43's no-interference rule both depend on. There's also a narrower, specific case, covered fully in the final lesson of this module, where an airspace authorization's conditions may specifically require the remote pilot to communicate with ATC — in that case, phraseology knowledge becomes directly operational, not just supportive.

The phonetic alphabet: why it exists and how it's used

Aviation radio communication uses a standardized phonetic alphabet — Alpha, Bravo, Charlie, and so on through Zulu — specifically because individual letters (especially similar-sounding ones like "B," "D," "E," "P," "T," and "V") are easily confused over a radio with static, background engine noise, or a weak signal, while the full phonetic words are far more distinguishable. An aircraft's identification (its registration or call sign) is spoken using this phonetic alphabet, letter by letter, rather than saying the raw letters themselves — so what's printed as "N12345AB" would be spoken as "November one two three four five Alpha Bravo."

Standard number pronunciation

Aviation radio communication also uses standardized number pronunciation, spoken digit by digit rather than as a whole number, to reduce ambiguity — an altitude of 1,000 feet is spoken as "one thousand," and a heading or frequency like 122.8 is spoken as "one two two point eight," not "one hundred twenty-two point eight." The number nine is pronounced "niner" specifically to avoid confusion with the German word "nein" (no) in international contexts and to distinguish it clearly from other similar-sounding words over a noisy radio.

Full reference chart of the standard aviation phonetic alphabet arranged in a clean grid from A to Z, each letter paired with its phonetic word: Alpha, Bravo, Charlie, Delta, Echo, Foxtrot, Golf, Hotel, India, Juliett, Kilo, Lima, Mike, November, Oscar, Papa, Quebec, Romeo, Sierra, Tango, Uniform, Victor, Whiskey, X-ray, Yankee, Zulu

The standard aviation phonetic alphabet, used to spell out call signs and identifiers clearly over the radio.

View Larger

The four-part structure of a typical radio call

A standard aviation position report, like the kind a pilot makes approaching a non-towered airport, follows a consistent four-part structure: who you're calling, who you are, where you are, and what your intentions are. For example: "Springfield traffic" (who you're calling — announcing to anyone listening on that airport's frequency), "Cessna one two three Alpha Bravo" (who you are — the aircraft's call sign, phonetically spelled), "five miles south, two thousand five hundred, inbound for landing runway two seven" (where you are and what you're doing — position, altitude, and intention), "Springfield traffic" (repeated at the end, again announcing to anyone listening). This structure repeats, with updated position and intention information, at each subsequent point in the pattern.

Why the structure matters for a listener, not just a speaker

Even a remote pilot who never transmits benefits from recognizing this structure, because it tells you exactly where to listen for the useful information in a radio call you overhear. The "where you are" segment — distance, direction, altitude, and intention — is the part that actually matters for building situational awareness about nearby traffic; the "who you're calling" and "who you are" segments are mostly useful for confirming you're hearing a relevant call at the correct airport.

Worked scenario: interpreting an overheard call

While monitoring a frequency near your operating area, you hear: "Springfield traffic, Cessna four five six Charlie Delta, entering downwind runway two seven, Springfield traffic." Applying the four-part structure: this is a call at Springfield airport, from a Cessna aircraft, currently entering the downwind leg for runway 27. Combined with the traffic pattern knowledge from the previous lesson, you now know approximately where that aircraft is (on the downwind leg, parallel to runway 27, likely to turn base and then final in the following minutes) — directly useful information for your own right-of-way and no-interference planning.

Readback: confirming a received instruction

When ATC issues an instruction over the radio — a clearance, a heading, an altitude — the receiving pilot typically reads the instruction back, repeating the key details to confirm they heard and understood it correctly. This "readback" step matters for a remote pilot to recognize when listening, because a readback confirms an instruction was actually received and understood, not just transmitted — useful context if you're trying to follow what's actually happening between ATC and nearby traffic near an operation requiring coordination, covered in the final lesson of this module.

Diagram breaking down a sample radio position report into four labeled segments in sequence: Segment 1 labeled Who You Are Calling reading Springfield traffic, Segment 2 labeled Who You Are reading Cessna one two three Alpha Bravo, Segment 3 labeled Where You Are and Intentions reading five miles south, two thousand five hundred, inbound for landing runway two seven, Segment 4 labeled Repeated Callout reading Springfield traffic, with each segment in its own labeled box connected by an arrow

A standard position report follows a consistent four-part structure: who you're calling, who you are, your position and intentions, and a repeated callout.

View Larger
Letters Phonetic words
A – FAlpha, Bravo, Charlie, Delta, Echo, Foxtrot
G – LGolf, Hotel, India, Juliett, Kilo, Lima
M – RMike, November, Oscar, Papa, Quebec, Romeo
S – ZSierra, Tango, Uniform, Victor, Whiskey, X-ray, Yankee, Zulu
Mistake Why it happens Correct understanding Regulation / source
Believing Part 107 requires a remote pilot to carry a radioRadio phraseology is a tested ACS topic, which can imply mandatory equipmentNo numbered Part 107 regulation requires radio equipage; the knowledge supports situational awareness and specific authorization conditions, not a general equipment mandate.ACS Task V.A
Assuming phraseology knowledge is only useful if you plan to transmitRadio communication sounds inherently two-wayA remote pilot who only listens still benefits significantly from being able to interpret overheard position reports.FAA Remote Pilot Study Guide
Pronouncing numbers as whole numbers instead of individual digitsEveryday speech uses whole-number pronunciationStandard aviation phraseology pronounces numbers digit by digit to reduce ambiguity over a noisy radio channel.FAA Remote Pilot Study Guide

If Part 107 doesn't require a radio, why is this content on the knowledge test at all?

ACS Task V.A tests the underlying knowledge because it supports situational awareness (via monitoring, covered in the next lesson) and because some specific authorization conditions do require direct ATC communication (covered in the final lesson). The knowledge is relevant to real operations even though it isn't a blanket equipment requirement.

Do I need to memorize the entire phonetic alphabet for the test?

Full recall of all 26 words is a reasonable study goal, since sample questions have tested recognition of specific phonetic words. Practically, being able to recognize the pattern (each letter maps to a specific standardized word) matters more than perfect instant recall of every single one.

Why is the number nine pronounced "niner" in aviation phraseology?

To avoid confusion with similar-sounding words over a noisy radio channel and in international contexts (including avoiding confusion with "nein," the German word for "no"), the number nine is specifically pronounced "niner" rather than the standard English pronunciation.

Test Your Knowledge

Answer the questions below to check your understanding. Every answer can be found in the lesson above.

Loading questions...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions ? Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.