[CQ-Contest] Malicious Interference during SS

[Ed K1EP]

Although I didn't encountered that jammer, I was nearby on 14.277 
from about 1327Z to 1416Z.  Earlier, I did receive what I thought was 
intentional interference around 0530Z on 7.207.   I had been running 
on 7.207 for about an hour at the time.  I had a small pileup going 
and as I recall, two CA stations called me at once.  I worked the 
first station and was attempting to work the second station when all 
of a sudden there was a strong and incredibly wide non-voice signal 
that wiped out my receiver.  The signal came out of no where and 
persisted.  Apologies to WK6I who I was trying to work, but there was 
no way that I could hear anything.  After a couple of minutes of 
incredulous listening, I moved on.

At 11/22/2008 05:00 AM, Jiri Culak wrote:
>Hello Rich
>
>BTW: I suffered in CQ WW exactly the same and it was east coast station
>around 14.275
>I have seen some spots about other guys complaining and the station
>would not give out his callsign either.
>
>73
>Jiri M0ITY
>
>Kind regards
>
>Jiri Culak
>
>LWSS Ltd.
>
>13 Robjohns Road
>
>CM1 3AG - Chelmsford
>
>tel. 01245 251 500
>
>jiri at lwss.co.uk
>
>  LWSS Logo
>
>-----Original Message-----
>From: cq-contest-bounces at contesting.com
>[mailto:cq-contest-bounces at contesting.com] On Behalf Of Richard Thorne
>Sent: 20 November 2008 23:40
>To: cq-contest at contesting.com
>Subject: [CQ-Contest] Malicious Interference during SS
>
>I'm curious how the malicious interference was this year.  I operated at
>
>K5NA this year.  I had a major problem around 14.281 this year.  I was
>sucked into a conversation with a station who would not use his call
>sign.  He told me that I was splattering so I adjusted my mic gain and
>compression.  The ham thanked me and said it was fixed.  After a few q's
>
>he said I was splattering again, I figured out he was playing games.
>Soon after he was transmitting recordings of my cq's.  I was able to
>work through it for a while but my rate suffered so I ended up moving.
>
>In this particular case it was at the beginning of the contest.  I had
>made a few qso's about starting 15 minutes prior to the contest so I had
>
>established that the frequency was not previously used and there were no
>
>frequency conflicts.
>
>So how did it go for every one else this year?  I guess in the future I
>need to add 14.280 to the list of  frequencies to avoid.  The sstv
>window has been on my list for quite some time.
>
>Rich - N5ZC