How to handle a visual approach to a non-active runway under Radar SOPs.

Outline

• Opening: A pilot asks for a visual approach to KGWO, but not to the active runway. The main rule: coordination plus APREQ for the specified runway.

• Why it matters: Safety, predictability, and orderly traffic flow. The active runway sets the pattern; a non-active runway request can ripple through the system if not handled properly.

• What APREQ is and how it works: Approved Visual Approach, the formal mechanism that moves the request from a pilot to the controllers in the loop. It clarifies runway choice, routing, and sequencing.

• The step-by-step protocol: acknowledge, coordinate with the right people, issue APREQ, confirm runway and traffic, monitor, and log.

• Why not just instruct or deny: both options miss the core requirement—coordination and documented intent.

• A practical scenario: a concrete, plausible sequence of events at KGWO to illustrate the flow.

• Practical tips for smooth handling: concise comms, correct phraseology, and keeping everyone in the loop.

• Common pitfalls to avoid: assumptions, misinterpreting “visual approach,” and forgetting to file the APREQ.

• Wrap-up: the safety and efficiency payoff of following the coordination process.

Article: When a visual approach request lands on KGWO’s radar, there’s a simple, important rule that keeps skies safer and traffic moving: coordinate and file an APREQ for the specified runway. It sounds straightforward, but it’s the kind of thing that separates a calm hand on the controls from a near-mumble of confusion in the cockpit and the cabin. Let me walk you through why this matters, what APREQ is, and how the whole moment should unfold.

Why this matters in the real world

Imagine you’re at a busy airport. The active runway is where most arrivals come in, touch down, and roll out. The traffic pattern—the rhythm of inbound streams, departure vectors, and sequencing—has grown used to a particular flow. Now, a pilot points to a different runway and says, “Visual approach to runway X.” The pilot is signaling a desire for a visually guided arrival, but the runway they’re aiming for isn’t the one currently intended for instrument approaches or sequencing. Without proper coordination, you risk misalignment: conflicting patterns, missed separation, and a scramble to reshuffle arrivals midstream. Not ideal, right? The smart move is to pause, coordinate, and document. That’s where the APREQ comes in.

What APREQ is and why it matters

APREQ stands for Approved Visual Approach. It’s the formal mechanism that allows pilots to request a visual approach to a specific runway, while ATC confirms that it’s safe and feasible given current traffic and weather. It’s not just a formality; it’s a shared understanding. The controller who receives the APREQ can convey intent to the tower and other units, confirm runway usage, and set expectations for sequencing. It helps keep the airport’s traffic flow clear and predictable.

Here’s the thing: the active runway is the backbone of the arrival pattern. If someone asks for a visual approach to a non-active runway, you need to pause the current flow long enough to verify that this alternate path won’t disrupt established procedures. APREQ provides that safety net. It signals “we’re temporarily adjusting the plan,” not “we’ll wing it.” That clarity matters for everyone on the ground and in the air.

A practical, step-by-step way to handle the request

1. Acknowledge and assess. When the pilot asks for a visual approach to a non-active runway, acknowledge the request promptly. A quick, calm readback helps. Something like: “Roger, visual approach requested to Runway X. Stand by while we coordinate.” You’re not saying yes or no yet—you’re buying a moment to verify.

2. Initiate coordination with the right people. This is where you loop in the necessary players: approach control, the control tower, and, if required, the supervising facility or the appropriate authority. The goal is to make sure everyone who touches the landing sequence knows about the request and can weigh in on feasibility given current arrivals and the weather.

3. File and communicate the APREQ. The APREQ is the official mechanism to document the visual approach to the specified runway. It’s a cue to all involved that a non-standard path is being considered and that a coordinated plan has to be in place before the approach proceeds. This isn’t a hurry-up tactic; it’s a safety brake that ensures proper separation and alignment.

4. Confirm runway and traffic conditions. Once the coordination is complete, confirm: the runway in use, current wind, and the traffic picture around KGWO. If conditions or patterns have shifted, you’ll need to adjust. The pilot should know which runway is intended for the approach and what the expected sequencing looks like.

