ARRL

Quote by N9HTZ

Quote by W3WN

Quote by N9HTZ

< snip >
However, last weekend, they started operating right on top of a 17M net that was in progress and refused to QSY after being asked. 17M wasn't included as a band to be used inthe contest but 17M was full of contestors.
< snip >
Really? Contesters on 17 meters? Are you sure it was hams operating in a contest, or was it something else... like DX'ers in a pileup for a rare station working split?

Don't suppose you can mention specific times, frequencies, or calls involved?

Quote by N9HTZ

< snip >
You have cited a clear and present danger caused by ARRL contestors that must be addressed and mitigated.

With all due respect, the MMSN has been sharing 20 meters with contesters on the weekends for decades. So with all due respect to Tom Clancy, this is hardly a "clear and present danger."

Most of those contests are not sponsored by the ARRL -- only three events (ARRL DX SSB, ARRL Sweepstakes SSB, and ARRL Field Day, which is not a contest) come to mind. This isn't an "ARRL" problem.

Is MMSN so inflexible that it is unable to adopt contingency plans in the events the band is crowded? If other groups can manage this, why can't they?

Sir, with all due respect, The QRM from contestors on the 14.300 Maritime nets was either drirectly on that frequency and/or very close frequencies, that goes a bit beyond sharing the 20M band with contestors. OK, no one can be linked to dangerous situation on that weekend because of contestors...this time.

Quote by N9HTZ

Since the17M OMISS net had moved from its normal 18.165 and I made no contacts in my log, I can't remember the exact frequency. I bellieve that it was 18.158 (?). However, the net started at 1900 UTC and the incidents occurred throughout the net and grew continually worse. The 17M band was literally full of contestors. However, the other fellow is claiming that I'm lying about this.