After a missed approach, write 'MA' under the approach name and keep the strip.

Outline (skeleton)

• Hook: a missed approach is a tense moment, but the right move is straightforward and radio-clear.

• The core rule: after a missed approach, write “MA” under the approach name and do not remove the flight progress strip.

• Why this matters: documentation, shared situational awareness, and clean sequencing with other traffic.

• What the other options imply and why they’re not enough by themselves.

• How the MA notation fits into the bigger SOP picture: steps for controllers, pilots, and the team.

• Quick practical takeaways and a touch of real-world texture to keep the topic human.

• Close with a reminder: small notes, big safety impact.

What happens when a missed approach takes place

Let’s set the scene. You’re watching the radar, you’re listening for a go-ahead, and suddenly the approach doesn’t end with a landing. Maybe the weather spins its own little weather tango, or the aircraft decides to go around for safety. Either way, a missed approach isn’t just a single moment; it’s a signal to reset the plan, confirm options, and keep everyone in the loop.

The one action that keeps the TIC (traffic information center) aligned is this: write “MA” under the approach name on the flight progress strip and do not remove the strip. That tiny notation is doing a lot of heavy lifting.

Why the MA notation on the strip is the right move

• A clear historical marker: It creates a precise record that this aircraft attempted an approach but did not land. This matters for later reviews, for reconstructing events, and for understanding how the airspace was managed during that window.

• Shared situational awareness: Controllers at the tower, approach, and en route centers all refer to the same, unambiguous signal. The MA tag flags the need to re-sequence, re-clear, or coordinate for another option without guessing what happened.

• Safe sequencing and spacing: Once a missed approach is noted, you’ll decide how to slot in the aircraft again—whether that means another approach, a hold, or a different routing. The MA mark helps you plan and communicate that flow without confusion.

• A dependable protocol: SOPs are built on repeatable, simple steps. The MA notation is a standard tool that every controller recognizes. No one has to second-guess what’s happened or what’s next; the strip tells the story in real time.

What the other choices imply, and why they miss the mark

• Remove the strip immediately (A): If you wipe away the strip, you erase the visible trace of what happened. It’s like erasing a page from a flight log. Not only does that hinder accountability, it also muddies the timeline for anyone who needs to review the sequence of events. In high-stakes airspace, you want a clear, auditable trail, not a clean slate.

• Record the missed time (C): Time-stamping is useful, but it’s not enough by itself. The flight progress strip carries the operational context: which approach was in progress, what the clearance was, and how the controller team is coordinating. Time alone doesn’t communicate the status or the required next steps.

• Notify the supervisor about the missed approach (D): Communication channels are essential, sure. But notifying a supervisor is not a substitute for the live, standardized documentation that keeps the entire sector aligned. The MA notation on the strip is immediate, visible, and actionable for the entire team; a separate report later can be redundant or forgotten in the rush of traffic management.

How the MA notation fits into a living SOP

Think of the flight progress strip as a running, shared diary of what’s happening in the airspace. After a missed approach, the MA mark serves as a headline for that aircraft’s next moves. Here’s how it typically flows:

• Immediate next steps: The controller evaluates options—another instrument approach, a circling maneuver, or a hold. The MA tag signals, “We’re not done here; plan for the next clearance.”

• Coordination: The MA note prompts quick, targeted coordination with the pilot and with other units that might be affected—sector controllers, arrival procedures, or tower staff. It’s not just a bureaucratic mark; it’s a live cue to adjust spacing and sequencing.

• Documentation continuity: The strip stays in view, with MA as a standing flag, until the aircraft reaches a safe, stable state or is cleared for a new approach. This continuity helps minimize miscommunications and preserves a coherent thread for post-event review.

• Human factors at play: In a busy controller environment, small cues matter. MA is short, unambiguous, and easy to spot at a glance. It reduces cognitive load during a moment when attention is already stretched.

A practical snapshot of the moment

Here’s a simple, human way to picture it. The aircraft is on final for Runway 22. Winds shift, visibility changes, and the go-around is executed. On the strip, you don’t erase the moment you didn’t land; you annotate it. You write MA under the approach name, something like “RWY22 MA,” and you keep the strip in view. Then you move on to the next clearance—perhaps a new approach, perhaps a hold—guided by the MA flag. Everyone in the loop sees the same signal, and the next steps unfold with fewer delays or misinterpretations.

A note on timing and teamwork

Missed approaches aren’t just about the flight path; they’re about timing and teamwork. The MA notation helps ensure that:

• The pilot receives a clear, immediate cue that the original approach has not resulted in a landing, and that another path is being pursued.

• Other aircraft in the same airspace don’t inadvertently receive conflicting instructions or late updates because the status of the first aircraft is not clearly reflected.

• The control team can maintain safe separation while the aircraft figures out its new plan, keeping the overall flow of traffic smooth and predictable.

Keeping the human touch in methodical procedures

It’s tempting to see SOPs as a cold checklist, but the truth is they’re about people working together under pressure. The MA notation is a tiny token that supports trust and clarity. It’s a shared language that seconds into minutes, saves confusion, and keeps safety front and center.

Tips you can carry into real-life operations

• Be vigilant about the strip’s status. If a missed approach occurs, maintain the MA tag until the aircraft is cleared for a subsequent action.

• Avoid the temptation to erase or overwrite the strip in a hurry. A clean, readable log is worth its weight in efficiency when things calm down.

• Communicate clearly with the pilot. If the next move is another approach, specify the type, the runway, and any changes in altitude or speed that matter.

• Coordinate early with adjacent sectors. A missed approach can ripple through airspace, so share the plan promptly to prevent conflicting instructions.

• When in doubt, rely on the established protocol. SOPs exist because they work under pressure and spots where human judgment can wander off path.

A final thought

Missed approaches are part of flight operations, not a failure of skill. The key is how you document and communicate what happened. The MA notation on the flight progress strip isn’t flashy, but it is indispensable. It builds a reliable timeline, supports clear handoffs, and keeps the whole team oriented toward safety and efficiency.

If you’re new to the world of radar SOPs, you’ll notice one recurring theme: small actions done consistently matter a lot. Writing MA under the approach name and leaving the strip in place is one of those small actions that carries big weight. It’s a practical, plain-language rule that helps the airspace work as a single, coordinated system.

So next time you watch a missed approach unfold, think of that strip and the MA mark. It’s the quiet hinge that unlocks the next phase of safe and orderly traffic management. And if you ever wonder what moves you from confusion to clarity, this is a good place to start: a moment of precise notation that keeps the whole sky in view, one line at a time.