RTTY
[Top] [All Lists]

Re: [RTTY] US call signs (BARTG)

To: roger@g3ldi.co.uk, RTTY <rtty@contesting.com>
Subject: Re: [RTTY] US call signs (BARTG)
From: "Joe Subich, W4TV" <lists@subich.com>
Date: Tue, 08 Jan 2013 17:04:54 -0500
List-post: <rtty@contesting.com">mailto:rtty@contesting.com>

Perhaps it would have been far better in the US if a W6xx ( perhaps
a vanity call ) was the ONLY licence with W?xx. Then, when W6xx moved
to Fla, all he would have to do is sign W4xx. Simples!

Let's see ... UK with 58,500 +/- total licenses has three ITU callsign
blocks (2E, G, M).  US with 680,000 +/- total licenses has three and
one half (K, N, W and AA-AL) callsign blocks.  To be able to reserve
a two or three character suffix across all prefixes (BTW, does that
work if I move to KH6 or KP2?), the US would need *ALL* of the full
callsign blocks.

As a matter of fact ... *ignoring the numeral*, all of the possible
1x2 and 1x3 calls signs would not cover 10% of the US licensees.  Add
all of the possible 2x2 calls and you're still less than 35% of the
US amateur population.  The *British* system would not work in the US.
Time for BARTG to stop trying to dictate licensing policy to the US
- *period*.

Perhaps amateur licenses should become a state matter and each US
state could have a full callsign block (or two or three) like some
of the areas in Europe that are smaller than counties in the US.

73,

   ... Joe, W4TV


On 1/8/2013 2:01 PM, Roger Cooke wrote:
Hi Y'all.

Phil is right!  The only difference is that he would not be allowed to
operate on the mainland
as GU0SUP/G. He would actually benefit, because he would just drop the U
and become a
plain old G0SUP. You see, the licensing here at least had the
forethought to issue Phil with
GU0SUP but at the same time there was NO issuing of a G0SUP.
   Perhaps it would have been far better in the US if a W6xx ( perhaps a
vanity call ) was the
ONLY licence with W?xx.  Then, when W6xx moved to Fla, all he would have
to do is sign
W4xx.  Simples!

I guess it would not have been quite that simple though as there are far
more amateurs in
the US, but more logical!!!

The horse has gone now..............:'(


73 de Roger, G3LDI

On 08/01/2013 15:20, pcooper wrote:
Hi all, and HNY,

Well, has this opened a can of worms, or what??

I don't want this to be taken the wrong way, BUT, Bob K0RC wrote (and
echoed the thoughts of many others too!)
So basically what you're saying is if I want to keep my call sign, the
FCC has locked me out of moving to another district?
Why not is my answer. Let's think about this another way, if you will
indulge me.
Now let me explain..............

As  GU, I am often hunted down in contests for that extra mult, and I
am more than happy to play along, and I enjoy the fun I get from this.
BUT..... What would you W's think if I was allowed to go to the UK
mainland and operate as GU0SUP?
I can't do this, but what would you all think if I could?
Would you be happy to chase GU0SUP then, only to find out later on
that I am just a plain old G?

All that BARTG is asking (and a few other contests also ask this!) is
that you sign accordingly.
So, if you are a W6 operating in Florida, then why shouldn't you sign
W6XXX/4 ??

You'd expect me to do this if I was allowed to operate in England as
GU0SUP (maybe as GU0SUP/G) wouldn't you?

OK, so it adds another letter to your call, but so what, I am having
to send 6 characters for my call.

I know that this also causes you a little grief with LoTW, but many
folk currently do this, so why not? It isn't THAT difficult.

This is just a different way of thinking about these things!

73 all

Phil GU0SUP

_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty


_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty

_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty

<Prev in Thread] Current Thread [Next in Thread>