.......annnnd.... I just pushed the PTT and totally forgot what I was gunna say... Is usually why I do it.

200hr Wonder wrote:.......annnnd.... I just pushed the PTT and totally forgot what I was gunna say... Is usually why I do it.

Same.

What annoys me more than anything is when "currently" and "at this time" are used in the same sentence. I don't think either is even necessary... if you make a position report, I'm going to assume you're telling me your "current" position, not where you were 5 minutes ago.

Or how about "all stations"... what's up with that as well?

Just another canuck wrote: What annoys me more than anything is when "currently" and "at this time" are used in the same sentence. I don't think either is even necessary... if you make a position report, I'm going to assume you're telling me your "current" position, not where you were 5 minutes ago.

The CFS has an guideline on the back cover for a position report. One of the items is "time." I use "currently" to meet that part of the guideline. What do others do when reporting "time?"

C23flyer wrote: I use "currently" to meet that part of the guideline.

You don't need to say it... it's completely obvious you are talking about the present. Is there anyone out there that makes a position report in regards to where they were or where they're going? And if for some reason you do, then say so.

Whatever, it doesn't matter... just don't use "currently" and "at this time" in the same report. Please.

Just another canuck wrote:

C23flyer wrote: I use "currently" to meet that part of the guideline.

You don't need to say it... it's completely obvious you are talking about the present. Is there anyone out there that makes a position report in regards to where they were or where they're going? And if for some reason you do, then say so.

Whatever, it doesn't matter... just don't use "currently" and "at this time" in the same report. Please.

Oceanic, and any other non-radar position reports require stating where you were, where you're going, and where after that, but no need to say "currently" "at" "now" "presently" "at this time"

"FABC 55N50W 1234 FLIGHT LEVEL 350 ESTIMATING 55N40W 1310 NEXT 55N30W"

I will strip that from my next PR. Thanks

And.....

what's funnier is that the French do it too. I keep hearing "Eeeeeeeeeeeeeeeeeeeeeeeeet" on initial calls with Montreal.

Willo Three Bravo wrote:

Just another canuck wrote:

C23flyer wrote: I use "currently" to meet that part of the guideline.

You don't need to say it... it's completely obvious you are talking about the present. Is there anyone out there that makes a position report in regards to where they were or where they're going? And if for some reason you do, then say so.

Whatever, it doesn't matter... just don't use "currently" and "at this time" in the same report. Please.

Oceanic, and any other non-radar position reports require stating where you were, where you're going, and where after that, but no need to say "currently" "at" "now" "presently" "at this time"

"FABC 55N50W 1234 FLIGHT LEVEL 350 ESTIMATING 55N40W 1310 NEXT 55N30W"

Okay now I'm curious.

What do you say if you are reporting over a fix you are actually over at that instant? Do you just say the present time or say "I'm over it now"?

Just another canuck wrote:

200hr Wonder wrote:.......annnnd.... I just pushed the PTT and totally forgot what I was gunna say... Is usually why I do it.

Same.

What annoys me more than anything is when "currently" and "at this time" are used in the same sentence. I don't think either is even necessary... if you make a position report, I'm going to assume you're telling me your "current" position, not where you were 5 minutes ago.

Or how about "all stations"... what's up with that as well?

What is that phrase associated with making assumptions.....

So if I'm making a late IFR progress because of freq congestion (likely forgetfullness) you will assume that I am over the fix now as opposed to the time I state? Would you base separation on that...

.

Oceanic, and any other non-radar position reports require stating where you were, where you're going, and where after that, but no need to say "currently" "at" "now" "presently" "at this time"

"FABC 55N50W 1234 FLIGHT LEVEL 350 ESTIMATING 55N40W 1310 NEXT 55N30W"

Okay now I'm curious.

What do you say if you are reporting over a fix you are actually over at that instant? Do you just say the present time or say "I'm over it now"?

Well, by the time you call and get a reply, especially HF, that instant has long passed. Mind you, if your foresight is impeccable and you call prior to being actuallly over the fix, get the reply, and the first few words out exactly before you cross the reporting point............

...This past week I have been hearing "...annnnd..." a lot. Seems every other transmission someone is saying that....

