← All sessionsHomeSearch
Part 107 Made Easy·Radio Communications·0:26:42

Section 5: Radio Communications — Listen Always, Transmit Never (Except One Emergency)

Greg Lead instructor - former flight-school manager, flew in France in his youth, flies out of Prescott AZ. The chapter's whole thesis: a remote pilot never transmits, but a remote pilot who LISTENS owns the traffic picture.

The short version

  1. The legal line first: 'you are not allowed to transmit on aviation radio frequency' - no FCC license, no key-down, ever. Even he, a licensed pilot standing on his own runway during a gear-up emergency, couldn't legally transmit. The single carve-out: declaring a genuine in-flight emergency.
  2. The phonetic system in full (Alpha through Zulu, worldwide), with just two special digits - 3 is 'tree', 9 is 'niner' - and the digit-by-digit law: 4,500 is 'four thousand five hundred', NEVER 'forty-five hundred'; runway 'zero-nine', heading 'zero niner zero', frequencies with 'point'. Above 18,000 ft the words switch to flight levels.
  3. Untowered reality check: position calls are OPTIONAL - 'they should be making radio calls, but they don't have to' - so your ears never get the full picture. The channels: UNICOM (a human with airport info, zero authority), CTAF (self-announce - airport name at BOTH ends of every call, because distant airports share frequencies), Multicom 122.9 when neither exists, and the dying FSS network.
  4. The self-announce script, worked end to end at 'Sedona': 10-mile inbound -> midfield downwind -> base -> final -> clear -> departing, every call bracketed by 'Sedona traffic'. Towered fields flip the flow: ATC directs, the pilot reads back verbatim.
  5. Chart plumbing: CT = tower frequency (star = part-time), 'C' suffix = CTAF, and after a part-time tower closes its frequency BECOMES the CTAF. Exam trap: don't grab the AWOS frequency when the question wants CTAF.

The concepts

01

The listen-only rule and its single exception

He carried a radio to a gear-up landing at his own flight school - and legally could only listen.

Aviation transmission requires licensing a remote pilot doesn't hold; keying up is an FCC violation, full stop. The whole value is one-directional: LISTENING to ATC and CTAF around your operating area tells you who's inbound, which runway is active, and when final is occupied - spatial awareness no app matches for latency. The lone exception: a true emergency (his example: a rogue drone penetrating controlled airspace near traffic), where declaring on the radio is permitted.

Why it matters

This is the chapter's operating doctrine - everything after it exists so your listening actually decodes into a traffic picture.

Go deeper

In one line: Remote pilots: listen always, transmit never (FCC licensing) - except to declare a genuine emergency. Radio's purpose: ATC-pilot and pilot-pilot traffic coordination.

'Not allowed to transmit on aviation radio frequency' (l4547 0:02)

Emergency declaration is the one exemption (l4547 0:03)

Even licensed pilots without a station license can't transmit from the ground (l4547 0:02-0:03)

Optional FAA read: Radio Communication Phraseology and Techniques (l4547 0:01)

Try it now

Spend ten minutes on LiveATC.net with a nearby field's CTAF - count how many of the calls you can place on a mental map of the pattern from section 4.

▶ Watch this taught:

02

Alpha to Zulu, 'tree' and 'niner', and the digit-by-digit law

'Forty-five hundred' is wrong on the radio and wrong on the exam. Every digit gets its own word.

The ICAO alphabet is planet-wide - he used the same one flying in France. Two digits change sound: 3 = 'tree', 9 = 'niner' (0 stays 'zero', never 'oh'). Numbers unravel digit by digit: 4,500 = 'four thousand five hundred'; 10,500 = 'one zero thousand five hundred' - ten, eleven, twelve 'don't exist' on the radio. Runway zero-nine, not runway nine. Frequencies take 'point': 122.1 = 'one two two point one'. Altitudes spell out fully below 18,000 MSL; above that, flight levels drop the last two zeros - 20,000 becomes 'flight level two zero zero'. Headings and speeds: always digits ('zero niner zero', 'three two zero knots').

