Unable, the One Word That Hands Control Back to the Pilot, and Why Saying It on the Radio Is Never Rude

Saying “unable” to air traffic control is not rude, unprofessional, or a sign of a weak pilot. It is standard phraseology that tells a controller you cannot safely or legally comply with an instruction, and under Federal Aviation Regulation 91.3 you are the pilot in command with final authority over your aircraft. A good controller hears “unable” and simply builds you a new plan.

Why “Unable” Matters More Than Any Other Radio Word

Most pilots - especially students - will do almost anything a controller asks. Turn for spacing, keep the speed up, follow traffic they can’t see yet. In a new pilot’s head, the voice on the radio is the boss.

It isn’t. The controller is not the pilot in command. You are.

We hand a student that authority on paper, then train them, mostly by accident, to give it right back to the first calm voice on the frequency. We teach compliance so hard we forget to teach refusal. Refusal, said the right way, is a safety tool.

What Does “Unable” Actually Mean in Aviation?

“Unable” is standard phraseology found in the Pilot/Controller Glossary. It means I cannot comply with that instruction. It is the correct, expected, professional response when a controller asks you to do something you can’t safely or legally do.

It is not the same as “no thanks” or “I’d rather not.” When you say “unable,” you are giving the controller accurate information about what your airplane can and cannot do. The moment they hear it, they build a new plan.

When Should I Tell ATC “Unable”? Three Real Scenarios

Scenario 1: A Speed You Can’t Make

You’re eight miles out, descending into a busy Class Charlie airport in a Cessna. Approach says, “maintain 170 knots to the marker.” Your airplane wide open barely does 120 knots.

You say: “Unable 170, we can give you 115 knots.” That’s the whole transmission. The controller was sequencing you behind a regional jet and guessed at your speed. Now they know the real number - they’ll slow the jet, turn you out, or run you in behind. Their problem to solve, and you just handed them the number to solve it.

Compare that to the pilot who hears 170 and thinks I’ll try. They firewall the throttle in a descent, blow through approach speed, and arrive hot, high, and fast, wrestling a stabilized approach they don’t have. Polite got them into a corner. “Unable” would have kept them out of it.

Scenario 2: An Altitude That Puts a VFR Pilot in the Clouds

Night flight. You’re VFR-only, no instrument rating, and a broken layer is moving in that you didn’t love on the briefing. Tower says level at 3,500 feet - right in the base of the clouds. This is where get-home-itis and please-the-controller line up and shove you into conditions you’re not rated or current for.

You say: “Unable, I need to stay VFR. I can accept no higher than 2,800 feet.” If that doesn’t work, use the other magic words - “request” or “I’d like to divert” - and take yourself somewhere with better weather and a longer drive. Nobody ever died of a long drive.

On your checkride, the examiner is looking for exactly this. They aren’t testing whether you’ll obey the imaginary controller - they’re testing your aeronautical decision making. The Airman Certification Standards spell this out under the risk management and communication tasks. Declining an unsafe clearance with standard phraseology isn’t failing the test. It’s passing it.

Scenario 3: A Taxi Clearance You Only Half-Caught

You’re taxiing at an unfamiliar field. Ground rattles off a string of taxiways and a hold-short, and you catch about half of it. The polite pilot reads back something confident and wrong, then starts rolling.

Don’t be that pilot. Key up and say “say again,” or “unable to copy all of that, request progressive taxi.” Progressive taxi means the controller walks you turn by turn across the airport. Controllers would rather give you ten progressive instructions than clean up one runway incursion. You asking for help is the easiest part of their day.

What Must I Always Read Back to ATC?

Some instructions carry a mandatory readback, and hold-short instructions are at the top of that list. If a controller says “hold short of runway 27,” you say the words back - “hold short runway 27” - plus your call sign.

If you didn’t understand it, don’t guess. Say “say again.” If you can’t accept it - you’re already rolling and can’t stop in time - say “unable” and tell them what you can do. Guessing on a hold-short instruction is how two airplanes end up on one runway. Never guess near runways.

Won’t I Sound Like an Amateur If I Say “Unable”?

Here’s the truth from the other side of the glass. Controllers are not grading your radio work. They are moving metal safely through their airspace, and to do that they need accurate information about what your airplane will and won’t do.

A pilot who says “unable 170” is giving them gold. A pilot who says “wilco” and then can’t deliver is handing them a surprise at the worst possible moment. The pilots who sound the most professional are almost always the ones comfortable saying “unable,” “request,” and “say again.” Real radio confidence isn’t machine-gunning a clearance back - it’s knowing your limits and your airplane’s limits and defending them out loud without apology.

How Do I Build the Confidence to Say “Unable”?

Knowing it and doing it are two different animals. Four steps to build the muscle before you need it:

1. Rehearse silently. On your next flight, for every clearance you accept, ask yourself: Could I say no to this? What would I say instead? The word shouldn’t be a stranger the first time you need it for real.

2. Know your real numbers cold. Your actual best climb rate on a hot day, not the book number on a standard day. Your realistic approach speed. The slowest you can safely fly clean and dirty. “Unable” is only useful when you can follow it with the truth.

3. Practice the trade. Almost every “unable” comes with an offer: Unable that heading, I can give you a right turn. Unable that altitude, I can accept 3,000. Unable to hold short in time, I can exit at the next taxiway. That offer tells the controller you’re a teammate, not a roadblock.

4. Give yourself permission to disappoint a stranger. The reason pilots don’t say “unable” isn’t a knowledge gap - everyone knows 91.3. It’s a social gap. We don’t want the sigh on the frequency. Let that go. Nobody in that radio is going to fly your airplane when it all goes quiet.

The Regulation Behind It All

FAR 91.3 is short and blunt: the pilot in command is directly responsible for, and is the final authority as to, the operation of that aircraft. Those are the exact words the FAA chose.

The second half goes further: in an in-flight emergency requiring immediate action, the pilot in command may deviate from any rule to the extent required to meet that emergency. That is an enormous amount of authority sitting in your lap every time you strap in.

Saying “unable” isn’t rebellion. It’s the system working exactly the way the FAA designed it - the pilot in command as final authority, giving the controller honest information so the two of you can build a plan that keeps the airplane safe.

Key Takeaways

• “Unable” is standard phraseology, not an insult - it tells ATC you can’t safely or legally comply, and they’ll build you a new plan.
• FAR 91.3 makes you the final authority over your aircraft and lets you deviate from any rule in an emergency.
• Always pair “unable” with an offer - the speed, altitude, or heading you can accept - so your refusal becomes a solution.
• Hold-short instructions require a full readback; if you didn’t catch it, say “say again,” and never guess near runways.
• Declining an unsafe clearance passes the checkride - examiners want to see aeronautical decision making, not blind compliance.