What should a controller do when an aircraft approaches without a strip?

Radar SOPs: When an aircraft shows up without a strip, what should the controller do?

Let me set the scene. In radar operations, a strip isn’t just a tidy piece of paper or a screen blip. It’s a quick, trusted snapshot of an aircraft’s position, altitude, speed, and intent. When a plane approaches without one, the concern isn’t “how quickly can I file the form?”—it’s “how safe is this close encounter, and what do I need to know right now to keep everyone on the ground and in the air out of trouble?” Here’s the thing: the right move is to contact the aircraft and clarify its position. Not because you enjoy a procedural scramble, but because direct communication buys calm, clarity, and control when the airspace gets crowded.

Why talking first beats guessing later

If a strip is missing, you don’t have the full picture. A strip might be out of date, or a plane could be maneuvering in ways not yet reflected on your screen. The quickest path to safety is to connect with the aircraft and gather fresh information. This isn’t about playing a hunch; it’s about establishing a direct line to confirm critical details such as where the aircraft is, how high it is, how fast it’s flying, and what its current intentions are.

Think of it like this: you’re a conductor guiding a busy orchestra. The score in your head is accurate, but if a musician wanders onstage without their cue, you pause, speak up, and confirm their position and plan before you hand out the next baton. In radar control, the “cue” is altitude, position, and heading; the “musician” is the airplane. Clear, direct contact helps you synchronize the next steps without letting miscommunication ripple through the rest of the airspace.

What to say and what to listen for

Calling the aircraft is about precise, calm communication. Here’s a practical approach you can adapt on the fly:

• Establish contact quickly. Use standard radio procedures to identify the aircraft if you can, then state your position and ask for its position relative to known fixes or intersections.

• Gather key data. Ask for current altitude, price of altitude changes (are they climbing, descending, or level?), airspeed, heading, and any flight plan status they can share. If you know their last reported information, refer to it as a baseline and request an update.

• Clarify intentions. Are they inbound for a fix, a different runway, or an alternate destination? Do they require priority because of an emergency, or are they simply missing a strip and seeking situational awareness?

• Confirm, don’t assume. Have them read back their altitude and heading if any doubt remains. Verbal confirmation reduces the chance of misinterpretation.

• Plan next steps together. Once you have a clear picture, you can issue instructions that fit the current situation and the broader traffic picture.

Now, a quick note on the alternatives you’ll hear in the cockpit

• Ignore the aircraft until a strip is available. Tempting as it may sound in a busy moment, this is a poor choice. It creates a safety gap, increases uncertainty, and can lead to miscoordination with other traffic. It’s the kind of move that invites mistakes when the radar picture doesn’t tell the full story.

• Advise the aircraft to hold until a strip is available. Holding without understanding why can stall flow, risk sequencing for landings and departures, and push the problem onto the aircraft rather than solving it on the ground. Let the pilot know what you know, and why you’re asking for more information.

• Post an emergency strip immediately. Emergencies are serious and require swift, decisive action, but you don’t jump to this step unless you’ve confirmed distress signals or an imminent threat. In most cases, establishing contact first will reveal whether an emergency strip is truly needed, or if a normal correctional path exists.

The handful of steps that turn confusion into control

Here’s a practical sequence that keeps the flow smooth and the aircraft safe:

• Establish contact and identify the aircraft. If you can positively identify the call sign, that’s a good sign you’re in the right lane.

• Confirm position. Ask for current position relative to a known point or fix. If you can see the aircraft on your radar, ask for its reported position rather than assuming it’s where it last appeared.

• Verify altitude and speed. A mismatch between assumed altitude and actual altitude can be dangerous, especially in crowded airspace.

• Gather flight plan status. If you know the route, ask if there have been any last-minute changes or filed intentions you should be aware of.

• Issue necessary guidance. Depending on what you learn, you might assign altitude or heading changes to keep traffic safely spaced, or authorize speed adjustments to slow or speed up the sequence.

• Keep the strip status current. If you can recreate or update the strip from the data you’ve gathered, do it. If not, note the missing strip in your internal log and prepare for the next information update.

A touch of realism from the field

Let me explain with a quick analogy. Imagine a busy highway at dusk. Cars appear on the radar of the traffic system, but one car comes up the ramp without a license plate or a clear speedometer readout. The right move isn’t to ignore it or wave it through; it’s to reach out via radio, confirm the vehicle’s speed, direction, and intent, and then adjust the flow of adjacent cars so you don’t cause a pileup. You keep the road moving, with eyes on every blip, and a plan that can adapt in real time. That’s the essence of handling an incoming aircraft without a strip.

Common pitfalls—and how to sidestep them

• Don’t assume you know the aircraft’s position just because it looked close on your scope. The aircraft could be shifting, climbing, or descending in ways your screen doesn’t immediately reflect.

• Don’t broadcast unnecessary information. You want to be clear and concise, giving the pilot only what they need to know to stay safe and move efficiently.

• Don’t delay contact while you hunt for data in old notes or stale strips. The priority is safety, not paperwork. Use live conversation to fill the gaps.

• Don’t forget to coordinate. If the approach path intersects with other traffic, loop in the relevant sectors so you maintain a safe, smooth flow of aircraft.

Practical tips for real-world operators

• Practice crisp, standard radio calls. You don’t have to sound robotic, but consistency matters. A clear, repeatable pattern helps pilots understand what’s expected.

• Leverage all displays and data sources. If you have primary radar and secondary radar, use both to build a robust picture. If you can, cross-check altitude and speed with other systems.

• Keep your preferred phraseology handy, but adapt it to the moment. If the airspace is tight, you’ll use shorter phrases. If the situation allows, you can be a touch more explanatory to reduce ambiguity.

• Document the incident. A quick note about the missing strip, the contact attempts, and the outcome helps with post-event review and future response.

• Learn from near-misses. Even a close call with no strip should become a learning point: what was known, what wasn’t, and how the team could improve the information loop next time.

A broader perspective: safety is a team sport

Radar control isn’t a solo act. It’s a chorus of pilots, dispatchers, and air traffic professionals who weave a shared safety fabric. When a plane shows up without a strip, the best move is a calm, confident dialogue that brings everyone into the same moment. In that moment, you are not just issuing directions; you’re managing risk, preserving sequencing, and protecting lives.

If you’re new to this, you might wonder how often such situations arise. They aren’t daily headlines, but they do happen—especially in busy airspace or during transition periods. The key takeaway is simple: prompt, clear contact with the aircraft provides the most reliable path to safety and orderly movement. It reduces uncertainty, supports accurate traffic management, and keeps the operation from spiraling into confusion.

Closing thoughts: the core idea in one sentence

When an aircraft approaches without a strip, the safe, effective move is to reach out, identify the aircraft, and clarify its position and intent before making any other decisions.

If you’re curious about how this plays out in different regions or airspace structures, you’ll find that the same principle holds: direct communication first, data gathering second, and coordinated action third. The radar picture may change with every blip, but the map you rely on—clear contact, verified position, and a shared plan—stays constant.

So next time you’re at the radar scope and a plane arrives with no strip in sight, remember the human element at the heart of every decision. A quick call, a careful question, and a grounded plan can turn a tense moment into a controlled flow of safe, predictable air traffic. And that’s the quiet victory of good radar management.