Why it matters

The FAA question bank tests exactly these renderings - and decoding real radio traffic requires hearing them as normal.

Go deeper

In one line: ICAO Alpha-Zulu; 3='tree', 9='niner'; every figure digit-by-digit; 'point' for decimals; full altitude below 18,000, flight levels above; headings/speeds as digits.

Globally standard alphabet - same in France (l4548 0:00)

Only 3 and 9 change; zero is 'zero' (l4548 0:01)

EXAM: 4,500 = 'four thousand five hundred'; 10,500 = 'one zero thousand five hundred' (l4548 0:02)

Flight levels above 18,000: drop two zeros (l4548 0:02-0:03)

Heading 090 = 'zero niner zero' (l4548 0:03)

▶ Watch this taught:

03

Clock positions and call signs: who's where, and who's talking

'Traffic, ten o'clock, two miles, southbound' - if you're heading north, that traffic is left of your nose and coming AT you.

Traffic calls use the aircraft's own nose as 12 o'clock: 3 is right, 6 behind, 9 left - all relative to HEADING, not north. Call signs are registration numbers ('tail numbers'), fronted by 'November' for US general aviation: first contact uses the full sign ('November one two three Alpha Bravo'), then everyone may clip to the last three ('three Alpha Bravo'). Jets may swap 'November' for the type ('Citation 570 Lima Tango'); airlines use flight numbers ('United 146'). The FAA's sample question runs the clock logic: heading 360, 'traffic ten o'clock' = left-forward quadrant, converging.

Why it matters

This is the decoding key for everything you'll overhear - and clock-position reasoning appears verbatim on the exam.

Go deeper

In one line: Clock positions relative to own heading; call sign = November + tail number (full first, last-3 after); jets may use type, airlines use flight number.

Clock face rides the aircraft's nose, not the compass (l4549 0:00)

Full tail number first, then last-three abbreviation (l4549 0:01)

'November' prefix for US GA (l4549 0:01)

EXAM: heading 360 + 'traffic ten o'clock two miles southbound' = left, converging (l4549 0:02)

▶ Watch this taught:

04

UNICOM, CTAF, Multicom 122.9 — and why your ears aren't a sensor you can trust

The quiet frequency doesn't mean an empty pattern - at untowered fields nobody HAS to say anything.

Position calls at untowered airports are optional: 'they should be making radio calls, but they don't have to' - so silence proves nothing; keep your eyes working. The channels: UNICOM is a person on the field (often weekends only) answering requests - active runway, wind, pattern count - with no control authority. CTAF is the self-announce channel, sometimes the same frequency as UNICOM, and at part-time towered fields the TOWER frequency becomes the CTAF after closing. No CTAF or UNICOM listed? The nationwide Multicom: 122.9. Flight Service Stations, the old briefing infrastructure, have been 'closing left and right' as services moved online.

Why it matters

For a drone pilot the operational takeaway is negative knowledge: radio silence never clears the pattern.

People get this wrong

If the CTAF is quiet, the pattern is empty.

Untowered radio calls are voluntary. Silence means only that nobody chose to talk - see-and-avoid stays fully on your eyes.

Go deeper

In one line: Untowered calls optional; UNICOM = human info service, no authority; CTAF = self-announce channel (may share UNICOM or after-hours tower freq); Multicom 122.9 when neither listed; FSS network shrinking.

Calls optional - never rely on hearing all traffic (l4550 0:00)

UNICOM: runway/wind/traffic on request, no control (l4551 0:00)

After-hours towered fields: tower freq becomes CTAF (l4551 0:01)

Multicom 122.9 as the no-frequency fallback (l4551 0:02)

FSS closures over 'the last five years' (l4551 0:01)

▶ Watch this taught:

05

The self-announce script — and towered readback

Every call opens AND closes with the airport's name - because the same frequency may serve airports sixty miles apart.

