With all due respect, Dave, but if you made even a single contact in the
contest with high power, you you should claim your category High Power. If
your buddy visited you during the contest and made a single contact while
you went to toilet, it is Multi Operator category.
Since frequencies in Yuri's log were recorded, contest sponsor could mark
contacts "outside the allowed frequency" as zero point ones. People who
worked him lose nothing, who loses is just him. IMHO this approach would be
better than DQing!
73 Mirko, S57AD
2012/6/24 David Gilbert <xdavid@cis-broadband.com>
>
> <snip>
> What if I start a contest operating high power and then decide after two
> hours that propagation is so good that I want to switch to low power? I
> can't just delete the early high power contacts from my log because that
> would give a bunch of other participants a NIL and probably get my entry
> flagged as unstable, so should I expect the sponsor to delete them for
> me just so I can jump categories?
> <snip>
>
>
> On 6/23/2012 10:37 AM, Mirko S57AD wrote:
> > I recall that some 25 years ago JARL DQed well known JA club station
> (high
> > power) in AA contest CW for it was operated (beside A class operators) by
> > some ops with just 25W licence privileges.
> >
> > In the past, here in S5 (and in former YU) operators with lower licence
> > classes weren't allowed to operate bands or powers outside their licence
> > privileges, even in presence of operators with right (higher) privileges.
> >
> > Since violation of frequency privileges was discovered by frequencies
> > recorded in the log, the simpliest solution would be (IMHO) to remove
> those
> > Qs (thus reducing his score) rather than DQ him.
> >
> > 73, Mirko S57AD
> _______________________________________________
> CQ-Contest mailing list
> CQ-Contest@contesting.com
> http://lists.contesting.com/mailman/listinfo/cq-contest
>
>
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
|