FANDOM


Redgauntlet
VenatorTurbolasers-HH

Manufacturer

N/A

Built

2561

Dimensions

  • 1137m length
  • 548m (width)
  • 268m (height)

Propulsion

  • SFTL Engine
  • 4 Primary engines
  • 2 Secondary engines
  • 2 Tertiary engines

Armor

  • 1.3 meters Titanium-C
  • Energy Shielding

Armament

  • 22 70mm PDG
  • 2 Torpedo tubes
  • 50 Port/Starboard Howitzers

Captain(s)

  • Captain Des' Ali (UEG)

Group

  • Western Fleet Command
    • 5th Carrier Strike group

Fate

Destroyed

 The UNSC Redgauntlet (CC-201-1) was a light cruiser in service with the UNSC Navy. 

Operational HistoryEdit

The Redgauntlet mostly has been assigned to dull patrol missions or planetary defense for the few years it has been in service. On January 18th 2577 the Redgauntlet was assigned to flagship of Battlegroup Sierra for Operation Gatehouse, an anti-piracy mission in Exon space. 

Joined the UNSC 5th Fleet at Earth in February and departed for the Large Magellanic Cloud Galaxy to set up outposts however it was pulled to find an alien race called the Garmillans. The task force was ambushed after being forced to exit slipspace. Redgauntlet was torpedoed lowering her shields and then struck by plasma beam to its open central hanger. The ship was abandoned for the duration of the battle. Afterwards it was towed and used as fire ship.

DesignEdit

Much of the Carrier is taken up by the flight deck which runs along the middle of the ship. Smaller hangers sit inside the side of the middle as well as two on the outer side and one underneath the ship. The ship is able to land as well as work on water.

ComplementEdit

  • 1,300 Marines of the 501st
  • 21st Battalion (760)
  • 1,000 Naval and maintenance personnel
  • 150 Fighters (Shindens and GA-TL1 Longswords)
  • 36 D77H-TCIH Pelican Dropships and 15 D77/LAATi 


Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.