....am I being 'punked' on the air by y'all y'all?

FamilyGuy wrote:What is that phrase associated with making assumptions.....

So if I'm making a late IFR progress because of freq congestion (likely forgetfullness) you will assume that I am over the fix now as opposed to the time I state? Would you base separation on that...

I understand where you're coming from here. If you state a position, I think it's safe to ASSume it's current position. If it's not, state otherwise...

gustind wrote:"......Any conflicting traffic please advise"

Well no shit, I ain't just gonna sit in my plane while you collide with me.

This is a practice that goes back to that first cross-country. Maybe mention it in the flight training forum.

annnnnnd... there is also 'hey!"
"HEY this is air canada 123..."
it says "hey!", as if there were happiness or surprise, I guess one time there will be a, "hey center we're allready @ 18000 to FL 3-2-ho!".... ......

"hey" is for horse as my mother used to say...

Sometimes, I'll use Annnddd to start a radio transmission (as an ATC), just to signal to the pilots to pause their conversations and pay attention for a moment, because I have something important to say. It's better to do that, I find, than to repeat myself.

gustind wrote:"......Any conflicting traffic please advise"

The reason to say this one is to give the ident again, as in:
"... any conflicting traffic please advise <ac ident>"

At least for me, it's only partway through a transmission that my lower brain functions decide to wake the higher brain functions and point out that I'm pretty much nob on with the other guy. By then, the higher brain has missed the ident and sorely hopes it gets repeated!

Doc wrote:One of my favs is "Center, this is ABC with a request.."
Why not just make your request?? "Center, this is ABC requesting FL220..." Too hard for ya?

And, um, er, have a merry Christmas!

Depends on the request. If you're just asking for FL220 then you're correct, say it in one go.

But if you wanna request "another simulated NDB GNSS Overlay then on the missed if we could maintain VFR out of the control zone to the east etc etc etc" you wanna make sure hes listening, I figure.

And yeah, never understood the "and" thing, though I occasionally find myself doing it..

-Jonathan G.
CYWG

I understand you are often talking on 2 or more freq at once. This is why I'll usually say "Center YYY, request." That way, you'll get back to me when you have time and not busy talking to someone else on an other freq.

scopiton wrote:annnnnnd... there is also 'hey!"
"HEY this is air canada 123..."
it says "hey!", as if there were happiness or surprise, I guess one time there will be a, "hey center we're allready @ 18000 to FL 3-2-ho!".... ......

"Hey Hay River traffic, ...."

or how 'bout

"Hi High Level radio..." haha

I hafta agree with all the single pilot "We" sayer's, I'm one myself... not so much an "aaaand..." user thou, but I see where you're comming from.

In my area center sends on all frequencies when working multiple frequencies so no need to worry about cutting the them off. However, I don't see much difference between "ABC with request" and "ABC request FL123". Either way if they don't hear you you have to repeat. I always just make the request unless it's a complicated one.

It drove me so nuts for so long I switched to helicopters where the VHF is rarely even on as i get to swear on the FM....

stl

yrp wrote:

gustind wrote:"......Any conflicting traffic please advise"

The reason to say this one is to give the ident again, as in:
"... any conflicting traffic please advise <ac ident>"

I don't want to beat a dead horse (this has been argued many times on here) but usually what I miss is the AREA as well as the aircraft. If you start out with 'blah-blah traffic, ABC etc....' by the time I hear something familiar (altitude, rwy #) that might apply to me I start listening. Trouble is, I may have missed that initial position report. So now that you have my attention, all I hear is '... any conflicting traffic please advise ABC'. Well, great! I know who to contact, but unfortunately I missed WHERE you are which makes it tough to determine if you are a conflict in the first place.

So, to fix this, at the end of my position reports I repeat the area as well as my call sign.

"Fort Francis traffic, GABC 30nm east at 10,000', rwy 30 in 5 mins. GABC Fort Francis"

and --- errr--- what really pees me off, (about myself) is when I start a call to outer tower informing him of my destination or next reporting point and without warning I cannot seem to remember the name of the place. This can cause all kinds of umming and erring.

Old age?
Bob