Over the past year at the airports I operate from, I’ve seen it dozens of times: a student pilot gets an unexpected ATC request.
“Extend downwind.”
“Give me a 360 for spacing.”
“Continue through final.”
“Expedite takeoff.”
“Head straight to the numbers.”
The student’s instinct? "I guess I have to do it."
Here’s the key: you are always responsible for the safe operation of your airplane. If ATC gives you an instruction that you’re not prepared for, it’s okay (and sometimes necessary) to say, unable.
Controllers make these requests to manage traffic efficiently. They may not know you’re a student or how comfortable you are with a short approach or an unexpected maneuver. And they certainly don't know what's happening inside the aircraft. That’s why pilots communicate clearly: “Unable short approach, student pilot,” or “Unable 360, request normal pattern.” Controllers are professionals and hear this all the time, and it keeps everyone safe. They're not going to take it personally.
Trying to follow an instruction you don’t fully understand or aren’t ready to execute can create a lot more risk than politely declining. Ask for clarification, request an alternative, or stick to something you can handle safely.
ATC instructions are important, but they don't override your judgement. Communication is a two-way street and sometimes the safest answer is simply, unable.
