"TheSmokingGnu" wrote in message
...

No you didn't, otherwise you would have found the answer in the Great
Repository of Human Knowledge. But then, I don't expect trolls to be able
to read in the first place.

http://en.wikipedia.org/wiki/Quotation_marks


http://en.wikipedia.org/wiki/Quotati...28incorrect.29



Do you have to take classes to be so pedantic? I've already explained the
vernacular, the onus is now on you to understand the topic at hand.


You've got it backward. I'm explaining these things to help you understand
them.



I find it funny that you only considered /me/ to be the one under these
influences. Time to think outside the troll box.


I can only work with what you write.



I departed. I corrected for winds and flew a proper upwind in-line with
the runway. He departed, and did not. The winds were such that his track
was inside of mine. I made the turn crosswind. He did not inform anyone of
his intentions beyond taking the runway. Our tracks nearly intersected. He
was distracted by something (else he would have been making
intent/position reports, or responding to ours). There were a lot of other
aircraft in that patch of sky that day, and I was working a scan not
entirely in his direction at the time of the incident. My copilot did spot
him, and we managed to avoid each other.


As I recall, your complaint was that his failure to depart from the downwind
was the cause of the incident. That clearly was not the case.



Ad hominem. You wanted an example?


Yes, and that is not an example.



I assume nothing, remember? I expect him to be doing both, and will look
for that first. Failing that, we go into contingency mode.


If you weren't assuming that he'd be adhering to a non-required "standard"
practice why are you complaining?



Faculty, not facility. I goofed there (and bad. I dunno how that got in
there).


CTAF is a frequency, not a faculty.



http://dictionary.reference.com/browse/unnecessary

That's not an FAA source. How can I know what officially constitutes
"unnecessary" chatter when the FAA doesn't define it?


Good question. Let's get back to "standard". Please provide an official
FAA definition of "standard" before we move on.



I already have, multiple times. Want it again?

They don't expect traffic there, in that direction, at that altitude, at
that speed.


Why do they assume traffic won't be there, in that direction, at that
altitude, at that speed? Didn't you say assuming was bad?



My god, do you take everything literally?

I meant "better than Freud". I will refrain in the future from trying to
make snide inferences, so that your limited ability to understand
articulated speech is not questioned.


How does one make a snide inference?



Why, since not only is it painfully obvious, but you refuse to make one of
mine?


Because citing one is the only way to make your case. If there was one to
cite, you'd have cited it.



Such as?


"Then you should have quoted him the right-of way rules (planes below
have right over those above, planes on approach have right over those in
the pattern), and told him that you were taking your CLEARANCE and using
the RUNWAY."

"You'll get lots of people that, for example, won't depart the pattern on
the
downwind..."

And there was that cryptic reference to "descent vectors".



Where did you establish that? As I recall, you're relying on Jay's
assumptions about spacing and separation, and whether they were
appropriate or not. How can you both disprove a point and rely on its
premise for your conclusion?


Yes, we're relying on Jay's statements about the spacing. If the spacing
was as he reported then there was sufficient spacing.



Besides, without definitive objective proof, the premise could never be
established in the first place, since it's an anecdote, and made under no
pretense of authority.


The problem is his anecdote does not support his conclusion.



The controller was expected in this circumstance to amend the 172's
clearance such that they were told to either land long or continue
rolling. Expected, not required. You cannot make the argument that the
controller did not share the bulk of the responsibility in this case to
properly inform and administer the aircraft in his care. A simple
amendment, comment, or otherwise remark to EITHER aircraft would have
avoided the entire situation, but instead the controller allowed it to
unfold and then attempted to clean up afterwards. It's a sign of poor
controller-dom.


That was an unreasonable expectation on Jay's part. I can easily make the
argument that the controller does not share the bulk of the responsibility
in this case to by demonstrating that the controller did not make an error.