WQ6X Works Another W00LY 160-Meter Contest

This year's ARRL 160-meter contest came out of nowhere - literally - on Thursday, N6KI put the call out for operators.  The only OPs available were Dennis, WM6Y (Phil), N6CY (Rick) and me - WQ6X.  When my 1st operating shift came up (12:30am to 4:00am), most of the 225 "routine" stations were already in the log, while East of California, most OPs were still SnooZing soundly.

Middle-of-the-night contests require accommodation of S&P (Search & Pounce) in between frequency-running to alleviate the Boredom (bore-dumb) Factor.  The recent addition of the self-spotting-allowed rule in some ARRL contests makes for a slight improvement in QSO-rates during frequency runs.  Otherwise, it takes two CQ calls be-4 the RBN (Reverse Beacon Network) stations report/update the CQ's to the internet spotting servers.

After 4 frustrating hours I managed to add a WHOPPING 36 QSOs to the log, altho JA3 and V31 mults were 2 of those log entries.  Ironically, to work VE6 and a K8 (Mi) station, the best signal levels were made by pointing the Tri-square array to the WEST - GO Figure).  (Recent update: being that the Tri-square has been "broken" in the past, the assumption is currently being made that the phasing-cable system is out of "calibration".)

On the following Monday morning, looking back on the weekend, I found it amazing that I/We managed to accomplish what We DiD, when We DiD It as Well as We DiD!  While dealing w/the
solar CME that delivered a glancing-blow to the F-Layer of our atmosphere certainly created a signal challenge, the REAL Difficulty (and has been increasingly so in the last 6+ weeks) are the purposeful MIS-SPOTS being sent to the DX cluster(s).  

At first, I thought it was some sort of server glitch until some of the mis-posted callsigns were "too cute" to have been accidental or algorithmic mistakes.  A not-insignificant amount of operating time was spent deleting those entries from the call lists and bandmap(s).  If I knew what the CORRECT callsign should be, I would spot it properly (and trust that other OPs will do the same for me).
This egregious behavior has prompted me to send an e-mail to the ARRL contest coordinator
(Sean Kutzko) asking what can be done about this, and, can the offenders in some way be sanctioned.

Soapbox comments from the submitted logfile can help fill-in some of the technical details:

In the end, the ARRL 160 contest turned out to be an embodiment of a number of different
operating-factors to navigate thru in order to get the message out.  Unlike most contests,
the ARRL 160 & 10 meter contests are JUST that - single-band events; altho the 10-meter
GiG can be run mixed-mode (Cw and Ssb), whereas the 160-GiG is Cw only (altho the CQ-160
contests run a different weekend for each mode).  No matter which mode, we run in a single-band contest, whenever the band is not happening (for whatever reason), there's nothing left to do but Sit, Twiddle-our-thumbs, call CQ and Wait.

When it was all over, NX6T put 477 QSOs in the log (77 made by WQ6X).  Running as WQ6X
(from the EB section), 23 QSOs made it into the LoG - just enough to say "I Wuz THERE!".

To get a sense for some of the technical details about the WQ6X operation, the 3830 Soapbox comments say it best:

Did YOU work the ARRL 160-meter radiosport contest?

Is NX6T or WQ6X in YOUR LoG?