5. Issue the approach clearance and any clarifications. After the APREQ is in place and the runway is confirmed, issue the appropriate clearance or guidance. If the visual approach to the specified runway is approved, clearly state the terms: the runway, the expected path, and any altitude or speed constraints necessary to maintain safe spacing.

6. Monitor and adapt. As the aircraft executes the approach, continuously monitor the traffic picture. If others shift or if weather changes, be ready to adapt. Documentation matters here too—the record should reflect that the APREQ was approved and the coordination occurred, so future decisions can reference what happened.

7. Debrief and log. After the aircraft lands, capture the outcome: did the pilot actually follow the visual approach to the specified runway? Were there any deviations? What, if any, follow-up coordination is needed? A brief debrief helps keep the system sharp for the next request.

Why instructing to follow standard procedures or denying a request isn’t the right move here

In this scenario, simply instructing the aircraft to follow standard procedures or denying the request doesn’t meet the core requirement: coordination and proactive communication. Standard procedures exist for a reason, but they don’t account for an unusual request that targets a non-active runway. Denying without coordinating can create confusion, while pushing ahead with standard patterns can disrupt other traffic and jeopardize safety. The correct approach—coordinate and file an APREQ—ensures everyone’s on the same page and that the airspace stays orderly.

A quick, real-world-minded example

Let’s paint a plausible moment at KGWO. A flight asks for a visual approach to Runway 27, but Runway 33 is the runway in use for arrivals. You pause, contact Approach and Tower, and initiate an APREQ for the Runway 27 visual approach. Approach confirms there’s a safe gap in the arrivals’ sequence, and Tower says Runway 27 is available for a visual approach under calm winds. With everyone in the loop and the APREQ filed, you guide the aircraft to join the airspace and proceed with the air traffic plan. The result is a smooth, safe arrival without ruffling the feathers of the other flights already in the pattern. It feels almost routine, but that routine is built on precise coordination and clear, documented intent.

Tips for smooth handling in the field

• Keep comms concise and precise. Short phrases, clear intent, and a calm tone help avoid miscommunication.

• Use the standard phraseology when possible, but adapt to the local language and the radar room’s defaults. Consistency reduces mistakes.

• Always confirm the runway and traffic picture before approving the APREQ. If there’s doubt, ask for a quick update rather than assuming.

• Document the coordination. The APREQ isn’t just a checkbox; it’s part of the official record. A good log helps with future decisions and safety audits.

• Remember the difference between a visual approach and other visual/infrared or contact-type approaches. Visual is about the pilot’s ability to see and avoid, while maintaining separation and following the plan in coordination with ATC.

Common missteps to watch for

• Assuming a non-active runway request can be slipped into the existing pattern without coordination. It can create conflict if other traffic isn’t aware.

• Confusing “visual approach” with a “contact approach.” They’re different tools with different conditions and coordination needs.

• Skipping the APREQ step or failing to log the coordination. Without the APREQ, you lack a formal record of what was approved and why.

A final thought on the flow

Radar SOPs aren’t about red tape for red tape’s sake. They’re about keeping skies safer and decisions clear. When a pilot asks for a visual approach to a runway that isn’t active, the right move isn’t to rubber-stamp a request or to shut it down outright. It’s to bring everyone into the loop, formalize the plan with an APREQ, and then carry the approach with confidence. The outcome—less ambiguity, better spacing, smoother arrivals—benefits the whole operation, from the cockpit to the tower to the ground crews.

If you find these moments fascinating, you’re not alone. The magic—and the pressure—of air traffic control lives in those precise micro-decisions that keep flights safe and on time. The next time you hear a pilot request a visual approach to a non-active runway, you’ll recognize the same careful choreography: acknowledge, coordinate, file the APREQ, confirm, and proceed with a plan that everyone can trust.

Bottom line: Make coordination and APREQ for the specified runway. It’s the clear path to safety and efficiency when the unexpected request lands on KGWO’s radar.