The SET session went well. My wife had to work late, so I was able to get on the local VHF net which is affiliated with the NTS, in order to pass on our SET report. Admittedly, it's been years since I have handled any traffic. However, I was very active back in the 80s, serving for a long time as a NCS of the very traffic net I checked into. In fact, I was assistant to the Net Manager for quite a while there, also. So while I'm rusty, I'm no neophyte to traffic handling.
Here's the sticky part. I made my message as brief as possible, but it still came to a check of 27. And I got to listen about it. Yes, I understand the ARRL message form has lines for 25 words, but c'mon, really?
These messages were local in scope and weren't bound for the Second Region Net or anything like that. And it was only two stinkin' words over. You're going to give me flack for that? I hate to sound like an old crotchety curmudgeon, but back in the day, we sometimes handled messages with checks as long as 30 or even sometimes 35 words. And if some evening, you're lucky enough to get a ton of check ins, you're not going to send a net report because it would be over 25 words?
Seems to me the NTS should be begging for traffic, not making remarks so that people couldn't be bothered.
72 de Larry W2LJ
QRP - When you care to send the very least!
My response to the complaining NCS would have been "W2LJ - clear" and turned off the rig
ReplyDelete