Picture a controller in a darkened radar room, watching a single aircraft cross her screen. For the last twenty minutes it’s been hers. She’s kept it clear of the traffic around it, guided it through a band of weather, and held it steady on course. Now it’s approaching the edge of her airspace, the invisible line where her sector ends and the next one begins. Beyond that line she can’t help the aircraft. Her radio will not reach it, her radar will hand off to someone else’s screen, and the pilots will soon be talking to a controller she may never meet.
There’s a precise thing she does at that boundary, and a precise thing she doesn’t do. She doesn’t simply stop talking and let the aircraft drift across the line, trusting that it will be fine. And she does not try to fly it all the way down to a runway that was never hers to manage. What she does is make the handoff. She calls the next sector, confirms they see the aircraft, and passes on what they need to know: altitude, heading, intentions, anything unusual she has been watching. Only when the next controller has positive contact, only when they’ve acknowledged that the aircraft is now theirs, does she tell the pilots to switch frequencies. Then, and only then, does she let go.
That moment holds a whole discipline inside it. The handoff is not the afterthought at the end of the real work. It is the work. And there are two ways to get it wrong, both of them quiet, both of them dangerous. You can drop it: go silent at the boundary and assume the system will catch what you release. Or you can hold on too long: decide that because the aircraft was yours, it’s yours to land, and fly it into someone else’s airport. One leaves the thing unattended. The other puts it where it does not belong. A good controller does neither.
Noticing isn’t the finish
You may never sit in a radar room, but if your work puts you anywhere near other people’s problems, you cross these boundaries all the time. You see something. Sometimes you can handle it yourself, start to finish, and you should. But often the thing you’ve noticed is bigger than the reason you came, or it belongs to someone with a different skill, a different mandate, a different relationship with the person in front of you. That is the edge of your sector. It is the point where the most useful thing you can do is no longer to act, but to pass.
And there’s a version of all of us that does the hard part well and then fumbles the easy part. We do the careful work of seeing. We even name the thing plainly. And then we stop, and let it drift across the line, and assume someone downstream will pick it up. Usually no one does. The observation was real, the person was interested, and it still went nowhere, because the moment that mattered was the handoff and the handoff never happened.
The two ways a handoff fails
It’s worth being precise about the two failures, because they feel like opposites and they are really the same mistake wearing different clothes.
The first is dropping it. You saw something, you may even have mentioned it, and then you moved on, trusting the system to route it. But the system does not know it exists. There’s no flight plan, no next controller, no one holding the thing you set down. It simply sits at the boundary until it’s forgotten.
The second is holding on too long. Because you were the one who saw it, you decide it’s yours to finish. You start doing work that’s not yours: scoping the solution, quoting the price, promising a timeline you can’t actually control. It feels like ownership and initiative. It’s really the thing that causes the collision, because you are now flying an aircraft toward a runway you do not manage, cut off from the people who do.
A clean handoff has three parts
Between those two failures sits the move, and it has three parts.
First, confirm the other person wants it passed. Ask the person in front of you whether this is worth taking further. “Would it help if I got the right person to look at this properly?” You are testing interest, not assuming it. Sometimes the answer is yes, please; sometimes it’s we know, it’s handled. Both are fine, and both are theirs to give.
Second, pass on what the next person needs. Tell them what you saw in enough detail that they can act without starting from nothing. Altitude, heading, intentions. A handoff that arrives as a vague “there might be something over there” is barely better than silence.
Third, confirm positive contact before you let go. Do not release the thing into the void and hope. Make sure a specific person has it and knows it’s now theirs, and tell the person you have been helping who will follow up and roughly when. The handoff isn’t complete the moment you speak. It’s complete when someone on the other side has acknowledged the catch.
The restraint is the point
Here’s the part that’s easy to miss. A controller’s authority comes partly from what she refuses to do. She will not fly the plane to the ground, because that is not her job, and pretending it is would make everyone less safe. That same restraint is what makes you trustworthy at a handoff. If you notice something and immediately try to own the whole thing, the person starts to wonder what you are really after. If you notice it, name it plainly, and then say, “this is bigger than what I came here to do, let me get it to the person who can actually help,” you have done something rare. You have put their interest ahead of your grip on the moment.
Handing off is a form of trust, not a loss of it
There is a fear underneath all of this: that handing something off means losing it. Losing the credit, the relationship, the control. In a well-run system the opposite is true. The pilots trust the controller more, not less, because she passed them cleanly to the next set of safe hands. Guiding someone to the right person, and making sure they land well, is not giving them away. It is the last and most generous thing you do while they are still yours. And it compounds: the people who do this well become the ones everyone else routes things through, precisely because they can be trusted to pass things on without dropping them and without hoarding them.
So the next time you see something sitting at the edge of your sector, remember the controller at the boundary. Do not go quiet and hope. Don’t try to fly it to a runway that is not yours. Make the call, confirm that someone has it, tell the person you have been helping who takes it from here, and then, cleanly, let go.
Questions to Consider
- When did you last notice something bigger than your role and let it drift across the line, trusting someone would catch it? Did they?
- Where are you more tempted: to drop a handoff, or to hold on too long and do work that was never yours?
- How do you confirm positive contact before you let go, so that a specific person actually has it, rather than releasing it into the void?
- What would change in how people trust you if you became known as the one who always passes things to the right hands and never drops them?
- Is there something sitting at the edge of your sector right now that someone is still quietly waiting for?
