How to manage comm, nav, and ATC

VIII.F evaluates how the pilot maintains the instrument scan while simultaneously communicating with ATC and using radio navigation aids (GPS, VOR). The maneuver simulates the most common real-world VFR-into-IMC scenario — the pilot has lost visual reference and is asking ATC for help while flying solely by instruments. The skill is workload management: the scan can't drop while the radio is in use.

The scan is the priority. If the choice is between completing a radio transmission and maintaining the scan, the scan wins. ATC will repeat themselves; the airplane won't recover its own altitude.

Setup

1. Begin from a stable straight-and-level (VIII.A baseline).
2. Brief the simulated scenario: what's the current heading, altitude, position? What's the target (destination, alternate)?
3. Verify radio setup: frequencies pre-loaded if possible (active + standby), GPS active waypoint correct, VOR tuned and identified.
4. Pre-brief radio calls mentally if heavy comm is expected — knowing what you're going to say reduces in-flight cognitive load.

Protect the scan during comm

The scan is the default state. Comm tasks insert without replacing it.

While the radio is in use:

1. Glance at the AI before keying the mic — confirm attitude is stable.
2. Transmit in a short, scripted format.
3. Return to the scan immediately — AI, primary instruments cycle.
4. Listen for the response while continuing the scan.

The temptation is to focus on the radio call until it's complete; this drops the scan for 5–15 seconds. The discipline: the scan continues during transmissions.

Communicate effectively

ATC communication under instruments follows the standard format:

• Whom you're calling (e.g., "Center" or "Approach").
• Who you are (callsign).
• Where you are (position).
• What you want (request).

Example: "Approach, Cessna 12345, 10 miles south, 3,000 feet, requesting flight following."

For unusual situations (VFR-into-IMC):

• Declare the situation: "Cessna 12345, VFR-into-IMC, request vectors to VMC."
• Listen carefully to vectors and altitude assignments.
• Read back assignments.

Use navigation effectively

GPS and VOR provide situational awareness — current position, distance to next fix, course guidance.

Under hood:

• GPS use is typically through the moving map and active flight plan. Glance to confirm position, track, distance, ETA.
• VOR use requires identifying the station (Morse code), setting the course, tracking the CDI.
• Automation (autopilot, if equipped) reduces cockpit workload during comm — but only if the pilot trusts and verifies the automation's behavior.

The maneuver tests effective use of these tools while the scan continues. A pilot who fumbles with the GPS for 30 seconds while losing altitude has failed the scan-protection standard even if the GPS interaction is successful.

Demonstrate the integrated skill

VIII.F.S2 specifies "effective use of automation while maintaining instrument scan." The integrated skill is:

1. Initiate the comm or nav task with a stable airplane.
2. Execute the task in short, brisk increments.
3. Return to the scan between increments.
4. Verify the task completion + airplane status periodically.

Example: setting up a new GPS waypoint:

• Scan check (AI, altimeter, ASI, HI) → stable.
• 2 seconds of GPS interaction → enter the waypoint identifier letter.
• Scan check → stable.
• 2 seconds of GPS interaction → next letter.
• Scan check → stable.
• ...

Better to take 30 seconds with five scan checks than 10 seconds without any. The standard is the maintenance of flight, not the speed of the secondary task.

Common pitfall: heads-down on automation. The GPS or autopilot interface is engaging — touch screens, menus, confirmation prompts. A pilot who's deep in the menu for 20 seconds may have the airplane drifting outside tolerances when they look up. Cycle the scan; don't extend the menu interaction without scan checks.