“The CQ World Wide DX Contest Committee is making a concerted effort to crack down on cheating.
After disqualifying more than 50 logs from the 2014 contest and banning one station from competing for the next five years due to alleged “log padding” – or adding contacts that were never made – the committee said it would test new software designed to detect the practice by running it on all logs submitted in the past four years.
Any logs that show evidence of adding unverifiable QSOs will be dealt with on a case-by-case basis, according to a post on the CQWW blog by Contest Director Randy Thompson, K5ZD. See August CQ‘s “Contesting” column for an in-depth discussion of honesty and cheating in contesting.”
Source: CQ Newsroom
“Hi folks, I’ve had many questions since I started my YouTube channel awhile back on how to operate Ham Radio out in the field. The 3 prim... Read more
Located in the South China Sea just west of the Philippines, Scarborough Reef is without a doubt the rarest and most controversial entity on th... Read more
The RSGB Awards Manager has reviewed the current 50MHz awards offered by the Society and concluded that the existing 50MHz 2-Way Countries a... Read more
The JUENTAI JT-UV6DR is a compact hand held transceiver providing 4 watts in the frequency range of 136-174 MHz and 400-480 MHz. – The JUENTAI J... Read more
“How does the SunSDR2 PRO perform in a multi operator contest environment? We wanted to test the PRO in the toughest possible environment, a mul... Read more
New Band For ZS Hams Sharp-eyed Roger, G3XBM, has brought attention to the recent news of a new amateur allocation granted to South Africa’s ama... Read more
Paradan Radio Antenna Disconnect Reduce the chance of station equipment damage from lightning or static charges. The Antenna Disconnect automatically... Read more
: file_get_contents(https://plusone.google.com/_/+1/fastbutton?url=https%3A%2F%2Fqrznow.com%2Fcq-ww-contest-committee-to-review-past-entries-for-evidence-of-cheating%2F): failed to open stream: HTTP request failed! HTTP/1.0 404 Not Found
on line 151