RESTRICTED |
---|
29 AUG 23
| RGHQ-51 Operational Names Selector |
---|
IntroductionThis document serves three functions:
Operational TypesThe Corps conducts three broad types of operation, each covered by the award of a specific service medal as indicated:
"combat" here means actual warfighting against a hostile enemy with extreme risk to property, life and limb.
The Naming of OperationsOnly Flight Operations, that is those that contain actual off-world missions are accorded a name, which is normally selected at the annual intelligence conference, or at the end of the current Tour (calendar year), usually during the last operation, time permitting.The naming convention for operations conducted from RGHQ-51 here in the UK is to use the title of battles or sieges fought upon British soil. Table 4 lists the names of available events (white background), and those that have already been used (greyed out). To the right of each is the year(s) that the historical action(s) took place, followed in the case of used names, by the CON number and operational date. Table 2 is a complete record of all operations ever conducted by the Regiment, arranged in chronological order, detailing CON number, type/number, and date. As an aid year headings are included. Table 3 is an alphabetical record of the names of all Flight Operations, complete with their CON number and date. Operational Reference Tag ConstructionWith the exception of Flight operations which can be referred to just by their name, they and all others, use an Operational Reference or Op.Ref., this is the string of characters used to identify and describe any given operation. See Table 1 below for the elements used.The OpRef always begins with the CON number, made up of the word CON for CONTACT, a hyphon for readability, and 3 digits, for example: "CON-099". To this a series of suffixes are appended to transmit more information about the event. The suffixes are composed of 1~3 letters, a hash mark, and 2 numbers, the latter serving as a counter for the type. The exception is the CRE tag, which has 6 letters, separated by a hyphon, a hash mark, and 2 digits, see Table 1. The hash mark may seem unnecessary, however in a text rich with abbreviations, their presence helps identify the string as an Operational Reference. The suffixes are just stacked one after another, separated by a slash "/", ideally in order of importance to the operation, with the exception of the optional asterisk, which always comes last. The asterisk is added at the very end to denote a Flight Operation when its name is not known, or omitted for any reason, such as in 201 Personnel Files or the Awards Granted pages, where Op. names would simply take up too much space. Table 1: Operational Reference ElementsTBA = To Be Advised/Added: to be read as appropriate to context. |
|
BLANK
BLANK
|
BLANK
Events in greyed out entries with block capital text have already been selected. Only those with a white background are available.
|
BLANK
Top |
---|
End of Page
RESTRICTED |
---|