8 times you should say no as a pilot
Being a student pilot is a lot like being an 8th grader: sometimes you just want to fit in. Since I learned to fly at a towered airport, I was especially worried about being a bad teammate: making a mistake on the radio, breaking some unwritten rule or upsetting air traffic control (ATC). Whenever possible, I wanted to say yes and fit into the flow.
I suspect most pilots are the same way. After all, we are typically the can-do type who view “no” as a sign of weakness. But as much as we like to press the push-to-talk button and calmly proclaim “wilco,” sometimes you simply have to say no – even when it’s uncomfortable. It’s not being lazy or being a bad pilot, it’s prioritizing safety over convenience.
Here are 8 times it’s not just advisable but required to say no:
Say no to a takeoff clearance if you’re not ready. “Cessna 12345, cleared for immediate takeoff, traffic on 1 mile final.” It happens all the time at busy airports, but this scenario is packed with subtle pressure to start moving – now. Resist the urge to rush. No matter how much you want to help out, you’re not doing your job as pilot in command if you take off before you’re ready. In fact, the deadliest accident in aviation history can ultimately be blamed on a 747 taking off before both pilots were ready.
Say no to “max forward speed” on final if you can’t safely do it. If there’s a Learjet or a Boeing behind you for the runway, you may hear ATC ask you to fly as fast as you can on final in order to keep the spacing acceptable for him. If you have 500 hours in the airplane and can do it, by all means, comply with the request and make everyone’s life easier. But if you’re on your first solo cross country, you’re under no obligation to accept this request – and it is a request. You might have to turn off final or do a 360, but that’s better than arriving at the threshold high, fast and unstabilized.
Say no to land and hold short if you’re unsure. So-called LAHSO operations are pretty rare these days, but you might get issued this instruction at a bigger airport with intersecting runways. If you’re not absolutely certain you can land and hold short of the crossing runway, and if you haven’t previously studied the chart and briefed the procedure, don’t say yes. Sure, the controller may not be happy, but he’ll be a whole lot less happy if you accept but can’t do it.
Say no if you really don’t have the airport in sight. This is another situation where ATC often exerts a subtle pressure on pilots: “Clermont County Airport is 12 o’clock, 5 miles, report it in sight.” The controller would love for you to call the airport in sight and get rid of you. Some pilots fudge this, assuming that since the GPS shows the position of the airport, they can simply say yes and keep navigating until right on top of the airport. This trick will probably work 90% of the time, but the one time it doesn’t, you’ll really wish you were still talking to ATC. If you don’t have the airport in sight, the answer is no. Simple as that.
Say no to an approach clearance if you’re not stabilized. For instrument pilots, the start of an approach is a critical time: the airplane is descending towards terrain and obstacles without visual reference. If you’re not certain of your position – and if the airplane isn’t configured and slowed down properly – accepting an approach clearance and chasing the needles will not make things better. Ask for a delay vector and go back out to re-intercept the final approach course. Good landings are the result of good approaches, so insist on starting them the right way.
Say no to a crossing restriction you can’t make. Another concern for IFR pilots, and occasionally VFR pilots, is when ATC asks you to pass a certain waypoint at or below a certain altitude. Often this is a simple clearance to comply with, but sometimes ATC asks for the impossible. If you do the math (hint: your GPS’s VNAV function saves a lot of time) and find out you’ll need to maintain 2000 ft/min down, you probably need to let ATC know it’s not possible. This isn’t the end of the world – just be honest and let them come up with a plan B.
Say no to a more experienced pilot when you’re uncomfortable. Not all pressure comes from ATC; sometimes other pilots are guilty too. Years ago, as a brand new Private Pilot, I was staring intently at the weather maps at the airport as I tried to figure out a way to fly home. A much more experienced pilot, in an effort to be helpful, leaned over my shoulder and gave some advice: “looks worse than it really is – I think you’ll be fine.” I ended up taking off, but I shouldn’t have. I had let the older pilot’s opinion influence me, substituting his personal minimums for mine. Never again. Your decision is your decision, and sometimes that means politely thanking another pilot and saying no to yourself.
Say no to pushy passengers if the weather is marginal. Passengers can also offer their opinion, even if you don’t want it. This is tricky, especially with friends and family, since we love to show off our piloting skills and “get the job done.” But general aviation flying is supposed to be fun, and if the weather doesn’t look fun it’s your job as PIC to say no. It may be disappointing, but it’s the right call – no matter who the passenger is.
Fitting in is a good thing most of the time and there’s no virtue in being a nuisance, so use your PIC authority wisely. But if you’re ever unsure or uncomfortable, you have every right to say no. In fact, most good controllers will tell you that they expect it.
- Flying for youth - March 13, 2023
- Soft Field Takeoff – HD Flight Maneuver Spotlight - August 22, 2022
- Slow Flight – HD Flight Maneuver Spotlight - July 25, 2022
Another time to be careful:
Approach and tower like to point out traffic inbound to your landing runway. Your acknowledgement, “In Sight” is often followed by “Follow the traffic, cleared to land”. I’ve found it better to say “Looking, no contact” if I’m not sure I can maintain visual contact. It’s always better to fly your plane and let the controller do his job of separation a little longer.
Say “NO” when a passenger asks to bring a friend or wants to carry an object/item that you’ve not included in your W&B calc… and (a) you don’t have time to update your calcs, or (b) you have ANY doubt that you’ll remain within your envelope AND that the flight can be conducted safely at that weight/Balance.
Say “NO” for any flight – no matter how ‘important it might be’ – to ALL of the following people: to yourself – though you might be embarrassed or might miss some meeting or event: to your passengers – though cancelling the flight or making an unplanned diversion might cause ‘inconvenience’ or whatever; and anyone else (family, friends, business associates, etc.) -for whatever reason when current and forecast weather is beyond your capability (for you, the pilot OR for the aircraft!), you encounter any mechanical issues, or any other condition/situation arises that might affect the safe outcome of your flight.
Great article. The word, “unable” is a great tool in your vocabulary. ATC is there to serve you. Not the other way around although pilots do their best to work with ATC. Remember, Air Traffic Controllers have a plan A, B, and, most likely, a C in the event you can’t comply. If you are unable to comply, tell them. If able, let them know what you can do and that will help ATC work with you on a solution.
The word is unable. Using no will catch you grief.
It would be helpful to include an example on HOW to proactively say no for each of these cases. Since this is intended for low-time pilots, concrete examples help much more than vague paragraphs. For example, for the first case, simple “Not ready yet, we’ll wait for next window” would do.
Occasionally we get an ATC who speaks very fast and issues directions barely within the time he has his mic button pressed. This situation, on more than one occasion, has left me not knowing exactly what that controller said or wants me to do. When I encounter this controller, I will respond with “new pilot, say again more slowly.” It’s not a good ideas to guess what the controller said and try to repeat his instructions. Know what he said by asking him to repeat his instructions so that you can clearly hear and understand his instructions. Your request might slow things down a bit but it beats the heck out of having to have a discussion with the FAA.