Local Nets
In my area, I check into three local CW nets almost every night. These nets occur between 7:30 PM and 9:00 PM local time which works well for me as I am already at my shack desk either playing radio or purusing some other hobby.Utah Code Net
This net meets daily at 0130Z on 3570 KHz +/- QRM. It is intended as a training net and is listed as a Slow Net on the FISTS website. A great deal of information on this net can be found here.Mountain States Net
This net meets daily at 0200Z on 3570 KHz +/- QRM. It is intended as a training net and is listed as a Slow Net on the FISTS website. A great deal of information on this net can be found here.Traffic Routing - Follow The Traffic
Traffic accepted by this net is taken by another amateur checked into the net. This may be the intended recipient as is often the case with simple net reports. Otherwise, the traffic is "bumped up" to the next higher level.In the case of the Utah Code Net or the Mountain States Net, the next higher level net is the Twelfth Region Net (TWN). TWN covers the states of Arizona, Colorado, New Mexico, Utah, and Wyoming. TWN is part of an even higher level net called the Pacific Area Net.
Suppose, for example, W7YV (that's me) has traffic for a non-amateur (3rd party) friend in Colorado. Here is how it might work:
- W7YV checks into the Utah Code Net and lists traffic for the Twelfth Region Net.
- W7YV is told to standby while the NCS continues to call the net.
- Another amateur, W7DML, checks in.
- The NCS knows that W7DML routinely checks into the TWN. The NCS directs both W7YV and W7DML to go "up 5" to handle the traffic. When this is completed, W7DML now has the traffic and will (most likely) check into the TWN CW net later that night and pass the traffic.
- The procedure with TWN works the same way. W7DML checks into TWN and, if another amateur checks into the net that is known to handle Colorado traffic, then the NCS of TWN will direct them both to handle the item.
What happens when it doesn't work that way? Well, there are many different scenarios - far too many to explain in this short article. It does happen, sometimes, that there is nobody to pick up the ball and run with it.
The key to making the system a success is that the operator the receives a piece of traffic has only three choices: (a) dispatch the traffic to another amateur for handling; (b) deliver the traffic directly to the intended recipient; or, (c) send a "service message" back to the originator that the message could not be delivered.
If the operator chooses to "drop the traffic," then he or she isn't really a qualified traffic handler and ought not be pretending to be one.
