"Any Traffic, Please Advise"

[Bumblebee]

when people are reporting their position why would you call in the dark?

Valid point. Of course, a frustratingly clogged frequency only becomes more so with the atitapa call. With multiple people in the pattern, is the expectation for everyone to key up at once and say their position?


I am just being a jerk, i dont care about the call either way. Although i will advise regardless of the call, if i think we are going to be in conflict.

 

[FlyinSol0]

when people are reporting their position why would you call in the dark?

Not sure i understand. I just mean when zap calls three mile final and i am on downwind, ill give him the old "im mid field downwind and will extend it to let you in front" type call, even if he didnt ask. However, Im usually not going to tell him where i am if i think we wont hit each other, even of he asked all traffic on the area to please advise.

 

[RookiePilot]

I like this thread, and I believe I can see each side of the dispute. Where adding the tag at the end of a transmission may be beneficial.
Just my 2¢
Been gone awhile in the Peace Corps,

 

[Bumblebee]

However, Im usually not going to tell him where i am if i think we wont hit each other, even of he asked all traffic on the area to please advise.

So apparently, you want to make that decision for both of you. IDK, I think it's a good idea to make position reports even if no one is around...

if you don't respond to a request for advisory, then apparently the repeated requests don't bother you.

 

[FlyinSol0]

So apparently, you want to make that decision for both of you. IDK, I think it's a good idea to make position reports even if no one is around...

if you don't respond to a request for advisory, then apparently the repeated requests don't bother you.

I think You misunderstand me. I make all the Usual radio calls, even if no one is there. I meant i wouldnt repeat my crosswind call just because u ask me to, if you are forty two miles out. If i hear you entering a downwind, i will repeat myself.

 

[Autothrust Blue]

Meh, personally, I've said it. Sometimes its useful in places that are filled with local yokels who won't necessarily say anything until you get their attention. It also helps while you're taxiing out to say something like, "hey, anybody up?" because if you're at an airport (like PAGS) that has extensive local traffic and highly localized reporting points, a "sure, I'm over the Porpoises at 1500, you've got plenty of time" is way more informative than some arbitrary distance and direction. I use things that "work." When it warrants it, I'll say it, most of the time it doesn't warrant it. But in certain circumstances - like departing an uncontrolled field in the middle of the night - something like, "BFE traffic, Freighter 123 is getting ready to depart 36, anyone inbound?" might jar the other sleepy freightdog out of his sleep deprived stupor and cause him to take heed. Especially if you're blasting off VFR to pick up a clearance in the air. Just sayin'. In fact, I'll admit to it, I say and have said a lot o things that aren't "standardized" because sometimes the situations don't fit standardization all that well. Especially if clarification is required. A "uh, yeah, let's go over this step by step, I'm unfamiliar" has saved my certs a time or two. Just sayin'.

:yeahthat:

Nothing in the AIM prohibits the use of plain language or phraseology outside standard if required and situationally appropriate. Some of the busy uncontrolled places I've been require nonstandard phraseology for the purposes of separating ourselves from one another, too.

What bugs me far worse, and it seems the OP (or someone) has mentioned that this is not even a recognized radio term, is people saying "1234 in the box, comin' atcha with the flash," or "29.92 in the window," or the infamous ill placed "roger." I don't think you'll find these as recognized radio terms either, except of course for the latter. There are many others out there that I guess people think make them sound cool. The point is, if it gets the intended message across while breaking up the monotony of flight and not sounding like robots all the time, have at it.

The "one two three four and here it comes/with a flash/push the button" or "nines and twos" or what have you—all that chinsy crap—have far more potential to actually hurt someone, I think.

Pet peeve that will, in fact, cause a pilot deviation or worse: you WILL read back at least your abbreviated callsign (if the ATC specialist has used it first) or your full callsign when given a control instruction. "One two three four, here it comes." <- Okay, which aircraft is that? Did Beercan two seventy four acknowledge for someone else?

 

[averettpilot]

Well said.

 

[Corporate Pilot]

How many radios you got in that jet? Monitor ctaf in the second comm a few miles out before they switch you?

Potomac approach can be very busy at times and it is hard to monitor two radios at once. Your idea works great in to KBFE but not so great when you are going into a busy area. The airport you are going into may not that busy but the approach frequency may be very busy.

I came out of KMTN last Thursday and it was hard to get checked in with departure because the frequency was so congested. And yes again it was Potomac.

 

[Corporate Pilot]

if only that were true...I have had to prompt people to speak up, even when I knew they were there...the most recent one I knew they landed and was waiting for a clear of the runway call, we were only 3 miles, it was smokey vis, and we didn't wan to have to go around, I finally got the call when I said we were turning final, and they had been off (according to one of our air attack guys) but just didn't tell us.

That is what I am talking about. These guys or gals will not come up on the freq unless asked to and then it still may not happen.

 

[inigo88]

if only that were true...I have had to prompt people to speak up, even when I knew they were there...the most recent one I knew they landed and was waiting for a clear of the runway call, we were only 3 miles, it was smokey vis, and we didn't wan to have to go around, I finally got the call when I said we were turning final, and they had been off (according to one of our air attack guys) but just didn't tell us.

I don't think you'll get any argument from anyone that you shouldn't be able to directly query someone, or "request traffic advisories, xyz airport"

"(callsign or) Last aircraft to land on runway XX, did you clear the runway?" - is a much more direct and effective way of getting the information you want then asking "Any traffic in the area please advise." The latter is pretty ambiguous.

And the argument is really if every new inbound aircraft asked "Any traffic in the area please advise?" and the chaos of multiple people trying to answer at once ensued, it would be harder to get a word in edgewise to actually query that specific aircraft and get the information you needed. Plus it seems to have the "crying wolf" effect on the people already on the frequency... after the fifth time they hear it they're probably less likely to answer (lame as it sounds that's been my experience).

So maybe the best compromise is, use it when you need it but don't overuse it and desensitize everyone? :dunno:

(I think I've shared more than my $.02 on this so I'll just gracefully bow out now. )

 

[MFS]

Just turn off the radio and have a good time.

 

[Autothrust Blue]

Just turn off the radio and have a good time.

RDO-1: "Santa Paula traffic, yellow Decathlon, upwind over the city, 1,500', Santa Paula.
RDO-1: "Santa Paula traffic, yellow Decathlon, left crosswind, Santa Paula."
INT-1: "Gee it's quiet today."
INT-2: "Yeah."
RDO-1: "Santa Paula traffic, yellow Decathlon, left downwind two two, Santa Paula."
INT-1: "Oh, traffic on base, in sight."
RDO-1: "Santa Paula traffic, yellow Decathlon, left base two two, Santa Paula."
RDO-1: "Santa Paula traffic, yellow Decathlon, final runway two two, Santa Paula."

After landing—discover aerobatic area frequency and not CTAF dialed in. "Oh, that's why!"