Based upon my readings and understandings, as well as, practical field communications, I propose the adoption of the following code usage when utilizing flags, torches, lanterns, and homographic signals.
1) General Service Code for alphabetical transmissions as listed in both Brown and Myer’s Manual. Which are to include the abbreviation and abbreviation rules to be applied. Although complete spellings of words of importance or which may be confusing should be compulsory to avoid confusion when sending messages of urgency.
2) Standardized Pre-Concerted Code adoption, based upon years of reenacting and scenario sequencing (of which I will work-up for a web review)
3) Medical Emergency Code Standardization
4) Stutter Code- for use as an event specific scenario sequencing or pre-concerted.
5) Signature Code- to identify stations, commands, or Unit identifications.
6) Ciphered Message or a change in code elements for use in tactical and drill communications only, by use of cipher-signal/key-adjustment.
All opening communications will be assumed to be in pre-concerted code (#2 above).
Alphabetical or GSC to be invoked by sending 22222 (five-two’s) (#1 above) and closed (back to pre-concerted) in the same.
Standard 3’s or 5’s usage as follows: 3= end word, 33= end sentence, 333= end message cease signaling.
Medical emergency code invoked by sending repeatedly until answered the pre-concerted combination 2112 . 2112 (M M Stutter), this code will then remain in place until a 333 is sent and confirmed.
Stutter Code: combination of letter doublets pre-concerted and sent alone, which carry the highest priority and be event specific for a pre-arraigned action or sequence to take place.
Signature Code: Numerals, which have been, event specifically identified to indicate signal stations, commands, commanders, unit identifications as deemed required by CSO.
These will typically be set-up with 1’s for federals and 2’s for confederate for fast identification. (ie. 1= fed command, 11=fed artillery, 12= General Smith/ 2=confed command, 21= confed artillery, 22= General Jones). Signature Identification for “TO” will be applied at the onset of the message by flagging signature followed by the signature code, then 3, followed by message body. Signature Identification for “FROM” will be made by flagging signature after message body followed by the signature code, then a 33, if more to follow, or 333 for end message. The use of which should be compulsory for all official aerial correspondence.
Ciphered Messages should never be used for open communications and its use confined for tactical or drill use only, when the messages are sent between parties completely versed and practiced in its usage, as it will prevent a broad communication effort which is our main thrust. It’s usage is to be invoked using a cipher signal/key adjustment and may be applied to a cipher disk, pre-concerted/Stutter alternative or a change in code elements usage (ie 3-element or 4 element codes). This done by using a pre-concerted key adjustment numerical code (single digit) sent followed by a 3, and then the cipher signal, indicating the shift or change, followed by 33, then the enciphered message.
I will be more than happy to write-up specifics for the above, if a general agreement on what is stated here is indeed acceptable for our usage. I don’t want to waste a lot of time writing specifics before some basics can be agreed upon.
Lets hash this out first, then the specifics…
Let me know…..