How can I disguise this so readers won’t know what’s on my mind?

I don’t really know, so I’ll just launch into it directly.

I check in to four nets every week, and sometimes five. What follows is evident on all of the nets, and even in ordinary QSOs.

The other day, during the early check-in part of the net, when the NCS asked for a clarification of one fellow’s CALL, there was a pause, and a “Gent” called in and said, “Late check in. This is xxxxx.” The “Gent” had not been listening or paying attention. Poor operating.

About the same thing happens when the NCS acknowledges a list of calls and unkeys his mike. Or he has just received a correction for his list and unkeys. He didn’t say, “standing by for more check-ins.” He just unkeyed. Here comes “Hustle Harry” with his call. Was he listening to what was going on? Poor operating.

Here’s another one. NCS asks for a repeat of one’s call to clarify. “Quicky Quentin” gives his call, at the same speed he did earlier. Still not clear or understood by the NCS. Let’s try a third time! You guessed it. “Quentin” comes back with his own brand of phonetics, just as quickly as he gave his call the first time. NCS says, “Thanks for checking in “Quicky Quentin” and never mentions the guy’s call. He never was able to make it out. Poor operating.

BTW, some years ago FCC said the proper phonetics were and are the standard list. FCC said the many “cutsie” phonetics we all have are not legitimate for satisfying the regs about IDing. Poor operating.

Next, I’ve heard this one too often. NCS says, “Is there any other business for the net”? “Impetuous Ivan” gives his call and proceeds to make his announcement, without being acknowledged by NCS. Poor operating.

“Illiterate Irene” doesn’t know into which group of the alphabet her suffix belongs. The NCS says, “Check-ins from Alpha to Mike.” “Irene” checks in with xxØWxx. ‘Nuff sed! Poor operating.

Another personal “favorite” of mine before I get off the soapbox, is a matter of clear speech, when the calls include a “Z” and it sounds more like “C”. Some wonder why another op can’t get the call right. (All those “E” sounding letters are often difficult to understand … B, C, D, E, G, P, T, V, Z).

That’s all for this time. I’ll be listening to those nets hoping you do too, and learning about good and poor operating.

73

SOME ITEMS FOLLOW FROM THE BAILEY HUNDO ON 6/19/10

1. USE “TAC” CALL (IF ASSIGNED) AND INCLUDE OWN CALL SIGN AS OFTEN AS NEEDED TO STAY LEGAL … (AT LEAST EVERY TEN MINUTES).

2. WHEN THE NET USES MORE THAN ONE FREQUENCY AND WHEN CALLING MENTION THE FREQ BEING USED … “NET CONTROL , WØXYZ, ON .895…”

3. BEING AWAY FROM YOUR RIG MEANS LETTING NCS KNOW WHEN YOU LEAVE EVEN FOR A FEW MOMENTS AND WHEN YOU COME BACK.

4. BEFORE CALLING ANOTHER (NON NCS) STATION SEEK NCS PERMISSION TO “GO DIRECT TO ….”

5. BEFORE RELAYING TRAFFIC BE ACKNOWLEDGED BY NCS (OR ANOTHER STATION) BEFORE PROCEEDING. DON’T JUST START TALKING.

6. BEFORE SENDING TRAFFIC, ESPECIALLY NUMBERS, WAIT FOR RECEIVING STATION TO SAY HE/SHE IS “READY TO COPY”.

7. RECEIVING STATION SHOULD CONFIRM TRAFFIC (ESPECIALLY NUMBERS) RECEIVED FOR ACCURACY.

9. TALKING TOO FAST WASTES TIME. YOU’RE NOT ALWAYS UNDERSTOOD, WHICH MEANS HAVING TO REPEAT, WASTING TIME AND THE POSSIBILITY FOR MISTAKES IF NOT ASKED TO REPEAT.

10. TALKING TOO LOUD OFTEN PUTS YOUR SIGNAL OUT OF THE PASSBAND OF YOUR RIG AND/OR REPEATER INPUT, CAUSING DISTORTION. TALKING MORE LOUDLY DOES NOT MAKE UP FOR A WEAK SIGNAL TO THE REPEATER OR OTHER STATION. IT MAKES THINGS WORSE.

11. DON’T HESITATE TO TELL A STATION HIS/HER AUDIO IS TOO LOUD OR TOO WEAK COMPARED WITH OTHER STATIONS.

12. LISTENING TO OTHER NETS, EMERGENCY AND OTHERWISE, IS GOOD LEARNING FOR BOTH GOOD AND BAD PRACTICES. LEARN THE DIFFERENCE. HAVING A HAM LICENSE DOESN’T MAKE ANY OF US EXPERT.

ADMITTEDLY THERE ARE MANY OTHER PRINCIPLES WHICH SHOULD BE OBSERVED, ESPECIALLY IN ARES SITUATIONS.