Communications Ch-ch-ch-ch-Changes

[Eclipse]

Word is the specialty tracks will be updated soon as well, your best bet is just to turn and face the strange...

All dated today:

CAPR 100-1
http://members.gocivilairpatrol.com/media/cms/R100_001_162D77B8183A1.pdf
"revises guidance on communications plans, exercise
planning, and communications reports; eliminates 180 day deadline for ICUT skills evaluation;
expands guidance about spectrum management; requires updating of the online repeater directory
to reflect sites in and out of service; addresses communications program leadership development;
clarifies networks, traffic types, and logs; defines broadcast traffic; introduces the concept of
calling channels; provides details about emergency communications; addresses inter-operation
with military units; updates guidance about use of amateur radio by CAP members; addresses use
of Part 15 devices such as WiFi; restricts ISR radio channels 10 and 11 from use by CAP; clarifies
methods for CAP support to other agencies; expands guidance about use of memoranda of
agreement; adds compliance items as attachment 1; and moves definitions of terms to attachment 2"

CAPR 100-3
http://members.gocivilairpatrol.com/media/cms/R100_003_4C83447E87350.pdf
"Divides former Chapter 2 into separate chapters about communications procedures, NET operating
procedures, and formal traffic procedures. Aligns mission statement with CAPR 100-1. Clarifies
descriptions of radio NETs. Revises guidance on precedence designators. Updates guidance on
logging. Expands and clarifies NET and formal traffic procedures. Adds guidance about constructing
formal traffic, including use of military block printing, group counts, and message numbers.
Clarifies the roles of roll calls and ops normal checks. Adjusts proword list and rules for transmitting
punctuation. Adds new attachments."

CAPF105 (apparently this has "issues")
http://members.gocivilairpatrol.com/media/cms/F105_85BEE46AF31EF.pdf

CAPF 105A
http://members.gocivilairpatrol.com/media/cms/CAPF105A_6_APR_2016_16C8DBEC25A3B.pdf

[JeffDG]

My concern with this regulation is now "communications managers" (a term defined nowhere in the regulation), can direct subordinate commanders to modify communications plans with a 30 day deadline.

Staff does not direct.  Hell the Region DCS-Communications doesn't have the authority to direct the Wing DC to the men's room, and certainly shouldn't have the authority direct the Wing Commander to rewrite a document.

2.5. Review of Annual Plans. Communications managers at each level may direct revision of plans from subordinate units.

[lordmonar]

Staff officers direct all the time.

It is called functional authority.

In this case the functional authority is granted to the communications managers by the national commander when he approves the regulation.

Sorry.   That dog don't bite.

Next.

[SarDragon]

CAPF105 (apparently this has "issues")

http://members.gocivilairpatrol.com/media/cms/F105_85BEE46AF31EF.pdf

How so?

[Eclipse]

CAPF105 (apparently this has "issues")

http://members.gocivilairpatrol.com/media/cms/F105_85BEE46AF31EF.pdf

How so?

Don't really know - the Wing  DC said they were aware of issues with it so stop telling them about it.
It opens and looks fine to me in Chrome.

It's a Comm form, maybe it won't open on a VIC-20

[Brad]

Loads fine for me.

See you all after the weekend once I have a chance to read through all this, lol!

I'm just bracing for the mountain of corrections coming my way probably. Turned my annual comm plan in the other day under the old regs. That and the other problem of redoing all my callsigns.

[Eclipse]

the other problem of redoing all my callsigns.

That was mentioned, too.  Is that for all stations or just VHF. My wing just went an re-licensed everybody.

[Brad]

the other problem of redoing all my callsigns.

That was mentioned, too.  Is that for all stations or just VHF. My wing just went an re-licensed everybody.

The shift from 4 digits to 2 digits is for HF only thank God. Does still raise the question of "first numerically siuffixed" for ones greater than 10 though, like 410 vs 411.

7.13.1:

...The suffix number for VHF and ISR will not exceed four digits and HF will not exceed two digits. The first numerically suffixed tactical call sign shall always be assigned to the commander, including blocks of call signs assigned to groups and subordinate units.

[Eclipse]

My wing hasn't been assigning blocks, since people are too transient / circularly assigned.
(Other then the double-digit ones go to Wing).