The worked pattern at 'Sedona' (fictional), Cessna 123 Bravo Foxtrot, runway niner: 'Sedona traffic, Cessna 123 Bravo Foxtrot, 10 miles south, inbound for landing, Sedona traffic' - then entering midfield left downwind, base, final, clear of runway, departing - all bracketed the same way. The double name exists because CTAF frequencies are shared regionally; you must know WHICH airport's pattern you're hearing.

Towered fields invert the flow: ATC directs ('enter left downwind runway niner', 'you're number two following the Piper on final') and pilots READ BACK each instruction verbatim - the readback is the confirmation layer. He recommends a cheap handheld scanner for field listening.

Why it matters

Recognizing where in this script a call sits tells you exactly where that aircraft is in the racetrack from section 4 - the two chapters are one skill.

Go deeper

In one line: Self-announce = [airport] traffic + callsign + position/intent + [airport] traffic, at 10-mile, pattern-entry, base, final, clear, departing; towered = ATC directive + verbatim readback.

Airport name at start AND end of every call (l4552 0:00-0:01)

Call sequence: 10-mile -> entry -> base -> final -> clear -> departing (l4552)

Shared CTAFs 50-60+ miles apart force the naming (l4552 0:00)

Towered: verbatim readback required (l4553 0:00)

Sequencing calls: 'number two following the Piper on final' (l4553 0:01)

▶ Watch this taught:

06

Finding the frequency: CT, the C suffix, and the AWOS decoy

The chart gives you three numbers near an airport - the exam graders know exactly which wrong one you'll grab.

Sectional decode: 'CT' precedes the control-tower frequency (Prescott: 125.3), a star means part-time; UNICOM appears separately (122.95 there - used for fuel and services). The Chart Supplement gives tower hours in Zulu and confirms the after-hours arrangement: tower closed, same 125.3 becomes the CTAF. Untowered fields mark CTAF with a 'C' suffix (his example 122.7 C). The exam's staged versions: Dallas Executive after-hours CTAF 127.25; Kirtland CTAF 122.8 sitting right next to an AWOS frequency on the same figure - the flagged trap being reading the weather station's number as the traffic frequency.

Why it matters

Chart-figure frequency questions are near-guaranteed - and the CT/C/AWOS discrimination is the entire difficulty.

Go deeper

In one line: CT = tower freq (star = part-time); C suffix = CTAF; after-hours tower freq becomes CTAF; UNICOM listed separately; never confuse the adjacent AWOS number for the CTAF.

CT 125.3 with star = part-time tower, Prescott example (l4554 0:00)

Tower hours in Zulu via Chart Supplement (l4554 0:01)

Closed tower -> its frequency IS the CTAF (l4554 0:01)

'C' suffix marks CTAF at untowered fields (l4554 0:02)

EXAM: AWOS beside CTAF on the figure - the classic decoy (l4555 0:01)

▶ Watch this taught:

Every concept, three clicks deep

The same concepts as a quick reference: the closed row is the glance, open is the study card, and every timestamp jumps into the recording.

01The listen-only rule and its single exceptionRemote pilots: listen always, transmit never (FCC licensing) - except to declare a genuine emergency.

Remote pilots: listen always, transmit never (FCC licensing) - except to declare a genuine emergency. Radio's purpose: ATC-pilot and pilot-pilot traffic coordination.

'Not allowed to transmit on aviation radio frequency' (l4547 0:02)

Emergency declaration is the one exemption (l4547 0:03)

Even licensed pilots without a station license can't transmit from the ground (l4547 0:02-0:03)

Optional FAA read: Radio Communication Phraseology and Techniques (l4547 0:01)

02Alpha to Zulu, 'tree' and 'niner', and the digit-by-digit lawICAO Alpha-Zulu;

ICAO Alpha-Zulu; 3='tree', 9='niner'; every figure digit-by-digit; 'point' for decimals; full altitude below 18,000, flight levels above; headings/speeds as digits.

Globally standard alphabet - same in France (l4548 0:00)

Only 3 and 9 change; zero is 'zero' (l4548 0:01)

EXAM: 4,500 = 'four thousand five hundred'; 10,500 = 'one zero thousand five hundred' (l4548 0:02)

Flight levels above 18,000: drop two zeros (l4548 0:02-0:03)

Heading 090 = 'zero niner zero' (l4548 0:03)

03Clock positions and call signs: who's where, and who's talkingClock positions relative to own heading;

Clock positions relative to own heading; call sign = November + tail number (full first, last-3 after); jets may use type, airlines use flight number.

Clock face rides the aircraft's nose, not the compass (l4549 0:00)

Full tail number first, then last-three abbreviation (l4549 0:01)

'November' prefix for US GA (l4549 0:01)

EXAM: heading 360 + 'traffic ten o'clock two miles southbound' = left, converging (l4549 0:02)

04UNICOM, CTAF, Multicom 122.9 — and why your ears aren't a sensor you can trustUntowered calls optional;

Untowered calls optional; UNICOM = human info service, no authority; CTAF = self-announce channel (may share UNICOM or after-hours tower freq); Multicom 122.9 when neither listed; FSS network shrinking.

Calls optional - never rely on hearing all traffic (l4550 0:00)

UNICOM: runway/wind/traffic on request, no control (l4551 0:00)

After-hours towered fields: tower freq becomes CTAF (l4551 0:01)

Multicom 122.9 as the no-frequency fallback (l4551 0:02)

FSS closures over 'the last five years' (l4551 0:01)

05The self-announce script — and towered readbackSelf-announce = [airport] traffic + callsign + position/intent + [airport] traffic, at 10-mile, pattern-ent…

Self-announce = [airport] traffic + callsign + position/intent + [airport] traffic, at 10-mile, pattern-entry, base, final, clear, departing; towered = ATC directive + verbatim readback.

Airport name at start AND end of every call (l4552 0:00-0:01)

Call sequence: 10-mile -> entry -> base -> final -> clear -> departing (l4552)

Shared CTAFs 50-60+ miles apart force the naming (l4552 0:00)

Towered: verbatim readback required (l4553 0:00)

Sequencing calls: 'number two following the Piper on final' (l4553 0:01)

06Finding the frequency: CT, the C suffix, and the AWOS decoyCT = tower freq (star = part-time);

CT = tower freq (star = part-time); C suffix = CTAF; after-hours tower freq becomes CTAF; UNICOM listed separately; never confuse the adjacent AWOS number for the CTAF.

CT 125.3 with star = part-time tower, Prescott example (l4554 0:00)

Tower hours in Zulu via Chart Supplement (l4554 0:01)

Closed tower -> its frequency IS the CTAF (l4554 0:01)

'C' suffix marks CTAF at untowered fields (l4554 0:02)

EXAM: AWOS beside CTAF on the figure - the classic decoy (l4555 0:01)

Tools referenced

ToolCoverageMomentContext
Chart SupplementdemonstratedTower hours + after-hours CTAF confirmation
LiveATC.netmentionedRecommended for live/archived listening practice worldwide
Pilot's Handbook of Aeronautical Knowledge (PHAK)mentionedChapter pages assigned for radio phraseology
Airman Certification Standards (ACS)mentionedArea 5 Task A mapping

Session materials

Archived locally on V: — click to open. Companion pages link to the LMS.

Action items

    Extraction notes

    This page was built from an auto-generated transcript, which garbles product and people's names. Those were corrected silently in everything above and logged here for transparency. The warnings flag claims that were true on the recording day but change fast.

    Transcript corrections applied

    The transcript saysThe trainer actually means
    the p-hackP-HAK - Pilot's Handbook of Aeronautical Knowledge
    live ATC netLiveATC.net
    Universal Integrated CommunityUNICOM = Universal Communications (FAA definition; instructor gloss or garble)
    (garbled gear-up anecdote text)non-recoverable ASR noise inside the flight-school story - disregard

    True on recording day — verify before relying