Net Control Script for Field Day

Listed below is the script to be used for the Field Day sessions of Central Ohio Traffic Net.

Checklist for Net Control operators:

  1. Please be sure to start the net on time. Check with WWV, United States Naval Observatory Master Clock, or another accurate source for the correct time.

  2. Be in position and start preparations five minutes before the start of the net.

    1. Have the operating schedule in front of you so you know whether to expect assigned liaisons or if you should expect to take realtime volunteers. Beware that you might have multiple liaisons, those bringing traffic to this net (transmitting, "TX") and those receiving traffic from this net ("RX") to the liaison. Where TX or RX aren't specified the station should liaise both directions.

    2. Move stations off frequency to pass traffic when possible. Be sure that you have COTN's Standard Operating Procedures (SOP) and know the Signal Operation Instructions (SOI) in that document so you know where others will be prepared to operate.

  3. Do not forget to draft your session report immediately at the conclusion of the net. See that you submit the report online in accordance with By-Law 9. If you cannot submit the report online yourself, send the report by radiogram to another station who can submit the report online for you. Either way, you will receive a confirmation by radiogram, reporting the figures entered into the system. If you do not receive confirmation or the figures are wrong, contact the Operations Officer or Net Manager to ensure the correct data are recorded.

  4. Remember that Field Day will bring operators who are unfamiliar, untrained, or unpracticed with handling traffic. Be patient and encouraging, moving them off frequency to move traffic where possible so there is no particular time pressure and an experienced station can receive the traffic and help them through the process, all while keeping the net productive on the control frequency.

Script for Net Control:

The # symbol means drop carrier. Also, remember to identify the net every 10 minutes. ("This is the Central Ohio Traffic Net, (your call) is net control.")

This is the Central Ohio Traffic Net, a part of the Ohio Section of the National Traffic System. We meet daily to handle traffic. This is a directed net and net control will control the net. Your net control is (your callsign), my name is (your name), and I am located at (your location). Our standard operating procedures are available online at I will call for stations in order, first I will call for assigned liaisons, then stations with traffic. Where possible I will direct movement of that traffic off frequency, and will continue to call for stations with traffic. Before we begin, is there any emergency or priority traffic? #

If any traffic is listed here, call for a station to help pass the traffic listed.

Ohio Single Sideband Net Liaisons? #

Record any OSSBN liaisons and traffic (if any).

Buckeye Net Liaisons? #

Record any BN liaisons and traffic (if any).

Winlink Liaisons? #

Record any Winlink liaisons and traffic (if any).

Any Other Liaisons? #

Record any other liaisons and traffic (if any), as well as which group, station, or net they're representing.

Stations with traffic only. Answer with your callsign in standard speaking alphabet. When I acknowledge you and ask you to "list traffic," please indicate where your traffic is headed and how much. If you do not hear me say your callsign, wait until I call for stations with traffic again and wait for acknowledgement. #

Record all stations and their traffic. Repeat this as often as is needed.

If you have traffic listed and an outlet for it (such as a liaison), then determine where you need them to exchange traffic (use the SOI, see SOP), ask the receiving station if they can operate on the frequency/repeater that you intend, if so, do the same for the sending station, and if both can work there, use the procedure "??8RX [receiving station full callsign or unambiguous suffix] take ??8TX [sending station full callsign or unambiguous suffix] to 2C2 [or wherever you just confirmed] to receive 1 [or whatever number of] message[2], both return to this frequency after traffic is passed or if contact cannot be established." Give both stations time to acknowledge. Receiving station should answer "Going, ??8RX" [full callsign] and after that, sending station should do the same.

Stations with or without traffic, or returning stations? #

Record all stations and their county. Repeat the call until you have no answer and move on to the next item.

Try to pass traffic going to the SNL first, and try to send all traffic closer to its intended location (e.g., traffic for Gahanna should go to a Gahanna or Northeast Franklin County station, if possible). Rather than making an open-ended call for a volunteer for the traffic, find a station nearby and ask the station "Will you take Gahanna traffic?" If the station is hesitant, offer to find a helper, an experienced operator who will copy the traffic along and answer any questions the newer operator has.

Move traffic using the "if you have traffic listed and an outlet for it" procedure above. Remember Field Day operators are generally trying to make contacts for points, so get their traffic and excuse them from the net as expeditiously as you can. If a liaison station is on frequency and can hold traffic for later in the same session rather than taking it to the other net, direct the liaison to do so, allowing the Field Day operator to return to making contacts, and keep the traffic listed, but now it is "on" the liaison's station and must be passed again for relay toward delivery if the liaison station is not the right outlet.

Any announcements and IF requests should be handled after all traffic is passed (unless the IF deals with a specific piece of traffic).

Once all traffic has been passed, make the announcements that you prepared before net from the COTN Announcements and Event Calendar, one at a time. After each one, confirm that the announcement was understood. ("Any questions or comments on the announcement?")

All traffic and business brought to the net has been taken care of. Is there any more business for this session? #

Take care of any additional business listed. After everything is done, excuse each non-liaison station from the net, and make the net "free" using the voice procedure "THIS NET IS FREE." The net is still in session, and stations not excused are still in the net, but the frequency is open for any amateur operation, e.g., if a station comes to the frequency expecting to move traffic, someone will be there to do the job. If the frequency starts to get busy, you may at any time return the net to directed status using the voice procedure "THIS NET IS DIRECTED."

You should close the net at (a) the top of the hour if there is no traffic pending, (b) just before the start of the next scheduled net session if there is listed traffic so the next net control operator can handle it, or (c) when the net is clear of traffic if it's after the start of the next hour and before the start of the next scheduled net.

The Central Ohio Traffic Net is closed at (local time). Thanks to everyone who participated, especially those who brought or took traffic.

Thanks to the

If using 146.97, Central Ohio Radio Club

If using 146.76, Central Ohio Radio Club

If using 52.70, Central Ohio Radio Club

If using 147.24, Capital City Repeater Association

for the use of this repeater. Please check us out on the web at WWW.COTN.US. (your call) is clear after a control function. #

When compiling your net report, use the number of minutes from the calling of the net to the end of the traffic handling -- the time that you announced. Please submit your session report as soon as you can using the online form if you can. If you cannot, find someone to take the report for you for submission to the web site.