[SCCC] SCCC Digest, Vol 194, Issue 21

[Drew Arnett]

Put me down for filling in some team that hasn't filled it's quota of
team members, as I won't turn in a large score.  Hope to play a bit in
the RTTY test.  Good fun.

Best regards,

Drew
kb9fko

On Thu, Feb 21, 2019 at 5:00 PM <sccc-request at contesting.com> wrote:
>
> Send SCCC mailing list submissions to
>         sccc at contesting.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://lists.contesting.com/mailman/listinfo/sccc
> or, via email, send a message with subject or body 'help' to
>         sccc-request at contesting.com
>
> You can reach the person managing the list at
>         sccc-owner at contesting.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of SCCC digest..."
>
>
> Today's Topics:
>
>    1. NAQP RTTY This Saturday - Call For Teams (Dennis Younker NE6I)
>    2. Re: W6TK - ARRL DX CW (Bill Haddon)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 20 Feb 2019 20:43:14 -0800
> From: "Dennis Younker NE6I" <NE6I at cox.net>
> To: "'Southern California Contest Club'" <SCCC at contesting.com>
> Subject: [SCCC] NAQP RTTY This Saturday - Call For Teams
> Message-ID: <003c01d4c99f$f7606620$e6213260$@cox.net>
> Content-Type: text/plain;       charset="us-ascii"
>
> The NAQP RTTY contest is this Saturday. If you'd like to be on an SCCC team,
> please let me know.
>
>
>
> Rules can be found here: http://ncjweb.com/NAQP-Rules.pdf
>
>
>
> I'll need:
>
>
>
> Your call:
>
> Call to be used in contest:
>
> Estimated amount of time on:
>
> Estimated number of QSOs:
>
>
>
> 73, Dennis NE6I
>
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 20 Feb 2019 21:14:40 -0800
> From: Bill Haddon <haddon.bill at gmail.com>
> To: Steve <k0xp at k0xp.com>
> Cc: SCCC Reflector <sccc at contesting.com>
> Subject: Re: [SCCC] W6TK - ARRL DX CW
> Message-ID:
>         <CAJsKOHTdhWgOXSsuH5purWTpwNf25A_66THSBzB4f=jn2i171g at mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> The V4 station I orignally flagged with the no-call-announcement syndrome
> did not have large pileups on Sunday afternoon.  The final reported score
> of 1.5M (22.5 hrs) could be compared with YS1/AA4NC (39 hours) of 3.5M in
> the same category.  AA4NC announced his call sign very very frequently.
>  Same for W6PH and really most other stations.
>
> Next time I'll deal with the situation more forcefully.
>
> Another point. . most of you have very reliable, fast internet connections
> .  in some rural locations, such as ours, it's  not always so pretty, and
> spots may not be available during a contest all the time.
>
> Thus I like the CQWW policy, whether operating assisted or otherwise.
>
> 73 Bill n6zfo
>
>
> On Mon, Feb 18, 2019 at 7:56 PM Steve <k0xp at k0xp.com> wrote:
>
> > At 09:44 PM 2/17/2019, Bill Haddon wrote:
> > >Still a rule would be useful,. .  so if I were to write to W3UL, I could
> > >cite the rule and say please don't do this.  But there is no rule for ARRL
> > >contests.
> >
> > He would just claim "But the pileup was causing me to have to do this
> > and that..." and nothing gets resolved.
> >
> > But honor in radiocontesting prevails. If enough folks ostrasize such
> > misbehavior in some personal way, the perpetuator eventually gets the
> > message. Merely talking about misbehavior, without mentioning
> > names/callsigns, on public forums can be sufficient notice to the
> > guilty. There are always those who can't believe folks might be
> > speaking of THEM, however.
> >
> > Steve, K0XP
> >
> > _______________________________________________
> > SCCC mailing list
> > SCCC at contesting.com
> > http://lists.contesting.com/mailman/listinfo/sccc
> >
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> SCCC mailing list
> SCCC at contesting.com
> http://lists.contesting.com/mailman/listinfo/sccc
>
>
> ------------------------------
>
> End of SCCC Digest, Vol 194, Issue 21
> *************************************