3rd Fang (Clan Steel Viper)

Clan Steel Viper.jpg
Third Fang Cluster
Disbanded 3075 (Destroyed)[1]
Affiliation Clan Steel Viper
Parent Command Rho Galaxy


The Third Fang was a second line cluster, after the Battle of Tukayyid it was composed primarily of test-down warriors from clusters that had fought in that battle. Few experienced warriors were willing to command the Third at this time, and its CO, Star Colonel Yvgeny, dealt with the shame of defeat on Tukayyid by turning to drink. Other warriors and technicians assigned to the Cluster also displayed a lethargy or masochistic streak that would have been out of place in a front-line Cluster.[2] [3] From or prior to March 3053 it was stationed on Benfled, but by 3060 it had been transferred to Jabuka.[4] [5] [3]

On March 24, 3053 the Third Fang was engaged by a Maskirovka unit posing as a Federated Commonwealth raiding party. The Viper warriors managed to drive their assailants off, though the Maskirovka agents achieved their objective of recovering a SAFE operative posing as a Clan technician.[3]

By 3067 the cluster had moved to New Kent.[6]

The final fate of the Cluster is not known, but they would not have survived the destruction of Rho Galaxy or that of Clan Steel Viper in 3075.[1]


Rank Name Command
Commanding Officers of the 3rd Fang Cluster
Star Colonel Yvgeny 3053 - 3067[3] [2][6]


In the 3050s the cluster was often opposition force during training cycles for the clusters of Alpha Galaxy. This gave the Cluster an advantage in defensive operations and they knew how to use Inner Sphere tactics against raiders with great effect.[2]

Composition History[edit]


Third Fang - Regular/Questionable [2]


Third Fang - Regular/Questionable [6]

  • 100% full strength with 85% of the force equipped with OmniMechs


  1. 1.0 1.1 The Wars of Reaving, p.149-150
  2. 2.0 2.1 2.2 2.3 Field Manual: Warden Clans, p. 147, "3rd Fang Profile"
  3. 3.0 3.1 3.2 3.3 Horn and Fang
  4. Objective Raids, p. 30
  5. Field Manual: Warden Clans, p. 168
  6. 6.0 6.1 6.2 Field Manual: Update, p. 80