Battlestar Yashuman

Battlestar Galactica 2004 Continuity
Battlestar Galactica 2004, Caprica and Blood & Chrome

Battlestar Yashuman
Audio Version
General Information
Affiliation:	United Colonies of Kobol Colonial Fleet
Fate:	Destroyed, 0 ACH Over Caprica
Technical Specifications
Class:	Valkyrie-class
Type:	Battleship
Length:	649 meters (2,129 ft)
Width:	235 meters (771 ft)
Height:	69 meters (226 ft)
Armament:	12 Main Dual KEW Batteries 4 Secondary Single KEW Batteries Missiles
Defenses:	19 Primary CIWS Dual KEW Batteries 22 Secondary CIWS Dual KEW Batteries Armor plating
Aviation facilities:	2x Flight Pods 2x Flight Decks 6x Viper Launch Tubes
Complement:	Viper Mk VIIa Viper Mk VIIb Raptors
Propulsion:	4x Sublight Engines Manoeuvring Thrusters
FTL:	Yes

Yashuman was a Valkyrie-class battlestar in service in the Colonial Fleet during the Fall of the Twelve Colonies. Unlike her newer sister ships, a Flight I Valkyrie-class, she lacks the distinctive spoiler-like structure on her upper engine assembly. During the fall, Yashuman was a flagship for Caprica's orbital defense patrol, consisting of three Valkyrie-class battlestars in the standard Colonial formation.

Minutes before Zero Hour, Yashuman detected several Cylon basestars in orbital grid 15-2 and relayed this information to Caprica Control. She was informed that Cylons had already infiltrated the systems and that Caprica Controls DRADIS was down, so she initiated her attack run without any orders. Seconds later, her Command Navigation Program (CNP) was also infiltrated, leading to total system failure. She was presumably subsequently destroyed shortly after.

Design

Armament

Main Dual KEW Battery

Being a smaller battlestar, ships of this class do not appear to possess the heavy turrets seen on the Jupiter or Mercury-class. Instead, they are equipped with several smaller turrets strategically scattered throughout the ship. These smaller turrets and multiple secondary and tertiary weaponry serve as a defense mechanism against incoming ordinance. This design choice allows for a more agile and versatile approach to combat, ensuring that the ship can effectively protect itself in battle.

The Valkyrie-class battlestar was equipped with a formidable main armament consisting of 22 dual-purpose KEW (kinetic energy weapons) batteries. These batteries served a dual function, acting as both standard kinetic weapons found on Jupiter-class battle stars and as a platform for launching Colonial ship-to-ship missiles.

Secondary armament includes four single-gun KEW (Kinetic Energy Weapons) positioned on the dorsal side of each flight pod. These weapons presumably provide a flak screen to protect the landing combat-air-patrol fighters from enemy attacks during their landing.

Anti-missile and Anti-Fighter protection on the battlestar was ensured by 29 Dual KEW CIWS batteries. These batteries, although resembling the design of the main batteries, were noticeably smaller in size and were strategically positioned all around the hull of the battlestar, creating a more even distribution. Interestingly, these weapons were also cleverly placed between the sublight engines, allowing for a near 360-degree protection coverage. This arrangement ensured the battlestar was well-equipped to defend itself from potential threats.

Fighter Complement

In a departure from the standard battlestar design, the Valkyrie introduces a unique feature: instead of the traditional launch tubes positioned at the sides of the two flight pods, it incorporates six forward-facing launch tubes (three for each pod) located at the front of each flight pod. This design choice is likely due to the smaller size of the Valkyrie class, as the flight pods are only 33.5 meters wide at their widest point. Although not officially confirmed, it is widely speculated that ships belonging to this class can support not only multiple squadrons of Viper fighters but also numerous Raptor multipurpose craft. This configuration allows for enhanced maneuverability and strategic positioning during combat operations.

Computer Systems

Coming from the 1st Cylon War, it is presumed that, in their original design configuration, ships of this class lacked the advanced computer technology and networking of more modern battlestars for fear of Cylon infiltration. However, it is also presumed that most, if not all, ships of this class have been heavily upgraded since then. These upgrades would have included implementing more sophisticated computer systems and enhanced networking capabilities to facilitate new technologies, like main Battery-fired missiles. Despite these upgrades, several ships of this class were still shown as being shut down by Cylon infiltration of their Command Navigation Program (CNP) during the Fall of the Colonies.

Crew

The crew complement of the Valkyrie class is not explicitly stated, but it can be inferred from the information about the Jupiter-class. The Jupiter-class initially required a crew of 5000 people, so it is reasonable to assume that the smaller Valkyrie-class would have a significantly reduced crew size in its original configuration. It is worth mentioning that the crew size of the Valkyrie-class may have decreased significantly after the war due to upgrades and refits made to the class. These modifications could have resulted in more efficient systems and technologies, potentially reducing the need for a large crew.

Therefore, while the exact crew complement of the Valkyrie-class remains unknown, it is likely that, especially with the introduction of the Command Navigation Program (CNP), the crew complement shrined down significantly, even from the original compliment.

Propulsion

Ships of this class are equipped with four main rearwards-facing sublight engines mounted in pods onto their outer hull. These engines are strategically positioned, with two on the ship's dorsal surface and two on its ventral surface. In addition to these main engines, smaller maneuvering thrusters are scattered throughout the ship, allowing quick and agile movements during combat scenarios. To enable faster-than-light travel, at least one FTL (Faster-Than-Light) drive is installed aboard the ship. However, it is worth noting that the ship's main engines are relatively unarmored, and the half-exposed position of the FTL drive on the dorsal side further exacerbates this vulnerability.

This exposed location is a significant weak spot, as demonstrated during the Battle of Scorpion Shipyards. In this battle, a Cylon raider, armed with only three conventionally armed missiles, could exploit this weakness and ultimately destroy a docked battlestar of Valkyrie-class.

Behind the scenes

• Battlestar Yashuman represents its class and Battlestar Galactica in general in Roblox's Project Stardust.

Gallery

Orbital Defense Patrol