[Top] [All Lists]

Re: [CQ-Contest] Barking up the wrong ARRL DX tree

To: cq-contest@contesting.com
Subject: Re: [CQ-Contest] Barking up the wrong ARRL DX tree
From: Cqtestk4xs@aol.com
Date: Mon, 4 Apr 2005 11:06:53 EDT
List-post: <mailto:cq-contest@contesting.com>
The problem is
that DX contesting essentially is a non-competitive exercise for the
vast majority of the United States and 
Canada.......................................de W4PA
I disagree.  The majority of the US does have a shot at winning the contest.

The problem is one of geographical location, but not in the traditional sense 
of the way people usually speak of it.  Most contesters would agree that 
there is an advantage to the Northeast US and Canada for the ARRL DX.  My 
are the same as yours...too bad, live with it.  It is possible to win the 
contest outside the Northeast if things go just your way as they did in 2001, 
when my station took first place low power US/VE in both the CW and SSB.  Both 
set the current records for that class.

We are not just talking geographical advantage, we are talking two sets rules 
to operate by in the contest.  There is one set of contest rules for VE and 
one set for W/K.  

For 2004 I did 40 only in both contests.  But, does anyone here actually 
think that I would have had  any chance against a well equipped VE station who 
decided to go 40 SSB only?  His contest rules state, he can operate 7040-7100 
7150-7300.  My contest rules state I can only operate 7150-7300. That's fair? 
 I don't think so.  It's like trying to be competitive in a 20 meter DX 
contest with a general class license limited to 14225 and above.  Except, the 
general class guy can upgrade.  We, who are extra class, can't upgrade to the 
frequencies the VE guys have.  We are stuck with different rules for the 

There are two ways to fix that......allow only 7150-7300 for all W/VE.  Or, 
list the results and the corresponding plaque winners in two separate 
classes......VE and W.

Bill K4XS
CQ-Contest mailing list

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