Sarna News: Bad 'Mechs - Icestorm

Editing 167th Phalanx (Clan Steel Viper)

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
 
{{infoBoxMilitaryCommand
 
{{infoBoxMilitaryCommand
| image = [[Image:Clan Steel Viper logo.png|191px]]
+
| image = [[Image:Clan Steel Viper.jpg|150px]]
| Designation = 167th Phalanx
+
| Designation = One Hundred and sixty-seventh Phalanx
 
| Formed =
 
| Formed =
 
| Disbanded = [[3073]] (Destroyed)
 
| Disbanded = [[3073]] (Destroyed)
Line 12: Line 12:
  
 
==History==
 
==History==
The '''167th Phalanx Cluster''' was stationed on [[Persistence]] in 3054.<ref>''Objective Raids'', p. 30</ref> It lost a [[Trinary]] of infantry to a raid by [[Clan Wolf]] in [[3056]] and had not recovered it by [[3061]].<ref name=FMWCp149>''Field Manual: Warden Clans'', p. 149</ref>
+
The '''167th Phalanx Cluster''' was stationed on [[Persistence]] in 3054.<ref>''Objective Raids'', p. 30</ref> It lost a [[Trinary]] of infantry to a raid by [[Clan Wolf]] in [[3056]] and had not recovered it by [[3061]].<ref name=fmwc149> ''Field Manual: Warden Clans'', p. 149</ref>
  
 
In [[3067]] the Cluster was stationed on [[Marshall]] and by this point had been upgraded to a Fang Cluster.<ref name=fmu80/>
 
In [[3067]] the Cluster was stationed on [[Marshall]] and by this point had been upgraded to a Fang Cluster.<ref name=fmu80/>
Line 27: Line 27:
 
| colspan="4" style="background: #efefef;" | '''Commanding Officers of the 167th Phalanx'''
 
| colspan="4" style="background: #efefef;" | '''Commanding Officers of the 167th Phalanx'''
 
|-
 
|-
| [[Star Colonel]]||[[Karol Breen]]||[[3058]]<ref name=FMWCp149/>
+
| [[Star Colonel]]||[[Karol Breen]]||[[3058]]<ref name=fmwc149/>
 
|-
 
|-
 
| Star Colonel||[[Petere]]||[[3067]] - [[3073]]<ref name=fmu80/><ref name=WoR124/>
 
| Star Colonel||[[Petere]]||[[3067]] - [[3073]]<ref name=fmu80/><ref name=WoR124/>
Line 34: Line 34:
  
 
==Tactics==
 
==Tactics==
The [[Galaxy Commander]] had given the order to the Star Colonel of the Cluster in the late 3050s to use all opportunities to secure victory. This included urban warfare, traps and other ''dirty [[Inner Sphere]] tactics''.<ref name=FMWCp149/>
+
The [[Galaxy Commander]] had given the order to the Star Colonel of the Cluster in the late 3050s to use all opportunities to secure victory. This included urban warfare, traps and other ''dirty [[Inner Sphere]] tactics''.<ref name=fmwc149/>
  
 
==Composition History==
 
==Composition History==
 
===3056===
 
===3056===
'''167th Phalanx'''<ref name=fmwc138>''Field Manual: Warden Clans'', p. 138</ref><ref name=FMWCp149/>
+
'''167th Phalanx'''<ref name=fmwc138> ''Field Manual: Warden Clans'', p. 138</ref><ref name=fmwc149/>
 
* 1 [[BattleMech]] [[Trinary]]
 
* 1 [[BattleMech]] [[Trinary]]
 
* 3 Conventional Infantry Trinaries
 
* 3 Conventional Infantry Trinaries
 
* 1 Aerospace Trinary
 
* 1 Aerospace Trinary
  
===3061===
+
===3057-3061===
'''167th Phalanx''' (Regular/Reliable)<ref name=FMWCp166>''Field Manual: Warden Clans'', p. 166</ref>
+
'''167th Phalanx'''<ref name=fmwc149/>
:CO: Star Colonel Karol Breen<ref name=FMWCp149/>
+
* 1 BattleMech Trinary
:* 1 BattleMech Trinary<ref name=FMWCp149/>
+
* 2 Conventional Infantry Trinaries
:* 2 Conventional Infantry Trinaries
+
* 1 Aerospace Trinary
:* 1 Aerospace Trinary
 
:Note: At this time the unit was stationed on [[Persistence]].<ref name=FMWCp166/>
 
  
 
===3067===
 
===3067===
'''167th Fang''' - Veteran/Reliable<ref name=fmu80>''Field Manual: Updates'', p. 80</ref>
+
'''167th Fang''' - Veteran/Reliable<ref name=fmu80> ''Field Manual: Updates'', p. 80</ref>
 
* 90% strength
 
* 90% strength
  
Line 59: Line 57:
 
In the late 3050s and early 3060s the Cluster suffers supply difficulties and must start a battle with only half standard ammunition loads.<ref name=FMWC185>''Field Manual: Warden Clans'', p. 185</ref>
 
In the late 3050s and early 3060s the Cluster suffers supply difficulties and must start a battle with only half standard ammunition loads.<ref name=FMWC185>''Field Manual: Warden Clans'', p. 185</ref>
 
</div>
 
</div>
 
 
==Notes==
 
==Notes==
* In 3067 the unit is listed as the 167th Fang, while this could simply be a mistake it could represent an upgrade in matériel for the unit and a change in designation. The cluster was rated at 90% strength.<ref name=fmu80/>
+
* In 3067 the unit is listed as the 167th Fang, while this could simply be a mistake it could represent an upgrade in material for the unit and a change in designation. The cluster was rated at 90% strength.<ref name=fmu80/>
  
 
==References==
 
==References==
 
<references />
 
<references />
 
 
==Bibliography==
 
==Bibliography==
 +
* ''[[Field Manual: Warden Clans]]''
 
* ''[[Field Manual: Updates]]''
 
* ''[[Field Manual: Updates]]''
* ''[[Field Manual: Warden Clans]]''
 
 
* ''[[Objective Raids]]''
 
* ''[[Objective Raids]]''
 
* ''[[The Wars of Reaving]]''
 
* ''[[The Wars of Reaving]]''
  
 
[[Category:Clan Steel Viper Commands|Phalanx, 167]]
 
[[Category:Clan Steel Viper Commands|Phalanx, 167]]

Please note that all contributions to BattleTechWiki are considered to be released under the GNU FDL 1.2 (see BattleTechWiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)

Advanced templates:

Editing: {{Merge}}   {{Moratorium}}   {{Otheruses| | | }}

Notices: {{NoEdit}}   {{Sign}}   {{Unsigned|name}}   {{Welcome}}

Administration: {{Essay}}   {{Policy}}   {{Procedure}}

Template used on this page: