Air Traffic Control and Communication: Radar, Radios, Weather, and Procedures

7.7.1 Principles of Radar (How Radar “Sees” Aircraft)

Radar (radio detection and ranging) is a system that uses radio waves to detect objects and determine their direction and distance. In aviation, radar matters because controllers need a reliable way to know where aircraft are—even when visibility is poor or it’s night—so they can keep traffic safely separated and efficiently sequenced.

What radar measures (the two core outputs)

Radar fundamentally answers two questions:

1. How far away is the target? (Range)
   A radar transmitter sends out a burst (a pulse) of radio energy. If that energy hits an aircraft, a small portion reflects back to the radar antenna as an echo. The radar measures the time delay between transmission and return. Because radio waves travel at (approximately) the speed of light, longer delay means the target is farther away.

2. What direction is the target? (Azimuth/Bearing)
   Most surveillance radars use a rotating directional antenna. The antenna’s pointing direction at the moment the echo is received gives the bearing of the target from the radar site.

Primary vs. secondary radar (the big idea)

In aviation, you’ll often hear about primary surveillance radar (PSR) versus secondary surveillance radar (SSR):

• Primary radar detects aircraft by reflected energy—no equipment is required on the aircraft.
• Secondary radar relies on the aircraft carrying a transponder that replies to interrogation (covered in later sections).

Primary radar is valuable because it can detect “anything that reflects,” but that is also a drawback—weather, terrain, and buildings can create clutter.

What can degrade radar performance (and why that matters operationally)

Radar is not magic; it has limits that influence how ATC operates:

• Line-of-sight limitations: At low altitude or far from the radar, the Earth’s curvature and terrain can block returns.
• Clutter: Reflections from ground/sea/structures can mask aircraft, especially near the airport.
• Weather attenuation and scattering: Heavy precipitation can weaken signals or create noisy returns.
• Target characteristics: Small aircraft and aircraft aspect angle can affect how much energy reflects back.

Example (conceptual)

If an aircraft disappears from primary radar at low altitude on departure, the “problem” may not be the aircraft—it may be radar coverage (terrain masking) at that altitude and distance. Controllers may use procedural separation, different radar sources, or require higher climb before radar identification is reliable.

What commonly goes wrong in student understanding

A frequent misconception is assuming radar always provides altitude. Primary radar does not inherently provide altitude; altitude typically comes from aircraft transponders (Mode C/S) or other surveillance sources.

Exam Focus

• Typical question patterns:
  • Explain how radar determines range and bearing.
  • Compare primary vs secondary radar capabilities and limitations.
  • Identify why radar coverage may be limited near terrain or at low altitude.
• Common mistakes:
  • Saying radar “reads altitude” without mentioning transponder-derived altitude.
  • Ignoring line-of-sight constraints (treating radar like it works through mountains).
  • Confusing “radar sees everything” with “radar sees only aircraft.”

7.7.2 Components of Secondary Surveillance Radar (SSR)

Secondary Surveillance Radar (SSR) is a cooperative surveillance system—meaning the aircraft must participate. Instead of relying on weak reflections, the ground system sends an interrogation, and the aircraft’s transponder sends back a coded reply. This matters because replies are strong, information-rich (identity and altitude), and less affected by clutter than primary radar.

The main SSR building blocks (ground + air)

SSR is easiest to understand as a “question-and-answer” loop:

1. Interrogator (ground transmitter)
   The SSR ground station transmits an interrogation signal. Think of it as: “Aircraft out there—reply with your code (and maybe altitude).”

2. SSR Antenna system (ground)
   Often co-located with other radar antennas, the SSR antenna radiates interrogations and receives transponder replies. Antenna directionality and rotation help associate replies with bearing.

3. Transponder (aircraft equipment)
   The aircraft receives the interrogation and sends back a reply containing information such as an assigned identity code and, if equipped/selected, altitude.

4. Receiver/Decoder/Processor (ground electronics)
   The ground equipment decodes the replies and associates them with the antenna azimuth and timing to create a track.

5. ATC Display and tracking system
   The processed data is displayed to controllers (often integrated with tracking, conflict alerting, and flight plan data).

SSR “modes” (what kind of information is returned)

SSR is commonly described in terms of modes, which indicate what is being requested/returned:

• Mode A: returns an aircraft identity code (the “squawk”).
• Mode C: returns pressure altitude (from the aircraft’s altitude encoder) along with identity.
• Mode S: adds selective addressing (interrogating a specific aircraft), improved data capability, and supports advanced surveillance functions.

(Exact implementation details can vary by region, but the key learning point is: Mode A = identity, Mode C = altitude, Mode S = more advanced/selective data.)

Example (how SSR improves tower/approach work)

Two aircraft may be close together on the radar screen. Primary radar might show two similar “blips.” SSR can label them with different identity codes (and altitude readouts), helping controllers positively identify each target and maintain correct separation and sequencing.

What commonly goes wrong

Students often assume SSR works without aircraft equipment. It doesn’t—no working transponder (or not turned on) means no SSR target, even though the aircraft might still appear on primary radar.

Exam Focus

• Typical question patterns:
  • Identify the ground components vs the aircraft component in SSR.
  • Explain what information Mode A and Mode C provide.
  • Describe why SSR is generally cleaner than primary radar in clutter.
• Common mistakes:
  • Mixing up who “initiates” the exchange (ground interrogates; aircraft replies).
  • Claiming SSR can detect non-cooperative targets without a transponder.
  • Confusing Mode C altitude (pressure altitude) with indicated altitude corrected for local pressure.

7.7.3 Tower Control of Departures, Arrivals, and Ground Operations

An airport control tower manages traffic in the immediate vicinity of the airport—both in the air close to the field and on the movement areas (runways and taxiways). Tower control matters because most high-risk conflicts—runway incursions, wrong-surface landings, and takeoff/landing conflicts—happen close to the ground where reaction time is short.

What the tower is responsible for (big picture)

Tower responsibilities commonly include:

• Runway operations: issuing takeoff and landing clearances and ensuring runway separation.
• Traffic pattern management: coordinating aircraft in the circuit/pattern.
• Ground movement control: managing taxi routes, runway crossings, and apron/spot coordination (exact division can vary by airport).
• Coordination with approach/departure control: transferring control/communications as aircraft arrive/depart.

How tower control works (the basic workflow)

1. Build situational awareness
   Controllers integrate out-the-window observation, surface surveillance (where available), radio reports, and coordination calls.

2. Issue clearances and instructions
   A clearance is an authorization (for example, to take off). An instruction may be a required action (for example, “hold short”). Controllers use standardized phraseology to reduce ambiguity.

3. Maintain separation and prevent runway incursions
   Tower uses procedures and, where applicable, surveillance tools to ensure that only authorized aircraft/vehicles are on an active runway and that arriving/departing aircraft have required spacing.

4. Coordinate handoffs
   Arrivals are typically handed from approach control to tower; departures are handed from tower to departure/approach control after takeoff.

Example (departure from a controlled airport)

A typical sequence is:

• Clearance delivery (IFR clearance or VFR instructions, as applicable)
• Ground control taxi clearance to the runway holding point
• Tower takeoff clearance when runway and airspace conditions permit
• Tower hands the aircraft to departure/approach control after liftoff

What commonly goes wrong

A major operational risk is readback/hearback error—the pilot reads back something incorrect (wrong runway, wrong hold short point), and the controller fails to catch it. Another common issue is assuming “taxi to runway” includes crossing all runways; at many airports, runway crossings require specific authorization.

Exam Focus

• Typical question patterns:
  • Describe tower responsibilities for runway vs taxiway operations.
  • Explain why standard phraseology and readbacks are critical near the runway.
  • Analyze a runway incursion scenario and identify where the breakdown occurred.
• Common mistakes:
  • Treating tower as responsible for the entire region (confusing tower with approach/en route control).
  • Ignoring coordination/handoff steps between tower and approach.
  • Forgetting that ground operations are part of ATC safety, not just “logistics.”

7.7.4 Sequencing Approaches and Departures with Approach Control Radar

Approach control (often called terminal radar or TRACON in some systems) manages aircraft in the terminal area around one or more airports—sequencing arrivals, integrating departures, and setting aircraft up for instrument or visual approaches. This matters because airports are “funnels”: many aircraft converge into limited airspace and runway capacity, so careful sequencing prevents conflicts and reduces delays.

What “sequencing” really means

Sequencing is building an orderly arrival and departure flow so that:

• each arriving aircraft reaches the final approach in the correct order and spacing
• departures can climb out without conflicting with arrivals
• runway changes, wake turbulence categories, and speed differences are managed efficiently

Core tools approach control uses

1. Radar identification and tracking
   Approach uses surveillance (SSR/Mode S and sometimes primary) to track position and altitude.

2. Vectors
   A radar vector is a heading instruction issued to guide an aircraft onto a desired path (for downwind/base/final, to intercept an approach course, or to provide spacing).

3. Speed control
   Controllers may request specific speeds (when operationally appropriate) to fine-tune spacing—especially when mixing fast jets and slower turboprops.

4. Vertical management
   Controllers assign altitudes to keep aircraft separated and to set up for descent profiles into the approach.

5. Holding and flow restrictions
   When demand exceeds capacity, aircraft may be placed in holding patterns or delayed through metering programs (exact mechanisms vary).

Example (building an arrival sequence)

Imagine three arrivals inbound to the same runway:

• Aircraft A is fast and high.
• Aircraft B is slower and already lower.
• Aircraft C is between them.

Approach may vector Aircraft A onto a longer downwind and reduce its speed, allowing B to proceed more directly. C may be turned to follow B with a planned spacing. The key is that approach control is continuously balancing lateral path length, speed, and altitude to create a stable final approach stream.

What commonly goes wrong

A common misconception is that radar sequencing is “just turning airplanes.” In reality, effective sequencing is 3D problem-solving—heading + altitude + speed, constrained by aircraft performance and approach procedures. Another frequent error is forgetting wake turbulence implications: heavier aircraft can require increased spacing behind them (spacing rules are authority-specific, but the operational concept is universal).

Exam Focus

• Typical question patterns:
  • Describe how approach control uses vectors, speed, and altitude to sequence traffic.
  • Explain the difference between tower sequencing (runway vicinity) and approach sequencing (terminal area).
  • Interpret a simple radar-sequencing scenario and choose the best controller action.
• Common mistakes:
  • Ignoring speed differences (assuming all aircraft can “fit” the same spacing).
  • Forgetting departures must be integrated with arrivals (runway is shared capacity).
  • Confusing “cleared for approach” with “cleared to land” (tower issues landing clearance).

7.7.5 Interpreting Weather for Departures and Arrivals

Weather interpretation is a safety-critical ATC and airport management skill because weather directly drives runway selection, approach availability, traffic rates, and go/no-go decisions. Poor weather can increase separation needs, reduce visibility on the surface, and force instrument procedures.

The weather elements that most affect operations

1. Wind (direction and speed)
   Wind influences runway choice because aircraft prefer taking off and landing into the wind to reduce groundspeed and required distance. Crosswinds and tailwinds can exceed aircraft or runway limits.

2. Visibility and runway visual range (RVR)
   Low visibility impacts whether visual operations are possible and whether an instrument approach can be used to the required minima (minima depend on the specific approach and rules in use).

3. Ceiling (cloud base height)
   A low ceiling affects whether pilots can maintain visual separation and whether instrument approaches are required.

4. Precipitation and thunderstorms
   Heavy rain can reduce visibility and braking action; thunderstorms bring wind shear, microbursts, lightning risk to ramp personnel, and significant tactical reroutes.

5. Icing and freezing levels
   Icing conditions affect climb/descent performance and can drive deicing operations, delays, and altered runway/taxiway use.

6. Altimeter setting / pressure
   Pressure affects indicated altitude and aircraft performance calculations; it also matters because transponder Mode C reports pressure altitude, which systems convert using local settings.

Common aviation weather products you’re expected to interpret

• METAR: a routine surface observation (wind, visibility, weather, clouds, temperature/dew point, pressure).
• TAF: a terminal forecast describing expected conditions over a period.
• PIREPs: pilot reports, especially helpful for turbulence, icing, and cloud tops.
• Radar/satellite products: used to assess precipitation intensity and storm movement.

(Exact formatting and codes can differ slightly by state system, but the operational interpretation skills are similar.)

Example (operational interpretation)

If the wind shifts significantly, the airport may switch runways. That change triggers a cascade: arrival routes and approach procedures change, departure routes change, taxi flows change, and controllers must resequence traffic. Understanding weather isn’t just “reading a report”—it’s anticipating operational consequences.

What commonly goes wrong

Students sometimes treat visibility and ceiling as interchangeable. They’re different: you can have good visibility below a low overcast (good visibility, low ceiling) or poor visibility with a high ceiling (haze/fog). Both can restrict operations, but in different ways.

Exam Focus

• Typical question patterns:
  • Given a weather scenario, predict impacts on runway selection and arrival/departure rates.
  • Interpret basic METAR/TAF elements (wind, visibility, ceiling, significant weather).
  • Explain how thunderstorms/wind shear change ATC strategies.
• Common mistakes:
  • Choosing a runway based on convenience instead of wind and operational constraints.
  • Confusing ceiling with visibility (or assuming one implies the other).
  • Ignoring surface impacts like braking action and ramp lightning procedures.

7.7.6 VHF and UHF Radio Bands and How to Access Them

Aircraft communicate with ATC primarily by radio. Two key frequency ranges are VHF (Very High Frequency) and UHF (Ultra High Frequency).

Definitions (frequency ranges)

• VHF generally refers to frequencies from $30\,\text{MHz}$ to $300\,\text{MHz}$.
• UHF generally refers to frequencies from $300\,\text{MHz}$ to $3000\,\text{MHz}$.

In civil aviation, most routine voice communications use the VHF aeronautical band (commonly in the 118–137 MHz region, depending on national allocation). UHF voice communications are widely used in military aviation (commonly in the 225–400 MHz region). Exact allocations are set by national/International telecommunications and aviation authorities.

Why frequency band matters

The band affects:

• Range and line-of-sight behavior (both VHF and UHF are largely line-of-sight)
• Antenna size/design
• Who you can talk to (civil vs military networks, and what facilities are equipped)

How you “access” ATC frequencies (what the pilot/controller actually does)

From a user perspective, “accessing” a frequency means selecting it correctly and transmitting properly:

1. Tune the frequency
   Aircraft radios typically have an active frequency (what you’re listening/transmitting on) and a standby frequency (preselected). Swapping standby to active is a standard workflow to reduce workload.

2. Select the correct radio (COM1/COM2)
   Many aircraft have multiple radios. You must transmit on the radio tied to the selected frequency you intend to use.

3. Monitor before transmitting
   Good practice is to listen to ensure you don’t “step on” another transmission.

4. Use push-to-talk (PTT) correctly
   Press-and-hold while speaking; release to listen. A partially stuck microphone can block the frequency for everyone.

Example (handoff)

After departure, tower instructs “contact departure” on a new frequency. You tune departure in standby, brief-check you copied it correctly, then swap it active at the appropriate time and make initial contact.

What commonly goes wrong

A classic error is tuning the right frequency but transmitting on the wrong radio—or having the right radio selected but with volume/squelch mis-set, leading to “lost comm” that isn’t truly a failure.

Exam Focus

• Typical question patterns:
  • Define VHF vs UHF and relate them to typical aviation users.
  • Explain why VHF/UHF communications are largely line-of-sight.
  • Describe the steps to correctly change frequencies during a handoff.
• Common mistakes:
  • Treating VHF and UHF as “long-range like HF” (they’re not; they’re mainly line-of-sight).
  • Forgetting active vs standby workflow (leading to missed calls).
  • Blaming ATC for lost comm when the wrong radio is selected or volume is down.

7.7.7 Radio Communication, Phraseology, and Light Signals

ATC communications are designed to be standardized and unambiguous—because unclear language causes real accidents. Phraseology matters as much as technology: even with perfect radios and radar, misunderstandings can create runway incursions and loss of separation.

What good radio communication looks like

Effective ATC/pilot communication follows a predictable structure:

• Who you are calling (facility name)
• Who you are (callsign)
• Where you are (position) and/or what you want/are doing
• Key details (altitude, ATIS code, runway, request)

Standard phraseology reduces the chance that two people interpret the same words differently.

Readbacks and hearbacks (the safety loop)

Many critical items require a readback by the pilot and a hearback by the controller (the controller must actively confirm it was read back correctly). Typical “critical items” include:

• runway assignments and hold short instructions
• takeoff and landing clearances
• heading/altitude/speed instructions
• clearances and restrictions that affect separation

A common failure chain is: controller issues instruction → pilot mishears → pilot reads back incorrectly → controller doesn’t notice → conflict occurs.

Light gun signals (when radios fail)

If radio communication is not possible (or as a backup), towers can use a signal light (often called a light gun) to communicate with aircraft or vehicles.

Typical meanings (commonly taught in many systems) include:

Because exact wording can vary slightly across regulatory publications, the high-level point is: green = go/clearance, red = stop/unsafe, and alternating colors = caution—and you must know the official meanings for the ruleset you operate under.

Example (standard phraseology benefit)

If a controller says “hold short runway two-seven,” that has a precise meaning: stop before the runway holding position marking. If instead casual language is used (“wait there a second”), the pilot may stop in the wrong place—especially at complex intersections.

What commonly goes wrong

Students sometimes overfocus on sounding “natural.” In aviation, sounding natural is less important than being precise and predictable. Another common error is forgetting to include the callsign in readbacks, which increases the risk of another aircraft acting on the clearance.

Exam Focus

• Typical question patterns:
  • Identify why standardized phraseology and readbacks prevent runway incursions.
  • Interpret a short radio transcript and spot the communication breakdown.
  • Match light gun signals to the correct instruction.
• Common mistakes:
  • Omitting callsign or key readback items (runway/altitude/heading).
  • Assuming “cleared” applies broadly (clearances are specific).
  • Mixing up flashing vs steady light meanings (especially on the ground).

7.7.8 Function of Transponders

A transponder is an aircraft radio device that responds to SSR interrogations by transmitting a coded reply. Transponders matter because they allow ATC to reliably identify and track aircraft, associate a radar track with a flight, and (when enabled) receive altitude information.

What a transponder does (step by step)

1. Receives interrogation from SSR ground equipment.
2. Processes the request (what mode is being interrogated).
3. Transmits a reply containing requested data.

This “active reply” is why SSR targets are typically stronger and clearer than primary radar returns.

Key transponder functions you should know

• Identity code (squawk): a code assigned by ATC (or selected per procedures) that helps identify the aircraft.
• Altitude reporting: when enabled, the aircraft transmits pressure altitude (commonly associated with Mode C or Mode S capability).
• IDENT feature: when the pilot activates IDENT, the aircraft’s target is highlighted on the controller’s display temporarily, helping identification.

Operational importance

Transponders support:

• Positive identification (matching a target to a known aircraft)
• Altitude monitoring (detecting level-offs and deviations)
• Safety nets (many modern ATC systems use transponder-derived tracking for conflict alerts)

Example (why IDENT is useful)

If a controller sees multiple targets near a fix, they may ask one aircraft to “IDENT.” The highlighted response helps ensure the controller is talking to the correct aircraft before issuing a vector or altitude instruction.

What commonly goes wrong

Pilots sometimes forget to select the appropriate transponder mode (for example, altitude reporting not enabled), leading to a target with no altitude readout—this can increase controller workload and may reduce available services in some airspace.

Exam Focus

• Typical question patterns:
  • Explain how a transponder enables SSR tracking versus primary radar.
  • Describe what information is provided by identity code vs altitude reporting.
  • Explain the purpose of the IDENT function.
• Common mistakes:
  • Treating the transponder as a “GPS tracker” (its core function is replying to interrogation).
  • Confusing pressure altitude reporting with local altimeter-indicated altitude.
  • Forgetting that if the transponder is off/malfunctioning, ATC may have reduced identification capability.

7.7.9 Causes of Lost Communication and Lost Communication Procedures

Lost communication (lost comm) occurs when two-way radio communication between aircraft and ATC cannot be established or maintained. It’s a major safety concern because ATC separation depends on knowing what the pilot intends to do—and because other aircraft may be relying on predictable behavior from the NORDO (no radio) aircraft.

Common causes of lost communication

Not all “lost comm” events are equipment failures; many are human or configuration errors:

• Incorrect frequency (mis-copied, mis-tuned, or wrong active/standby swap)
• Wrong radio selected (COM1 vs COM2 transmit selection)
• Volume/squelch/headset issues (you may transmit but not hear, or vice versa)
• Stuck microphone (hot mic) blocking the frequency for everyone
• Electrical failure affecting radios or audio panel
• Antenna/coax damage reducing transmit/receive capability
• ATC facility coverage issues (terrain shielding at low altitude)

A practical first step is always to suspect the simple things—wrong frequency, wrong box selected—before assuming full radio failure.

Immediate pilot actions (general best practice)

Procedures are defined by the governing aviation authority and can differ by airspace and flight rules (VFR vs IFR), but the common building blocks are:

1. Troubleshoot quickly
   Check volume, headset, audio panel, circuit breakers (as appropriate), correct frequency, and radio selection.

2. Try alternate frequencies
   Contact the last facility on another published frequency if available; try the next expected facility frequency.

3. Use emergency/guard frequency
   Many systems use an emergency frequency monitored by ATC and other aircraft (for example, $121.5\,\text{MHz}$ is widely used as a civil VHF emergency/guard frequency).

4. Use transponder codes and features
   Squawking a standard lost-communications code (commonly $7600$ in many systems) alerts ATC that you may be NORDO.

5. Seek relay
   Another aircraft can relay messages between you and ATC.

6. Use light signals
   If approaching a towered airport, look for light gun signals.

What to do if you are VFR vs IFR (conceptual)

• If VFR: The overarching goal is to remain in visual meteorological conditions (VMC), keep clear of conflicts, and land as soon as practical at an appropriate airport while following local rules.
• If IFR: The goal is to behave predictably so ATC can protect airspace around your expected route and altitude. Many training syllabi teach mnemonics to remember route and altitude priorities; the exact rule wording depends on the authority, but the concept is: follow the most recently assigned/expected routing and maintain an altitude that is both authorized and safe (including obstacle clearance), then proceed to a suitable approach and land.

Example (why predictability is everything)

If ATC clears you “direct ABC, then as filed,” and you lose communications, the safest system-level behavior is usually to fly what ATC last authorized (and what ATC will assume you are flying). If you improvise a shortcut without being told, ATC cannot reliably protect other traffic from you.

What commonly goes wrong

A dangerous misconception is: “If comm fails, do whatever seems best.” In controlled airspace, improvisation can create conflicts. The right mindset is: be predictable, follow published/regulatory lost-comm procedures, and use all available signaling methods (transponder, light signals, relays).

Exam Focus

• Typical question patterns:
  • Identify likely causes of lost comm and distinguish equipment failure from setup error.
  • Describe a logical lost-comm troubleshooting sequence.
  • Explain how transponder code $7600$ and tower light signals fit into lost-comm management.
• Common mistakes:
  • Skipping basic checks (audio panel/radio selection) and declaring an emergency prematurely.
  • Forgetting to use guard/emergency frequency or to attempt relay.
  • Acting unpredictably under IFR instead of following the applicable published rules.