The Word Unable, the Most Powerful Word on the Radio, and Saying No to a Controller Who Just Told You to Do Something You Can't on the Way Into Oshkosh

The word “unable” is the single most powerful tool in a pilot’s radio vocabulary. Under 14 CFR 91.123, you must comply with ATC clearances and instructions - but that same regulation states that if an amended clearance is one the pilot cannot comply with, or an emergency requires it, the pilot in command is not required to comply. When a controller gives you an instruction you cannot safely accept, saying “unable” isn’t rude or weak; it’s the most professional call you can make.

Is the Radio a Chain of Command?

No. It feels like one - the controller has a calm, certain voice, and you’re a student with sweaty palms and a kneeboard sliding off your leg. But that is not how the system works.

Read 14 CFR 91.123. When you operate in controlled airspace under ATC, you comply with clearances and instructions. But the same regulation carves out the exception in the same breath: if a pilot is given priority by an emergency, or if an amended clearance is one the pilot cannot comply with, the pilot in command is not required to comply. In an in-flight emergency requiring immediate action, the PIC may deviate from any rule to the extent required to meet that emergency.

Translated out of legal language: you are always the pilot in command. The controller is a partner - a very good one - but the airplane is yours and the final call is yours.

Why Is “Roger” So Dangerous?

When you key up and say “roger,” you’ve told the controller three things at once: message received, I understand, I will comply. The controller then builds their entire picture on top of that promise. They turn the next airplane behind you. They clear someone onto the runway. They stop watching you as a problem because you told them you were handled.

So when you say “roger” to something you can’t actually do, you haven’t avoided a conflict - you’ve hidden one. And you’ve hidden it from the one person who could have helped you fix it.

“Unable” does the opposite. It hands the problem back into the system while there is still time and airspace to solve it.

How Do I Say No to a Controller Who Gives Me a Bad Heading?

Scenario: You’re inbound to a Class Charlie airport. Approach is busy and says: “Cessna 172SW, turn left heading 360, descend and maintain 2,500, expedite through 3,000 for traffic.”

You’re already at 2,600 - the descent is no problem. But that left turn to 360 points you straight at a Bravo shelf, a tower, or a cloud deck you’ve been carefully staying under. You’re VFR. You cannot enter that cloud. Period.

The trap: the instruction came fast, came with authority, and most of it was fine. The temptation is to swallow the whole thing and sort it out later. Don’t.

Instead, key up: “Approach, 172SW is unable that heading, VFR, I’ve got a cloud deck to the north. I can give you 330.”

That’s the gold standard: Unable. Because. Alternative. You said no, handed them the reason, and offered a solution. The checkride examiner is looking for exactly this - not blind compliance, but positive aircraft control and sound aeronautical decision making.

What If I Can’t See the Traffic I’m Told to Follow?

Scenario (Oshkosh, AirVenture week): You’re on the Fisk arrival into Wittman Regional Airport, flying it by the NOTAM - 90 knots, 1,800 feet, following the railroad tracks. The controller says: “Blue high-wing, good rock, enter a right base for runway 36, follow the yellow Cub, keep your speed up.”

But you look, and there is no yellow Cub in your windshield. They want you to follow traffic you don’t have and turn a base behind it - into the busiest runway in the world.

This is the exact moment a well-meaning pilot says “roger, 36” and turns anyway, into airspace where he can’t see the airplane he’s supposed to be spacing off of. That is how mid-airs happen.

Say it: “Negative contact on the Cub, unable the base, I’ll keep it coming straight ahead.”

Yes, the Oshkosh arrival is a listen-only, minimize-the-chatter operation - but listen-only does not mean comply with something unsafe. It means keep the frequency clean for the normal case. When you genuinely can’t do the thing, a short “negative contact, unable” is worth every bit of airtime it costs. You are never required to fly a spacing instruction against an airplane you don’t have in sight.

What If a Descent Puts Me Too Close to Terrain?

Scenario: You’re being vectored - for practice approaches or sequencing - and get “maintain 3,000.” But you’re over rising terrain, it’s night, and you know 3,000 puts you uncomfortably close to a ridge line out there in the dark.

On a visual or VFR flight following, the responsibility for terrain is yours. It always has been.

“Unable 3,000, I need 4,500 for terrain.” You don’t owe anyone an apology for staying alive. If the ground proximity is screaming, you don’t even need permission - 91.123 lets you deviate to the extent required in an emergency. Climb first, then tell them what you did as soon as you can. Aviate, navigate, communicate - in that order, every time.

How Do I Actually Say “Unable” Under Pressure?

Knowing you should say it and being able to spit it out at a heart rate of 160 are two different animals. Three habits build the reflex:

1. Break the “roger” reflex. Many of us learned to say “roger” just to fill silence, because silence felt like failure. Kill that habit. A two-second pause while you think is fine. “Standby” is a complete sentence. “Say again” is a complete sentence. And “unable” is a complete sentence.

2. Use the formula: Unable. Because. Alternative. Say the word, give the reason in about four words, offer what you can do. “Unable that descent, VFR under a Bravo shelf, I can hold this altitude.” Short, clean, solvable. Controllers love a pilot who hands them a fix instead of a puzzle.

3. Chair-fly it on the ground. Sit in your car or at the kitchen table and run the scenario, saying the word out loud. The first time you use a word should never be the moment terrain is out the window. Make “unable” as automatic as your call sign.

How Do I Know When It’s Really an “Unable”?

Here’s the line that separates students from certificated pilots: “unable” is about capability and safety, not comfort. There’s a difference between “I cannot safely do this” and “I would prefer not to.”

A controller asking you to keep your speed up on final at Oshkosh when you’re stabilized and comfortable? That’s not an unable - that’s just the show. Do it.

But a controller asking you to fly into a cloud, follow traffic you can’t see, descend into terrain, or bust your own personal minimums? That is an unable, every single time. Learning to feel the line between inconvenient and unsafe is the whole ballgame. That judgment is what the certificate actually certifies.

And if saying it feels scary - like talking back to a teacher - reframe it. The controller isn’t grading you; they’re a professional trying to keep a lot of aluminum out of the same cubic foot of air. A confused, compliant pilot is a hazard. A clear, honest pilot who says “unable” is a partner. Be the partner.

Key Takeaways

• “Unable” is your right and your responsibility under 14 CFR 91.123 - the pilot in command is not required to comply with a clearance they cannot safely accept.
• “Roger” makes three promises (received, understood, will comply); saying it to something you can’t do hides a conflict instead of solving it.
• Use the formula every time: Unable. Because. Alternative. - say no, give the reason, offer what you can do.
• You are never required to follow traffic you can’t see or descend into terrain; on a visual or flight following, terrain avoidance is yours.
• Distinguish unsafe from merely inconvenient - “unable” is for capability and safety, not comfort.