We do very little comms that would use that scheme in a meaningful way.

Everyone knows who "wing001" is, but beyond that, it doesn't really matter on the nets, and tactically they change anyway.

[SarDragon]

the other problem of redoing all my callsigns.

That was mentioned, too.  Is that for all stations or just VHF. My wing just went an re-licensed everybody.

The shift from 4 digits to 2 digits is for HF only thank God. Does still raise the question of "first numerically siuffixed" for ones greater than 10 though, like 410 vs 411.

7.13.1:

...The suffix number for VHF and ISR will not exceed four digits and HF will not exceed two digits. The first numerically suffixed tactical call sign shall always be assigned to the commander, including blocks of call signs assigned to groups and subordinate units.

Does your wing have more than 90 HF stations? I know my wing doesn't. There might be a little a little inconvenience initially with the 2-digit call signs, but ours are mostly assigned by position, and not to specific individuals, so I don't think it will be a huge deal.

As for the "first numerically suffixed tactical call sign" business, I'm guessing it will be 411, using your example. Having four digits available will allow more convenient usage of blocks, although I'm not a big fan of that scheme. We have a half-assed attempt of that in place now, and when we have a local mission, there are too many call signs with 7's and 5's for me to easily keep track of. We have 127, 357, 455, 755, 575, 550, and a couple of others I don't specifically recall, in use locally.

[JeffDG]

Staff officers direct all the time.

It is called functional authority.

In this case the functional authority is granted to the communications managers by the national commander when he approves the regulation.

Sorry.   That dog don't bite.

Next.

Can you cite one other CAP regulation that vests power to direct Wing Commanders in Region Staff?

[JeffDG]

Everyone knows who "wing001" is, but beyond that, it doesn't really matter on the nets, and tactically they change anyway.

Most folks know the 1-4, but very few knew what 5 was for.  I guess now we only have to static assign 1

[avguy]

Staff officers direct all the time.

It is called functional authority.

In this case the functional authority is granted to the communications managers by the national commander when he approves the regulation.

Sorry.   That dog don't bite.

Next.

Can you cite one other CAP regulation that vests power to direct Wing Commanders in Region Staff?

CAPR 20-1 15(a)?

[tribalelder]

Reg Change means end of an era--Member owned equipment -- those legacy Taits, vertex's, ht-1000's soon gone --VHF nets to p-25.

Sad day for a guy who learned to solder building his first CAP radio from an Allied Radio Knight Kit. (It was on 26.620)

[PHall]

Reg Change means end of an era--Member owned equipment -- those legacy Taits, vertex's, ht-1000's soon gone --VHF nets to p-25.

Sad day for a guy who learned to solder building his first CAP radio from an Allied Radio Knight Kit. (It was on 26.620)

Raise your hand if you have assembled a Heathkit HW-18 (aka the Hot Water 18).

[Holding Pattern]

Who do I forward typos to?

[JeffDG]

Who do I forward typos to?

Your commander.

[LSThiker]

Who do I forward typos to?

Your commander.

From having conversations with Jeanne Stone, the publications manager, she has stated that members can go direct to her for typos.  She can change those without having to go through the approval process.  Nevertheless, it is always best to talk with your commander to at least inform him/her of your actions.  Of course, it would be best to collect all typos and send one email as opposed to numerous multiple emails.

[SarDragon]

Reg Change means end of an era--Member owned equipment -- those legacy Taits, vertex's, ht-1000's soon gone --VHF nets to p-25.

Sad day for a guy who learned to solder building his first CAP radio from an Allied Radio Knight Kit. (It was on 26.620)

I only see a recommendation, not a requirement, for P25 on nets.

[Eclipse]

I only see a recommendation, not a requirement, for P25 on nets.

And only an indication that the burden of compliance is on the member for privately owned
equipment, and that CAP encryption keys will not be loaded on them, which is reasonable since
the idea of encryption is that it be secure.

There is plenty of legitimate CAP activity which doesn't need encryption and would be appropriate
for PORs. Air shows, encampments, bivouacs, and general practice.

On ES and other similar activity, it serves no purpose for the general public to be able to
listen in, and while this won't 100% prevent it, there's also no reason for CAP or the USAF to
actively support it, either.