Handbook

UA.V.A.K2

OperationsRadio Communications ProceduresUA.V.A.K2
Exam Weight: 35-45%
Refs: AC 107-2; AIM; FAA-H-8083-25; FAA-G-8082-22

UA.V.A.K2: The description and use of a Common Traffic Advisory Frequency (CTAF) to monitor manned

ACS Area V — Operations Task A: Radio Communications Procedures References: AC 107-2; AIM; FAA-H-8083-25; FAA-G-8082-22


Key Concepts

Purpose of CTAF and Why Remote Pilots Monitor It

At airports without control towers, pilots use a designated advisory frequency (CTAF) to coordinate. IFR aircraft switch to this frequency when approved by ATC and follow recommended traffic advisory procedures. This frequency often controls pilot-activated runway lighting. Monitoring CTAF helps remote pilots stay aware of manned traffic around the runway, which is crucial for avoiding conflicts. Ground vehicles with radios also monitor CTAF to maintain safety and avoid active runways/taxiways, enhancing situational awareness near the airport surface. [1]

ATC may provide "traffic advisories" when workload permits, but pilots must still see and avoid other aircraft. In CTAF environments, there is no controller, so monitoring is essential but not a substitute for visual scanning and maintaining a safe distance from the traffic pattern. [4]

What You’ll Hear on CTAF: Standard Self-Announce Calls

Understanding typical CTAF calls helps interpret manned aircraft intentions:

  • Initial inbound report: About 10 miles from the airport, pilots report altitude, aircraft type, position, landing or overflight intentions, and request wind and runway information if needed. [1]
  • Pattern position reports: Announcements for downwind, base, and final legs help build the traffic picture. [1]
  • Runway clear: A call made after exiting the runway. [1]
  • Outbound calls: Include initial taxi advisory, departure announcement with runway, and whether the pilot will remain in or depart the pattern. [1]

Standard phrases like “10 miles southeast descending through [altitude] landing [airport]; request wind/runway,” “entering downwind/base/final for Runway [number],” “clear of Runway [number],” and “departing Runway [number], remaining in the pattern/departing to the [direction]” help discern traffic flow, runway use, and potential conflicts with planned operations near the airport. [1]

Practical Monitoring Tips for Remote Pilots

  • Know the band: Aviation VHF radios operate on 118.0 to 136.975 MHz with 0.025 MHz spacing. They are line-of-sight, so higher altitude aircraft can be heard from farther away than those at lower altitudes or on the surface. [2]
  • Distinguish tower/ground from CTAF: At towered fields, ground control uses 121.6–121.9 MHz for surface communications, not CTAF. Ensure you have the correct advisory frequency for nontowered fields, and monitor the tower/local control frequency at towered fields if needed and lawful. [3]
  • Expect IFR traffic on CTAF: IFR pilots switch to CTAF when cleared by ATC and follow self-announce patterns, introducing instrument arrivals into VFR sequences. Continuous listening is crucial when operating nearby. [1]
  • Anticipate other users: Ground vehicles monitoring CTAF can alert you to runway closures, back-taxi operations, or other surface hazards affecting flight paths or runway selection. [1]
  • Limitations of advisories: Even with ATC involvement elsewhere, not all traffic may be called. On CTAF, there is no controller, so use radio monitoring to complement visual deconfliction and maintain a conservative distance from traffic patterns and approach/departure paths. [4]

By understanding CTAF self-announcing, VHF bands, and the roles of IFR aircraft and ground vehicles, remote pilots can better predict manned aircraft movements and keep small UAS clear of runways, taxiways, and flight paths at and around airports.

Test Yourself

UA.V.A.K2

No practice questions are currently available for this specific knowledge element.