ATC and Pilots: When to Keep your Mouth Shut and when to Speak Up
By Robert Mark on September 28th, 2015ATC and Pilots
This sounds a bit pathetic, but most of the professional pilots I’ve known in my life have been smart alecks, me included … always ready with an opinion, whether anyone asked for it or not. We’re all control freaks to some degree I suppose, not an earth-shattering revelation of course, because those are the kind of people you want around when it’s time to grab the controls and say, “I’ve got it.”
Sometimes knowing when not to grab the microphone in the cockpit though, can be just as important, especially for me when it comes to ATC at least. I spent a decade of my aviation life in a control tower and behind a radar scope, which was just enough to qualify me – by my standards of course – as an expert.
Madison Wi (MSN)
Case in point to grabbing that microphone occurred at Madison, Wis., a few weeks ago with a student in the Cirrus. We were VFR in right traffic for Runway 31 and requesting multiple “option approaches,” the ones that leave it to us to decide whether we’ll make a full stop, stop and go, low approach, or whatever might be left. The long runway, 18-36, was closed for construction and some itinerant traffic was using Runway 3-21. BTW, tower assigned us Runway 31 which I did wonder about with traffic on Runway 3, but then since every controller runs their traffic patterns a little differently I thought no more about it.
After the third or fourth option approach, the tower cleared us to land on Runway 31, but never explained why. On touch down, I simply forgot and told the student “let’s go” and he added full power and reduced the flap setting. As soon as we broke ground the “cleared to land” part flashed in my mind. Maybe 100 feet in the air, the local controller in MSN tower firmly reminds me that when he says cleared to land, he means cleared to land. I really tried not to respond, but of course I did, “Sorry about that. My fault. But 18/36 is closed right?” as in, so what was the real problem other than my failure to follow orders. I honestly didn’t know.
Someone in the tower keyed the mic as if they were going to say something and then decided against it. We landed about 15 minutes later and the ground controller reminded me that I had earlier been cleared to land on Runway 31 and that they really need me to follow instructions in the future. Of course you know I keyed the microphone and asked again what the issue was other than blowing the order … “Did I conflict with some other aircraft?” “No, but you were cleared to land, not for an option,” he said. Since the other pilot was becoming uncomfortable with the exchange I just said, “Roger. Thanks,” and let it go. After all, I did blow it. I just would have liked to have known a bit more, but I decided to just let it go.
Kenosha Wi. (ENW)
Jump ahead a month or so and I’m again acting as CFI in the traffic pattern at Kenosha, Wis., this time having watched the other pilot I’m flying with land out of a really nicely handled circling instrument approach. We decide to stay in the VFR traffic pattern for a bit so the controller in the tower – obviously working both tower and ground himself – taxies us to Runway 7 Left. As we taxi, I hear him chatting with a Citabria pilot he’s sending to Runway 7 Right. About now I became occupied watching my pilot prepare for another takeoff.
Some part of my brain must have heard the tower clear the Citabria for takeoff from the right runway with a left turn out, just before he cleared us from the left runway, but it remained one of those distant notes in my brain until we were about 200 feet in the air. That’s when I saw the taildragger cutting across our path from the right. I instinctively told the pilot I was flying with to head right behind the Citabria as the ENW controller mentioned him as “traffic ahead and to our right.” He was a lot more than that. If we hadn’t turned, it would have been close.
The pilot flying with me looked at me in wonderment as I just shook my head and keyed the microphone … “nice tower.” No response.
I rang the tower manager a few days later on the phone because I wanted him to know how close I thought we would have been had we not banked right after takeoff. I told him I thought the ENW tower controller just plum forgot about the taildragger off the right when he cleared us for takeoff. I got it. It happens. I just wanted to see if I’d missed something here too.
Sad to say but the tower manager at Kenosha never rang back.
This is where it becomes tough for me. Should I ring the tower manager again and risk sounding like a know-it-all? I make mistakes too. What do you think? Let me know at rob@jetwhine.com.
Note: This story ran originally at the AOPA Opinion Leaders blog.
Related Posts:
Aviation Minute Via iTunes
September 28th, 2015 at 5:06 pm
I think you did the right thing, calling and explaining what happened from your perspective. I wouldn’t call again.
September 29th, 2015 at 5:56 am
Rob,
I would not only follow up with the Kenosha Tower manager for his sake, I’d have followed up with the Madison Contoller for your sake. It can only help operations when pilots and controllers can examine issues from each other’s perspective.