Lyttelton Times announces regular meetings to practice church music. We’re piecing together this timeline and would like your help.If you’re able to supply new events or dates, or add to the information we already have, let us know. And in all Battlegroups, individual Regiments or Battalions could be detached to deal with low-level insurgency or a specific focused target, or to support a Navy operation-although Imperial tactical thinking did restrict the use of Armor Regiments to full-scale Battlegroup offensives.A timeline of key events in Christchurch’s musical history. For instance, the 1st Tapani Assault Battlegroup at Tallaan were the primary Imperial Army presence in Tapani sector, representing a largely defensive deployment that due to political considerations nevertheless warranted a Major General in command. 3ya grvad battle group build full#Of course, not all battlegroup deployments were for offensive operations, and not every operation required a full battlegroup. Imperial battlegroups were usually deployed in full strength in situations where a sizeable enemy force had to be destroyed in the field: they were capable of stand-alone operations where a well-organized military resistance controlled an area of a planet, and they also served as the primary tactical subdivisions of a Corps deployed for a full-scale planetary conquest campaign. The Galactic Empire used the term for both naval and army units. In the Confederacy of Independent Systems, the name was applied to units within ground armies, though these often had fleets attached to them for galactic deployment with which the name was used in conjunction. It was most commonly used to denote groups of naval flotillas, commonly grouped fleets, and in a few cases, such as in the Republic Navy during the Clone War, referred to specific fleets themselves. The wing had forty pilots, twenty-five sensor techs, twenty-five controllers and one hundred and ten ground crewmen. These wings were also stationed in prefabricated garrison bases. Six flights made two squadrons of TIE/LNs, while three flights made a TIE bomber squadron and one flight of TIE/fcs served as spotters. The result was this downsized wing of 40 TIEs organized into ten flights. The Army insisted on its own wing of support fighters for ground missions, while the Navy wanted to keep control of its TIEs. The Plescinia Entertainments CS-Mark 10 allowed players to control full assault groups while playing the Great Battles of the Empire series. Ī battlegroup could also be augmented per their Order of Battle (OB), in which case the additional units were commanded by the battlegroup's second-in-command. In addition there were 188 support personnel and two security platoons of 76 troopers for a total of 274 personnel. A Battlegroup had the usual principle staff of five officers (SG1 to SG5), but in addition the SG5 (Battlegroup "Headquarters" officer) had a 4-man "substaff" (SG51 to SG54). Ī Battlegroup's commanding officer (CO) was typically at least a High Colonel, although it was possible for the CO to be as senior as a Major General (the 1st Tapani Assault Battlegroup based on Tallaan was one such example). During the first years of the Empire, a Battlegroup was composed of 8,192 troopers, and was composed of four regiments. A Battlegroup was committed only for major offenses against a known concentration of enemy resistance. Although precise numbers varied depending on the specific type of unit, the overall strength of most Battlegroups was on the order of roughly 15,000 men, including a little better than 10,000 front-line troops. 2.5 Rebel Alliance/New Republic/Galactic AllianceĪ typical Imperial battlegroup consisted of four Regiments, and four Battlegroups in turn formed a standard Corps.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |