Mike Boehler
Pre-takeoff checklist
- Joined
- Sep 14, 2010
- Messages
- 141
- Location
- Sharon Springs, NY K31
- Display Name
Display name:
Mike Boehler
I feel like the next argument will be whether to wear white after labor day?
I'll settle for your opinion, which is no more correct or incorrect than mine.
Which is still obtaining permission from ATC... since you're nit picking.
That's fine, mine is based on logic. What is yours based on?
Pardon the intrusion, but...
If logic says that a VFR pilot should not call "Clearance Delivery" for VFR departure instructions because VFR departure instructions aren't related to a "clearance", why doesn't logic also say that the VFR pilot should not call the "ground" controller for departure instructions since VFR departure instructions aren't related to movement on the ground?
Just asking.
Pardon the intrusion, but...
If logic says that a VFR pilot should not call "Clearance Delivery" for VFR departure instructions because VFR departure instructions aren't related to a "clearance", why doesn't logic also say that the VFR pilot should not call the "ground" controller for departure instructions since VFR departure instructions aren't related to movement on the ground?
Just asking.
Don't try to disrupt Steven's "logic" with real logic.
You'll only make him angry.
What he really means is that he hasn't thought of any other meaning, so there must be no other meaning.
I wouldn't call ground for departure instructions, I'd call ground for a taxi clearance.
It's entering Class C without being in contact with ATC, something you said cannot be done.
OK, that makes sense, but only if you confine Ground as being a controller that only gives you taxi instructions.
However, in post #107, you said that when there's a Clearance Delivery and a Ground frequency, and there is no specific instructions on whom to contact prior to a VFR departure, you said because you're not getting a "clearance" that logic would say you should "Call Ground."
And, in the very next post #108 you said Ground does much more than give a taxi clearance, i.e. "Ground issues an altitude restriction, beacon code, and taxi instructions."
I'm just saying that, as corroborated by your own explanation of what transpires, logic also suggests that one would not call "Ground" for a transaction that produces an an altitude restriction or a beacon code. Taxi instructions alone - yes. Discussions about VFR flight-related intentions including direction of departure and destination, and controller-provided information to be used in flight including altitude restrictions and beacon codes - no.
If my memory is correct that you're a current or retired controller, then your experience is invaluable and I thank you for sharing it, but logic alone doesn't really seem to help in determining whether to initially call CD or Ground when it's not specified.
And that happens how often?
How many pilots actually obtain authorization prior to the flight instead of simply contacting approach to get in?
Quit finding every tiny anomaly miles away from real-world situations just to prop up your argument.
I don't see how. The only reason I call ground is for the taxi clearance but nothing prohibits ground from doing more.
Yes, I'm departing a towered field so a taxi clearance is required. Ground is the place to obtain that.
***
Two clearances are needed to become airborne from a towered field, taxi and takeoff. Neither of them are generally issued by CD.