Handbook

UA.V.A.K8

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

UA.V.A.K8: Phraseology: altitudes, directions, speed, and time.

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


Key Concepts

Establishing Two-Way Communications and What to Say

  • Before entering Class C airspace, establish two-way radio communication with the ATC facility and maintain it while inside. Your initial call should efficiently provide position, altitude, radar beacon code, destination, and a request for Class C services. If ATC replies with your callsign followed by “standby,” communications are established; if ATC replies without using your callsign, they are not established and you may not enter. If workload prevents services, ATC may instruct you to remain outside until they can accommodate you. The Class C “Outer Area” is normally 20 NM from the primary airport and is procedural, not charted. Plan calls far enough out to avoid infringing the boundary without authorization[6].
  • When operating on VHF, note that aviation radios use 118.0–136.975 MHz and are typically “720” or “760” channel sets with 25 kHz spacing (e.g., 118.025, 118.050). VHF is line-of-sight—higher altitude yields greater range—so anticipate terrain/structure shadowing near the surface[1].
  • En route, ATC centers (ARTCCs) use sector “discrete” frequencies. Expect frequency changes as you progress through sectors; reserve these frequencies for control-related use, and obtain weather/flight data via FSS, company radio, or other appropriate facilities[4].

Altitude, Direction, and Speed in Clearances and Procedures

  • When departing a traffic pattern, continue straight out or exit with a 45° turn beyond the departure end of the runway—left turn in left traffic, right turn in right traffic—after reaching pattern altitude. Do not continue on a track that would penetrate the departure path of a parallel runway. Clear, concise transmissions about departure intentions help deconflict traffic (“departing straight-out,” “departing with a 45° left turn”) and align with pattern-direction expectations[1].
  • Obstacle Departure Procedures (ODPs) may publish crossing altitudes and speed restrictions. These are for obstacle clearance and/or design constraints and cannot be canceled or amended by ATC. Expect to read back and comply precisely; do not negotiate these values on frequency[4].
  • RNAV SIDs and graphic ODPs are RNAV 1, requiring total system error not more than 1 NM for 95% of total flight time. This performance expectation underpins how tightly you must adhere to assigned headings/paths and speed/altitude constraints when these procedures are in use[4].

Time and Distance Terminology You’ll Hear and Use

  • Expect Further Clearance (EFC) time and Estimated Time of Arrival (ETA) are core timing references. If you lose communications and your clearance limit is an initial approach fix, begin the descent/approach as close as possible to the EFC time if received; otherwise, as close as possible to ETA computed from your filed or ATC-amended ETE. If the clearance limit is not an approach fix, proceed to one and commence descent/approach using the same EFC-or-ETA logic[5].
  • For GPS RAIM-dependent operations, verify RAIM availability for the intended route and time during preflight. If a continuous loss of RAIM of more than five (5) minutes is predicted for any part of the flight, delay, cancel, or reroute. When relying on certain receivers, check non-precision approach RAIM at airports spaced at intervals not to exceed 60 NM along the RNAV 1 track, ensuring “Terminal” or “Approach” RAIM will be available at ETA[2].
  • Oceanic RNP planning uses specific distance and time qualifiers: RNP 10 based on a single LRNS currently applies to the Gulf of Mexico; unless otherwise approved, the basic RNP 10 time limit is 6.2 hours between position updates when only INS/IRU provide long-range navigation. RNP 10 or RNP 4 eligibility permits 50 NM lateral separation when properly annotated on the ICAO flight plan (Item 10 “R” and Item 18 “PBN/A1” for RNP10 or “PBN/L1” for RNP4)[7].
  • Some special operations embed explicit distance/time safety thresholds you may need to recognize or brief on frequency. Example: helicopter hot refueling should not be conducted when electrical storms are within 10 NM, and radio transmissions should be avoided during fueling to reduce ignition hazards[8]. Potential hazards at heliports/helidecks are disseminated via NOTAMs; timely notification supports safe decision-making and clear advisory broadcasts[3].

Lost-Communications Phraseology and Actions

  • If you lose two-way communications, set your transponder to Mode A/3, Code 7600. Attempt to reestablish contact on the last assigned frequency, with an FSS or ARINC, and monitor NAVAID voice features. Using 121.5 MHz is permissible. If FSS/ARINC contact is made, report position, altitude, last assigned frequency, and request further clearance from the controlling facility[5].

Test Yourself

UA.V.A.K8

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