Welcome to Flightinfo.com

  • Register now and join the discussion
  • Friendliest aviation Ccmmunity on the web
  • Modern site for PC's, Phones, Tablets - no 3rd party apps required
  • Ask questions, help others, promote aviation
  • Share the passion for aviation
  • Invite everyone to Flightinfo.com and let's have fun

Visual Approach Procedure

Welcome to Flightinfo.com

  • Register now and join the discussion
  • Modern secure site, no 3rd party apps required
  • Invite your friends
  • Share the passion of aviation
  • Friendliest aviation community on the web
I agree lumcevac. It's good food for thought. I don't think we were actually ever disagreeing about anything. Heh! :D

h25b - I'm not sure that anyone here was getting on your case. I've certainly done this very thing from time to time, and this is the first I've heard where a controller has gotten pissed about it. Your story has, however, forced me to consider the error of my ways!
 
Interestingly, Don Brown's latest article (from Avweb) touches on this very thing. Keep in mind that Don is a center controller, so that may change his perspective a bit:

I've got to go back and touch on a few other points about your clearance limit. Again, let's look at the clearance that started this article.

"Airliner one twenty three, cleared to SHINE, hold northwest, as published, expect further clearance one five three zero."

That clearance changes your clearance limit. It does not change your routing. It does not clear you direct to SHINE. Likewise, an advisory to "... expect radar vectors ILS runway two four Hickory" does not change your routing. Don't use your advanced NAV to slide over towards the intercept point or an IAF. If you were cleared direct to the airport and your routing hasn't been changed, then you are supposed to be flying direct to the airport.

I see both of these errors on a constant basis. I mentioned it to a pilot the other day on the frequency and he didn't seem to appreciate it. I'm going to tell you like I told him: If it keeps happening -- sooner or later -- we won't be talking about it ... we'll be filing paperwork. Lest you forget, I work in a Center. We have the Operational Error Detection Program (a.k.a., "The Snitch Machine"). If you make a turn to someplace without a clearance, get close to another airplane and the machine goes off -- the talking is over. The machine goes off at the manager's desk and an investigation starts.
 
My only comment is that 3 miles seems a little excessive...I prefer a mile or even a little less, and even in busy airspace haven't had anybody complain about that.

I do, however, fly with guys who like the 3 mile fix. I've also flown with a guy who departed Class D on his downwind ;)

Fly safe!

David
 
I fly with a guy who when given "direct" to an airport will go direct to a local VOR or nav facility if VOR is not present. I've tried to get him out of this as I am sick of explaining to ATC where we are going. Not a big deal if the VOR is terminal but I'm sick of 17 miles off of direct for his insecurities.

This guy also can't seem to figure out how to fly anything published. When told to fly 090 to intercept an outbound radial on an arrival, leading to xxxxx intersection he will hit "direct, enter" and make the turn. Sometimes I wonder how we all survive in this industry. Mid you he is a 16,000 hour guy who knows everything.
 
again

all solved with "uh, can (tail number) do (insert request) instead, if its not too much trouble?"

insert Texas or Georgia red-neck drawl if PIC on King Air
 
The secret here is to read back all direct clearances to the field as "pretty much." For example, "XXX321, Cleared direct Dodge City."

The appropriate response is "XXX321, cleared pretty much dodge." This may also be supplemented, or exchanged with "more or less," or the less-desirable, "generally." When a later controller asks if you were cleared direct XXX airport or WONSA, you can say "I heard we were generally cleared pretty much XXX, more or less, that okay with you?"

A quick visit to the pilot-controller glossary will reveal that the proper controller response is "Roger, whatever." If the controller gets upset, makes threats, or tells you anything resembling "no," then it's best to just do what he says, so nobody gets hurt.

This works the same for altitude assignments. Always preface an altitude readback with "about." Controllers love that. "XXX, PD to about two three zero." "Left heading about two seventy, climb and maintain about three five zero, more or less."

You get the idea. Never commit to anything. Also, be certain to answer queries with questions. "XXX, say assigned altitude."

The appropriate response is "XXX, what altitude do you think we were assigned," or the more personal, "how do you feel about this altitude?"

When frequency congestion isn't an issue, an intellectual discussion on the matter is also appropriate. "XXX, say assigned altitude."

"XXX, what does assigned really mean, and how does it relate to the bigger question; why are we here?"

During especially heavy frequency congestion, controllers prefer crisp, quick responses. "XXX, say assigned altitude."

"XXX, Assigned Altitude."

On those rare occasions that any of these approved tactics don't work, you can always just turn off the transponder. Then, in a foriegn accent, quickly call the controller on the same frequency and say "Hockatok control, Wunderbar Six Tree Tree Niner ist peeking up ana Ee, El, Tee, und sees a rahtha largish bowl of fiher duwn beelow." Then land, before the jig is up.

Or, you could just proceed to the destination, and make your request for any deviations the old fashioned way.
 
BE200Driver said:
I fly with a guy who when given "direct" to an airport will go direct to a local VOR or nav facility if VOR is not present. I've tried to get him out of this as I am sick of explaining to ATC where we are going. Not a big deal if the VOR is terminal but I'm sick of 17 miles off of direct for his insecurities.

This guy also can't seem to figure out how to fly anything published. When told to fly 090 to intercept an outbound radial on an arrival, leading to xxxxx intersection he will hit "direct, enter" and make the turn. Sometimes I wonder how we all survive in this industry. Mid you he is a 16,000 hour guy who knows everything.
:confused:
I would be driven up the wall by that. I feel your pain.
 
h25b said:
Again, for the record (and 3rd time to admit it, what I was doing was technically wrong) I'm just curious to see how many out there do what I did. Thought I'd point out that there's some controllers out there that don't like it and there might be some pilots on the board here that would find this experience useful. That's all, now I'll drop it.

Yeah, we do it all the time in our Hawker too (tell the FMS to go direct to the FAF or, if flying the visual, a point derived off the rwy centerline 5nm out) when instructed to proceed 'direct' to the airport. Haven't been slapped for doing so, although I agree it's probably 'technically' wrong, but give me a break. BFD is right.
 
Most controllers at my home airport know my voice so they figure if I'm within 3 miles either side of the airport on a visual, I'm having a good day... And so are they! :D TC
 

Latest resources

Back
Top