Jim,
Our calls are valid anywhere worldwide ... but I understand your point.
Respectfully - a K9 or any standard CONUS amateur call is rather vanilla.
Probably wisely so, the FCC does not require "call by call area" any longer as
you well know. With our mobile society ... we all have heard a hog-podge of
calls not matching actual locations. On the east coast, it seems like half of
the New England ham population now lives in Florida ... and I am sure things
are similar elsewhere.
There is little need for most US "vanilla" stations to accurately ID exact call
area or location - grid; maybe a different situation. The ARRL DXCC - USA is
not a greatly sought after, rare DX entity. Hawaii, Alaska, Guam, Puerto Rico
to an extent, etc are somewhat different. They may not be rare ... but they
are sought after by some for various reasons. It was funny -- I recently
worked someone on 160 who told me that he "soiled his adult diaper when he
heard my AH6 call sign." That pretty well sums up the call issue.
The situation is much different when working DX. For me, it is almost a "must"
to accurately ID call and location ... which is easily done by using a
non-standard compound call sign. You would be surprised at some of the hate
FT8 anonymous comments I sometimes receive because of my call. It is easy of
course to track down these folks by tracking the nasty response frequency back
to a previous transmission when the station used a call sign.
So respectfully Jim - no ... operating K9 from K6-land is not like operating
AH6 from W4-land.
In case you did not see my latest response to Bill and others ... here is an
extract of my most recent email / posting related to that issue.
But in closing -- checked out your QRZ page ... used to listen to WLW - a
landmark station on AM ... and visited the R.L. Drake factory shortly after the
tornado wiped out Xenia several years ago. My first really good SW receiver
was the Drake SW-4 - fantastic. Now the extract.
Best Regards, Danny W4/AH6FX
........
On SSB and RTTY I always sign asAH6FX/W4 to control expectations. When using
versions 1.8.* and 1.9.* I signW4/AH6FX on FT8 to, again, control expectations
– people seem to recognize theW4/ first and recognize my locations.
Butexpectations are sometimes hard to control as you can imagine. I do notwant
anyone thinking they are working Hawaii when I am in northern Virginia.
Although the FCC does not requireUS stations to sign /[slash] portable, etc …
the FCC does not prohibit us from doing so. I use an “adapted”call sign
protocol specified in CFR Part 97. Say I was a Canadianstation operating in
Virginia … FCC says that station should sign as, forexample, VE1ABC/W4
Nokesville. I have never heard a foreignstation include the nearest town, as
required by the FCC, but I certainlyhave heard them properly sign VE1ABC/W4 or
whatever. That is the problemI often have, and stubborn me - I am adapting the
FCC guidance to my situation. Although I am not a foreign station operating in
the USA, tomany hams I am DXCC-Hawaii when in fact I am DXCC-USA … Virginia to
be exact. My adaption of the /W4 or W4/ is my attempt to inform folks in am
inW4-land. ...........
On Friday, December 21, 2018 2:07 PM, Jim Brown
<[email protected]> wrote:
On 12/21/2018 8:44 AM, DX Jami via wsjt-devel wrote:
> nonstandard call signs such as mine - W4/AH6FX ... or AH6FX/W4
Hi Danny,
US callsigns, with no / identifiers, are valid anywhere in the US. While
using one is legal, it is completely un-necessary. Your call is AH6FX
anywhere in the US, and I view it as a nuisance. I live in California,
and my call is K9YC anywhere in the US.
The only time that you or I have a good reason to sign /anything would
be if we were operating in a contest from a different DXCC entity than
our prefix implied.
73, Jim K9YC
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
