The Unable Call, the ATC Instruction Every Student Is Afraid to Refuse, and the PIC Authority That Means Nothing If You Never Use It
Learn when and how to tell ATC 'unable' - the two-word radio call that FAR 91.3 and the AIM are specifically designed to support.
Most student pilots rehearse clearance readbacks until they are automatic. The fear is freezing on frequency. But the more common, more dangerous problem is reading back a clearance you cannot or should not comply with - and then executing it anyway, hoping for the best.
FAR 91.3 establishes that the pilot in command is directly responsible for, and the final authority on, the operation of an aircraft. The Aeronautical Information Manual (AIM) makes the practical implication explicit: when a pilot receives an ATC instruction they cannot safely comply with, the pilot is expected to say so. The word the system uses is “unable.”
Why Do Student Pilots Avoid Saying Unable?
Compliance is drilled from day one. Readbacks are verbatim. Transmissions are short. Instructions from controllers are followed promptly and professionally. That framework is correct the overwhelming majority of the time - controllers are professionals who understand the airspace, and coordination keeps runways clear and aircraft separated.
The unintended side effect is that students sometimes internalize a false belief: that saying no to ATC is wrong, that the controller knows what your airplane can do, and that pushing back on frequency makes you the problem.
None of that is true. A controller’s radar shows a target. It does not show your pilot’s operating handbook (POH), your personal minimums, or the cloud tops at your three o’clock. The pilot is the only instrument in the system with that information. If you do not transmit it, the system runs on bad data.
When Is “Unable” the Right Call?
There are three main categories where “unable” applies:
Performance-based unable. You are inbound on a windy afternoon. Approach clears you to land runway 14. You run your crosswind numbers: 22 knots of crosswind component. Your C172’s demonstrated crosswind component is 15 knots per the POH. Your personal minimums card says 12 knots.
The call: “Approach, Skyhawk niner-two-four Foxtrot Whiskey, unable runway one-four due crosswind, requesting runway two-eight.”
You said what you cannot do, why you cannot do it, and what you can do instead. In nearly every case the controller responds: “Roger, runway two-eight, cleared to land.” The exchange takes fifteen seconds.
Performance-based unable also covers altitude assignments. If an assigned altitude puts you uncomfortably close to terrain in mountainous areas, say so. If a clearance places you in known icing conditions and your aircraft has no anti-ice equipment, say so.
Weather-based unable. You are VFR at 4,500 feet. Approach asks you to descend to 3,000 for traffic sequencing. You look ahead: 3,000 drops you into cloud tops. You cannot determine whether it clears or goes solid. Descending into those clouds is illegal for a VFR pilot and dangerous for any pilot not prepared for IMC.
The call: “Approach, Cessna four-five-niner Tango Alpha, unable three thousand, IMC at that altitude, maintaining four thousand five hundred.”
The controller cannot see that cloud layer on scope. You can. This is precisely why PIREPs (pilot weather reports) exist. When you say unable due to IMC, you are handing the controller information they need and cannot otherwise obtain. The same logic applies to turbulence severe enough to compromise aircraft control, or any developing condition that changes what your airplane can safely handle.
Operational uncertainty on the ground. You are at an unfamiliar airport. Ground issues a taxi clearance with two turns, a hold-short, a runway crossing, and a continuation to the runup area. You caught most of it. You are not fully certain about the crossing instruction.
Do not move the airplane.
FAA runway incursion data shows a consistent pattern: a significant percentage of incursions involve a pilot who was not confident in a taxi clearance but moved anyway, because they did not want to admit uncertainty on frequency. The readback gave the controller confidence. The confidence was not warranted.
The call: “Ground, Cessna four-five-niner Tango Alpha, I’m unfamiliar with the field, request progressive taxi.”
Progressive taxi is a published ATC service. Controllers use it with airline crews at unfamiliar airports, in low visibility, any time a pilot asks. It costs nothing. Getting a runway crossing wrong on an active taxiway costs everything.
How Do You Structure the Unable Call?
Three parts:
- Who you are calling and who you are (if you are initiating the exchange)
- The word “unable” and the specific instruction you cannot execute
- An alternative, if you have one
“Approach, Cessna four-five-niner Tango Alpha, unable descent to three thousand due IMC, requesting maintain four thousand five hundred.”
No apology. No lengthy explanation. When you include an alternative, the controller can resolve the issue in one more transmission. When you do not have an alternative, “unable” alone is still a complete call. Give the controller something to work with whenever possible.
What About “Say Again” and “Verify”?
These calls live in the same neighborhood as “unable” and exist for the same reason.
“Say again” means you need the controller to repeat a transmission you did not fully copy. If you caught an altitude assignment but are unsure whether it was 3,000 or 13,000, you say “say again altitude.” The controller repeats it. Done.
“Verify” is used when you believe you understood correctly but want confirmation. “Verify altitude assignment three thousand.” The controller confirms or corrects. This is especially useful when you are not confident your own readback was accurate.
None of these calls - unable, say again, verify - are admissions of failure. They are the radio vocabulary the system was built for. When pilots stop using them out of embarrassment, ATC starts operating on bad information. A controller who gets a “say again” is not frustrated; they are grateful. The alternative is a pilot executing the wrong clearance, which is exactly what everyone in the system is trying to prevent.
What Is the Difference Between “If Able” and a Mandatory Instruction?
The FAA Pilot/Controller Glossary (published as part of the AIM package) defines this distinction explicitly.
When a controller says “if able, turn left ten degrees for traffic,” the phrase “if able” acknowledges you might not be able to comply. If you cannot, you do not need to say unable. You say “negative, maintaining present heading” and give the reason if relevant. The instruction was already conditional.
“Turn left heading two-seven-zero, traffic twelve o’clock” is a mandatory separation instruction. It requires immediate compliance unless compliance itself creates the safety problem - a narrower and more serious category.
“Expedite” deserves specific attention. When approach says “expedite your climb to six thousand,” it means climb at the best practical rate your aircraft can achieve - not beyond what your aircraft can physically do. If you are already at maximum continuous power in a best-rate climb, you are expediting. Tell them: “Climbing at best rate.” That is a precise answer that tells the controller exactly what they are getting. If expediting would put you into IMC or through terrain you are not confident about, unable applies.
Does ATC Ever Say “Unable” Back to You?
Yes. The system is symmetrical.
You request a Class Bravo transition. The controller responds: “Unable Bravo transit, Bravo is closed below three thousand, suggest flight following below the Bravo.” That is ATC telling you they cannot accommodate your request with the current traffic picture - and offering an alternative.
Controllers have constraints. Pilots have constraints. “Unable” is the word both sides use when a proposed clearance or request does not work. It is not confrontation. It is information exchange.
Knowing the word flows in both directions makes it easier to say. You are not fighting the controller. You are doing exactly what they do when traffic will not accommodate a request: giving the system accurate information so it can find a workable solution.
How Do You Build the Reflex to Say “Unable” Under Pressure?
The word freezes pilots on frequency because it has never come out of their mouths under any kind of pressure. Reading FAR 91.3 and understanding the regulation is not the same as being able to execute the call when an approach controller is waiting and an airplane behind you needs sequencing.
Ask your CFI to build scenarios around this during pattern work, cross-country planning, and sim sessions. Have them issue clearances where the right answer is unable. Say it out loud with the radio in your hand in a moving airplane. Build the muscle memory the same way you build clearing turn habits or before-landing flow - through repetition until it comes automatically.
The Airman Certification Standards (ACS) for the private pilot checkride lists PIC responsibility and authority as a tested area. The examiner wants to see that you understand what holding a certificate means. The airplane is yours. The decision is yours. Knowing when to invoke that authority - including when to tell ATC you cannot comply - is part of what the certificate represents.
Key Takeaways
- FAR 91.3 makes the pilot in command the final authority on aircraft operation - this is a legal foundation, not a formality
- “Unable” applies in three main categories: performance limitations, weather conditions, and operational uncertainty on the ground
- Structure the call as: identification, the word “unable” plus the specific instruction, and an alternative when you have one
- “Say again” and “verify” serve the same purpose - use them without embarrassment; they exist precisely for these situations
- The unspoken readback - complying with a clearance you do not understand or cannot safely execute - is where accidents originate, not in saying unable
Radio Hangar. Aviation talk, built by pilots. Listen live | More articles