OBT Forum
General BattleTech => General Discussion => MechFactory => Topic started by: Takiro on February 16, 2010, 08:02:29 AM
-
Takiro BTSD Equipment Catalog « on: February 08, 2008, 04:57:51 PM »
Okay folks I have wanted for the longest time to consolidate all of our "official" designs into one place. Got alot of requests and with Walegrin's help complied all BTSD equipment we released thus far including their Heavy Metal files. Thanks also go to MK for helping to organize this thread. I will try to place subsequent releases here as well in the future. Enjoy!
BTSD Equipment Index
BAX-8M Battleaxe
Ice Talon BAX-8M
Mitchell Attack Hovertank
Pack Mule VTOL Transport
FM Terran Republic 2785
ASN-22 Assassin
BLK-1 Bulwark
JVN-11N Javelin
MAD-3Q Marauder
MAD-4R Marauder
PRW-1LR Prowler
THG-12A Thug
Coblitz Main Battle Tank
Anchorage class Dropship
Genesis class Corvette
Bainbridge class Destroyer
Sovremenyy class Battlecruiser
Hegemony class Battlecruiser
Project Phoenix
CLNT-5R Clint
CHR-2A Challenger
PHX-1X Phoenix Aerofighter
Light Attack Fighter
Medium Attack Fighter
Heavy Attack Fighter
Sea Wolf Fast Attack Submarine
Nautilus Ballistic Missile Submarine
Mercenary Guild
LGN- 1 Legionnaire
137-A Omega
C-10A Crow Aerospace Fighter
HLR-66 Hellraiser Aerospace Fighter
Marechal Light Tanks
Technical Readout: 2800
House Kurita
Himeko class Corvette/Raider
Inoshishi class Corvette
Same class Corvette
Kaze class Destroyer
Kumo class Destroyer
Nami class Destroyer
Atago class Heavy Cruiser
Byakuren class Battlecruiser
Igarashii class Battlecruiser
Mogami class Cruiser
Tone class Carrier
Hiei class Battleship
House Marik
Guardian class Corvette
Libertad class Corvette
Fulbaum class Destroyer
Vester class Destroyer
Stewart class Destroyer
Alexander class Destroyer
Themistocles class Destroyer/Carrier
Dido class Frigate
Aeneas class Cruiser
Sian class Battlecruiser
Varyag class Battlecruiser/Carrier
Nemesis class Carrier
Design Challenges
1. Coblitz Main Battle Tank
Warthog Assault Tank
2. Aetius IFV
3. Gorgon Heavy Tank
4. Styx Heavy Assault Tank
5. Merrill Strike Tank
6. Sea Wolf Fast Attack Submarine
Nautilus Ballistic Missile Submarine
7. Shrike Hovertank
Phalanx ISV
Drachen Battle Tank
8. Dione class Dropship
9. C-10A Crow Aerospace Fighter
HLR-66 Hellraiser Aerospace Fighter
10. Marechal Light Tanks
-
Takiro Battleaxe and the Frost Talon « Reply #1 on: February 08, 2008, 05:04:00 PM »
BAX-8M Battleaxe
Mass: 70 tons
Chassis: Earthwerk BAX II
Power Plant: VOX 280
Cruising Speed: 43.2 kph
Maximum Speed: 64.8 kph
Jump Jets: Rawlings 58
Jump Capacity: 120 meters
Armor: Kemplar 5000
Armament:
2 Magna Mk III Large Lasers
2 Doombud LR Missile Ten-Packs
2 Magna Small Lasers
Manufacturer: Earthwerks-FWL, Incorporated
Primary Factory: Keystone
Communications System: Neil 9000
Targeting and Tracking System: RCA Instatrac
Mark XII
Type: BAX-2M Battleaxe
Technology Base: InnerSphere Level 2
Tonnage: 70 tons
Equipment Mass
Internal Structure: 7
Engine: 280 16
Walking MP: 4
Running MP: 6
Jumping MP: 4 4
Heat Sinks: 15 (30) 5
Gyro: 3
Cockpit: 3
Armor Factor: 144 9
Internal Structure Armor Value
Head 3 9
Center Torso 22 20/ 7
R/L Torso 15 15/ 5
R/L Arm 11 14
R/L Leg 15 20
Weapons and Ammo Location Critical Mass
Large Laser Right Arm 2 5
Large Laser Left Arm 2 5
LRM 10 Right Torso 2 5
Ammo (LRM) 12 Right Torso 1 1
LRM 10 Left Torso 2 5
Ammo (LRM) 12 Left Torso 1 1
Small Laser Right Torso 1 0.5
Small Laser Left Torso 1 0.5
OVERVIEW
A design long in the making the Battleaxe is finally coming into its own. The ‘Mech was originally engineered in 2513 by Earthwerks Incorporated to compete in a bid issued by Hegemony General Olaf Sternson. His specifications called for a mobile Heavy ‘Mech with enough firepower to cripple any contemporary BattleMech design. Of course Earthwerks wasn’t the only entry into the competition. The chief rival for the bid turned out to be the upstart StarCorp Industries who put forth their own design called the Warhammer.
Both designs performed well in extensive testing but only one would be chosen. Despite great maneuverability and long range firepower the Battleaxe lost out. Even Earthwerks’ officials were forced to admit that the Warhammer had slightly more offensive and defensive capabilities. However, the Battleaxe was still an effective BattleMech and Earthwerks refused to give up on it.
Without a major military contract Earthwerks began production runs of the Battleaxe for sale to almost any interested consumer. They followed this unprecedented action with a wide spread ad blitz that is still remembered today. This corporate strategy was successful for a time and resulted in an economic war between Earthwerks and StarCorp. This all came to an end however in the early days of the Star League when a Hegemony Warhammer squared off against a Marik Battleaxe in what was supposed to be a friendly exercise. The confrontation caught on film for all to see went violent fast with both Mechwarriors going weapons hot simultaneously. Again the Warhammer came out on top defeating the Battleaxe decisively.
After that pivotal confrontation the Warhammer stood supreme reducing the Battleaxe to a mere second line curiosity. Production of this “Poor Man’s Warhammer†ceased soon afterward and it appeared that the Battleaxe was destined for the scrapyard. Recent events have proven that assessment a little premature.
CAPABILITIES
Star League engineers bought to the Free Worlds League after the Amaris Coup have made fundamental changes to the original Battleaxe design. Building on the strengths of the Battleaxe itself and the League as a whole the redesign bore little resemblance to the Warhammer. The two Particle Projection Cannons on the original design were replaced by twin Large Lasers thanks to the weapons limited supply in Marik space. Typically the PPC was imported during the Star League era but with interstellar trade dropping to record low levels and domestic production already failing to meet FWLM needs an alternative had to be found. Coupled with the fact that the PPC is also the preferred weapon of the Terran military giving it a low standing in the Free Worlds League the change made perfect sense. While Large Lasers do less damage and lack the range of the PPCs their smaller size allows the inclusion of larger LRM racks. The original two LRM 5s were increased to LRM 10s making the Battleaxe more of a missile carrier. Many Mechwarriors say the new Battleaxe feels like an Archer-Warhammer hybrid. The original design’s SRM 6 was replaced by two Small Lasers giving the Battleaxe some close range protection. The weight saved by this change went to provide additional armor plating which was a concern left over from the first design. The highest piece of technology now seen on the improved Battleaxe is Double Heat Sinks. These extremely efficient heat dissipaters enable the Battleaxe to utilize all of its equipment without fear of overheating. The rest of the Battleaxe remains unchanged from its original design. This includes the highly reliable VOX 280 Fusion Engine, the Rawlings 58 Jump Jets, and the same basic chassis.
DEPLOYMENT
The new Battleaxe as an exclusive Marik BattleMech can be found only in the Free Worlds League. The first production run is slated for deployment in the Marik Guard and Marik Militia. Future production will no doubt go first to Federal units like the Atrean Dragoons then Marik allies all over the League. The exception to this rule will be the Regulan Hussars who will get access to the Battleaxe after Ronin Incorporated of Wallis completes their change over from the Warhammer. Oriente and Andurien forces are likely to be the final recipients of the Battleaxe because of their opposition to the policies of Captain-General Kenyon Marik. Some Andurien commanders have even gone so far as to request any Warhammers discarded by other units while simultaneously deriding the Battleaxe. So far the Tematagi factory in the far off Rim Commonalty, which is owned by Nimakachi Fusion Products Limited, has been overlooked and to continues to produce the Warhammer. It remains to be seen how long this situation will last.
The older Battleaxe ‘Mechs can still be found in every InnerSphere realm. The LCAF has slightly more of these venerable war machines than other militaries because the original BattleMech factory was located on the world of Hyperion in the Tamar Domains. All the Great Houses, except Marik, have relegated these machines to rear line duty were they are almost universally kept in poor condition. The FWLM has begun to refit their Battleaxe contingent which will soon surpass House Steiner’s in both size and quality.
VARIANTS
At least one variant of the BAX-8M is currently planned. Possibly the most highly anticipated League ‘Mech ever before made is Kenyon Marik’s yet unnamed personalized Battleaxe which will be equipped with cutting edge Star League technology. While many have speculated on the advanced equipment that might be included on the Captain-General’s BattleMech the exact details remain a closely guarded state secret. Right now the rarity of Star League tech prevents mass production of this advanced variant of the Battleaxe but if House Marik can one day master these scientific secrets Earthwerks may yet be able to manufacture these unquestionably formidable ‘Mechs for the entire FWLM.
* Battleaxe BAX-8M.hmp (6.71 KB - downloaded 4 times.)
* Frost Talon BTX-8M.hmp (6.68 KB - downloaded 1 times.)
-
Takiro Mitchell Attack Hovertank « Reply #2 on: February 08, 2008, 05:05:40 PM »
Mitchell Attack Hovertank
Mass: 50 tons
Movement Type: Hover
Power Plant: 265 Vlar XL Fusion Engine
Cruising Speed: 108 kph
Flank Speed: 162 kph
Armor: Pantherskin VII Ferro-Fibrous with CASE
Armament:
1 Magna Hellstar II PPC
2 Harpoon-6 SRM Launchers
1 Tri-Axe Machine Gun
Manufacturer: Mitchell Vehicles
Primary Factory: Terra
Communication System: Stony AIX with Guardian ECM
Targeting & Tracking System: Apple Churchill 2000 with Beagle Active Probe
OVERVIEW:
The Star League Defense Force (SLDF) deployed some of the most exotic high tech military equipment ever before seen. One of these developments was the ultra sophisticated Kanga Hover/Jump Tank. Its unique jump jets never before mounted on a vehicle gave it unmatched battlefield maneuverability. The intricate system that makes this one of a kind vehicle go, the AL2200 Computer, is now gradually being phased out. This is thanks to the Usurper’s brutal and complete destruction of the computer’s manufacturer, Nirasaki Computers Collective. As a result the New Republic has so far been unable to reproduce this vital component of the Kanga. Even though enough spare computers have been stockpiled by the TRAS to keep the Kanga in the field for a number of years its numbers will surely continue to dwindle.
With these facts in mind the Terran Royal Command made replacing the Kanga a priority. They set high standards for any potential successor to this premier military vehicle. To make up for the loss of combat maneuverability they decreed that the new tank must be faster than its predecessor and outfitted with a turret that contains the bulk of its weapon systems. They also stated their desire to improve upon the Kanga’s firepower and overall armor protection. With the storm clouds of war gathering on the horizon the Royal Command demanded an accelerated research and development phase to expedite production.
Mitchell Vehicles, the manufacturer of the Kanga, stepped forward to accept the challenge set down by the New Republic. This was in spite of the fact that the company had been savaged during the Amaris Coup. Virtually all of its facilities had sustained some type of major damage during the war. However it has managed to recover quickly thanks to its new corporate leader, Graham Mitchell. In addition Mitchell received top priority during Project Phoenix along with substantial government aid because of the company’s fierce patriotic zeal over the centuries. As a result the company moved from their annihilated headquarters on Graham IV back to their ancient home of Detroit on Terra. Their first new design since the fall of the Star League the Mitchell Attack Hovertank was named in honor of General Alvarez “Bull†Mitchell who was the original creator of the Kanga. The tank has become the pride of a revitalized Mitchell Vehicles.
CAPABILITIES:
Mitchell Vehicles decided that the TRAS maneuverability requirement for this new hovertank while permitting the shortest of design periods for expedited manufacturing would only allow the use of an engine already in production. Luckily the 265 Vlar XL Fusion Engine was just entering production for the Aetius IFV and perfectly fit Mitchell’s specifications. The inclusion of this state of the art power plant would enable the new tank to outpace the Kanga by 32 kph at flank speed. They next moved to include a turret with a more formidable weapons array than previously featured on the Kanga. For the tank’s main gun they included the weapon that is fast becoming a favorite of the new Terran military, the PPC. This primary cannon is supported by two Short Range Missile Six-racks that provide superb firepower during close quarters combat. Also to defeat any infantry that might try to engage the hovertank a machine gun was included. All of these offensive systems mounted in the turret the new design met another of its criteria. Designers went a step further insisting on increased armor protection especially since the tank’s silhouette had been enlarged with the addition of a turret. Thanks to six tons of ferro-fibrous armor also used on the Aetius this improved protection was achieved nicely. Engineers also included a CASE to safeguard the crew in the event of an ammunition explosion. Still not satisfied with the design Mitchell engineers resolved to equip the tank with the very best electronics package possible. First off they added the Beagle Active Probe to provide the best detection capability to the crew. Finally a Guardian ECM Suite was included to further enhance the new tank’s overall defensive wherewithal. The only drawback to this superior design appears to be its high price tag. The Terran military pleased with this excellent new design quickly approved it for full production.
VARIANTS:
Still a young design with a bright the Mitchell’s many proponents have already proposed a number of variants for this premier Terran hovertank. The most promising seems to be a simple switch of the Mitchell’s SRMs for Narc Missile Beacons. In conjunction with a supporting LRM unit this could be very devastating to any battlefield opponent no matter its size.
Technology Base: - I.S. Hover Vehicle - Level 2 - 50 tons
Equipment Mass
Internal Structure: 5
Engine: 265 XL 10.5
Cruising MP: 10
Flank MP: 15
Power Amplifier: 0
Heat Sinks: 10 – Single 0
Control Equipment: 2.5
Crew: 4 Members 0
Lift Equipment: 5
Turret: 1.5
Armor Factor: 108 - Ferro-Fibrous 6
Internal Structure Armor Value
Front 5 22
Left 5 21
Right 5 21
Rear 5 22
Turret 5 22
Weapons, Ammo, and Equipment Location Space Tonnage
PPC Turret 1 7
SRM 6 Turret 1 3
SRM 6 Turret 1 3
Machine Gun Turret 1 0.5
Ammo (SRM) 30 Body 1 2
Ammo (Machine Gun) 100 Body 1 0.5
CASE Body 1 0.5
Guardian ECM Body 1 1.5
Beagle Active Probe Body 1 1.5
* Mitchell Attack Hovertank.hmv (4.66 KB - downloaded 2 times.)
* Mitchell Attack Hovertank NARC Variant.hmv (4.35 KB - downloaded 1 times.)
-
Takiro Pack Mule VTOL Transport « Reply #3 on: February 08, 2008, 05:07:55 PM »
Pack Mule VTOL Transport
Mass: 30 Tons
Movement Type: VTOL
Power Plant: Leneex 160
Cruising Speed: 105.4 kph
Flank Speed: 159.8 kph
Armor: StarSlab/5.5
Armament:
2 SperryBrowing Machine Guns
Manufacturer: Paulina Weapons
Primary Factory: New Vandenberg
Communication System: Garret M250
Targeting & Tracking System: TracTex Alpha-2
Type: Pack Mule VTOL Transport
Technology Base: Inner Sphere
Movement Type: VTOL
Tonnage: 30 tons
Equipment Mass
Internal Structure: 3
Engine: 160 9
Type: Fusion
Cruising MP: 10
Flank MP: 15
Heatsinks: 10 0
Control Equipment: 1.5
Lift Equipment: 3
Power Amplifier: 0
Turret: 0
Armor Factor: 48 3
Armor Value:
Front: 12
R/L Side: 12
Rear: 10
Turret: 2
Weapons & Ammo Location Tonnage
Machine Gun Front 0.5
Machine Gun Rear 0.5
Ammo (100) Body 1
Cargo Body 9
Overview:
During the early days of the Reunification War, the Taurian Defense Forces continually stymied the SLDF forces with their superior mobility and unconventional tactics. Forced to adapt to these tactics, the SLDF developed their famous Striker regiments, which were capable of long term deployments away from their base. The key to the Striker regiments was the Cobra VTOL transport, which was able to rapidly transport supplies and personnel from the SLDF bases to the Striker regiments in the field. The Concordat military officers long admired the Cobra, but even after the end of hostilities they were unable to acquire the design as the SLDF prohibited Aldis from selling the design to any one else.
Following the Uprisings, the Concordat found itself in possession of a number of Cobras. The largest concentration was with the 29th Royal CAAN, which had defected to the Concordat. Other examples were found with SLDF units which had joined the Concordat, examples captured from the SLDF and even a few that were rebuilt from damaged Cobras. Seeking to increase the number of Cobras in service, several were turned over to Paulina Weapons of New Vandenberg, where they were disassembled and studied. Rather then simply copy the Cobra, the Paulina engineers modified the design to adapt it to local components, easing manufacturing. The new design was so different that the VTOL was renamed the Pack Mule.
Capabilities:
The Pack Mule is intended to serve as a transport for the Concordat’s forces. The Pack Mule is typically used to transport troops and supplies from rear bases to foward operating areas, allowing the troops to operate independently for long periods of time.
The biggest difference between the Pack Mule and Cobra is the power plant. Since the Concordat does not produce the Hermes 100 used by the Cobra, the Paulina engineers looked for an alternative power plant. Rather then develop a 100 rated fusion engine, which would be costly and time consuming, they decided to mount the readily available Leenex 160 in the Pack Mule. Formerly shipped to facilities throughout the Federated Suns and Capellan Confederation for use in the Locust Battlemech, Leenex has seen it’s sales plummet with the disruption of interstellar trade. Reduce to producing the few Leenex 160s the Concordat’s industries require, their plant on Perdition had significant excess capacity. Leenex quickly ramped production up for the Pack Mule and has had no problems meeting Paulina Weapons needs. The use of the Leenex 160 had the added benefit of increasing the speed of the Pack Mule, making far more maneuverable.
The other major change is to the weapons and defensive systems. Lacking the ability to produce the advanced McArthur Anti-Missile System, the designers were forced to drop the AMS from the Pack Mule. It is hoped that the increased speed will offset the loss of the AMS.
The designers also removed the medium laser, replacing it with forward and rear mounted machine guns. This change was made at the insistence of the TDF, which felt the presence of the laser system would encourage pilots to engage in combat, rather then trying to avoid it. The machine guns can be used to provide suppressing fire around a landing zone, forcing any infantry in the area to keep their heads down.
The changes made to the Pack Mule have resulted in a slight smaller cargo capacity then the Cobra. This change has had minimal impact on the Pack Mules operations.
In all other aspects, the Pack Mule is nearly identical to the Cobra, except for the substitution of locally manufactured components for the Cobra’s original equipment. At one point there was some consideration given to using Paulina’s DL Ferro-Fibrous armor which is also used on the Cyrano, but this idea was dropped due to the added cost and limited availability of the armor.
Deployment:
The Pack Mule has been deployed to a number of Taurian units. The largest concentrations of Pack Mules are assigned to the Concordat Commandos, Red Chasseuers, 159th Hussars and Hyades Light Infantry. It is planned to assign the Pack Mule to every front line Concordat regiment as soon as sufficient numbers can be produced. As the Cobra VTOLs are being replaced with Pack Mules, the Cobras are being reassigned to the 29th Brisbane Planetary Marines, formerly the SLDF’s 29th Royal CAAN Marine regiment. The 29th has stated a preference to the original model, and by assigning all remaining Cobras to the regiment it simplifies maintenance.
* Pack Mule VTOL Transport.hmv (4.8 KB - downloaded 2 times.)
-
Takiro FM Terran Republic BattleMech Variants « Reply #4 on: February 08, 2008, 05:13:38 PM »
BATTLEMECH VARIANTS
General Ian Sinclair set out to rebuild the shattered 1st Army (Terran Military Region) of the SLDF immediately after assuming control of the Royal Command. For that purpose Commanding General Kerensky approved the creation of several new BattleMech designs. Impressed by the Marauders’ performance and the potential of the other ‘Mechs in its series the New Republic purchased the design rights from General Motors (which after the Amaris Coup had become a Federated Suns company).
Mitchell Vehicles picked up the rights to produce the MAD-4R Marauder and the DGR-3F Dragon Fire. They weren’t the only ones who wanted to make the proven Marauder. Independence Weaponry of Quentin was awarded a contract to produce an improved Marauder design that could also be used as the basis to refit existing ‘Mechs. This became the MAD-3Q Marauder. Other designs like the MTR-5K Maelstrom and the NSR-9J Nightstar were grabbed up by Krupp Stellar Works and Skobel 'MechWorks respectively. Both of these companies went onto design two further Marauder type BattleMechs, the BLK-1 Bulwark and the PRW-1LR Prowler.
Several other high tech variants were produced in large numbers by the Terran Republic. The Maltex Corporation of Errai has created ASN-22 Assassin and the THG-12A Thug. These speedy BattleMechs are both equipped with the ultra high tech Null-Signature System and will probably be deployed in special lances. These lances will include the SPR-5F Spector and EXT-4D Exterminator which are also equipped with the Null-Signature System. The still rebuilding Stormvanger Industries of Caph has also managed to upgrade the venerable Javelin class BattleMech with the new JVN-11N model. More variants are likely to appear soon within the TRAS due to the present state of affairs in the InnerSphere.
JVN-11N Javelin
Mass: 30 tons
Technology Base: Inner Sphere Level 2
Equipment Mass
Internal Structure: 3
Engine: 180 XL 3.5
Walking MP: 6
Running MP: 9
Jumping MP: 6 3
Heat Sinks: 10 (20) 0
Gyro: 2
Cockpit: 3
Armor Factor: 99 (Ferro-Fibrous) 5.5
Area Internal Structure Armor Value
Head 3 9
Center Torso 10 15 / 5
R/L Torso 7 10 / 3
R/L Arm 5 9
R/L Leg 7 13
Weapons and Ammo: Location Criticals Mass
SRM-6 Right Torso 2 3
Ammo (SRM) 15 Right Torso 1 1
Artemis IV FCS Right Torso 1 1
SRM-6 Left Torso 2 3
Ammo (SRM) 15 Left Torso 1 1
Artemis IV FCS Left Torso 1 1
ASN-22 Assassin
Mass: 40 tons
Technology Base: Inner Sphere Level 2
Equipment Mass
Internal Structure: EndoSteel 2
Engine: 280 XL 8
Walking MP: 7
Running MP: 11
Jumping MP: 7 3.5
Heat Sinks: 10 (20) 0
Gyro: 3
Cockpit: 3
Armor Factor: 120 7.5
Area Internal Structure Armor Value
Head 3 9
Center Torso 12 16 / 5
R/L Torso 10 14 / 4
R/L Arm 6 10
R/L Leg 10 17
Weapons and Ammo: Location Criticals Mass
LRM 10 RT 2 5
Ammo (LRM) 12 RT 1 1
CASE RT 1 .5
SRM 4 LT 1 2
Ammo (SRM) 25 LT 1 1
CASE LT 1 .5
Medium Laser RA 1 1
Small Laser RA 1 .5
Medium Laser LA 1 1
Small Laser LA 1 .5
Null-Signature System Various 7 0
THG-12A Thug
Mass: 80 tons
Technology Base: Inner Sphere Level 2
Equipment Mass
Internal Structure: EndoSteel 4
Engine: 400 XL 26.5
Walking MP: 5
Running MP: 8
Jumping MP: 0
Heat Sinks: 18 (36) 8
Gyro: 4
Cockpit: 3
Armor Factor: 248 15.5
Area Internal Structure Armor Value
Head 3 9
Center Torso 25 34 / 16
R/L Torso 17 25 / 9
R/L Arm 13 26
R/L Leg 17 34
Weapons and Ammo: Location Criticals Mass
SN PPC Right Arm 2 6
SN PPC Left Arm 2 6
2 Streak SRM-2s Right Torso 2 3
Ammo (SRM) 50 Right Torso 1 1
2 Streak SRM-2s Left Torso 2 3
Null-Signature System Various 7 0
(Thug notes; 2 Free Crits RT, 3 Free Crits LT)
* Javelin JVN-11N.hmp (2.57 KB - downloaded 1 times.)
* Assassin ASN-22.hmp (2.66 KB - downloaded 1 times.)
* Thug THG-12A.hmp (2.7 KB - downloaded 1 times.)
-
Takiro FM Terran Republic - Expanded Marauder Series « Reply #5 on: February 08, 2008, 05:28:04 PM »
MAD-3Q Marauder
Mass: 75 tons
Technology Base: Inner Sphere Level 2
Equipment Mass
Internal Structure: 7.5
Engine: 300 19
Walking MP: 4
Running MP: 6
Jumping MP: 0
Heat Sinks: 11(22) 1
Gyro: 3
Cockpit: 3
Armor Factor: 224 (Ferro-Fibrous) 12.5
Area Internal Structure Armor Value
Head 3 9
Center Torso 23 35 / 10
R/L Torso 16 24 / 8
R/L Arm 12 24
R/L Leg 16 29
Weapons and Ammo: Location Criticals Mass
PPC Left Arm 3 7
Medium Laser Left Arm 1 1
Medium Laser Left Arm 1 1
SRM 6 Left Torso 2 3
Ammo (SRM) 15 Left Torso 1 1
Artemis IV FCS Left Torso 1 1
CASE Left Torso 1 0.5
PPC Right Arm 3 7
Medium Laser Right Arm 1 1
Medium Laser Right Arm 1 1
SRM 6 Right Torso 2 3
Ammo (SRM) 15 Right Torso 1 1
Artemis IV FCS Right Torso 1 1
CASE Right Torso 1 0.5
MAD-4R Marauder
Mass: 75 tons
Technology Base: Inner Sphere Level 2
Equipment Mass
Internal Structure: 7.5
Engine: 300 XL 9.5
Walking MP: 4
Running MP: 6
Jumping MP: 0
Heat Sinks: 20 (40) 10
Gyro: 3
Cockpit: 3
Armor Factor: 224 14
Area Internal Structure Armor Value
Head 3 9
Center Torso 23 34 / 11
R/L Torso 16 23 / 8
R/L Arm 12 23
R/L Leg 16 31
Weapons and Ammo: Location Criticals Mass
ER PPC Right Arm 3 7
ER PPC Left Arm 3 7
Ultra AC/5 Right Torso 5 9
Ammo (Ultra AC) 20 Right Torso 1 1
Medium Pulse Laser Center Torso 1 2
Medium Pulse Laser Center Torso 1 2
PRW-1LR Prowler
Mass: 25 tons
Introduced: 2784
Chassis: Skobel Prowler with EndoSteel
Power Plant: Nissan 200 XL
Cruising Speed: 86.4 kph
Maximum Speed: 129.6 kph
Jump Jets: None
Jump Capacity: None
Armor: Starguard Ferro-Fibrous
Armament:
2 Blankenburg-50 Light PPCs
3 Blankenburg Medium Lasers
Manufacturer: Skobel 'MechWorks
Primary Factory: Terra
Communications System: Dalban Micronics
Targeting and Tracking System: DLK Type Phased Array Sensor System
OVERVIEW
Following the Usurper’s defeat General Ian Sinclair began to search for new
BattleMech designs that would replenish Star League Royal (Terran) units. These
advanced designs would eventually make up the new core of the Terran defense force. General Motors promising new Marauder series was ultimately chosen to fulfill this role. Two Mechs in that series, the Marauder and the Nightstar, had already proven themselves during the Amaris Conflict. Their excellent performance laid the foundation for the Marauder series developing reputation. Two other designs, the Dragon Fire and the Maelstrom, never made it off the drawing board in time to see action during that conflict. Despite this they showed a lot of potential and added to the series value. After purchasing the rights to the Marauder series from General Motors the Terran military requested two further designs based on the Marauder model. One, nicknamed the Mini Marauder was a light mech only one-third the size of the original with twice the speed. Skobel ‘Mechworks which had just been granted permission to begin production of the Nightstar accepted the design challenge. Working quickly and using advanced technology they came up with the Prowler. The new Mech entered production immediately on the retooled Jackrabbit line.
CAPABILITIES
While the Prowler is primarily designed as a Light ‘Mech Killer it can serve in several different roles. Its power plant, the Nissan 200 XL, provides the Prowler with maximum speed of over 129 kilometers per hour. This is more than ample to track down and kill all but the fastest BattleMechs. In addition, the Prowler makes an excellent raider and is adequately equipped for extended operations. The newly restored Blankenburg Technologies manufactured the Prowler’s weapons system, which is entirely energy based. Two Blankenburg Light Particle Projection Cannons give the Prowler its punch and allow it target ‘Mechs at longer ranges. These weapons allow the ‘Mech to snipe at larger opponents using its speed and range to peck away. The new Light PPCs are supported by three Medium Lasers that complete the ‘Mechs arsenal with some short range firepower. The Prowler also makes a fine Command Mech for Light Lances. This is because designers insisted on including the Dalban Micronics communications system that was featured so prominently on the Marauder. The Prowler’s targeting and tracking system is taken from the Nightstar also produced by Skobel now. The DLK Type Phased Array Sensor System is perhaps the finest in the InnerSphere as it gives the Prowler tremendous accuracy.
DEPLOYMENT
Three Terran units have so far received the Prowler; the Sinclair Fusiliers, the Terran Guard, and the Tau Ceti Rangers. The Fourth Tau Ceti Rangers have taken such a liking to the Prowler that they have begun to embrace the entire Marauder series and they currently field all six of its ‘Mechs (including the Marauder, the Dragon Fire, the Maelstrom, the Nightstar, the Prowler, and the Bulwark).
Type: PRW-1LR Prowler
Technology Base: InnerSphere Level 2
Tonnage: 25 tons
Equipment Mass
Internal Structure: EndoSteel 1.5
Engine: 200 XL 4.5
Walking MP: 8
Running MP: 12
Jumping MP: 0 0
Heat Sinks: 10 (20) 0
Gyro: 2
Cockpit: 3
Armor Factor: 80 5
Internal Structure Armor Value
Head 3 8
Center Torso 8 10/ 4
R/L Torso 6 8/ 3
R/L Arm 4 7
R/L Leg 6 11
Weapons and Ammo: Location Criticals Mass
Light PPC Right Arm 2 3
Light PPC Left Arm 2 3
Medium Laser Head 1 1
Medium Laser Right Arm 1 1
Medium Laser Left Arm 1 1
Cost – 3,660,416
Battle Value – 902
BLK-1 Bulwark
Mass: 50 tons
Introduced: 2784
Chassis: KSW Bulwark with EndoSteel
Power Plant: Vlar 300 XL
Cruising Speed: 64.8 kph
Maximum Speed: 97.2 kph
Jump Jets: None
Jump Capacity: None
Armor: PanzerSlab Type 5
Armament:
2 Blankenburg-250 Snub-Nose PPCs
1 Blankenburg-50 Light PPC
1 Blankenburg Medium Laser
2 Blankenburg Small Lasers
Manufacturer: Krupp Stellar Works
Primary Factory: Terra
Communications System: Dalban Micronics
Targeting and Tracking System: DLK Type Phased Array Sensor System
OVERVIEW
The sixth and final design in the Marauder series is the BLK-1 Bulwark made by Krupp Stellar Works. It was envisioned by the Royal Command as the main frontline medium BattleMech for the emerging Terran state. General Sinclair said that “the new ‘Mech would serve as the Bulwark of Royal units†and hence the name. Based heavily on the original Marauder, the Bulwark was engineered at the same time as the Prowler. The Krupp design team proceeded at a more deliberate pace and closely followed the progress of Skobel engineers working on the Prowler. This allowed them to correct some of the minor flaws in the Marauder series like the problematical collar that connects the ‘Mechs torso to its legs. The result is a highly reliable BattleMech that is a third smaller and fifty percent faster than the original.
CAPABILITIES
The Bulwark is a multi-propose BattleMech just like its big brother (the Marauder) and its little brother (the Prowler). Equipped with the Vlar extra light fusion engine the Bulwark has a maximum speed of just over 97 kilometers per hour, average speed for a medium ‘Mech. The Krupp design team chose to equip the medium sized Marauder with an entirely energy based armament for extended operations. This mirrored Krupp’s other Marauder type design, the MTR-5K Maelstrom. The Bulwark’s main weaponry are twin Blankenburg-250 Snub-Nose Particle Projection Cannons which gives it superior short range firepower. For longer range targets a Light Particle Projection Cannon was also included. Rounding out the Bulwark’s arsenal is one Medium Laser and two Small Lasers making the ‘Mech an excellent close range fighter. The Small Lasers were included almost as an afterthought by designers who wished to compensate for the Light PPCs minimum range. Fifteen double heat sinks dissipate all of the Bulwark’s waste heat fairly efficiently. The DLK Type Phased Array Sensor System, also used on the Prowler, grants the Bulwark’s Mechwarrior superior precision with its armament. The Bulwark makes an excellent command Mech for medium lances because of its Dalban Micronics communications system. This sophisticated equipment allows the Mechwarrior to coordinate his lance-mates activities quickly and efficiently.
DEPLOYMENT
The first Bulwark walked off the Krupp assembly line late in 2784. Like the Prowler only three Terran units have received the Bulwark so far. They include the Sinclair Fusiliers, the Terran Guard, and the Tau Ceti Rangers. The Fourth Tau Ceti Rangers obsession with the Marauder series also includes the new Bulwark. The design has had some excellent early reviews by several Mechwarriors from all three units.
Type: BLK-1 Bulwark
Technology Base: InnerSphere Level 2
Tonnage: 50 tons
Equipment Mass
Internal Structure: EndoSteel 2.5
Engine: 300 XL 9.5
Walking MP: 6
Running MP: 9
Jumping MP: 0 0
Heat Sinks: 15 (30) 5
Gyro: 3
Cockpit: 3
Armor Factor: 160 10
Internal Structure Armor Value
Head 3 9
Center Torso 16 23/ 8
R/L Torso 12 16/ 6
R/L Arm 8 15
R/L Leg 12 23
Weapons and Ammo: Location Criticals Mass
SN PPC Right Arm 2 6
SN PPC Left Arm 2 6
Light PPC Right Torso 2 3
Medium Laser Left Torso 1 1
Small Laser Right Arm 1 .5
Small Laser Left Arm 1 .5
Cost – 9,735,750
Battle Value – 1,293
* Marauder MAD-3Q.hmp (2.74 KB - downloaded 2 times.)
* Marauder MAD-4R.hmp (2.7 KB - downloaded 1 times.)
* Prowler PRW-1LR.hmp (3.96 KB - downloaded 1 times.)
* Bulwark BLK-1.hmp (3.74 KB - downloaded 1 times.)
-
Takiro FM Terran Republic - Coblitz and Anchorage « Reply #6 on: February 08, 2008, 06:12:40 PM »
Coblitz Main Battle Tank
Mass: 70 tons
Introduced: 2785
Movement Type: Tracked
Power Plant: Magna 350XL
Cruising Speed: 54.3 kph
Flank Speed: 86.6 kph
Armor: Grumman CRT Ferro-Fibrous Armor with Case
Armament:
1 Magna Hellstar II PPC
1 Holly-15 Long Range Missile Launcher
2 Holly SRM-2 Launchers
2 Ramsey-65 Machine Guns
Manufacturer: Grumman Industries
Primary Factory: Terra
Communication System: Hesperus 5 GT
Targeting & Tracking System: Lynx RM
OVERVIEW
The Coblitz Main Battle Tank was developed in the early 2780s to fill a need in
the Terran Republic Armed Services for a new main battle tank. The massive battles of the Amaris Crisis and the subsequent departure of the SLDF left the nascent Terran Republic Armed Services desperately short of equipment. Surrounded on all sides by potentially hostile nations, the Republic began a crash rearmament program. One of the first companies to respond was Grumman Industries. While many Terran industries were destroyed by the heavy fighting of the Amaris Crisis, Grumman some how managed to emerge from the crisis with only minimal damage to their factories. [Editor’s Note: It is believed that Grumman benefited from the location of their factories on Long Island in North America. Mostly isolated from the mainland, Amaris stationed only a few troops on the island. These troops were withdrawn from the island to counter the SLDF invasion. While the Amaris troops did inflict some damage on the factories before the left, the damage was mostly superficial and easily repaired.] While many other Terran companies were forced to use their cash reserves to rebuild their damaged and destroyed factories, Grumman was able to use their money to quickly buy up several defense companies, all of which were on the verge of bankruptcy. One of these companies was Killosh Industries, the manufacturer of the Magi Tank. The Killosh factories were completely leveled during the fighting and the company did not have the funds to rebuild them. As a result Grumman was able to buy the company and its surviving backup data core, which contained design data on all of the company’s designs, for a song. When the Republic issued a call for a new main battle tank the Grumman decided to enter the competition. The company’s corporate officers directed the design team to base the new tank on the same chassis as the Magi, in an effort to earn some return on their purchase of Killosh Industries. The Magi chassis required several major modifications in order to transform it from an urban combat vehicle into a suitable main battle tank. During the competitive testing phase, the new Grumman tank out performed all of its competitors. The design was quickly selected for production and named the Coblitz after the famous Field Marshal Mears Coblitz, commander of the Hegemony Armed Forces under Director James McKenna. [Editor’s Note: Field Marshal Coblitz was a strong proponent of the theory of rapid forward movement. During his time commanding Terran Armored Regiments, Field Marshal Coblitz was known for constantly driving his divisions harder and faster then any other commander in the HAF. The high speed of the new Grumman tank inspired the design team to assign the project the code name Coblitz. When the tank was accepted by the Republic Armed Forces the senior officers adopted the name Coblitz as the official designation for the design.]
CAPABILITIES
The Coblitz is designed to serve as the primary Main Battle Tank of the Terran
Republic Armed Forces. Based on the chassis of the Magi Tank, the Coblitz combines heavy armor and firepower with a high speed chassis.
While the Coblitz shares a common chassis the Magi, the design team needed to
make a number of changes in order to turn the design into an effective MBT. The
massive Magna 350 fusion engine of the Magi provided the tank with impressive
mobility, but that mobility came at a high price. The engine constituted more then 60% of the tanks’ mass, limiting the Magi to the firepower of a light tank. Fortunately advances in technology provided the engineers with a solution to this problem. The newly developed Magna 350 Extra Light Fusion engine develops the same amount of power as the original Magna 350, but weighs only half as much. This allows the Coblitz to retain the speed and mobility of the Magi, while freeing up a significant amount of mass for weapons. Of course the new engine doesn’t come with out a price; the Magna 350 Extra Light costs nearly twice as much as the standard model.
All of the weight that was freed up by switching to the lighter engine was used to
improve the weapons and armor. While the Magi were only effective against infantry and soft targets, the Coblitz is serious threat to other tanks and even Battlemechs. The main gun of the tank is the reliable Magna Hellstar II PPC. The PPC is mated to the Magi’s Lynx RM targeting computer, one of the most advanced systems available to the Star League. The fire control system provides the tank with the ability to track and engage several targets simultaneously.
The design team decided that to be an effective MBT, they would need to provide the PPC with a full 360 degree field of fire, which required the addition of a turret to the Magi chassis. In order to maintain the low silhouette of the Magi, thereby reduce the Coblitz’s exposure to enemy fire, the new turret is unmanned. The gunner and tank commander are seated in the hull of the tank and control the turret remotely. This results in a turret that is less then half a meter tall and only 2 meters wide. [Editor’s Note: The Coblitz is only 2.6 meters tall at its highest point and 3.7 meters across. By comparison the Magi is 2.2 meters tall and 3.7 meters across.] In addition to the PPC, the turret also carries a Holly-15 Long Range Missile Launcher. The LRM launcher is mounted so that it can be used for both indirect and direct fire.
The Coblitz also carries 2 Holly SRM-2 launchers on the front of the tank. These
are intended for use at close range, where the PPC and LRM are ineffective. Rounding out the weapons are 2 Ramsey-65 Machine Guns. These are the same guns that were mounted on the Magi and are used to defend against infantry.
While the Magi carried an impressive 9.5 tons of Ferro-Fibrous armor, the design
team considered that inadequate for a main battle tank. The Coblitz mounts 14 tons of Ferro Fibrous armor, which provides excellent protection to the tank. However rather then mount the Killosh Xtra-Weave carried on the Magi, the designers switched to the superior Grumman CRT armor. The main reason for the change was due to problems with the Killosh armor. The Killosh armor tended to suffer from hair line cracks during abrupt maneuvers. The Grumman armor is of a slightly different composition and not subject to this problem. With all of the ammunition carried on board the Coblitz, the design team decided to retain the CASE system, protecting the crew in the event of an ammunition explosion.
DEPLOYMENT
The Coblitz has been produced in large numbers. The tank has quickly become a
common sight in units throughout the New Republic.
Technology Base: InnerSphere Tracked Vehicle - Level 2 - 70 tons
Equipment Mass
Internal Structure: 7
Engine: 350 XL 22.5
Cruising MP: 5
Flank MP: 8
Power Amplifier: 0
Heat Sinks: 10 – Single 0
Control Equipment: 3.5
Crew: 5 Members 0
Suspension: 0
Turret: 1.5
Armor Factor: 251 - Ferro-Fibrous 14
Internal Structure Armor Value
Front 7 61
Left 7 50
Right 7 50
Rear 7 30
Turret 7 60
Weapons, Ammo, and Equipment Location Space Tonnage
PPC Turret 1 7
LRM 15 Turret 1 7
Ammo (LRM) 16 Body 1 2
2 SRM 2s Front 2 2
Ammo (SRM) 50 Body 1 1
2 Machine Guns Front 2 1
Ammo (Machine Gun) 200 Body 1 1
CASE Body 1 .5
Cost – 12,697,017
Battle Value – 830
Anchorage class Dropship
Type: Military Spheriod
Use: Nautical (Wet Naval) Carrier
Technology: InnerSphere Level 2
Introduced: 2772
Mass: 7,200 tons
Dimensions
Length: 85 meters
Width: 85 meters
Height: 110 meters
Fuel: 150 tons (4,500 fuel points)
Tons/Burn-day: 1.84
Safe Thrust: 3
Maximum Thrust: 5
Heat Sinks: 389 (778)
Structural Integrity: 30
Armor Factor: (Capital Scale)
Fore: 465 47
Sides: 461 46
Aft: 461 46
Weapons Range Values
Arc Type Heat S M L Extreme
- Long Tom 20 - - - 20*
- Arrow IV 30 - - - 60*
Nose PPC 45 3 3 3 -
Nose AC 9 3 3 - -
Nose Laser 60 4 4 4 -
FL PPC 45 3 3 3 -
FL AC 9 3 3 - -
FL Laser 60 4 4 4 -
FR PPC 45 3 3 3 -
FR AC 9 3 3 - -
FR Laser 60 4 4 4 -
AL PPC 45 3 3 3 -
AL AC 9 3 3 - -
AL Laser 60 4 4 4 -
AR PPC 45 3 3 3 -
AR AC 9 3 3 - -
AR Laser 60 4 4 4 -
Aft PPC 45 3 3 3 -
Aft AC 9 3 3 - -
Aft Laser 60 4 4 4 -
Cargo: 200 tons
Bay 1: Cargo 3 Doors
Bay 2: Heavy Vehicles (24) 6 Doors
Bay 3: Heavy Vehicles (12) 3 Doors
Escape Pods: 0
Life Boats: 20
Crew: 18
Armament:
1 Long Tom Artillery System
3 Arrow IV Systems
18 ER PPCs
18 AC/10s
30 ER Large Lasers
Overview:
During the late 21st century the wet navies of Earth began to decline. The birth of the Terran Alliance in 2086 led to a general decline in national militaries all over the planet. Newer technologies like improvements in aerospace engineering made naval surface craft obsolete. The final blow came with the colonization of Tau Ceti or New Earth. Following the first Exodus most planets had a single world government with no need to control the seas against rival nations. By this time other military innovations rendered wet navies completely extinct. It wasn’t until the mid 28th century when the Star League authorized many research projects to stay ahead of ever expanding House militaries that wet navies were even thought of again in a practical way. An idea was floated that if a large nautical (wet naval) force could be inserted onto a contested world with large bodies of water it could give the SLDF a strategic advantage. Many criticized this as backward thinking but the project went ahead. Work stopped with the Amaris Coup but was found in the aftermath by the rebuilding Terran authorities. Despite the high cost work went ahead on what was dubbed the Anchorage class Dropship for use by the Royal Marines.
Capabilities:
This dropship has many unusual capabilities. For starters the Anchorage can only set down in water not on land. This wet naval carrier was specifically designed to splash down on large bodies of water and stay a float indefinitely. Deploying a full battalion of nautical forces quickly the Anchorage is one of a kind. The lowest deck of the ship which is submerged when floating carries a company of submarines. While the deck above which is at water level when floating carries two companies of heavy nautical surface vessels. To facilitate the launching and recovery of these vessels the Anchorage has no landing struts (so it can’t land per say) and it’s engines are mounted center mass rather than in the dropships aft section. These engines are able to achieve 2.5Gs at maximum burn.
With nearly double the structural integrity of an Overlord class Dropship the Anchorage has excellent armor protection. The vessel’s armament is also impressive. One Long Tom Artillery Piece and three Arrow IV Artillery Systems keep any enemy nautical vessels far away from the Anchorage when it is a float. Also these Artillery Systems can help Marine forces advance on land providing devastating long range firepower. Eighteen Extended Range Particle Projection Cannons, eighteen Autocannon/10s, and thirty Extended Range Large Lasers round out the dropships arsenal. These weapons are responsible for keeping aerospace fighters away and when on sea destroying any units that are foolish enough to get too close.
Deployment:
The Wet Naval Carrier was named in honor of the final sea battle of the Amaris Coup. During the invasion of North America the SLDFs opening thrust came across the Bering Strait into Alaska. Despite a good start elite Amaris forces drove the SLDF back threatening to halt the invasion altogether. Using a daring flanking maneuver Star League forces came a shore at the city of Anchorage. Fighting off some stiff resistance the SLDF regained the invasion’s initial momentum and never looked back. So all Dropships of this class are to be named in honor of a famous sea battle from history. Entering limited production in 2772 it is unknown how many Anchorages will be constructed over time. Currently there are a total of five craft in service all with the Royal Marines but even with plans to expand that force it is doubtful that more than fifty of these vessels will ever be built.
* Coblitz Main Battle Tank.hmv (7.05 KB - downloaded 1 times.)
* Anchorage class Dropship.hma (5.49 KB - downloaded 2 times.)
-
Takiro FM Terran Republic - Warships « Reply #7 on: February 08, 2008, 06:23:23 PM »
Genesis class Corvette
In service: 2756
In class: 13
Mass: 400,000 tons
Sail Integrity: 4
Thrust: 4/6
Fuel: 3,000 tons
Structural Integrity: 60
Armor: 480 tons Lamellar Ferro Carbide (N: 96, FL/R: 86, AL/R: 86, A: 76)
Docking Collars: 2
Fighters: 18
Small Craft: 4
Crew: 169 minimum (29 Officers, 140 Enlisted)
Lifeboats: 20
Escape Pods: 0
Grav Decks: 1 95 meter
Cargo: 26,908 tons
Bay 1: Small Craft (4) 2 doors
Bay 2: Fighters (18) 6 doors
Bay 3: Cargo (26,908 tons) 2 doors
Other Equipment
Lithium Fusion Battery & HyperPulse Generator (HPG)
Weapons: (Heat Sinks: 2,505 [5,010])
Forward
6 Medium Naval PPCs
10 Extended Range Large Lasers
Fore Left/Fore Right
6 Medium Naval PPCs
10 Extended Range Large Lasers
Left Broadside/Right Broadside
10 Extended Range Large Lasers
Aft Left/Aft Right
3 Medium Naval PPCs
10 Extended Range Large Lasers
Aft
6 Medium Naval PPCs
10 Extended Range Large Lasers
Ammo:
None
OVERVIEW
When the SLS Genesis was launched in the year 2756, press agents working for Blue Nose Clipperships hailed it as the first of a new breed of Star League warship, the culmination of centuries of naval experience, incorporating the most advanced hardware available in a compact and lethal package which would set the pattern for all warships that would follow it. Of course this was not exactly the case.
The Genesis began her existence as Blue Nose Clipperships' offering to the competition that would eventually produce the Magpie class Corvette. Though rejected by the SLDF in favor of the substantially less expensive Di Tron design, a number of Admirals were none the less intrigued by the Blue Nose design, impressed with the combination of speed, armor protection and firepower they were able to accommodate on such a small hull. Seeing the ship as an ideal raider, they succeeded in convincing the remainder of the admiralty to contract the company to construct a handful of examples for evaluation. In the process Blue Nose decided to turn the class into a showcase of modern technology and advanced design.
Though SLS Genesis was launched amid great fanfare describing her as the future of naval warfare, many Admirals considered the Genesis and her sister ships to be far too radical. One famous complaint, which has recently resurfaced, had to do with what the ship was supposed to be. The Star League classified the vessel as a destroyer even though it was actually the size of a large corvette massing slightly less than the venerable Vincent class. Its performance and intended role further complicated things actually placing it within the frigate classification. Admirals simply didn't know what to do with the Genesis. Caught up heavily in Star League traditions, few used the ship as it was intended. Most just used the Genesis' under their command as simple pickets or AA ships, and as a result the class soon earned a reputation as an overpriced but adequate warship, which could do its job well, but had far too many expensive bells and whistles when compared to ships like the Lola III, Essex, and Dewey.
It took four years for the Genesis to break free of this reputation, and even then it took the direct intervention of General Kerensky. In 2760, Kerensky had all six existing Genesis class vessels organized into a single force, designated the 12th Fleet Destroyer Squadron, under the command of Rear Admiral Ross Lamarche. Assigned the task of suppressing pirate activities in the Taurian Concordat, Lamarche set his warships on long, independent patrols (which the Genesis was especially good at and was in fact designed for). The excellent performance of the Genesis and her sisters during this duty, including a string of highly successful strikes into the Pirate's Haven star cluster, finally validated the design. Blue Nose Clipperships (the original designers) was soon called upon to resume construction of the Genesis class (suspended in 2759) with an order for twenty more ships.
Three years later however, the Amaris Coup struck the Star League. Blue Nose had since completed seven new Genesis class vessels. Six of these, known informally as the Mis fleet (each was named for a character in Victor Hugo's classic novel Les Miserables), had already been assigned to the 12th Fleet Destroyer Squadron, while the seventh, the Cosette, was undergoing shakedown trials at Mars. After first helping to cripple the Blue Nose Yards, the Cosette moved in system along with a pair of Riga class destroyers in order to support SLDF ground forces fighting in Geneva. Unknown to the officers of the small fleet, however, Amaris had gained control of the SDS system. Both Rigas were lost to ground fire, while the Cosette found itself in a game of cat and mouse with the Caspar drones, eventually being caught and overwhelmed.
CAPABILITIES
One of the most surprising things about the Genesis was its massive weapons load. Despite its four hundred thousand ton mass, the Genesis packed an incredible arsenal of weaponry. Thirty medium naval PPCs in ten turrets give the ship firepower comparable to destroyers half again its size. The ship's secondary firepower is also remarkable. Dissatisfied with naval missiles for anti-fighter defense, the designers decided on an at the time unprecedented array of eighty improved large lasers. Though these lasers lack the range of naval missiles, they have more than enough range to engage fighters. A full wing of eighteen fighters further augments the Genesis' offensive power.
As it was supposed to be a showcase of the future of naval architecture, Blue Nose Clipperships spared no expense on their warship. Though carrying less than five hundred tons of armor, the advanced Lamellor Ferro Carbide composite provides excellent protection.
To increase the ship's flexibility, designers included a lithium fusion battery system, and a pair of docking collars. Compared to its contemporaries, the Genesis carried a pitiful amount of cargo, however a little less than twenty seven thousand tons of space was more than enough for the ship to operate continuously for a year.
DEPLOYMENT
The surviving twelve Genesis class ships, all part of the 12th Fleet Destroyer Squadron, led the way into the Terran Hegemony when Kerensky launched his campaign against Amaris. Genesis class vessels were often called upon to conduct highly dangerous scouting operations against occupied worlds, and more than once they did not come back. By the end of the campaign, only one ship, the Marius, was still operational. Four others, the Eponine, Gavroche, Javert, and the Genesis herself, were crippled but salvageable. Only the Javert and Genesis were repaired prior to the Exodus and together with the Marius departed the InnerSphere with General Kerensky. Despite their poor conditions the Eponine and Gavroche were targeted for immediate renovation by the fledgling Royal Navy do to their high tech advantages. As they were recommissioned the Terran Admiralty made the controversial decision to change the Genesis ship classification to that of Corvette. Some remain dissatisfied with this designation and predict it will cause problems within the fleet. Admiral Knight has voiced her support for the change stating that the Genesis will be able to serve the new nation best as a Corvette. Rumors of construction of new Genesis class Corvettes and other Star League era warships continue to abound. This will probably occur after the conclusion of the current naval renovation effort.
Bainbridge class Destroyer
In service: 2765
In class: 11
Mass: 620,000 tons
Sail Integrity: 4
Thrust: 5/8
Fuel: 3000 tons
Structural Integrity: 75
Armor: 337 tons, Ferro Carbide (N: 60, FL/R: 55, AL/R: 50, A: 48)
Docking Collars: 0
Fighters: 12
Small Craft: 6
Crew: 198 minimum (33 Officers, 165 Enlisted)
Lifeboats: 13
Escape Pods: 30
Grav Decks: 2, 175 & 150 meters in diameter
Cargo: 40,948 tons
Bay 1: Fighters (12) 3 doors
Bay 2: Small Craft (6) 1 door
Bay 3: Cargo (40,948 tons) 2 doors
Other Equipment
Lithium Fusion Battery & HyperPulse Generator (HPG)
Weapons: (Heat Sinks: 1,400 [2,800])
Forward
2 NAC-35s
2 NL-45s
2 ER PPCs
Fore Left/Fore Right
3 Light NPPCs
2 ER PPCs
Left Broadside/Right Broadside
2 NAC-35s
1 NL-45
2 ER PPCs
Aft Left/Aft Right
3 Light NPPCs
2 ER PPCs
Aft
4 NL-45s
2 ER PPCs
Ammo:
900 rounds of Naval Autocannon/35 ammunition
OVERVIEW
The Bainbridge –class DDA was designed to meet a need for a faster type of destroyer to screen the SLDF’s Sovremenyy and Milwaukee class cruisers.
Unlike its competitor, the Gorgon –class, the Bainbridge was not designed by a corporate committee; rather, she was designed by a team by SLDF naval officers loaned out to newly expanded Warship builder Zaker Aerospace. Based in the Castor system, the company had been a Jumpship builder for decades prior to 2756. In that year, Hugo Zaker, replacing his father Bruno, took the position of CEO. Hugo was a nervous man, always seeing threats to himself and his company. His obsession with defending himself led him to favor a stronger defense for the Star League, and in 2758 he ordered the construction of two new building docks capable of constructing destroyers. However, Zaker was seen as a nut by most of the SLDF’s Shipbuilding Office, and for a time it seemed that no orders would be forthcoming. Things changed however, with the DDA competition. Most of the SLDF’s normal contractors were busy with other projects, leading the Admirals to search for someone new. Given his low standing with the Powers-That-Be, Zaker might still have not landed that contract had it not been for his personal friendship with Ryan Richter. Richter’s concerns about the SLDF’s approach to shipbuilding mirrored Zaker’s own, and the two became close allies in pushing through their ideas. As one of the major forces behind whole concept of the fast cruiser, Richter had a good deal of influence regarding the ships intended to screen said cruisers. He used this influence to win Zaker the contract to develop and build the Bainbridge class DDA.
CAPABILITIES
The Bainbridge was built to accompany and screen fast cruisers. A Lithium Fusion Battery enabled it to scout ahead of these formations for enemy defenses prior to actual combat. It’s 4G maximum thrust gives it the acceleration to keep up with the cruisers; normally the DDAs were deployed ahead of the cruisers using their weaponry to clear a path for the bigger ships. The ship’s armament reflects the fact that the Bainbridge was intended to work with ships carrying long-range firepower. The main guns of the Attack Destroyer are six Naval Autocannon/35s mounted in pairs in the nose and in the broadsides. These cannons have immense striking power, but only limited range. To give the ship some weapons that can hit from a distance, the Bainbridge mounts three light NPPCs in each side, and also mounts a number of NL-45s for anti-dropship fire. Rounding out the ship’s array are 16 ER PPCs, which give a good anti-fighter capacity.
A desire to keep costs under control lend to the designers leaving off the Gorgon’s Lamellor ferro-carbide armor in favor of standard ferro-carbide plate. This decision turned out reasonably well; the ship is well armored for a destroyer and unlike its competitor its rear armor is still good (80% as thick as that in front). Moreover, the Bainbridge carries twice as many fighters as the Gorgon class. Given the three squadron fighter complements of the Milwaukee and Sovremenyy classes, it was intended that a complete fighter regiment be assigned to a fast cruiser and its three (intended) escorting DDA thus providing the fighters with an organic command structure. Last but certainly not least, the naval officers who designed the Bainbridge gave special attention to keeping her well maintained. The ships access panels are easy to open and her systems were designed with a view to making maintenance easy. Coupled with her excellent crew quarters, these features made a tour of duty on a Bainbridge an assignment to be coveted.
DEPLOYMENT
Like the Gorgon class, the first two vessels (the Bainbridge and the Ruben James) were assigned to exercises upon completion in the summer of 2765, these being done paired with the Sovremenyy class cruiser Udaloy. The trials of the Bainbridge class turned out much better than the competition, with the convoy raiding mission the Gorgon had failed at seeing the two DDAs swinging around and easily killing the Avenger –class dropships sneaking up on the cruiser, following the raiders pound the convoy’s accompanying Black Lion (the Nelson) to simulated scrap. The results of the trials convinced the admiralty to accept the Bainbridge as its new DDA and an order was placed for 54 of them.
Construction of the next pair, the Kane and the Fuller, began at once. On November 29th 2766 both ships were commissioned into the fleet. However, by this time events in the Hegemony had thoroughly alarmed Hugo Zaker. When the SLDF garrison of Castor had been pulled out in March they had been replaced by the 74th Republican Guard (the Hammurabi Division). For once Zaker’s instincts found an audience, for many within the SLDF harbored suspicions about Stephen Amaris. Alone among the Hegemony’s shipbuilding systems, Castor began to take precautions. Commodore Alan Burke, the system’s ranking naval officer had SLDF techs install a virus into the systems Caspar drones control computers, enabling Burke to take control of them at any time. On December 12th the SLDF’s 95th Special Operations Group (SOG) entered the system on its way to the Periphery. Burke and Zaker delayed the unit’s departure on every pretext, hoping to keep some ground forces close to hand. When Amaris made his move on the 26th, their planning was vindicated. The Hammurabi Division struck the local defense forces on the planet without warning and then tried to turn the system’s SDS weaponry against Burke’s ships. The shock they received when their drones would not respond soon paled compared to the shock when the drones moved in-system towards the planet and there engaged its ground-based weapons. Though the drones were all but wiped out, they crippled the defenses enough for Udaloy and the four DDAs to rain a furious barrage down upon the Amaris troops. As they did, the 95th SOG landed a safe distance away. When the bombardment lifted, they charged in and by the morning of the 29th the 74th Republican Guards were no more. Castor still belonged to the Star League.
Zaker continued production of the Bainbridge throughout the war to liberate the Terran Hegemony. Though production was slow due to lack of materials, the yard produced 6 more ships, with construction slightly outpacing losses. Bainbridge class ships were used in twos and threes to screen Sovremenyy class cruisers, often operating in the vanguard of planetary assaults. Despite this, on the eve of the assault on Terra there were six operational ships left and these were assigned along with the Sovremenyy class cruisers Sovremenyy and Udaloy to the lead group of SLDF warships for the attack. Though the DDAs gave a great accounting of themselves (by some counts, they and the two CAs destroyed 35 Caspars) all six were lost. They were not the last Bainbridge class ships produced though as Zaker Aerospace delivered one more ship, the Edsall, in 2780. Edsall left on the Exodus with General Kerensky.
Hugo Zaker wholeheartedly supported the foundation of the new Terran Republic after refusing to leave the InnerSphere and his family’s business. His shipyards in the Castor system have restored many vessels (mainly destroyer size and below) for the Royal Navy including a Bainbridge class Destroyer, the Peary. Zaker has also become obsessed with defeating the evil Captain-General Kenyon Marik who failed to help the Star League defeat the Usurper. Construction of new Bainbridges could commence as soon as the Terran Naval Restoration Project is completed.
Sovremenyy class Battlecruiser
In service: 2760
In class: 6
Mass: 830,000 tons
Sail Integrity: 5
Thrust: 5/8
Fuel: 2500 tons
Structural Integrity: 80
Armor: 1300 tons, Lamellar Ferro Carbide (N: 228, FL/R: 224, AL/R: 224, A: 224)
Docking Collars: 4
Fighters: 18
Small Craft: 8
Crew: 243 minimum (41 Officers, 202 Enlisted)
Lifeboats: 0
Escape Pods: 20
Grav Decks: 2, 55 & 90 meters in diameter
Cargo: 29,269 tons
Bay 1: Fighters (18) 4 door
Bay 2: Small Craft (Cool 2 doors
Bay 3: Cargo (29,269 tons) 2 doors
Other Equipment
HyperPulse Generator (HPG)
Weapons: (Heat Sinks: 2235 [4470])
Nose
2 Killer Whale Missile Launchers
Fore Left/Fore Right
3 Heavy Naval PPCs
1 Killer Whale Missile Launcher
Left Broadside/Right Broadside
3 Naval Autocannon/30s
2 Heavy Naval PPCs
Aft Left/Aft Right
3 Naval Autocannon/30s
2 Heavy Naval PPCs
1 Killer Whale Missile Launcher
Ammo:
60 Killer Whale Missiles
1200 rounds of Naval Autocannon/30 ammunition
OVERVIEW
Though General Rebecca Fredasa's New Arms order is best known for producing the Sovetskii Soyuz, the intent of the program was in fact far more reaching, with virtually every arm of the SLDF fleet due for modernization. Though the Periphery Uprising and the Amaris Coup would rip through the League before much of this work could be completed, a series of new ships none the less made it into service.
Among these was a new high speed cruiser intended to replace the aging and scarce Kimagure, giving the SLDF a fast attack capability its fleet thus far sorely lacked. The first of this new Sovremenyy class would enter service in 2760.
CAPABILITIES
When one gets a look at a Sovremenyy, it is not hard to imagine why the class earned the nickname Doppleganger. Blue Nose Clipperships used the basic design of their proven Sovetskii Soyuz as their template, and at first glance the two ships are almost indistinguishable. Only the slightly enlarged aft section and the twin forward PPC mounts give the Sovremenyy away.
However these similarities hide a world of differences in capabilities reflecting the two different design principles that went into the ships. The Sovetskii Soyuz was a stopgap measure, a design that compromised practically everything in the name of being produced as quickly as possible. The Sovremenyy compromises nothing in the name of expediency. The designers sought to squeeze every ounce of combat potential they could in the modified hull, and they succeeded in a grand style. Though the ship's main battery of fourteen Kreuss XX naval particle cannons and twelve Scarborough autocannons do not give the Sovremenyy the apocalyptic firepower of such heavily armed ships as the Black Lion, they still give her a terrifying punch, while the ship's heavy armor belt outclassed even some battleships thanks to the use of advanced Lamellor Ferro Carbide composites.
Anything the Sovremenyy can't outfight, it can almost certainly outrun thanks to its powerful propulsion system, allowing the ship to produce a full four Gs of thrust at maximum output. About the only thing missing from the design is a lithium fusion battery, and even this was only out of necessity. With so much else crammed in the hull, designers simply could not find the room for a LF battery without reducing the ship's already tiny cargo capacity even further.
DEPLOYMENT
Pending final approval for large scale deployment, Bluenose Clipperships produced Sovremenyys at a rather leisurely pace, launching six ships in the years leading up to the Amaris Coup. The last one produced, the Oktyabrskava Revolutsiva, was just completed on Christmas Eve 2766, and was seized intact by Stephan Amaris's forces. Unknown to everyone but Amaris's top officers, the ship remained over Terra as Amaris's last defense and possibly his escape craft until just a month before the final assault by Kerensky, when it and two battalions of Rim Worlds troops disappeared. It is believed the ship and troops fled to the Periphery to avoid destruction by the vengeful SLDF. Unfortunately the current situation prevents further investigation but the Oktyabrskava Revolutsiva and her crew are considered war criminals by the Terran Republic.
Three of the remaining ships; the Sovremenyy, Nesokrushimyy, and Udaloy were destroyed during the campaign to retake the Terran Hegemony from the forces of the Usurper. The Osmotritelnyy survived the Amaris Conflict intact and departed with General Kerensky on the Exodus. The Provornyy was damaged during Operation Liberation and repaired after the SLDF began Operation Exodus. In reality her crew elected to remain behind with the new Terran Republic, so the ship’s repair was prioritized later than other ship’s that left with Kerensky. The Provornyy became one of the first warships to be commissioned by the Terran Royal Navy.
Construction of new Sovremenyys, now reclassified as Battlecruisers by the New Republic, is being considered after the conclusion of the current naval renovation effort. This new construction would probably not begin for sometime as many serviceable derelict vessels still await repair.
Hegemony class Battlecruiser
Introduction: 2316
In Class: 72
Mass: 900,000 tons
Sail Integrity: 5
Thrust: 3/5
Fuel: 1,000 tons
Structural Integrity: 80
Armor: 1439 tons, Standard (N: 104, FL/R: 104, AL/R: 104, A: 104)
Docking Collars: 4
Fighters: 18
Small Craft: 8
Crew: 301 minimum (52 Officers, 249 Enlisted)
Lifeboats: 35
Escape Pods: 20
Grav Decks: 3 100 meters in diameter
Cargo: 40,310 tons
Bay 1: Fighters (18) 4 doors
Bay 2: Cargo (40,310 tons) 5 doors
Bay 3: Small Craft (Cool 2 doors
Weapons: (Heat Sinks: 5,310)
Fore Left / Fore Right
9 NAC 30s
1 White Shark Missile Launcher
Left Broadside / Right Broadside
12 NL 45s
2 White Shark Missile Launchers
Aft Left / Aft Right
12 NL 45s
2 White Shark Missile Launchers
Ammo:
1620 rounds of Naval Autocannon/30 ammunition
200 White Shark Missiles
Refit Notes:
Upgraded with Modern Interplanetary Drive, same thrust rating 3/5
Cargo: 121,182 tons
OVERVIEW
The pride of the Terran Navy was originally designated the Alliance class
Battlecruiser. The ship was designed by James McKenna following the success of the Dreadnought class Battleship, the Dart class Cruiser, and the Essex class Destroyer. Locked in a bitter partisan battle the Alliance Parliament nonetheless overwhelming approved funding for this new vessel. No doubt these corrupt politicians were hoping to keep Admiral McKenna busy rather than wisely investing in a cutting edge naval project. McKenna forged ahead in spite of this obvious pandering to create one of the finest warships of all time. As the ship neared completion the situation on Terra grew out of control as different political factions began to fight violently for control. Of course, McKenna took action to prevent further loss of life by forcibly disbanding the Alliance in favor of a new regime. On the same day that McKenna announced the government’s Charter he also officially renamed the Battlecruiser class in its honor, the Hegemony.
CAPABILITIES
James McKenna had envisioned the Hegemony class Battlecruiser as a formidable
mobile command vessel that could direct a major naval campaign effectively. The vessel utilized some of the most advanced technology of the day. For example, the Battlecruiser was the first warship ever equipped with Type II Fusion Engines enabling it to achieve an impressive 2.5Gs at maximum thrust. The warship’s superior speed and advanced communications gear allowed commanders to lead from any position along the battle front. In fact the Hegemony was so effect operating in mutually supporting battlegroups of six or more warships that many battlecruisers to this day, such as the Cameron class, are built around this principle. The main arsenal of the Hegemony is fashioned to take full advantage of its intended role. Eighteen Naval Autocannon/30s located in the forward sides provide most of the Hegemony’s punch. Forty eight Naval Laser-45s support these massive main guns and are located in the vessel’s broadsides and aft section. This weapon array created two very distinct gaps in its offensive coverage which is an intentional design element. The Hegemony would form a battleline with other warships covering the fore and aft of the line, presenting essentially a wall of death. This tactical doctrine, harkening back to the good ole days of sail powered warships calmly sailing broadside to broadside and hammering each other to bits, pretty much dictated a pure broadside fighter, and the Hegemony class is certainly that. Though unable to project fire directly forward or aft, the Battlecruiser could deliver a concentration of fire from her broadsides that was, for its day, unprecedented. Even the warship’s ten White Shark missile launchers included to provide small craft defense are located in the same areas. These missiles were often used in conjunction with the Hegemony’s other capital weapons. So the Battlecruisers eighteen fighter and four dropships were expected to take out any other small craft. The only major drawback was that the Hegemony only had forty thousand tons of cargo space available and as such could not operate independently. However, since the cruiser was designed to operate as part of a group this didn’t seem to matter very much.
DEPLOYMENT
The Hegemony class was not completed in time to see combat during the demise
of the Terran Alliance. Instead the warship’s first true test came during the Campaigns of Persuasion were it performed exceptionally well. After one hundred years of service the Battlecruisers underwent a major refit to install Modern Interplanetary Drives. This resulted in the tripling of the ship’s cargo space eliminating the Battlecruisers constant need of resupply. With this handicap removed the Navy began to deploy Hegemony’s in a more haphazard solo fashion. This combined with the neglect shown the fleet after the introduction of the BattleMech led to the loss of some vessels during the latter phases of the Age of War. Despite these setbacks the design went onto prove its worth during the Reunification War and the early years of the Star League. In the mid-2600s the League Admiralty called for a new Battlecruiser to fill the gap created by the aging Hegemony.
Unfortunately what they got was the Cameron class which was clearly outperformed by the ancient Hegemony class in a series of wargames. While this added to the vessels mystique and led to special refits for one Hegemony class ship, the vessels design age was clearly catching up. This was shown annually during regular maintenance which had to be doubled then tripled on these elderly craft. Appropriately this venerable class was finally retired after the Star League’s new Battlecruiser, named the Black Lion in honor the first Hegemony class ship, proved wildly successful. Some were sold to the Great Houses while others remained in mothballs serving as floating space museums until the Amaris Coup. Many of these formidable veteran ships serve in the fleets of every Great House including the Terran Republic.
NOTABLE SHIPS:
One of the best known warships of all time and the first ship of this class was the
THS Black Lion. The Lion served as the flagship for Director-General James McKenna throughout his reign. The grand old ship commanded by McKenna himself during the Campaigns of Persuasion distinguished itself several times over. Always at the vanguard of a Terran taskforce the Black Lion’s mere presence inspired Hegemony troops onward even during the hardest battles. Even in the dark aftermath of the Symra Ambush the battlecruiser’s mere appearance helped restore order. It wasn’t long after that James McKenna died but the Black Lion continued to serve on as the Hegemony’s flagship. Eventually the noble vessel was retired but not decommissioned in orbit of Earth where the ship was converted into a fully functional museum. Here it remained until the Usurper attempted to seize Earth. The crew of the ancient relic almost managed to maneuver the Lion into position to support the Black Watch. Republican troops in control of Terran SDSs fired first however and destroyed the Hegemony’s flagship. The remnants of the Black Lion crashed into the Pacific Ocean several miles from Unity City. Some have proposed a massive salvage operation to restore the old Terran flagship but this massive undertaking would clearly have to wait until the current threat level has receded.
Another Hegemony class that is known throughout the InnerSphere is the THS
Kiev. One of the final ships of her class launched in 2420 with advanced (now standard) systems the Kiev quickly distinguished itself. The invention of the BattleMech left the Terran Navy in poor condition and by 2470 the Kiev was one of the few Hegemony warships that remained battle worthy. When Director Theodore Cameron ordered a first strike against a gathering Marik fleet based at Oriente he chose the Kiev as his flagship. The assault was wildly successful with the Kiev playing a major role destroying three Marik warships and driving the Captain-General’s own Battlecruiser from the field. With this the ship became known as the Eagle’s Bane on both sides of the border. The ship while loved by the Terrans had no place in the Star League due to its past actions versus Marik and was retired. However after the League’s fall Ian Sinclair ordered her restoration resulting in Kenyon Marik’s vow to destroy the Kiev once and for all.
* Genesis class Corvette.hma (8.95 KB - downloaded 6 times.)
* Bainbridge class Destroyer.hma (9.17 KB - downloaded 4 times.)
* Sovremenyy class Battleruiser.hma (5.82 KB - downloaded 5 times.)
* Hegemony class Battlecruiser.hma (9.15 KB - downloaded 6 times.)
-
Takiro Project Phoenix - Clint, Challenger & Phoenix « Reply #8 on: February 08, 2008, 08:12:38 PM »
CLNT-5R Clint
Mass: 40 tons
Chassis: Andoran Model IIIes
Power Plant: Pitban 240
Cruising Speed: 64.8 kph
Maximum Speed: 97.2 kph
Jump Jets: Pitban LFT-50
Jump Capacity: 180 meters
Armor: Durallex Medium Ferro-Fibrous
Armament:
1 Donal PPC
2 Martell Model 5 Medium Lasers
Manufacturer: Aldis Industries
Primary Factories: Liverpool Terra
Communications System: O/P 300 COMSET
Targeting and Tracking System: Sloane 220 Lockover System with Beagle Active Probe
Type: CLNT-5R Clint
Technology Base: Inner Sphere
Tonnage: 40 tons
Equipment: Mass
Internal Structure EndoSteel 2
Engine 240 11.5
Walking MP: 6
Running MP: 9
Jumping MP: 6
Heat Sinks 10 (20) 0
Gyro 3
Cockpit 3
Armor Factor 125 7
Internal Structure Armor
Head 3 9
Center Torso 12 18/4
Right/Left Torso 10 16/4
Right/Left Arm 6 10
Right/Left Leg 10 17
Weapons and Ammo Location Critical Tonnage
PPC RA 3 7
Medium Laser CT 1 1
Medium Laser LT 1 1
Beagle Active Probe RT 1 1.5
Jump Jets RL 2 1
Jump Jets LL 2 1
Jump Jet RT 1 0.5
Jump Jet LT 1 0.5
Overview
The CLNT-5R is a new version of the venerable Clint which has recently entered service with the Terran Republic. Produced by Aldis Industries, the ‘Mech is something of a mystery. Following the collapse of the Star League Aldis used an unknown source of funding to purchase several bankrupt Terran weapons manufacturers. One of the companies they purchased was Lang Industries and their ‘Mech factory at Liverpool in Britain. The company quickly restored the Liverpool factory, which resumed production of Lang’s flagship product, the Shadow Hawk. It was soon after this that the company began production of the Clint. It is unknown how the company managed to put the Clint into production as there is no record of either Lang or Aldis having acquired the blueprints and technical schematics for the Clint. The company has refused to answer any questions about how they acquired the design and the Republic, needing all the weapons they can get, has not questioned the source of the design. The new Clint has proven very popular with Republic Mechwarriors and has been deployed with a number of units in the TRAS.
Capabilities
The Clint is designed to fill the role of a scout ‘Mech and flanker. The new model of the Clint combines the excellent mobility of the original model with a more potent weapons array and stronger armor. Unlike many other new designs deployed by the Republic, the Clint makes only limited use of advanced technology. This appears to have been a conscious choice of the design team, by using mainly proven technologies, they were able to keep costs down, speed manufacturing and reduce maintenance requirements.
The CLNT-5R uses the Pitban 240 engine, which is the same model that was used by the original version. Unlike many modern ‘Mechs, the Clint does not use an extra light engine. Using an older Pitban model not only reduced the cost of the design, but it also has the added benefit of dramatically increasing the life expectancy of the design. The high power output of the Pitban 240 enables the ‘Mech to move at high speeds, allowing it to excel as a scout mech. The Clint also retains the jump jets found on the original model, allowing it to quickly cross any obstacles it many encounter. However, unlike the original model, the CLNT-5R uses the Pitban LFT-50 model which is also used by the Shadow Hawk and is easier to repair and maintain then the original Andorean Model JJII.
The chassis of the Clint is built using advanced Endo Steel Alloys. The weight savings gained from the use of the lighter chassis was used to increase the amount of armor carried by the mech. The Clint’s 7 tons of Ferro-Fibrous armor provides the ‘Mech with almost twice the protection of the original model.
The main weapon of the Clint is the reliable Donal PPC. The use of the PPC solves one of the major problems faced by the original Clint, the limited amount of ammunition for the autocannon. In addition, the PPC provides the ‘Mech with a stronger punch than the old Armstrong Autocannon. In order to compensate for the added heat output, the Clint makes use of double heat sinks, which allows the ‘Mech to easily handle the added heat burden. Supporting the PPC are 2 medium lasers. These provide close in defense at ranges where the PPC is ineffective.
The design team also made significant changes to the Clint’s electronics, removing many of the unique components used in the original model. The communication system was replaced with the O/P 300 COMSET which is also used on the Shadow Hawk BattleMech. One of the few original electronic components that was retained on the new Clint was the Sloane 220 Lockover Targeting & Tracking system. The Sloane 220 Lockover system is one of the most advanced (and complex) targeting systems ever developed and provides the ‘Mech with excellent targeting accuracy. The Sloane 220 Lockover is supplemented by a Beagle Active Probe. The active probe’s advanced detection capabilities enable the Clint to quickly locate enemy units on the battlefield. Combined with the Sloane 220 Lockover, the system allows a Mechwarrior to quickly locate and destroy any potential threats.
One of the biggest problems with the original Clint was the use of nonstandard components which made the ‘Mech a maintenance nightmare. In order to increase the reliability and serviceability of the Clint, the new model was designed to use standard components. The use of standard components has proven very successful; the CLNT-5R has received very high marks from Republic technicians for reliability and ease of repair.
Deployment
The Clint has only recently entered service with the Terran Republic. The units were assigned to the Deneb Light Cavalry, where they quickly proved popular with the troops. The Deneb Light Cavalry use the ‘Mech as a light assault unit, providing support to the light ‘Mechs that are found in the unit. The Clint has also begun to be deployed to other units in the Republic as a replacement for destroyed or damaged scout ‘Mechs. The Clint has proven highly successful in this role, as the BattleMech’s heavy armor and weapons allow it to survive in situations where lighter ‘Mechs can not.
CHR-2A Challenger
Mass: 80 tons
Chassis: Wells 990
Power Plant: Vlar 320XL
Cruising Speed: 43.2 kph
Maximum Speed: 64.8 kph
Jump Jets: Hildco Model 12
Jump Capacity: 120 meters
Armor: Durallex Heavy
Armament:
4 Magna Mk III Heavy Lasers
2 Magna Mk II Medium Lasers
1 Magna Mk I Light Laser
Manufacturer: Earthwerks Limited
Primary Factories: Carver V
Communications System: Tek Battlecom with Guardian ECM
Targeting and Tracking System: Dalban Hirez
Type: CHR-2A Challenger
Technology Base: Inner Sphere
Tonnage: 80 tons
Equipment: Mass
Internal Structure 8
Engine 320XL 11.5
Walking MP: 4
Running MP: 6
Jumping MP: 4
Heat Sinks 20 (40) 10
Gyro 4
Cockpit 3
Armor Factor 247 15.5
Internal Structure Armor
Head 3 9
Center Torso 25 40/10
Right/Left Torso 17 26/8
Right/Left Arm 13 26
Right/Left Leg 17 34
Weapons and Ammo Location Critical Tonnage
Large Laser RA 2 5
Large Laser RT 2 5
Large Laser LT 2 5
Large Laser LA 2 5
Medium Laser LT 1 1
Medium Laser RT (R) 1 1
Small Laser H 1 0.5
Guardian ECM CT 2 1.5
Jump Jets RL 2 2
Jump Jets LL 2 2
Overview
The Challenger was designed in response to a design request by the Terran’s Marine Corps Royal CAAN units. In 2782 the Marines issued a request for a new assault ‘Mech to meet their specific requirements. Tasked with securing planetary beachheads, the Marines required an assault ‘Mech that would be capable of operating for extended periods of time without being resupplied. The Marine requirements also called for superior mobility and heavy armor. Very few companies were able to meet the marines’ stringent requirements. One of the few that did submit a design was Earthwerks. The Earthwerks proposal was based on the old Charger BattleMech. After the failure of the Charger, Wells Technologies faced serious financial problems. After Wells Technologies went bankrupt, the company’s factory and other assets were purchased by Earthwerks. The large Wells Technologies factory was retooled to produce Thunderbolt and Griffin BattleMechs, expanding Earthwerks BattleMech production capacity. The plans for the Charger, which were also acquired when Earthwerks purchased Wells Technologies, were quickly buried in the company’s computer core, with the expectation that they would never be used again. When the Marines issued the request for a new assault ‘Mech, the Earthwerks’ engineers quickly realized the Charger chassis ideal for the project. The Charger was a very robust design and well known for requiring minimal maintenance. The problem with the Charger was the massive LTV 400 series engine, which left little room for other equipment. The Earthwerks team quickly solved that problem by using the newly designed Vlar 320 Extra Light engine. This engine freed up enough space and mass to transform the Charger into a truly formidable design. The design was so radically different from the Charger that the company decided to rename it the Challenger. In 2783 the Challenger prototype was turned over to the Marines for testing. The design was vastly superior to all the other entrants and in 2784 the Marines chose the Challenger as their new assault mech. Problems then arose when Earthwerks was unable to meet the production schedule required by the Marines, due to the fact that their factories were already working at full capacity producing ‘Mechs for the Army. The main Earthwerks facility in Russia was of such poor quality that the Earthwerks personnel were forced to spend most of their time performing maintenance on the existing lines and so they had no time to help build a new line for the Challenger. The problem got so bad that the Marines threaten to revoke the contract if Earthwerks was unable to meet the production schedule. A last minute solution was worked out when Vice Admiral Lorenzo Gonzales met with Gregori Mendel, the CEO of Earthwerks. The Marines agreed to turn over their Carver V assembly facility, which had been established by the SLDF after the liberation of the planet, to Earthwerks. The factory had been producing Victor BattleMechs for the Marines as a stopgap measure until they could acquire a new ‘Mech better suited to their specific requirements. Since the Marines planned to halt production of the Victor when the Challenger entered service, the Carver V facility was the ideal factory to retool to manufacture the Challenger. The line was quickly retooled with the aid of Earthwerks and Marine engineers to produce the Challenger. The first Challenger walked off the assembly line in July of 2785 and the ‘Mechs are being assigned as quickly as they are built to the 1st and 2nd Royal Marines.
Capabilities
The Challenger is the Royal Marines premier assault mech. Unlike most designs used by the Royal Marines, the Challenger is not an Army design that was forced on them. Rather, the Challenger was designed to meet the specific requirements of the Royal Marines for a mobile, hard hitting ‘Mech capable of surviving on the modern battlefield.
The Challenger is based on the old Charger BattleMech chassis. While the design premise of the Charger was a failure, the chassis was well designed and well suited to the Marines’ requirements. The biggest problem with the Charger was the massive LTV engine used to power the mech. The engine took up so much space that there was little room left for other equipment. The Earthwerks engineers solved this problem by using the new Vlar 320 Extra Light engine. The Vlar engine generates 80% of the power of the LTV but weighs less then a quarter of the weight of the LTV engine.
The design team made good use of the extra space, turning the ‘Mech into an excellent front line combat unit. To compensate for the lower speed of the Challenger, the designers installed jump jets, which allows the ‘Mech to jump over obstacles. The Challenger uses the same, proven, Hildco Model 12 Jump Jets that are found on the Victor BattleMech. With so many Victors deployed in the Royal Marines, the use of the Hildco Jump Jets was an obvious choice as it simplified logistics for the Marines.
The Challenger also features improved armor compared to the Charger, allowing it to survive on the modern battlefield. By adding additional armor plating, the designers managed to improve armor protection by over 50%. During field trials, the armor layout of the Challenger managed to defeat all of the newest weapons deployed by the Republic’s weapons research and development team.
However, the biggest difference between the Charger and Challenger is the armament. Where the Charger had less firepower then a Locust with its 5 tiny lasers, the Challenger’s firepower is truly frightening. The main guns are 4 Magna Mk III heavy lasers. These are mounted in the arms and torso of the Challenger, replacing the Magna Mk I Light lasers. The Magna’s are highly reliable weapons and when fired at single target can severely damage or cripple many ‘Mechs.
Supporting the heavy lasers are 2 Magna Mk II medium lasers. Mounted in the BattleMech’s torsos, one of the Mk II’s covers the front arc, while the other covers the rear of the mech. The Marines insisted that the ‘Mech have at least some rear firing weapons, as it is not uncommon for their soldiers to be cut off by enemy forces during a landing operation. Rounding out the weapons is a single Magna Mk I light laser in the head. This is the only weapon retained from the Charger. While the designers tried to fit a Mk II laser in place of the Mk I, the space in the head precluded the mounting of the larger weapon.
With all of the energy weapons mounted on the Challengers, the ‘Mech features an improved heat dissipation system. The designers mounted 20 double heat sinks, which provides the design with more then adequate cooling.
While the Challenger uses the same com and targeting systems as the Charger, the designers improved the capabilities of the ‘Mech by mounting a Guardian ECM. While not required as part of the Marines original specifications, the Guardian ECM has quickly proven popular with the troops. While not as effective as the stealth systems found on the Exterminator or Spector BattleMechs, the Guardian ECM provides a small measure of stealth to the Challenger.
Deployment
The Challenger has only recently begun coming off of the factory line. The majority of the ‘Mechs produced to date have been assigned to the 1st Royal Marines, where they have been replacing the hodgepodge assortment of assault ‘Mechs used by the unit. A smaller number of Challengers have been assigned to the 2nd Royal Marine Brigade which is currently forming up. Unlike the 1st Brigade, currently utilizing a mix of Challenger and Victor assault ‘Mechs for the foreseeable future, the 2nd will only deploy the Challenger in their assault ‘Mech companies.
Variants
Currently there is only 1 variant of the Challenger. The CHR-2S is a designed as a sniper ‘Mech for the Marines. The CHR-2S replaces the 2 torso mounted Magna Mk III Heavy lasers with 2 Blankenburg Extended Range Lasers. The ER Lasers provides the ‘Mech with a strong punch at very long ranges. When used by specially trained Marine Mechwarrior snipers, the Challenger-2S can be used to take out high priority targets such as command ‘Mechs at long range. Current plans call for 1 out of every 4 Challengers manufactured to be a 2S model. There are rumors that the Republic may begin testing a new targeting computer system on the 2S which should increase the accuracy of the ‘Mechs weapons at extreme ranges.
PHX-1X Phoenix
Mass: 100 tons
Frame: FDS Type 42-D Aero
Engine: Vlar 300 Fusion
Armor: StarGlo Ferro-Aluminum
Armament:
3 Aeroquip Gauss Cannons
4 Magna Mk II Medium Lasers
Manufacturer: FDS
Primary Factory: Terra
Communications System: FDS UltraComm Model 101
Targeting and Tracking System: SynCom Aero Lord
Type: PHX-1X Phoenix
Technology Base: Inner Sphere
Tonnage: 100 tons
Equipment Mass
Engine: 300 Fusion 19
Safe Thrust: 5
Max Thrust: 8
Structural Integrity: 10
Heat Sinks: 10 (20) 0
Fuel: 400 5
Cockpit: 3
Armor Factor: 323 18
Location Armor Value
Nose 110
Wings 80 / 80
Aft 53
Weapons and Ammo Location Tonnage
Gauss Rifle Nose 15
Ammo (Gauss) 16 Nose 2
Gauss Rifle Right Wing 15
Ammo (Gauss) 16 Right Wing 2
Gauss Rifle Left Wing 15
Ammo (Gauss) 16 Left Wing 2
Medium Laser Right Wing 1
Medium Laser Right Wing 1
Medium Laser Left Wing 1
Medium Laser Left Wing 1
Overview
As the Exodus got underway the Terran Royal Command realized a massive military build up was necessary to adequately defend the New Republic. Dubbed the Quicksilver Program, this construction effort would utilize already tested Star League prototypes as the basis for new Terran military designs. The myopic focus on BattleMech production during the Star League era led to gaps in the upgrading of certain aerospace fighter classes. The lack of a modern 100 ton aerofighter was a glaring need given the enormous naval advantage maintained by the InnerSphere. As a result the Royal Command prioritized this craft’s development above all other fighter models. Using an experimental aerospace frame originally engineered prior to the Amaris Coup by Dekirk Aerospace helped dramatically speed the design process. Dekirk’s corporate successor, Federated Defense Systems, was able to rush the design into full production in a mere sixteen months. Proudly dubbed the Phoenix by the TRAS Aerospace Subcommand this new fighter is just now entering frontline service with several wings of the Royal Navy.
Capabilities
Engineering the most cutting edge aerospace fighter in existence in record time was no small feat. To accomplish their mandate designers included the Gauss Rifle which had never before been used on an aerospace fighter. Worries about potential damage from a catastrophic failure of the Gauss Rifle prevented its use in earlier aerospace fighters. The engineer's determination to use the Gauss Rifle overmatched the fears that the aerospace community had about the weapons. Little research had been done in the area and preconceived notions about the weapon’s liabilities seemed to rule the day. Thorough examination and analysis disproved many misconceptions about this formidable weapon. The tests were so successful that engineers decided to make the Gauss Rifle the primary weapon of the new fighter and worked hard to include several of them in the design. The final version of the Phoenix came with three Aeroquip Gauss Cannons specially tested and designed for its use. Besides the principal armament and advanced frame used to construct this aerospace fighter, two other advanced technologies went into the completed design. First off StarGlo Ferro-Aluminum provided the Phoenix with an incredible amount of protection against external attack. The second was Double Heat Sinks, which helped maximize the fighter’s operational capability while dissipating any possible excess heat. The rest of the Phoenix is actually less than revolutionary in terms of components used. For example, powering this state of the art fighter craft is the tried and true Vlar 300 Fusion Engine. This reliable old workhorse provides the Phoenix with ample power and maneuverability. This pattern continued when it came to deciding the fighter’s secondary weaponry. Rather than go with the innovative Snub Nosed PPCs to back up the fighter’s main armament the engineers choose to give the Phoenix four Magna Mk II Medium Lasers, whose higher reliability and lower weight were key factors in their decision. The communications system is an upgraded model of an earlier Ceres design for which FDS had acquired the rights. Like wise the targeting and tracking system, SynCom Aero Lord, is based on a previous model. This melding of old and new has produced an impressive aerospace fighter that promises to defend Terran skies for generations to come.
Deployment
The first production run of Phoenixes are just now entering service with a number of Escort Wings, where they will be deployed in the anti-ship role alongside other Terran heavy fighters and assault craft. In the future Attack Wings will receive the Phoenix for ground support missions of Terran Army units. Right now these new fighters are being swapped for the ancient Thunderbird class AeroFighters still in frontline service.
* Clint CLNT-5R.hmp (5.96 KB - downloaded 1 times.)
* Challenger CHR-2A.hmp (9.53 KB - downloaded 1 times.)
* Phoenix PHX-1X.hma (5.55 KB - downloaded 1 times.)
-
Takiro Project Phoenix - Conventional Attack Fighters « Reply #9 on: February 08, 2008, 08:15:23 PM »
Light Attack Fighter
Mass: 10 tons
Power Plant: 100 Hermes Fusion
Armor: Standard
Armament:
1 Magna Mk II Medium Laser
4 Magna Mk I Small Lasers
Manufacturer: Federated Defense Systems, Tauken Weapons Systems
Primary Factory: Terra, Addicks
Communications System: FDS Wireless Alpha Series
Targeting and Tracking System: Birdseye Direct
Type: Light Attack Fighter (Conventional)
Technology Base: Inner Sphere
Tonnage: 10 tons
Equipment Mass
Engine: 100 Fusion 4.5
Safe Thrust: 10
Max Thrust: 15
Structural Integrity: 10
Heat Sinks: 10 0
Fuel: 160 1
Cockpit: 1
Armor Factor: 8 .5
Location Armor Value
Nose 2
Wings 2 / 2
Aft 2
Weapons and Ammo Location Tonnage
Medium Laser Nose 1
2 Small Lasers Left Wing 1
2 Small Lasers Right Wing 1
Medium Attack Fighter
Mass: 25 tons
Power Plant: 200 Nissan Fusion
Armor: Standard
Armament:
2 Holly SRM-4s
2 Magna Mk II Medium Lasers
Manufacturer: Federated Defense Systems, Tauken Weapons Systems
Primary Factory: Terra, Addicks
Communications System: FDS Wireless Alpha Series
Targeting and Tracking System: Birdseye Direct
Type: Medium Attack Fighter (Conventional)
Technology Base: Inner Sphere
Tonnage: 25 tons
Equipment Mass
Engine: 200 Fusion 13
Safe Thrust: 8
Max Thrust: 12
Structural Integrity: 8
Heat Sinks: 10 0
Fuel: 160 1
Cockpit: 2.5
Armor Factor: 24 1.5
Location Armor Value
Nose 8
Wings 6 / 6
Aft 4
Weapons and Ammo Location Tonnage
Medium Laser Nose 1
Medium Laser Nose 1
SRM 4 Left Wing 2
SRM 4 Right Wing 2
Ammo (SRM) 25 - 1
Heavy Attack Fighter
Mass: 50 tons
Power Plant: 300 Vlar Fusion
Armor: Standard
Armament:
4 Holly LRM-5s
2 Magna Mk II Medium Lasers
1 Magna Mk I Small Laser
Manufacturer: Federated Defense Systems, Tauken Weapons Systems
Primary Factory: Terra, Addicks
Communications System: FDS Wireless Alpha Series
Targeting and Tracking System: Birdseye Direct
Type: Heavy Attack Fighter (Conventional)
Technology Base: Inner Sphere
Tonnage: 50 tons
Equipment Mass
Engine: 300 Fusion 28.5
Safe Thrust: 6
Max Thrust: 9
Structural Integrity: 6
Heat Sinks: 10 0
Fuel: 320 2
Cockpit: 5
Armor Factor: 48 3
Location Armor Value
Nose 13
Wings 12 / 12
Aft 11
Weapons and Ammo Location Tonnage
LRM 5 Left Wing 2
LRM 5 Left Wing 2
LRM 5 Right Wing 2
LRM 5 Right Wing 2
Ammo (LRM) 24 - 1
Medium Laser Right Wing 1
Medium Laser Left Wing 1
Small Laser Nose .5
Overview
Perhaps the most overlooked asset of the TRAS is the new Attack class Conventional Fighters (NOTE: A clear example of this is the Fighters omission from Field Manual: Terran Republic 2785). Many in the military continue to devalue these jets because of their limited battlefield role and their poor combat durability. However, the Attack Fighters were among the first new military equipment produced by the rebuilding Terran nation. The reasons for this appear to be threefold. First, some within the SLDF were impressed by the Periphery’s effective use of turbine powered jet fighters during the Uprising and realized that there was a niche for these craft in the military. Second, there was an obvious need to restore Terran militias annihilated by the Coup and these conventional fighters could fill this role nicely. Third, they were easy to build and relatively inexpensive. As a result their development was promoted by Ian Sinclair and undertaken enthusiastically by Federated Defense Systems (FDS). Engineers for the still growing defense conglomerate studied existing InnerSphere blueprints and captured Periphery designs to make the very best conventional fighters for Terran use. One year after the successful conclusion of Operation Liberation the first Attack jets rolled off the assembly line. In 2784 FDS agreed to license its design to Tauken Weapons Systems of Addicks since the increasing demand for the Attack class could not be met by its facilities alone. Company executives have not ruled out the possibly of widening the licensing agreement to include other Terran firms.
Capabilities
There are three distinct types of Conventional Attack Fighters produced by the New Republic which are identified by their weight classifications. Despite some unique differences all of these fighters utilize simple proven technologies that are commonly found throughout known space. These include standard armor plating, universal components and basic machine parts which make any repairs easy. This also simplifies production allowing rapid manufacturing of these jet fighters. The most complex part of these vehicles is their integral power plants. Fusion engines however are remarkably more common in Terran space than elsewhere in the Human Sphere. So naturally these high powered engines were part of these fighters core design rather than the more common internal combustion engine (ICE) seen on InnerSphere Conventional Fighters.
The Light Attack Fighter was designed for speed and firepower making it an extremely good interceptor. It has very good firepower for its size mounting four small lasers and a single medium laser. Unfortunately design limitations inherent in the construction of conventional fighters prevented mounting sufficient armor. The Light Attack Fighters only defense is its tremendous speed. In groups these tiny jets can serve as a good interceptor especially against VTOLs or other conventional fighters. Stand alone missions can also include the Light Attack Fighter undertaking reconnaissance for which it makes an excellent airborne platform
Engineered for ground support missions the Medium Attack Fighter can make a fierce opponent. Its armament includes two Short Range Missile Launchers which can decimate infantry and light vehicles. Two Medium Lasers that can be used for additional strafing fire or air combat complete this fighter’s formidable weaponry. Possessing good speed and enough armor to take a hit without crashing the Medium Attack Fighter may prove to be the bane of our enemies’ ground troops.
For the Heavy Attack Fighter designers really outdid themselves by including an impressive array of long range weaponry. Rather than mount a single bulky long range missile launcher designers choose to affix four Long Range Missile Launcher-5s to the fighter’s wings improving initial offensive estimates. While these weapons comprise the bulk of this jet’s armament two medium lasers and a single small laser were also included. This firepower is devastating for a conventional fighter allowing it to perform multiple missions. It also has impressive protection for a conventional fighter as only the largest weapons could destroy this jet with a single shot. On average the Heavy Attack Fighter can take two or more hits before having to retire. A larger fuel tank contributes to the fighters increased time in the air compared to the smaller Attack Fighters. The only drawback to the Heavy Attack Fighter is its slower speed.
Deployment
The Conventional Attack Fighters were originally intended as a stopgap measure for Terran Militias until they could be reequipped with aerospace fighters. Here they fulfilled their role admirably until the SLDF Exodus began. Kerensky’s departure led to the creation of the TRAS with its twin service branches divided strictly between space and planetary operations. The Royal Navy controlled all military assets that operated outside the bounds of a planet. According to the Terran Royal Command, this included Dropships and Aerospace Fighters, which can operate in both deep space and planetary atmospheres. This left the Terran Army with units that could operate solely within a planetary atmosphere. Despite putting up a determined resistance in this “organizational turf war†that led to the formal creation of the TRAS the Army was left without direct aerospace support. While the Navy has dedicated Aerospace Wings to facilitate ground actions, the Army is hesitant to rely on them, especially in a pinch. To compensate for this perceived lack of support the Terran Army has attached VTOLs and Conventional Jets, including the Attack Fighters, directly to its frontline formations. So far they have performed well but this action has left Militias short again.
Variants
So far there is only one variant for any of these Conventional Attack Fighters. On occasion Medium Attack Fighters swap out their weaponry for a single PPC greatly increasing its effectiveness as an air combatant.
* Light Attack Fighter.hma (7.63 KB - downloaded 3 times.)
* Medium Attack Fighter.hma (7.66 KB - downloaded 3 times.)
* Heavy Attack Fighter.hma (7.66 KB - downloaded 3 times.)
-
Takiro Project Phoenix - Terran Subs « Reply #10 on: February 08, 2008, 08:20:16 PM »
Sea Wolf Fast Attack Submarine
Mass: 50 tons
Movement Type: Submarine
Power Plant: Pitban Naval 270XL
Cruising Speed: 66.3 kph
Flank Speed: 97.4 kph
Armor: Elco Special Weave Ferro Fibrous Armor
Armament:
1 ELCO LRT 10
1 Maxell Large Laser
3 ELCO SRT 2
Manufacturer: Electric Boat Company
Primary Factory: Terra
Communication System: Mark 9 VLS Comsys
Targeting & Tracking System: Sonatrack
Type: Sea Wolf Fast Attack Submarine
Technology Base: Inner Sphere
Movement Type: Submarine
Tonnage: 50
Equipment: Mass
Internal Structure: 5
Engine: 270 11.5
Type: Fusion XL
Cruising MP: 6
Flank MP: 9
Heat Sinks: 10 0
Control Equipment: 2.5
Dive Equipment: 5
Power Amplifier: 0
Turret: 0
Armor Factor: 179 10
Location Armor Value
Front: 47
Right/Left Side: 44/44
Rear: 44
Weapons and Ammo Location Tonnage
1 LRT 10 Front 5
Ammo (LRT) 24 Body 2
2 SRT 2 Front 2
1 SRT 2 Rear 1
Ammo (SRT) 50 Body 1
1 Large Laser Front 5
Overview:
In 2735 General Rebecca Fredasa issued her New Arms Order to design and build new weapons for the SLDF. The main focus of the program was on developing new warships, BattleMechs and aerospace fighters for the SLDF. However the program did not completely ignore the conventional branches. One of the many programs launched as part of the New Arms Order was Project Neptune. The main goal of project Neptune was to develop a new generation of Submarines for the SLDF’s CAAN regiments. The contract was quickly awarded to Electric Boat Company in North America. [NOTE: Electric Boat Company is an ancient company, having been in existence for over 700 years.] Electric Boat Company (ELCO) is a small manufacturer specializing in wet naval vessels. Most of the company’s efforts are concerned with building large freighters and tankers but the company also maintains a small, but highly profitable warship branch. The company quickly designed the Sea Wolf class attack submarine to provide the CAAN units with a strong underwater offensive capability. The Sea Wolf was introduced into service in 2743 and continued to be produced until the outbreak of the Amaris Crisis in 2766. Following the liberation of Terra, the company, which managed to survive with only limited damage, [NOTE: Apparently the Rim World Troops had so little respect for Wet Navy vessels that they decided the company was not worth the effort to destroy the factory.] resumed construction of the Sea Wolf for the Terran Republic. The Sea Wolf continues to operate with the Republic’s Royal Marines.
Capabilities:
The Sea Wolf is designed as a fast attack submarine and is expected to fulfill three roles, providing defense for the Nautilus class Ballistic Missile Submarines, attacking any enemy forces entering into water areas and providing ship to shore bombardment capability.
The Sea Wolf is designed around the Pitban Naval 270XL engine. The engine is a special design from Pitban that has been adapted for optimum performance in a submarine. This engine provides the Sea Wolf with impressive maneuverability under water.
The main weapons of the Sea Wolf are a number of Torpedo launchers. The Sea Wolf carries a mix of both short range and long range torpedoes, providing an impressive punch at all ranges. The ship also carries a single Short Range Torpedo rack on the aft, providing defense against any units attempting to out maneuver the Sea Wolf. For shore bombardment, the Sea Wolf carries a Large Laser, while of only limited use underwater due to its range reduction, the laser allows the Sea Wolf to stand off from the coast and strike at targets.
To protect the sub against damage the design mounts an impressive 10 tons of Elco Special Weave Ferro Fibrous Armor. This armor was specially designed by Elco to resist the corrosive effects of salt water.
Deployment:
The Sea Wolf was deployed to all of the SLDF’s CAAN units prior to the Amaris Crisis. During the Periphery Uprisings the subs proved effective against the Periphery guerrillas who made use of wet navy vessels on several occasions. During the occupation, the Sea Wolf was used by the SLDF Marines defending Fort Quantico on the planet Carver V. The subs intercepted several attempts by the Amaris troops to assault the Marine regiments. The Amaris troops quickly learned that control of the sea belonged to the SLDF and its Sea Wolf submarines. Since the end of the Amaris Coup, the Sea Wolf has resumed production and is being assigned to the Republic’s Royal Marine Regiments.
Variants:
One variant has recently entered service with the Royal Marines. This model removes the Large Laser and uses the space freed up to add an additional forward firing Short Range Torpedo rack, a ton of Short Range Torpedo ammo and space for an entire platoon of naval commandos. It is expected that this model will be used to infiltrate commandos behind enemy line where they will be able to disrupt enemy operations.
Nautilus Ballistic Missile Submarine
Mass: 100 tons
Movement Type: Submarine
Power Plant: Pitban Naval 270XL
Cruising Speed: 33.3 kph
Flank Speed: 54.4 kph
Armor: Elco Special Weave Ferro Fibrous Armor
Armament:
3 ELCO Trident Ballistic Missile Launchers (Arrow IV)
2 ELCO SRT 2
Manufacturer: Electric Boat Company
Primary Factory: Terra
Communication System: Mark 9 VLS Comsys
Targeting & Tracking System: Sonatrack
Type: Nautilus Ballistic Missile Submarine
Technology Base: Inner Sphere
Movement Type: Submarine
Tonnage: 100
Equipment: Mass
Internal Structure: 10
Engine: 270 11.5
Type: Fusion XL
Cruising MP: 3
Flank MP: 5
Heat Sinks: 10 0
Control Equipment: 5
Dive Equipment: 10
Power Amplifier: 0
Turret: 0
Armor Factor: 179 10.5
Location Armor Value
Front: 47
Right/Left Side: 44/44
Rear: 44
Weapons and Ammo Location Tonnage
1 SRT 2 Front 1
1 SRT 2 Rear 1
Ammo (SRT) 50 Body 1
3 Arrow IV Front 45
Ammo (Arrow IV) Body 5
Overview:
The Nautilus was designed at the same time as the Sea Wolf Fast Attack Submarine. While the Sea Wolf was mainly intended for use against other naval combatants, the Nautilus was designed to provide shore bombardment capability. Very few worlds possess a wet navy, meaning there are very few threats to the Nautilus, allowing it attack enemy forces with near impunity. The Nautilus entered service with the SLDF CAAN regiments in 2743 and continued production until the Amaris Crisis. After the liberation of Terra, Electric Boat resumed production of the Nautilus for the Terran Republic’s Royal Marines.
Capabilities:
The Nautilus is designed to provide heavy fire support to land based forces. The sub carries 3 Trident ballistic missile launchers. The Trident is a specially modified Arrow IV missile launcher which is capable of firing without having to surface. Since the Nautilus does not have to surface to launch its missiles, the vessel is not vulnerable to air attacks, unlike surface naval vessels and conventional ground based artillery.
The Nautilus is fairly slow compared to the SLDF’s other main submarine, the Sea Wolf. This was due to the larger size of the Nautilus and the requirement to use the Pitban Naval 270 XL engine. [Editor’s Note: Early in the design cycle of both the Sea Wolf and the Nautilus the design teams were ordered by management to standardize on a single engine for both subs. There were several reasons for this requirement, not the least of which was the fact that it would lower the per unit costs of the engines, which were higher then a standard extra light engine due to the special requirements needed for the subs. The use of the same engine on both subs would also simplify logistics, which would appeal to the SLDF’s Quartermaster’s Corp.] The slow speed is not seen as a hindrance as the Nautilus is mainly used in a stand off support role.
For self defense the Nautilus carries 2 Short Range Torpedo racks. These are mounted in the fore and aft of the Sub and allow it to defend itself against enemy units which get too close. If the sub does come under fire, it carries 10.5 tons of Elco Special Weave Ferro-Fibrous armor to defend against enemy attacks.
Deployment:
The Nautilus was deployed with the SLDF’s CAAN units prior to the Amaris Crisis. During the Periphery Uprisings, the 29th Royal CAAN defected to the Taurian cause during the fighting on Brisbane. During the conflict the 29th’s Nautilus subs used their Tridents to bombard the SLDF forces. Possessing no submarines of their own, the SLDF forces were unable to neutralize the Nautilus subs.
During the Amaris Crisis, the Nautilus was used by the Marines on Carver V. The subs conducted a number of bombardment missions against the Amaris troops on planet. The missions destroyed large amounts of supplies and killed many troops, disrupting efforts by the Rim World’s troops to destroy the SLDF Marines.
Since the liberation of Terra, the Nautilus has been assigned to the Terran Republic Royal Marine regiments.
* Sea Wolf Fast Attack Submarine.hmv (4.42 KB - downloaded 2 times.)
* Nautilus Ballistic Missile Submarine.hmv (3.5 KB - downloaded 2 times.)
-
Takiro Mercenary Guild - BattleMechs « Reply #11 on: February 08, 2008, 08:23:19 PM »
LGN-1 Legionnaire
Mass: 80 tons
Chassis: LGN Magnus I
Power Plant: Pitban 240
Cruising Speed: 32.4 kph
Maximum Speed: 54 kph
Jump Jets: None
Jump Capacity: None
Armor: Armortechnik Standard
Armament:
2 Donal Particle Projection Cannons
1 Magnus Autocannon/10
1 Holly-6 Short Range Missile Rack
1 Magna Mk II Medium Laser
2 Magna Mk I Small Lasers
Manufacturer: Magnus Industries
Primary Factory: Galatea
Communications System: Rander Landcourier
Targeting and Tracking System: Wunderland Predator
Overview
The Legionnaire was first created as a stopgap design during the Regulators long journey home. Commissioned by Colonel McKinnely to replace lost equipment this effort would tax the resourcefulness of her rag tag band of survivors. Utilizing every asset at their disposal the project was plagued by all kinds of challenges but thanks to the determination of all involved it paid off. Incredibly about a company of these improvised war machines were completed by the time the Regulators returned to the InnerSphere. The effectiveness of this rather unsophisticated design convinced the emergent Magnus Industries to begin mass production. The growing market for mercenaries presented the new arms producer with an inviting consumer base. Although somewhat more refined from the original models because of assembly line demands this highly reliable ‘Mech promises to become a mainstay of the mercenary industry.
Capabilities
Simple and effective are the two words which best describe this BattleMech design. Besides the actual structure of the Legionnaire, which was painstakingly engineered by the Regulators themselves, and the Magnus Autocannon the components of this new design consist of existing equipment which has already been proven and are relatively easy to find. For example the Pitban 240 power plant can be found on several BattleMechs including the Awesome, Rifleman, Clint, and Spider. The armament which includes two Donal Particle Projection Cannons, one Holly-6 Short Range Missile Rack, one Magna Mk II Medium Laser, and two Magna Mk I Small Lasers is much the same. Even the electronics suite of the Legionnaire was made by two companies with ample manufacturing experience. While Rander Communications Equipment Incorporated and Wunderland Enterprises previously made electronics for venerable aerospace designs they easily translated their time tested methods to a BattleMech. Only the heat dissipation system of the Legionnaire is considered advanced by any standards. Designers had to mount Double Heat Sinks to account for all the waste heat generated by weapons fire as well as other normal operations. However, even these high tech items are fairly typical for modern day ‘Mech designs.
Deployment
Currently the Regulators field the majority of these designs including many of the newly manufactured runs. While these recent factory models are clearly superior to the forbearers both have prove to be quite effective. The latest version is easier to repair and generally superior in terms of quality. It is likely that the original Legionaries will be retired and one day placed on display somewhere to help illustrate historical significance of the Periphery Sweep. Other mercenary groups like the Grave Walkers, the White Lions, and the Fighting Armadillos have also obtained Legionaries. Many more have also expressed interest in acquiring the design for their operations.
Type: LGN-1 Legionnaire
Technology Base: Inner Sphere
Tonnage: 80 tons
Equipment Mass
Internal Structure: 8
Engine: 240 11.5
Walking MP: 3
Running MP: 5
Jumping MP: 0
Heat Sinks: 16 (32) 6
Gyro: 3
Cockpit: 3
Armor Factor: 232 14.5
Internal Structure Armor Value
Head 3 9
Center Torso 25 36/11
R/L Torso 17 24/8
R/L Arm 13 24
R/L Leg 17 32
Weapons and Ammo: Location Critical Tonnage
PPC RA 3 7
PPC LA 3 7
Autocannon/10 RT 7 12
Ammo (AC/10) 20 RT 2 2
SRM-6 LT 2 3
Ammo (SRM) 15 LT 1 1
Medium Laser CT 1 1
Small Laser CT 1 .5
Small Laser H 1 .5
137-A Omega
Mass: 100 tons
Chassis: OMA/HT X
Power Plant: Vlar 300
Cruising Speed: 32.4 kph
Maximum Speed: 54 kph
Jump Jets: Pitban LFT-100
Jump Capacity: 90 meters
Armor: Kemplar X9000
Armament:
4 Selitex Radionic Large Lasers
12 Ichiba 3000 Medium Lasers
Manufacturer: Renault-Prime Industries
Primary Factory: Terra
Communications System: Duoteck 200XT
Targeting and Tracking System: Faust/Shinji AT/TS
Overview
In 2765, First Lord Richard Cameron granted Renault-Prime Industries permission to begin testing their newly developed and much anticipated assault 'Mech called the Omega. As the manufacturer of the highly successful Flashman BattleMech many expected their new design to spread throughout the SLDF quickly. However, this was not to be as shortly after Renault-Prime had built their first prototype Omega the Usurper struck. Stefan Amaris ordered the Omega project moved from Procyon to Terra following his conquest of the Terran Hegemony so he could personally monitor its testing. Plagued by interference and general turmoil these efforts bore no fruit for the Usurper. After the successful conclusion of Operation Liberation much of the original research disappeared. Most assumed General Kerensky took much of this research including the prototype Omega with him on the Exodus. As Renault struggled to survive the fall of the Star League few thought that this design would ever make it to the battlefield. Terran military engineers knew differently as they worked tirelessly to get this formidable design from the drawing board to the frontlines. Their efforts combined with Renault’s changing fortunes have now paid off with the first full scale production run of the Omega class BattleMech now rolling of assembly lines near the company’s ancient headquarters.
Capabilities
The Omega was designed along the same lines as the Flashman. In essence a mobile laser battery, the Omega can lay down a withering barrage of laser fire that can incinerate most 'Mechs in a matter of seconds. The 18 HilTec double-strength heat sinks keep the heat potential down to a minimum as long as the weapon fire is staggered. Unfortunately, most of the test pilots involved in the project had a tendency to fire all the weapons involved. The addition of jump jets was added as an afterthought. News from the frontlines of the Periphery Uprising showed instances where lack of mobility had doomed many an assault because the 'Mechs could not support the rest of their company. The addition of jump jets was hoped to alleviate some of the SLDF’s concerns. The Pitban engine was a trusted design and was considered worth the cost involved. Combined with nineteen tons of Kemplar X9000 armor made the 'Mech particularly difficult to take down. Its Faust/Shinji targeting system provided accurate but somewhat spotty performance, a factor that wasn’t improved until the project came under the auspices of Terran engineers.
Deployment
With the first machines just sent to appropriate military units the Omega has no battlefield history. With double heat sinks this BattleMech’s only high tech item the Omega should have no supply problems experienced by other higher tech designs thanks to the war. The lion’s share of these impressive new ‘Mechs have gone of course to the Terran Guard and Sinclair Fusiliers. A small number reserved for mercenaries per Renault’s standard sale policies have gone to loyal units of the Republic, the Illician Lancers and the Blue Star Irregulars.
Type: 137-A Omega
Technology Base: InnerSphere
Tonnage: 100 tons
Equipment Mass
Internal Structure: 10
Engine: 300 19
Walking MP: 3
Running MP: 5
Jumping MP: 3
Heat Sinks: 18 [36] 6
Gyro: 3
Cockpit: 3
Armor Factor: 304 19
Internal Structure Armor
Head 3 9
Center Torso 32 47 / 14
R/L Torso 21 32 / 10
R/L Arm 17 34
R/L Leg 21 41
Weapons and Ammo Location Critical Tonnage
Large Laser RT 2 5
Large Laser RT 2 5
Large Laser LT 2 5
Large Laser LT 2 5
Medium Laser RA 1 1
Medium Laser RA 1 1
Medium Laser RA 1 1
Medium Laser RA 1 1
Medium Laser RA 1 1
Medium Laser RA 1 1
Medium Laser LA 1 1
Medium Laser LA 1 1
Medium Laser LA 1 1
Medium Laser LA 1 1
Medium Laser LA 1 1
Medium Laser LA 1 1
Jump Jet CT 1 2
Jump Jet LL 1 2
Jump Jet RL 1 2
* Legionnaire LGN-1.hmp (1.01 KB - downloaded 1 times.)
* Omega 137A.hmp (4.05 KB - downloaded 1 times.)
-
Takiro Mercenary Guild - Aerospace Fighters « Reply #12 on: February 08, 2008, 08:25:12 PM »
C-10A Crow
Mass: 60 tons
Frame: StarTech Mod III
Engine: Vlar 300 Fusion
Armor: StarGuard Standard
Armament:
2 Magna Mk III Large Laser
2 Magna Mk II Medium Laser
2 Holly-6 Short Range Missile Racks
Manufacturer: Warner Incorporated
Primary Factory: Quentin
Communications System: Tek BattleCom
Targeting & Tracking System: Tek Tru-Trak
Overview
The Crow fighter was first created in 2750 during the Star League's reign by Warner Incorporated as a follow up to their beloved Sparrowhawk. Upon creation the Star League was looking for a low tech and low cost, though very capable, heavy fighter that can fill a variety of roles. What came from it was a fast heavy strike fighter that works among command units performing guerrilla style tactics. The Crow can hold its own outside this role as well but it is not as common outside of it.
Capabilities
What makes the Crow somewhat popular is the fact that the technology is very easy to maintain. When it was created it was fitted with average technology that still worked well on other fighters or BattleMechs in its time. With many high technologies disappearing from the battlefields of the Succession War the Crow is unlikely to suffer any drawbacks. The Crow is combat efficient and easy to maintain. Usually this trade off creates problems but the Crow has no real design flaws even though some critics say that it is under gunned for its weight class. About the only problem with the Crow is its tendency to overheat, which could be a real trouble for any pilot who gets a little trigger happy. The Crow is considered the "heavy scout" of the sky because it can be paired with most light fighters. It can lay down some serious firepower with its dual Magna Mk III large lasers in the nose. For backup, it comes equipped with dual Magna Mk II medium lasers and dual Holly SRM-6 launchers. The SRM's are supplied with a single ton of ammunition but for the fighter's general role it seems to work just fine.
Deployment
The Star League used a number of Crows back in their time as a command unit in light fighter lances. These lances would often strike valuable targets then retreat to safety. After the Star League's fall and the start of the Succession War, the Crow became popular among most mercenary units mainly those with ties to the SLDF. The Crow is also reported in arsenals of many Successor States including the Terran Republic where production of these durable has only recently resumed.
Type: C-10A Crow
Technology Base: Inner Sphere
Tonnage: 60 tons
Equipment Mass
Engine: 300 Fusion 19
Safe Thrust: 7
Max Thrust: 11
Structural Integrity: 7
Heat Sinks: 15 5
Fuel: 400 5
Cockpit: 3
Armor Factor: 144 9
Location Armor Value
Nose 36
Wings 36 / 36
Aft 36
Weapons and Ammo Location Tonnage
Large Laser Nose 5
Large Laser Nose 5
Medium Laser Right Wing 1
Medium Laser Left Wing 1
SRM 6 Right Wing 3
SRM 6 Left Wing 3
Ammo (SRM 6) 15 - 1
HLR-66 Hellraiser
Mass: 70 tons
Frame: Redstar VIF
Engine: VOX 280 Fusion
Armor: SearWeave
Armament:
1 variable model Particle Projection Cannon
1 Holly-6 Short Range Missile Rack
2 variable model Large Lasers
4 variable model Medium Lasers
Manufacturer: Quickscell Company
Primary Factory: Oliver
Communications System: Rander ComLink
Targeting & Tracking System: Wunder TarSys
Overview
With an expanding market due to the formation of numerous new mercenary units the Quickscell Company realized that they needed to get a design quickly from the drawing board to the production line. After six months on the design board and six more in the prototype stage the Hellraiser was ready for full scale production. Initial sales of the Hellraiser were extremely limited thanks in large part to Quickscell’s poor reputation. It wasn’t until a fighter sold to the 802nd Independent Aerospace Wing which saw action in the battles of Corey and Wazan. One of the first aerofighters that was purchased it proved to be instrumental in the destruction of the CCS Mao Tse Tung. Sales of this aerospace fighter have skyrocketed since thanks to its key role in this massive battle. Its image boosted the Hellraiser is now in service with over thirty different mercenary units. The fighter looks so successful that it may clear Quickscell’s bad name so to speak. It had previously been known for producing faulty and defective merchandise.
Capabilities
Outfitted with a diverse weapons package the Hellraiser was designed to offer pilots versatility in combat. The only apparent flaw in the design is the choice of manufacturers for its weapons systems. Many times an order of fighters may have different brands of weapons outfitted on them depending on whoever Quickscell could find as the lowest bidder at the time. The only exception to this policy appears to be the Holly-6 Short Range Missile Rack which the company apparently made long term commitment too early on. Some units are simply replacing the weapons with higher quality as soon as delivered while others don’t care, or just don’t have the time, or materials. Other than that many of the other components used in the manufacturing of the Hellraiser are time tested. These include the venerable VOX 280 power plant and the SearWeave armor plating from the Ironsides that protects the craft. The electronics package was designed by two mainstays of the field. Rander Communications Equipment Inc supplied the basic but highly reliable Rander ComLink while Wunderland Enterprises added its new Wunder TarSys which works well with many different armaments.
Deployment
The Hellraiser has already seen action in over twenty different engagements around the InnerSphere. According to reports so far not a single one has been destroyed beyond the point of salvage. And with over a 90% survival rate the Hellraiser is quickly finding a spot in mercenary units’ TO&E. The most notable units the Hellraiser has been spotted in are the Freelances, Northwind Highlanders, Illician Lancers, Lexington Combat Group, and the unit that brought the fighter to fame the 802nd Independent Aerospace Wing aka the Warhawks.
Type: HLR-66 Hellraiser
Technology Base: Inner Sphere
Tonnage: 70 tons
Equipment Mass
Engine: 280 Fusion 16
Safe Thrust: 6
Max Thrust: 9
Structural Integrity: 7
Heat Sinks: 18 (36) 8
Fuel: 400 5
Cockpit: 3
Armor Factor: 192 12
Location Armor Value
Nose 64
Wings 48 / 48
Aft 32
Weapons and Ammo Location Tonnage
PPC Nose 7
SRM 6 Nose 3
Ammo (SRM) 30 - 2
Large Laser Right Wing 5
Large Laser Left Wing 5
Medium Laser Right Wing 1
Medium Laser Left Wing 1
2 Medium Laser Aft 2
* Crow C-10A.hma (3.85 KB - downloaded 2 times.)
* Hellraiser HLR-66.hma (4.6 KB - downloaded 2 times.)
-
Takiro Mercenary Guild - Marechal Light Tanks « Reply #13 on: February 08, 2008, 08:28:16 PM »
Marechal Light Tanks
Mass: 35 tons, 40 tons and 45 tons
Movement Type: Wheeled, Hover, and Tracked
Power Plant: 225 VOX Fusion
Cruising Speed: 75.6 kph (wheeled), 108 kph (hover), 54 kph (tracked)
Flank Speed: 118.8 kph (wheeled), 162 kph (hover), 86.4 kph (tracked)
Armor: Kemplar 1000
Armament:
1 Large Laser (All Models)
1 Medium Laser (All Models)
1 Flamer (Tracked only)
2 Small Lasers (Tracked only)
Manufacturers: Renault-Prime Industries
Primary Factory: Solaris
Communications System: Duotech 190V
Targeting and Tracking System: Faust/Shinji AT/TS
Overview
Seeking the greatest system flexibility between the varied motive systems for their new light tank, the Renault designers created a vehicle system, instead of a simple group of vehicles. The Marechal (Marshal) was the result. Every vehicle in the system has 90% compatibility of components, including weapons, electronics, power generation and armor plating. Even the initial investment for development would be aided by the anticipated acquisition of the SB-27 Sabre license, since the Marechal was designed to use the same 225-class Fusion engine as the fighter. All this promised to lower production costs for Renault and improve logistics for their consumers, something the marketing department focused on in sales.
Capabilities
The design started with a slightly boxy hull and low-profile turret. Conventional alloy armor plating was added, with similar protection levels provided to each vehicle in the system. Lastly, a simple duo of energy weapons were added: a heavy laser in the turret and a standard model on the glacis. The one exception to this is the Marechal-Bonne, the tracked model, which includes both a fusion-based flamer in the turret and a brace of light lasers to the left and right for infantry protection. The only difference between the vehicles in the series is the basic chassis and motive system, which does result in a slight mass difference between them, ranging from 35 up to 45 tons.
While the Bonne proved slightly slower than the designers preferred, the Marechal series was still fast enough to avoid most damage. As the slowest, the Bonne is only able to achieve roughly 85km/h on rough terrain, though its rugged tracks are capable of traversing nearly any obstacle. The Villars is the next vehicle in the system, a 6x6 wheeled model, able to hit nearly 130km/h on roads and well over 100km/h off-road. Finally, the Saxe hovercraft is the speediest of the system, exceeding 160km/h on smooth terrain like prairie, desert, water or pavement. Even with these speeds, the Marechal vehicles were given sufficient armor plating to defeat even the heaviest autocannon or energy weapon from any aspect. Repeated pummeling from such weapons did prove catastrophic in field tests, but designers felt that the maneuverability of the system negated this flaw.
Deployment
This easy to produce low cost series of vehicles has quickly spread throughout the mercenary community replacing battlefield losses from the Succession War. While the Marechals won’t ever be accused of being the most cutting edge design they have proven highly reliable in combat. They don’t run out of ammo and are easy to maintain. As their crews often remark “it is hard to outwork a Marechalâ€.
Type: Marechal Bonne
Technology Base: Inner Sphere Tracked Vehicle
Tonnage: 45 tons
Equipment Mass
Internal Structure: 4.5
Engine: 225 15
Cruising MP: 5
Flank MP: 8
Power Amplifier: 0
Heat Sinks: 16 – Single 6
Control Equipment: 2.5
Crew: 3 Members 0
Suspension: 0
Turret: 1
Armor Factor: 128 – Standard 8
Internal Structure Armor Value
Front 5 33
Left 5 25
Right 5 25
Rear 5 20
Turret 5 25
Weapons, Ammo, and Equipment Location Space Tonnage
Large Laser Turret 1 5
Medium Laser Front 1 1
Flamer Turret 1 1
Small Laser Left 1 .5
Small Laser Right 1 .5
Type: Marechal Villars
Technology Base: Inner Sphere Wheeled Vehicle
Tonnage: 35 tons
Equipment Mass
Internal Structure: 3.5
Engine: 225 15
Cruising MP: 7
Flank MP: 11
Power Amplifier: 0
Heat Sinks: 11 – Single 1
Control Equipment: 2
Crew: 3 Members 0
Suspension: 0
Turret: .5
Armor Factor: 112 – Standard 7
Internal Structure Armor Value
Front 4 31
Left 4 20
Right 4 20
Rear 4 20
Turret 4 21
Weapons, Ammo, and Equipment Location Space Tonnage
Large Laser Turret 1 5
Medium Laser Front 1 1
Type: Marechal Saxe
Technology Base: Inner Sphere Hovercraft
Tonnage: 40 tons
Equipment Mass
Internal Structure: 4
Engine: 225 15
Cruising MP: 10
Flank MP: 15
Power Amplifier: 0
Heat Sinks: 11 – Single 1
Control Equipment: 2
Crew: 3 Members 0
Lift Equipment: 4
Turret: .5
Armor Factor: 120 – Standard 7.5
Internal Structure Armor Value
Front 4 30
Left 4 22
Right 4 22
Rear 4 22
Turret 4 24
Weapons, Ammo, and Equipment Location Space Tonnage
Large Laser Turret 1 5
Medium Laser Front 1 1
* Marechal Light Tank Bonne.hmv (3.18 KB - downloaded 1 times.)
* Marechal Light Tank Saxe.hmv (3.11 KB - downloaded 1 times.)
* Marechal Light Tank Villars.hmv (3.11 KB - downloaded 1 times.)
-
Takiro First BTSD Design Contest - The Coblitz and the Warthog « Reply #14 on: February 08, 2008, 09:16:00 PM »
Warthog Assault Tank
Mass: 90 tons
Movement Type: Tracked
Power Plant: 270 LTV Extra-Light XL Fusion
Cruise Speed: 32.4 km/h
Maximum Speed: 54.0 km/h
Armor Type: Nakamura Manufacturing Ferro-Fibrous
Armament:
2 Poland Main Model A Gauss Rifles
3 Defiance B3M Medium Lasers
2 MainFire Point Defense Anti-Missile Systems
Manufacturer: Nakamura Military Vehicle Production
Location: Okayama, Japan, Terra
Communications System: Nakamura Communications Systems with Churchill Guardian
ECM Suite
Targeting & Tracking System: Nakamura T&T system
OVERVIEW:
As the Coblitz MBT competition was going on, a number of Terran military officials were pleasantly surprised by the quality of participants. The Ministry of Defense was keenly aware that they would need a lot of military combat vehicles in field if the New Republic was to survive the vultures of the InnerSphere from carving up there beloved home. The Nakamura entry was passed for the initial contract, within the hour they got their contract for build the tank for the Terran Republic. They named it the Warthog Assault Tank. The rest is in the history.
CAPABILITIES:
The only thing changed from the original version was the addition of CASE equipment at the loss of a half of ton of Ferro-Fibrous Armor. This was deemed to be vital the military as they didn’t want to lose veteran crews to ammo explosions that could theoretically happen to the four tons of AMS ammo the tank carried. The Warthog Assault Tank still used Twin Poland series Gauss Rifles as the primary weapons. These were put into a turret along with the 3 Defiance B3M medium lasers. It also kept the twin MainFire Point Defense Anti-Missile Systems as protection from the nasty Inferno rounds used by many forces to kill tanks. The Churchill Guardian ECM Suite also helps protect the Warthog from missile targeting systems like Narc Beacons and Artemis IV FCS.
DEPLOYMENT:
While the Warthog has been recently released to be mass produced, many of the frontline units of the New Republic have gotten this Assault Tank. Almost all of the tank crews love this design. The only problem noted is that the new smell of the tank doesn’t go away.
VARIANTS:
As this tank has just been released to mass production, there are no known official variants.
Technology Base: - I.S. Tracked Vehicle - Level 2 - 90 tons
Equipment Mass
Internal Structure: 9
Engine: 270 XL Fusion 7.5
Shielding & Transmission Equipment: 4
Cruise MP: 3
Flank MP: 5
Heat Sinks: 10 Single 0
Cockpit & Controls: 4.5
Crew: 6 Members 0
Turret Equipment: 3.5
Armor Factor: 313 - Ferro-Fibrous 17.5
Internal Structure Armor Value
Front 9 90
Left 9 61
Right 9 61
Rear 9 40
Turret 9 61
Weapons, Ammo, and Equipment Location Space Tonnage
2 Gauss Rifles Turret 2 30
3 Medium Lasers Turret 3 3
2 Anti-Missile Systems Turret 2 1
Ammo (Gauss Rifle) 32 Body 1 4
Ammo (AMS) 48 Body 1 4
CASE Body 1 .5
Guardian ECM Front 1 1.5
Calculated Factors:
Total Cost: 15,656,950 C-Bills
Battle Value: 1,412
Cost per BV: 11,088.49
Weapon Value: 1,797 / 1,797 (Ratio = 1.27 / 1.27)
Damage Factors: SRDmg = 38; MRDmg = 23; LRDmg = 14
BattleForce2: MP: 3T, Armor/Structure: 0 / 12
Damage PB/M/L: 5/5/3, Overheat: 0
Class: GA; Point Value: 14
Specials: ecm
-
Takiro Second BTSD Design Contest - Aetius IFV « Reply #15 on: February 08, 2008, 09:18:58 PM »
Aetius Infantry Fighting Vehicle (IFV)
Mass: 50 tons
Movement Type: Hover
Power Plant: 265 LTV Extra-Light XL Fusion
Cruising Speed: 108 kph
Flank Speed: 162 kph
Armor: Pantherskin VII Ferro-Fibrous with CASE
Armament:
1 Defiance B3L Large Laser
1 Defiance B3M Medium Laser
2 Zeus LRM 5s
Manufacturer: Yankee Weapons Systems
Primary Factory: Mars
Communication System: Ceres Metals Model 666 with Churchill Guardian ECM
Targeting & Tracking System: Apple Churchill 2000
OVERVIEW:
With the New Terran Republic asking for new military vehicles to rapidly replace
equipment lost in the Great Crusade, a call went out for an IFV to be issued to the troops. The Aetius IFV was born form this effort.
CAPABILITIES:
The Aetius is considered to be a rather unusual design to say the least. At 50 tons, it is amongst the heaviest hovercraft to be produced. The inclusion of an XL engine and Ferro-fibrous armor by many people to be an extravagance, but with this inclusion and its warload the vehicle literally wowed the trial judges. The inclusion of the 265 XL engine allowed flank speeds in excess of 150 km/h, the Aetius could literally scream across the battlefield. The warload of the Aetius is two LRM 5 racks, a large laser, and a medium laser. It also has 4 ton infantry bay for rapid deployment of entire platoons of foot or jump infantry anywhere on the battlefield. Seven and half tons of Ferro-fibrous armor, CASE equipment (to protect the crew and passengers from the lucky shot hitting the LRM ammo), and an Apple-Churchill Guardian ECM suite give the Aetius a rather robust defense, especially considering its speed.
Technology Base: - I.S. Hover Vehicle - Level 2 - 50 tons
Equipment Mass
Internal Structure: 5
Engine: 265 XL 10.5
Cruising MP: 10
Flank MP: 15
Power Amplifier: 0
Heat Sinks: 11 – Single 1
Control Equipment: 2.5
Crew: 4 Members 0
Lift Equipment: 5
Turret: 1.5
Armor Factor: 134 - Ferro-Fibrous 7.5
Internal Structure Armor Value
Front 5 35
Left 5 27
Right 5 27
Rear 5 18
Turret 5 27
Weapons, Ammo, and Equipment Location Space Tonnage
Large Laser Turret 1 5
Medium Laser Turret 1 1
2 LRM 5s Turret 2 4
Ammo (LRM) 24 Body 1 1
CASE Body 1 .5
Guardian ECM Turret 1 1.5
Infantry Bay Body 1 4
Calculated Factors:
Total Cost: 8,695,667 C-Bills
Battle Value: 786
Cost per BV: 11,063.19
Weapon Value: 583 / 583 (Ratio = .74 / .74)
Damage Factors: SRDmg = 14; MRDmg = 10; LRDmg = 3
BattleForce2: MP: 10H, Armor/Structure: 0 / 5
Damage PB/M/L: 2/2/1, Overheat: 0
Class: GM; Point Value: 8
Specials: tran4, if, ecm
* Aetius Infantry Fighting Vehicle (IFV).hmv (1.56 KB - downloaded 3 times.)
-
Takiro Third BTSD Design Contest - Gorgon Heavy Tank « Reply #16 on: February 08, 2008, 09:22:05 PM »
Gorgon Heavy Tank
Mass: 80 tons
Movement Type: Tracked
Power Plant: 320 XL
Cruising Speed: 43.2 kph
Maximum Speed: 64.8 kph
Armor: ArmorTek Advanced with CASE
Armament:
1 Corin Shortstar SN PPC
2 Brook Highfire-10 LBX Autocannons
1 Brook 50 Machine Gun
Manufacturer: Pegasus Defense Systems Ltd
Communications System: SkyNet 9 ASC
Targeting & Tracking System: PDS StoneGaze II
OVERVIEW:
When the TRAS started to look for a new heavy tank design to compliment the already successful Coblitz and Warthog, few people imagined the galvanizing effect this would have on the fledgling company Pegasus Defense Systems Ltd.
[Editor’s Note: Pegasus Defense Systems Ltd - An overview / A newcomer in the arena of military vehicles, many observers glancing at their formation data would dismiss Pegasus Defense Systems Ltd [henceforth referred to as PDS] as one of the many boom companies trying to make quick money from the current procurement drive by the TRAS; however they would be wrong. / PDS was formed on May 9 2784 by Derek Jones, Neil Smith, Susan McKenzie and Alex Hill. These four were the only surviving designers and engineer from Ford & Bridge Vehicle Enterprises, one of the many loyal companies destroyed during the Amaris Coup years because of perceived links to the resistance. Through them PDS can trace a lineage back to Ford & Bridge, and then back over eighty years to the foundation of the company in 2702. / It is rumored that the company name is derived from the last project the group were working on for Ford & Bridge, a 'Project Gorgon' [Pegasus was born from the blood of the killed Gorgon Medusa]. It should be noted that this is pure speculation, as none of the four founders are willing to comment on this or their work for Ford & Bridge during the occupation. / Due to the short time PDS has been active they have no vehicles in production, though it is known that a design is being submitted for the Terran Heavy Tank tender. / Extract From "Up and Coming Military Companies", Investors International Special Edition.]
Spending many weeks studying blueprints and field performance reports for the existing vehicles, the experienced design team identified three potential areas that opponents may be able to take advantage of. These were at short ranges, where both the Coblitz and Warthog were found lacking in armament, at medium ranges for the Warthog and at long range for the Coblitz.
Trying to design a heavy tank to compliment these areas was no easy task, and the team felt the most they could hope for was to showcase PDS's capabilities in the long term. This eventually resulted a solid tank they felt best suited the specifications, yet was unlikely to be the winning design.
This all changed when one of the engineering section found that the fast release couplings used in the engine compartment (to allow for rapid replacement of entire engines) were of the same type as the standard ones being used for items such as the power and ammunition feeds.
Realizing that combining this discovery with some modification to the chassis and turret they could create a truly unique vehicle, the design team scrapped the original submission and went back to the drawing board. Although this set back plans by several months they eventually created a heavy tank that easily met all the criteria they had, and was also a worthy equal to the vehicles it was designed to compliment, which they named the Gorgon.
There are three 'patterns' of Gorgon, and when completely assembled (chassis & turret) each receives a designator. Each is named for one of the mythological Gorgons based on that patterns capability. These are "Sthenno" (forceful), "Medusa" (ruler) and "Euryale" (far-roaming).
CAPABILITIES:
The Gorgon Heavy Tank is unique in that it is the only vehicle known to have a modular turret assembly (MTA), allowing technicians and engineers to quickly alter its role to suit the terrain and opposing forces by fitting one of three turrets to a standardized chassis; a straight-forward process for trained technicians, which can be completed in less than 30 minutes. This versatility coupled with a staggering 15.5 tons of ferro-fibrous armor and CASE means that the Gorgon is extremely hard to actually destroy, and even if immobilized is still a danger to enemy commanders.
Mounted in the chassis is one of the new Corin Shortstar Snub-Nosed PPCs for close to mid range defense against heavier opponents. Its power and deterrent factor make it popular with crews even though it is classed as a secondary weapon. A machine gun mounted in the turret is the Gorgons other integral weapon system used for infantry suppression. Other equipment to be found in the chassis are a SkyNet 9 Advanced Communication System, a large piece of hardware which gives commanders the ability to link in to all known battlefield communication networks employed by the TRAS ranging from satellite and dropship command nets to hardwire LANs, and the T&T StoneGaze II computer. This had to be created in house by PDS especially for the Gorgon as other systems encountered errors when interfacing with the MTA, and can track twenty contacts at the range of half a mile, automatically identifying them by profile or IR signature if they are in its database. If so it sorts them by threat rating based upon their distance and known capabilities, notifying the gunner and commander of the five 'greatest' threats.
The most common Gorgon to be found is the Sthenno pattern, which is designed for mid to close range engagements, and to this end mounts two of the recently improved Brook Highfire-10 LB-10X autocannons in the turret along with three tons of ammunition (normally two tons of HEAP and one of cluster). These are capable of engaging separate targets if necessary, but most crews prefer to concentrate their considerable firepower at one target where a couple of volleys can destroy all but the heaviest assault mechs.
VARIANTS:
The Medusa pattern turret was designed to give effective fire support on the battlefield, and mounts two of the reliable and efficient Holly LRM-15 launchers to do this. Each missile rack has been slaved to an Artemis fire control system, which when networked with the StoneGaze II makes this one of the most accurate and dangerous weapon combinations found on the battlefield. For combating opponents that manage to close with this Gorgon the turret also houses two Holly SRM-4 racks to deal with vehicle and light BattleMech threats, alongside a co-axial mounted MG for anti-infantry work. In a move to keep the turret profile as low as possible, thus helping to increase survivability, the SRM racks are mounted in a hinged assembly behind the turret, and swing up into position before firing. The whole design is rounded out with a generous ammunition supply, three tons for the LRMs and two for the SRMs, giving tank commanders the ability to carry a range of missile types to deal with most situations they expect to encounter.
The Euryale pattern turret easily lives up to its namesake. Designed for close battlefield artillery support its main armament is comprised of a Brokenback Arrow IV Missile System and a Brook Midfire-2 Autocannon. Both weapons provide this version of the Gorgon with accurate long range firing capabilities. The Arrow IV System comes with three tons of ammunition allowing both normal and homing missiles to be carried. This lets the Euryale to cover advances, and retreats, and provide sustained artillery support without being forced to retire for replenishment. The Autocannon provides ranged protection for this Gorgon variant if directly threatened on the battlefield by light vehicles and infantry.
Technology Base: - I.S. Tracked Vehicle - Level 2 - 80 tons
Equipment Mass
Internal Structure: 8
Engine: 320 XL 17.5
Cruising MP: 4
Flank MP: 6
Power Amplifier: 0
Heat Sinks: 10 – Single 0
Control Equipment: 4
Suspension: 0
Turret: 2.5
Armor Factor: 278 - Ferro-Fibrous 15.5
Internal Structure Armor Value
Front 8 77
Left 8 55
Right 8 55
Rear 8 36
Turret 8 55
Sthenno
Weapons, Ammo, and Equipment Location Space Tonnage
Snub-Nose PPC Front 1 6
2 LB 10-X Autocannons Turret 2 22
Machine Gun Turret 1 .5
Ammo (LB 10-X) 30 Body 1 3
Ammo (MG) 100 Body 1 .5
CASE Body 1 .5
BV: 827
Cost: 15,209,400
Medusa
Weapons, Ammo, and Equipment Location Space Tonnage
Snub-Nose PPC Front 1 6
2 LRM 15s Turret 2 14
2 Artemis IV FCSs Turret 2 2
2 SRM 4s Turret 2 4
Machine Gun Turret 1 .5
Ammo (LRM 15) 24 Body 1 3
Ammo (MG) 100 Body 1 .5
Ammo (SRM 4) 50 Body 1 2
CASE Body 1 .5
BV: 953
Cost: 15,331,800
Euryale
Weapons, Ammo, and Equipment Location Space Tonnage
Snub-Nose PPC Front 1 6
Arrow IV Missile Systems Turret 1 15
Autocannon/2 Turret 1 6
Machine Gun Turret 1 .5
Ammo (Arrow IV) 15 Body 1 3
Ammo (Autocannon) 45 Body 1 1
Ammo (MG) 100 Body 1 .5
CASE Body 1 .5
BV: 769
Cost: 14,725,200
* Gorgon Heavy Tank Euryale.hmv (7.74 KB - downloaded 2 times.)
* Gorgon Heavy Tank Medusa.hmv (7.74 KB - downloaded 2 times.)
* Gorgon Heavy Tank Sthenno.hmv (7.72 KB - downloaded 1 times.)
-
Takiro Fourth BTSD Design Contest - The Styx « Reply #17 on: February 08, 2008, 09:24:35 PM »
Styx Heavy Assault Tank
Mass: 100 tons
Movement Type: Tracked
Power Plant: 300 XL
Cruising Speed: 32.4 kph
Maximum Speed: 54.0 kph
Armor: Krupp 200 Ferro-Fibrous with CASE
Armament:
8 Martell Medium Lasers
1 Grizzard Model 200 Gauss Rifle
2 Mydron Minigun Machine Guns
2 McArthur Anti-Missile Systems
Manufacturer: Cardiff Arms International
Communications System: Dornman Echo II with Guardian ECM
Targeting and Tracking System: Garret D2J
OVERVIEW:
The TRAS were surprised by Cardiff Arms International that they were able to design and submit another vehicle so soon after they failed in the bid for the Terran Heavy Tank tender. Approaching the new design with the same thoroughness as previously, the designers spent months studying reports on the new TRAS tanks, and for some time could not think of any way to create a design without copying one of the existing models capabilities just bigger. This all changed when one of the team stumbled on some ancient footage of a military maneuver where the tanks carried their own infantry support. Taking this idea further they designed a tank that could not only add considerable firepower to any assault it would prove to have a nasty surprise when it reached its target or if attacked at close range; a platoon of regular infantry or squad of battle armor carried aboard. To complement and support both other vehicles and its troops it mounts a mix of long and short range weapons allowing it to engage targets in all terrain and distances.
CAPABILITIES:
A Grizzard Model 200 is the most obvious weapon mounted on the Styx and the most damaging from the perspective of a single gun. Able to engage targets at extreme ranges this rifle gives crews a one shot kill ability against many light mechs and vehicles and will cause severe damage to heavier opponents. Although many see this as the main weapon system, the majority of crews treat this as a secondary weapon until targets come into range of the eight Martell Medium Lasers. Trials have shown these lasers have the same damage potential as two 20 rated autocannons, at a better weight, range and no ammunition worries. These lasers can destroy light vehicles and mechs and even some in the medium weight bracket with ease, and are almost guaranteed to kill most opponents short of assault class Battlemechs in a couple of salvoes. With both of these systems being turret mounted this gives the Styx the ability to engage targets in any arc and at all ranges. Almost as an after thought the designers added two Mydron Miniguns and McArthur Anti-Missile Systems for additional defense against infantry and missile attacks respectively. One of each is mounted co-axially in the turret whilst the others are fixed to engage targets in the vehicles forward arc. The final 'weapon' of the Styx is the infantry bay, allowing it to transport up to a platoon of regular soldiers right into the thick of battle. This gives commanders a decisive edge in any combat they find themselves in, and has turned the tide in many engagements though many privates see being assigned to a Styx as a path to great honor and at the same time a quick death. The whole tank is finally encased in 18.5 tons of ferro-fibrous armor and the ammunition protected in CASE'd storage bays.
VARIANTS:
There are two minor variants being tested, both of which remove the infantry bay. The first replaces the bay with two streak SRM-2 launchers and a ton of ammunition, the second with a LRM-5 launcher tied to an Artemis FCS again with one ton of ammunition.
Technology Base: - I.S. Tracked Vehicle - Level 2 - 100 tons
Equipment Mass
Internal Structure: 10
Engine: 300 XL 14.5
Cruising MP: 3
Flank MP: 5
Power Amplifier: 0
Heat Sinks: 24 – Single 14
Control Equipment: 5
Suspension: 0
Turret: 2.5
Armor Factor: 332 - Ferro-Fibrous 18.5
Internal Structure Armor Value
Front 10 70
Left 10 66
Right 10 66
Back 10 60
Turret: 10 70
Weapons, Ammo, and Equipment Location Space Tonnage
Gauss Rifle Turret 1 15
8 Medium Lasers Turret 8 8
Machine Gun Turret 1 0.5
Anti-Missile System Turret 1 0.5
Machine Gun Front 1 0.5
Anti-Missile System Front 1 0.5
Guardian ECM Suite Body 1 1.5
Infantry Bay Body 1 4
Ammo (Gauss Rifle) 16 Body 1 2
Ammo (MG) 100 Body 1 0.5
Ammo (AMS) 24 Body 1 2
CASE Body 1 0.5
BV: 1,257
Cost: 19,370,000
* Styx Heavy Assault Tank.hmv (3.51 KB - downloaded 1 times.)
-
Takiro Fifth BTSD Design Contest - The Merrill « Reply #18 on: February 08, 2008, 09:27:20 PM »
Merrill Strike Tank
Mass: 60 tons
Power Plant: Hermes 360 XL
Cruising Speed: 64.8 kph
Maximum Speed: 97.2 kph
Armour: Strasbourg Armaments Type 4 with CASE
Armament:
1 Magna Hellstar PPC
1 Holly SRM 6
1 Apple Churchill Guiding Light NARC Missile Launcher
Manufacturer: Leopard Armor
Communications System: Skobel Wave VI Comm
Targeting and Tracking System: PDS StoneGaze II with Apple Churchill 442x TAG
OVERVIEW:
To complement their new heavy tanks, the TRAS called for a tracked medium tank weighing 60 tons with a top speed of 97 kph. Many companies balked when they saw the desired specifications, arguing that it would be almost impossible to financially justify the use of such a large, probably extra-light, engine in a vehicle smaller than 70 tons. Leopard Armor however decided the benefits to speed and free space would outweigh the costs, and pressed ahead with the design that would eventually produce the Merrill Strike Tank. Named after the famed Second World War general Brigadier General Frank Merrill, the engineers took inspiration from the unit he led so successfully during the conflict, and designed a vehicle that could range ahead of the main force and cause havoc in the enemies rear areas. To build a vehicle which met their own desires as well as the required specifications Leopard licensed the newly patented Omni-Turret technology [Editors note: before patenting this was known as the Modular Turret Assembly, or MTA] from Pegasus Defense Systems Ltd, allowing them extreme flexibility in the equipment load for the Merrill, as well as ease of maintenance and multi-role ability.
CAPABILITIES:
Joining the Gorgon Heavy Tank as the second vehicle in the TRAS to feature the PDS Omni-Turret system, the Merrill Strike Tank gives commanders unique control over their forces composition and role on the battlefield.
The first thing many notice about the Merrill is its blistering speed for a high end medium tank. A cruising speed of 64.8kph, a top speed of 97.2 kph and powered by an extra-light fusion engine means that the vehicle can keep up with many lighter units, and having no fuel concerns allow crews to stay in the field for extended periods, ranging far ahead of the main force and causing havoc behind enemy lines.
The chassis mounts integral CASE for the standard Holly SRM-6 and is encased in an adequate 7 tons of ferro-fibrous armor, though some so-called ‘experts’ have complained that this is an unacceptable level of protection, trials have shown this to be more than enough when coupled with the high speed and ECM provided by the CAST variant, which give opposing units serious problems when trying to engage the Merrill.
The final part of the chassis is the PDS Omni-Turret system, first used in Pegasus Defense Systems own Gorgon Heavy Tank, and the integral PDS StoneGaze II. This proven combination gives the design an advantage over many other similar vehicles as the Merrill can be reconfigured at a moments notice depending on the likely terrain and opponents it will encounter. [Editors note: There are rumors of this system replacing standard vehicle/turret design in the near future, but this is unlikely due to the high technological expertise required to integrate the Omni-Turret into a design, limited production facilities available and the cost of bringing new factories on line].
VARIANTS:
There are two variants of the Merrill, each one based around a different turret configuration. They are commonly in a 2/2 breakdown per lance, though this obviously depends on the make-up of rest of the unit, terrain and expected opposing forces.
The first, known as the FOST (Forward Observer Strike Tank), was designed to act as a forward observer and engage the enemies forward scouts. To this end the turret houses an Apple Churchill Guiding Light NARC Missile Launcher and a 442x TAG by the same manufacturer. These allow commanders to call down accurate and devastating fire support from a number of platforms, the favored being Euryale and Medusa pattern Gorgons. It also mounts the design standard Holly SRM-6 rack on the left side of the turret. Alongside this is a proven Magna Hellstar PPC, the same weapon that can be found on the majority of Marauder Battlemechs today. To supply the missile weapons the FOST carries one ton of SRM-6 rounds and two tons of NARC missiles.
The second goes by the moniker of CAST (Cavalry Assault Strike Tank) and this turret mounts a fearsome array of short range weaponry for the space available. The main gun is a new Magna Devilstar snub-nosed PPC, capable of delivering sustained, savage firepower as long as the fusion engine is operational. Joining the standard Holly SRM-6 is another launcher of the same make, though on the opposite side of the turret. Infantry and light vehicles can be engaged with the two Sperry Browning machine guns. Finally a Merrill CAST has an Apple Churchill Guardian ECM suite mounted, to give improved defense against the numerous missile threats found today, and carries two tons of SRM-6 ammunition, allowing the use of a variety of missiles as the situation demands.
Technology Base: - I.S. Tracked Vehicle - Level 2 - 60 tons
Equipment Mass
Internal Structure: 6
Engine: 360 XL 25
Cruising MP: 6
Flank MP: 9
Power Amplifier: 0
Heat Sinks: 10 – Single 0
Control Equipment: 3
Crew: 4 Members 0
Suspension: 0
Turret: 1.5
Armor Factor: 125 - Ferro-Fibrous 7
Internal Structure Armor Value
Front 6 30
Left 6 25
Right 6 25
Rear 6 20
Turret 6 25
FOST
Weapons, Ammo, and Equipment Location Space Tonnage
PPC Turret 1 7
SRM 6 Turret 1 3
NARC Missile Launcher Turret 1 3
TAG Turret 1 1
Ammo (SRM) 15 Body 1 1
Ammo (NARC) 12 Body 1 2
CASE Body 1 0.5
BV: 554
Cost: 10,426,400
CAST
Weapons, Ammo, and Equipment Location Space Tonnage
Snub-Nose PPC Turret 1 6
2 SRM 6s Turret 2 6
2 Machine Guns Turret 2 1
Guardian ECM Suite Body 1 1.5
Ammo (MG) 100 Body 1 0.5
Ammo (SRM) 30 Body 1 2
CASE Body 1 0.5
BV: 693
Cost: 10,515,200
* Merrill Strike Tank CAST.hmv (5.2 KB - downloaded 1 times.)
* Merrill Strike Tank FOST.hmv (5 KB - downloaded 1 times.)
-
Takiro Seventh BTSD Design Contest - House Vehicles « Reply #19 on: February 08, 2008, 09:31:58 PM »
Shrike Hovertank
Mass: 45 tons
Movement Type: Hover
Power Plant: 215 MaxLift Model B Hover Engine Fusion
Cruising Speed: 108 kph
Maximum Speed: 162 kph
Armor: Sian Standard
Armament:
4 Sian/Ceres Jaguar LRM 5s
2 Hellion-V Medium Lasers
Manufacturer: Hellespont Industries
Location: Sian
Communications System: Hellespont TiteBeam
Targeting and Tracking System: FireScan with IndirecTrack
OVERVIEW:
The Shrike was born during the arms race following the revocation of the Edict of 2650. Rushed into service to offer the CCAF commanders an effective screening and harassing unit, the initial production runs were notable for their faulty turret ring assemblies. This often caused the turrets to become jammed if they were rotated as the vehicle made high speed turns. Subsequent runs corrected this problem and the Shrike went on to serve throughout the CCAF.
CAPABILITIES:
Designed to match or exceed the combat speeds of recon units is service at the time. The Shrike can outrun many light BattleMechs as well. This speed serves it well; allowing it to engage targets at range, where hopefully they will not be able to accurately return fire.
VARIANTS:
While no official variants exist there are some vehicles from the initial production run still in service. These differ from the current version in that they lack the medium lasers of the latter. In their place is another Ceres Jaguar LRM launcher.
DEPLOYMENT:
Widely deployed throughout the CCAF where it often performs the dual role of scout and scout hunter. Apparently a number of Shrikes were used by Star League forces during the campaign to liberate Terra. It is unknown if any survive in the Terran military.
Technology Base: - I.S. Hover Vehicle - Level 1 - 45 tons
Equipment Mass
Internal Structure: 4.5
Engine: 215 Fusion 14.5
Cruising MP: 10
Flank MP: 15
Power Amplifier: 0
Heat Sinks: 10 – Single 0
Control Equipment: 2.5
Crew: 3 Members 0
Lift Equipment: 4.5
Turret: 1
Armor Factor: 96 – Standard 6
Internal Structure Armor Value
Front 5 29
Left 5 19
Right 5 19
Rear 5 13
Turret 5 16
Weapons, Ammo, and Equipment Location Space Tonnage
4 LRM 5s Turret 4 8
Ammo (LRM) 48 Body 1 2
2 Medium Lasers Turret 2 2
Calculated Factors:
Total Cost: 2,147,000 C-Bills
Battle Value: 744
Cost per BV: 2,885.75
Weapon Value: 467 / 467 (Ratio = .63 / .63)
Damage Factors: SRDmg = 15; MRDmg = 10; LRDmg = 5
BattleForce2: MP: 10H, Armor/Structure: 0 / 4
Damage PB/M/L: 2/2/1, Overheat: 0
Class: GM; Point Value: 7
Specials: if
Drachen DRH-2A Battle Tank
Mass: 55 tons
Movement Type: Tracked
Power Plant: 220 Nissan Fusion
Cruising Speed: 43.2 kph
Flank Speed: 64.8 kph
Armor: ArcShield Heavy Standard
Armament:
1 RAMTech 1200X ER Large Laser
1 Coventry 90mm Six-Rack SRM 6
1 Exostar LRM 15
Manufacturer: Quickscell Company
Primary Factory: Pandora
Communication System: O/P 300 COMSET
Targeting & Tracking System: Digital Scanlok 347
OVERVIEW:
The DRH-2A Drachen has a short and colorful history in the annals of the Lyran Commonwealth's development of military vehicles, finding itself as one of the Commonwealth's last development endeavors before the decline of the Star League and the first design to fall to the predations of the Succession Wars.
Built and designed by the Quickscell Vehicle Company of Pandora shortly before the Amaris Coup, the new combat vehicle was initially created as a modern compliment to one of Quickscell's other military products; the famed Manticore heavy tank. Using schematics from the Manticore factory located on the Capellan Confederation world of Ares, the Quickscell team settled on a fifty-five ton frame for the new DRH-2A along with a target audience for the new medium tank; the Lyran Commonwealth. The Lyran High Command, long aware that while their private 'Mech armies were limited in size by Star League law there was little preventing them from strengthening their weakened conventional forces. However, throughout most of the Star League, the Lyran's focus remained settled on building both a larger war fleet and on more pressing merchant matters, like the fiscal crisis of the early 2600s, which ultimately sidelined the proposed upgrade until the late 2750s, after the death of First Lord Simon Cameron. Reading the writing on the wall following Simon's unexplained demise, the LCAF quickly took a page from the Rim Worlds Republic's military during the Reunification War, and began looking for suitable armor candidates to add to the vehicle starved LCAF.
Though the Drachen was built during the Star League era, an era of peace and prosperity, the majority of the Inner Sphere began to suffer from a bout of anxiety following the death of First Lord Cameron. Perhaps it was the apprehension of having a young child sitting on the throne, or the sheer anxiety of the unknown, but every citizen knew the League was heading towards a crucible of reckoning. The numerous military contractors of the Inner Sphere were no different, and many began to mimic their civilian counterparts’ paranoia. The Quickscell Company, though it was primarily through the prompting of the Lyran Commonwealth, authorized their design teams to build the new Drachen utilizing Lyran-built parts almost exclusively. Although the present trend of using only locally built parts for the majority of a given design seems like it would be counted as good logical common sense, during the Good Years of the Star League the integrated economies of the Great Houses allowed companies a greater latitude to freely develop new designs using a wide assortment of materials from a variety of different realms. One of the greatest tolls laden by the horrors of the Succession Wars was that designs that were once herald as technological achievements, were often regulated to the scrap pile once the various and disparate industries that supported them were wiped out or dried up once the sphere-wide conflagration began in earnest.
CAPABILITIES:
Because of the intense political pressure brought to bear on the development of the Drachen, the Quickscell Company was forced to import two very important pieces of technology that would have unfortunate consequences for the battle tank in the near future. The first was the Drachen's power plant, the Terran-built Nissan 220 fusion engine. A well designed and efficient fusion torus, the Nissan engine gave the DRH-2A a respectable sixty-four kilometer an hour ground speed over most terrain, while also providing power for all of the tank's systems and weapons. Ironically, one of the original Drachen design schematics called for an I.C.E. and a significantly reduced speed, but was rejected by the Lyran High Command as being too dependent on fuel. Only centuries later in the fusion engine-starved Inner Sphere does the idea of an I.C.E. equipped Drachen seem like a virtual godsend. The second piece of equipment imported for the DRH-2A was the Exostar LRM 15, built by the Dynamics Corporation of Gallery. The Exostar was chosen for its reliability and cost, which was an important factor when determining subcontractors for the design’s production.
The remaining pieces of technology reads like a "Who's who" of Lyran military contractors, including a targeting and tracking system; the Digital Scanlock 347, by Tharkad based THI, along with an excellent Archshield Heavy armor belt built on Skye. However, the shining pieces of the Drachen's technological fusion were produced by RamTech and Dynamics of Corporation of New Kyoto. The first of these sophisticated systems was the powerful O/P 3000 ComSet Communications system built by Dynamics. The O/P 3000 utilized specially built core processors that provided redundant operating power in the event of battle damage or poor maintenance. Although the O/P 3000 was not as sophisticated or as powerful as some comparable communication systems, such as the ones found on the Crab or Black Knight class BattleMechs, the additional reserve capacity of the O/P type did lend the Drachen a more robust nature and a better performance rating in field operations.
However, it was the installation of the RamTech Extended Range Large Laser that set the new battle tank apart from its non-SLDF contemporaries. First installed in the Lyran Commonwealth’s Mako Class Corvette in the early 2700s, the large laser was given to the Commonwealth as part of a joint Terran-Lyran technology for resources exchange. Although the exchange was initially opposed by members of the Hegemony High Command who wanted the Terran state to retains its existing edge in military hardware, both the Director-General and the First Lord knew that the continued prosperity and survival of the Hegemony rested on growing economy; an economy that was becoming more and more dependent on foreign natural resources. For the Drachen, Quickcell mated the performance of the Exostar LRM 15 with the range and hitting power of the ER Large Laser, allowing the tank to retain a measure of firepower long after it has spent its last LRM reload.
BATTLE HISTORY:
Given the surprising swiftness of the Star League’s demise, it is little wonder that towards the end of the 28th century the Lyran Commonwealth’s High Command was breathing a small sigh of relief when it regarded programs like the Drachen and its acquisition of former planets in the Rim Worlds Republic. Believing that the strength of the Commonwealth was greater than that of its closest rival and neighbor, the Free Worlds League, the LCAF High Command authorized an assault on the fortified League world of Bolan in 2785. Descending on the planet garrisoned by House Marik regulars, the LCAF hit the world with three regiments of troops, including two whole battalions of Drachen battle tanks. Though the battle for Bolan lasted only a few weeks the Drachen performed exceedingly well. Few League units were prepared for an ER Large Laser mounted on a House design and lacked a proper response; as a result the fight for Bolan was unrivalled in its fury since the end of the Reunification War.
With Kenyon Marik’s revocation of the Ares Conventions in 2787, the conflict known as the First Succession War began in earnest. Initially the war went well for the Lyrans. Their use of orbital bombardment and atomic weapons allowed for considerable gain along the Free Worlds League border. During these assaults the Drachen, which was issued predominantly to units along the League border, achieved many notable successes but suffered tremendous losses. Production was barely able to keep pace with the number of tanks destroyed in combat. However, it was the League’s devastating attack on New Kyoto in 2794 that sent the ill fated Drachen into a spiraling decline with the destruction of the RamTech ER Large Laser manufacturing plant, damage to the Dynamics Plant, and the entirety of the Bolson Shipyard complex. The loss of the Bolson yards was especially hard on the Lyran state, which quickly lost the ability to build new Mako Corvettes, or provide maintenance to its existing warship fleet along the League border. Shortly thereafter with portions of its industry ruined by the FWL attack, a Draconis Combine assault destroyed the ‘Mech factory on Yed Posterior. The plant’s destruction forced the Commonwealth to relocate many of its remaining resources, especially those in the embattled Isle of Skye, to safer plants like Coventry Metal Works.
Throughout the remainder of the First Succession War the Drachen would continue to perform admirably, fighting forces from the Free Worlds League, the Capellan Confederation, and the Draconis Combine. As the First Succession War began to wind down along the Free Worlds – Commonwealth front with the signing of the Bella Accords in 2821, so did the Drachen’s role. As the Commonwealth’s ability to manufacture advanced components slowly dwindled, so did production of the Drachen decline as remaining resources were earmarked in favor of shoring up BattleMech production. By the end of the Second Succession War, damage to the Commonwealth’s industrial infrastructure was so poor that production of the Drachen almost completely ceased, and companies like Quickscell, once herald as first rate manufacturers were left producing products of dubious quality.
VARIANTS:
Quickscell’s production of the Drachen class battle tank resulted in only one variant of the armored vehicle. The DRH-3A variant of the Drachen tank, first introduced in 2798, with subsequent refinements in 2802, 2817, and 2832 was not an actual production vehicle, but rather a response to the industrial predations of the First and Second Succession Wars. Each revision in the unofficial DRH-3A saw the Drachen lose an irreplaceable piece of LosTech and move further away from its original capabilities. The first revision, in 2798 saw the Drachen lose one of its most important components, the Nissan 220 fusion engine after the Terran Republic invoked a strict policy of neutrality and closed the world to outside influences. With the loss of the Nissan 220, Quickcell was forced to make due with a less powerful CoreTek 215 fusion engine produced on Skye. Despite a similar profile, the use of the CoreTek could not produce the same level of power as the Nissan 220 and the tank’s speed was reduced.
Additionally, the interior of the tank was redesigned to accommodate the new engine, forcing the designers to relocate the LRM ammunition to a different section of the tank. The new ammunition container, though no less protected than before, was moved closer to the crew hold. During combat, due to its new location, penetration of the vehicle’s interior would almost guarantee complete destruction of the tank, and the death of the crew. This redesign was the most direct source of the vehicle’s decline during the early Succession Wars, as salvaged vehicles were a scare rarity.
The 2802 redesign was another blow to the Drachen when the Commonwealth’s supply of RamTech ER Large Lasers dried up following the attacks on New Kyoto by House Marik. Afterwards Quickscell utilized a locally produced and less sophisticated type. From 2802 onward, the tank would suffer from a variety of component swaps, some made by necessity, others for safety purposes, such as the Exostar LRM 15 swap for a Coventry Starfire, or the O/P 3000 swap for a TharsHes KR-AP Comm built on Tharkad, or the Arcshield Heavy armor belt built on Skye, then moved to a Coventry produced Lexington Limited. By the Third Succession War, the remaining Succession War-scarred Drachen battle tanks would stand as a stark contrast to the pristine technological wonders first built during the Star League.
DEPLOYMENT:
Before the fall of the Star League, the Drachen first saw modest deployment only with the Lyran Guards, which saw the Drachen enjoy a few small actions during the Amaris Coup as Guard regiments descended upon the ravaged Rim Worlds Republic ostensibly as “peacekeepers,†but in actuality as conquerors. With the exodus of the SLDF as the last remaining peacekeepers of the League, the LCAF High Command distributed the bulk of the relatively unproven battle tank to units stationed along the Free Worlds League border in preparation for commencement of the hostilities. After the attack on Bolan and throughout the First Succession War these embattled worlds along the LC/FWL would either host or serve as a final resting place for the Drachen. However, given the devastation of the fighting and the shear number of Drachens lost during the fighting, following the signing of the Bella Accords the LCAF began to distribute the DRH-2A more evenly throughout the military, with a few vehicles serving as far away as the Vega theatre by the end of the Second Succession War.
Technology Base: - I.S. Tracked Vehicle - Level 2 - 55 tons
Equipment Mass
Internal Structure: 5.5
Engine: 220 Fusion 20
Cruising MP: 4
Flank MP: 6
Power Amplifier: 0
Heat Sinks: 12 – Single 2
Control Equipment: 3
Crew: 4 Members 0
Suspension: 0
Turret: 1.5
Armor Factor: 128 – Standard 8
Internal Structure Armor Value
Front 6 30
Left 6 24
Right 6 24
Rear 6 20
Turret 6 30
Weapons, Ammo, and Equipment Location Space Tonnage
ER Large Laser Turret 1 5
SRM 6 Turret 1 3
Ammo (SRM) 30 Body 1 2
LRM 15 Turret 1 7
Ammo (LRM) 24 Body 1 3
Vehicle Cost: 2,452,358 Kroner
Battle Value: 611
Phalanx AW-25A Infantry Support Vehicle
Mass: 25 tons
Movement Type: Wheeled
Power Plant: 80 G&H PowerMaxx Multifuel I.C.E.
Cruising Speed: 43.2 kph
Flank Speed: 64.8 kph
Armor: 1/Star Slab Standard
Armament:
2 LRM 5s
3 Sperry Browning Machine Guns
Manufacturer: Memphis Motive Systems
Primary Factory: Memphis
Communication System: TriStar Multilink
Targeting & Tracking System: Tristar Trackmaster II w/ ArtiSpot
OVERVIEW:
The Phalanx Infantry Support Vehicle (ISV) was first produced in 2754 by Greene & Harvester Agricultural Systems. G&H had wanted to expand their production facilities, and at the time, the only way to secure government backed loans was to be in an critical industry. As the Federated Suns government did not consider their line of combines and AG equipment critical enough, a few choice gifts to the right local politicians and a rushed design job led to a solution. The Phalanx system was adopted by a number of planetary militias before it was even produced, and G&H was now a military industry and thus received the loans needed to expand their facilities. Unfortunately, after the loans were approved, G&H discontinued production of the Phalanx after only a token manufacturing run.
In 3032, after the acquisition of G&H by their parent company TriStar Interstellar, Memphis Motive Systems noted the Phalanx system and found a number of elements to their liking. Most favored was the simplified drive train and motive system, used in literally millions of G&H farm machines across the Federated Suns and in copied versions throughout the inner sphere and periphery. With a few modifications, including a quick-swap turret assembly and upgraded power and communications bus, the new Phalanx was in production.
CAPABILITIES:
The A model Phalanx carries a pair of Holly LRM-5 systems, which are used to
soften up opponents and to provide covering fire for retreats. Although the A lacks effective close-range fire support, it's thick armor provides adequate protection for retrival operations. Twin turret-mounted Sperry Miniguns provide anti-infantry fire, with a rear-mounted Sperry clearing a path for the disembarking troops.
The interior of the Phalanx is crowded, but high-output air conditioning and heating systems keep the crew and infantry relatively comfortable. The foldable benches for the troops retract into the sides and floor, leaving a bay for transport that is easily loaded via the rear ramp. The front-mounted winch can be removed and mounted on the rear, or to a special point inside the bay, to assist with loading.
Although designed in a hurry, the original Phalanx was a solid vehicle - after
all, IFV's have been in production for over a thousand years, so there is a large pool of ideas to draw from. The Phalanx is completely NBC sealed, and all of it's onboard electronics are EMP-proofed. The updated communications bus utilizes optical links, which prevents electronic detection units from picking up stray chatter. In addition, the engine features a "generator mode", a fuel-saving cylinder-swapping power cycle that allows the vehicle to serve as power source without emptying it's fuel reserves too quickly.
VARIANTS:
A number of Phalanx users use an A model with additional ammo in lieu of infantry as a minelayer, with an option to replace the turret assembly and platoon bay with an enlarged turret featuring an LRM-15 and 2 tons of ammo. The B model Phalanx is often seen in urban combat and peackeeping roles, carrying only two reinforced infantry squads.
Although there was a design study on adapting the vehicle for battlearmor, the
interior is simply too crowded and the speed too low for there to be any compelling reason to manufacture a new version.
Notable Vehicles & Crew:
"Betty Sue"
Betty Sue is the name of the 4th production Phalanx, in service to the Sherwood Reserve Militia, 4th Company. Her crew and attached infantry platoon have become the mascots of MMS's ad campaign, touting the reliability and easy maintenance of the Phalanx design.
--------------------------------------------------------
Type/Model: Phalanx AW-25A
Mass: 25 tons
Construction Options: Fractional Accounting
Equipment: Items Mass
Int. Struct.: 15 pts Standard 0 2.50
Engine: 80 I.C.E. 0 5.00
Cruise MP: 4
Flank MP: 6
Heat Sinks: 0 Single 0 .00
Cockpit & Controls: 0 1.25
Crew: 2 Members 0 .00
Turret Equipment: 0 .50
Armor Factor: 80 pts Standard 0 5.00
Internal Armor
Structure Value
Front: 3 20
Left / Right Sides: 3 15/15
Rear: 3 15
Turret: 3 15
Weapons and Equipment Loc Heat Ammo Items Mass
--------------------------------------------------------
1 Machine Gun Rear 0 100 2 1.00
2 LRM 5s Turret 0 24 3 5.00
2 Machine Guns Turret 0 2 1.00
1 C.A.S.E. Equipment Body 1 .50
Infantry Bay Body 1 3.25
--------------------------------------------------------
TOTALS: 0 9 25.00
Items & Tons Left: 1 .00
Calculated Factors:
Total Cost: 313,688 C-Bills
Battle Value: 196
Cost per BV: 1,600.45
Weapon Value: 96 / 96 (Ratio = .49 / .49)
Damage Factors: SRDmg = 5; MRDmg = 5; LRDmg = 3
BattleForce2: MP: 4W, Armor/Structure: 0 / 3
Damage PB/M/L: 1/1/1, Overheat: 0
Class: GL; Point Value: 2
Specials: tran3, if
--------------------------------------------------------
Type/Model: Phalanx AW-25B
Mass: 25 tons
Construction Options: Fractional Accounting
Equipment: Items Mass
Int. Struct.: 15 pts Standard 0 2.50
Engine: 80 I.C.E. 0 5.00
Power Amplifiers: 0 .10
Cruise MP: 4
Flank MP: 6
Heat Sinks: 3 Single 0 3.00
Cockpit & Controls: 0 1.25
Crew: 2 Members 0 .00
Turret Equipment: 0 .35
Armor Factor: 80 pts Standard 0 5.00
Internal Armor
Structure Value
Front: 3 20
Left / Right Sides: 3 15/15
Rear: 3 15
Turret: 3 15
Weapons and Equipment Loc Heat Ammo Items Mass
--------------------------------------------------------
1 Medium Laser Turret 3 1 1.00
1 SRM 4 Turret 0 25 2 3.00
1 Machine Gun Turret 0 100 2 1.00
1 C.A.S.E. Equipment Body 1 .50
Infantry Bay Body 1 2.25
--------------------------------------------------------
TOTALS: 3 7 24.95
Items & Tons Left: 3 .05
Calculated Factors:
Total Cost: 352,219 C-Bills
Battle Value: 180
Cost per BV: 1,956.77
Weapon Value: 107 / 107 (Ratio = .59 / .59)
Damage Factors: SRDmg = 8; MRDmg = 1; LRDmg = 0
BattleForce2: MP: 4W, Armor/Structure: 0 / 3
Damage PB/M/L: 1/1/-, Overheat: 0
Class: GL; Point Value: 2
Specials: tran2
* Shrike Hovertank.hmv (1.66 KB - downloaded 1 times.)
* Drachen Battle Tank DRH-2A.hmv (12.83 KB - downloaded 1 times.)
* Phalanx Infantry Support Vehicle AW-25A.hmv (3.93 KB - downloaded 1 times.)
* Phalanx Infantry Support Vehicle AW-25B.hmv (3.92 KB - downloaded 1 times.)
-
Takiro Eighth BTSD Design Contest - Fighter Carrier « Reply #20 on: February 08, 2008, 09:37:08 PM »
Dione class Dropship
Tech: Inner Sphere / 2740
Vessel Type: Aerodyne DropShip
Rules: Level 2, Standard design
Rules Set: AeroTech2
Mass: 7,000 tons
Hull: StarTech Mod II
Length: 151 meters
Power Plant: AeroFord Standard
Safe Thrust: 5
Maximum Thrust: 8
Armor Type: StarGuard Ferro-aluminum
Armament:
7 Imperator-B Autocannon/10
5 Holly LRM 15
18 Diverse Optics Sunbeam ER Large Laser
12 Diverse Optics Type 2 Medium Laser
Overview:
The Dione, named after one of saturns many moons. Is the smaller,
sister-vessel to the Titan dropship. The Dione project was intended to provide
the League with a new fighter carrier similar to the Titan, but smaller and
cheeper.
The Dione doesn't quite provide the fighter compliment the Titan does...
the primary design is built for 18 fighters and 2 assualt ships, and the
secondary for 20 fighters and more cargo. The advantage of the new design is
its use of newer technology now more common to save space and money. The new
double strength heatsinks allowed for the clasic nose-and-side fireing pattern
without the need for added sinks beyond the ones built in the engine.
The Dione, is not built for near the standup fight its sister the Titan
is capable of, so many weapons-bays were adjusted for range over damage. This
allows the Dione to take better advantage of its speed, of which it matches
the Titan well. The largest change was the use of the new Extended Range Large
Lasers now more common.
Also the Dione is built to be a fair amount more versitle, its better
suited for planet side landings and isn't nearly as long and un-weildy as its
older sistership.
Class/Model/Name: Dione
Mass: 7,000 tons
Equipment: Mass
Power Plant, Drive & Control: 2,275.00
Thrust: Safe Thrust: 5
Maximum Thrust: 8
Structural Integrity: 10 350.00
Total Heat Sinks: 113 Double .00
Fuel & Fuel Pumps: 306.00
Bridge, Controls, Radar, Computer & Attitude Thrusters: 53.00
Fire Control Computers: .00
Food & Water: (33 days supply) 10.00
Armor Type: Ferro-aluminum (746 total armor pts) 45.00
Standard Scale Armor Pts
Location: L / R
Fore: 206
Left/Right Wings: 180/180
Aft: 180
Cargo:
Bay 1: Cargo (1) with 1 door 249.00
Fighters (Cool with 2 doors 1,200.00
Bay 2: Cargo (1) with 1 door 250.00
Fighters (Cool with 2 doors 1,200.00
Bay 3: Fighters (1+1) (2) with 1 door 100.00
Small Craft (2) with 1 door 400.00
Life Boats: 4 (7 tons each) 28.00
Escape Pods: 4 (7 tons each) 28.00
Crew and Passengers:
5 Officers (2 minimum) 50.00
7 Crew (0 minimum) 49.00
7 Gunners (7 minimum) 49.00
42 Bay Personnel .00
Weapons and Equipment Loc SRV MRV LRV ERV Heat Mass
2 Autocannon/10(20 rounds) Nose 2(20) 2(20) -- -- 6 26.00
2 LRM 15(24 rounds) Nose 2(18) 2(18) 2(18) -- 10 17.00
8 ER Large Laser Nose 6(64) 6(64) 6(64) -- 96 40.00
2 Autocannon/10(20 rounds) L/RW 2(20) 2(20) -- -- 12 52.00
1 LRM 15(16 rounds) L/RW 1(9) 1(9) 1(9) -- 10 18.00
5 ER Large Laser L/RW 6(60) 4(40) 4(40) -- 120 50.00
4 Medium Laser 24 8.00
1 Autocannon/10(20 rounds) Aft 1(10) 1(10) -- -- 3 14.00
1 LRM 15(16 rounds) Aft 1(9) 1(9) 1(9) -- 5 9.00
4 Medium Laser Aft 2(20) -- -- -- 12 4.00
1 Lot Spare Parts (1.71%) 120.00
TOTALS: Heat: 298 7,000.00
Calculated Factors:
Total Cost: 477,763,200 C-Bills
Battle Value: 5,925
Cost per BV: 80,635.14
Weapon Value: 8,585 (Ratio = 1.45)
Damage Factors: SRV = 222; MRV = 142; LRV = 40; ERV = 0
Maintenance: Maintenance Point Value (MPV) = 68,720
(38,381 Structure, 25,800 Life Support, 4,539 Weapons)
Support Points (SP) = 25,657 (37% of MPV)
BattleForce2: MP: 5, Armor/Structure: 13 / 12
Damage PB/M/L: 23/20/15, Overheat: 0
Class: DL; Point Value: 59
* Dione class Dropship.hma (3.07 KB - downloaded 3 times.)
-
Takiro Draconis Corvettes « Reply #21 on: February 13, 2008, 10:06:51 PM »
Himeko class Corvette/Raider
Tech: InnerSphere
Introduced: 2673
In Class: 40
Manufacturer: Wakazashi Enterprises (Dover /Draconis Combine)
Mass: 150,000 tons
Length: 300 meters
Sail Diameter: 500 meters
Fuel: 3,000 tons (15,000)
Tons/Burn Day: 19.75
Safe Thrust: 4
Maximum Thrust: 6
Sail Integrity: 3
KF Drive Integrity: 5
Heat Sinks: 458
Structural Integrity: 80
Armor: (240 tons, Improved Ferro-Aluminum)
Fore: 40
Fore-Sides: 40
Aft-Sides: 40
Aft: 40
Cargo:
Bay 1: Cargo (14,490 tons) 2 doors
Bay 2: Small Craft (14) 8 doors
Dropship Capacity: 3
Grav Decks: 0
Escape Pods: 20
Lifeboats: 0
Crew: 87 minimum (14 Officers, 73 Enlisted)
Weapons: (Heat: 458)
Nose (Heat: 164)
2 Naval Laser 45s
2 LRM 5s
2 PPCs
Fore Left/Fore Right (Heat: 60)
2 White Shark Missile Launchers
Aft Left/Aft Right (Heat: 90)
1 White Shark Missile Launcher
3 PPCs
Aft (Heat: 144)
2 Naval Laser 45s
2 LRM 5s
Ammunition:
120 White Sharks
48 volleys of LRM ammo (2 tons)
Overview:
A near failure when it was first designed; the Himeko was the brainchild of Yuriko Ono, a talented naval engineer who had emigrated to the Draconis Combine from her home in Nagasaki, Japan in 2660. In the 2670s, the Combine military had come to the decision to modernize its antiquated corvette fleet, soliciting designs from a number of its most prominent shipyards. Several prototypes were evaluated extensively, and despite their good performance the Combine choose to go in another direction. Not interested in wasting anything, the DCA acquired all three of the Himeko prototypes. The Himeko, Murasaki Shikibu, and Takahashi Rumiko all entered service in 2673.
(Editor's Note: Because she was the primary designer behind the corvette, Yuriko Ono was given the honor of christening these ships. Somewhat irritated with the male oriented society she had grown up with and was still surrounded by, she chose the names of women she considered her personal heroes. Himeko was a Japanese ruler from the end of the 3rd century CE, while Murasaki Shikibu wrote the early 11th century novel Tales of Genji. The name of the third ship, Takahashi Rumiko, is commonly believed to be in reference to a graphic novelist whose work enjoyed considerable popularity in both Japan and North America during the late 20th and early 21st century, however, this is not the case. In fact it is named for an administrator of the world of Shimonseki, who governed in the early 25th Century. Though a fair, judicious leader and even a hero for her role in averting a massive uprising in 2430, she is a largely unknown figure in history.)
Capabilities:
The Himeko is not a particularly impressive anti-ship platform, and neither was it intended to be. Yuriko Ono's design was intended to deal with general patrol and security duty, where its primary opponents would be pirates and smugglers. In this respect the light main armament of four naval lasers and six naval missile tubes is more than adequate. A collection of PPCs and small missile racks provide secondary anti-fighter defense.
Three docking collars and fourteen small craft bays allow the Himeko to transport a wide variety of supporting craft, which was originally intended to allow the ship to cover a wider patrol area. Unfortunately the docking collars made the ship too costly compared to others, which was the primary reason behind its rejection. Later, when adapted to serve as a raider, this allowed for a considerable raiding force to be transported to the battlefield.
A tough hulled, well armored ship, the Himeko could take a lot of punishment for a ship of its size. Heavily modified, her hull would become the basis for the later Inoshishi class corvette. Both designs have gone onto operate together frequently during the Succession War.
Deployment:
As early as 2690, Combine naval officers had begun to realize the Himeko's suitability for covert operations and raiding, and reportedly all three ships of the class were constantly engaged in espionage and harassment against the Combine's neighbors. They were so successful in this role that when the Edict of 2650 was repealed in 2755, the Combine commenced construction of thirty seven additional ships.
During the Succession War, these new ships have seen extensive action transporting raiding forces deep into enemy territory. Though often able to either slip past or outmaneuver local defense forces, these raids have often been costly for the attacking forces. As with all of the Combine's warships, the number of Himeko class ships in service has steadily declined since the start of hostilities.
Inoshishi class Corvette
Tech: InnerSphere
Introduced: 2758
In Class: 120
Manufacturer: Various (Draconis Combine)
Mass: 150,000 tons
Length: 350 meters
Sail Diameter: 500 meters
Fuel: 2,000 tons (10,000)
Tons/Burn Day: 19.75
Safe Thrust: 4
Maximum Thrust: 6
Sail Integrity: 3
KF Drive Integrity: 5
Heat Sinks: 1,000
Structural Integrity: 80
Armor: (240 tons, Improved Ferro-Aluminum)
Fore: 52
Fore-Sides: 52
Aft-Sides: 28
Aft: 28
Cargo:
Bay 1: Cargo (2,655 tons) 1 door
Bay 2: Small Craft (4) 2 doors
Dropship Capacity: 0
Grav Decks: 2 (50-meter diameter)
Escape Pods: 10
Lifeboats: 0
Crew: 89 minimum (15 Officers, 74 Enlisted)
Weapons: (Heat: 962)
Nose (Heat: 240)
4 Naval Autocannon 20s
Fore Left/Fore Right (Heat: 146)
1 Naval Autocannon 20
1 Barracuda Missile Launcher
3 Autocannon 5s
Aft Left/Aft Right (Heat: 576)
1 Naval Autocannon 20
1 Heavy Naval PPC
3 Autocannon 5s
Ammunition:
400 rounds of Naval Autocannon/20 ammunition
20 Barracuda Missiles
280 rounds of Autocannon/5 ammunition
Overview:
After the Edict of 2650 was repealed, every Great House rapidly expanded their military forces, however the expense associated with naval construction left most of the states concentrating on their ground arms. Every nation built new warships, of course, but in most respects, nobody was going to the same lengths to expand their fleets the way they were expanding the ground arm. The Draconis Combine was perhaps the one exception, and in their zeal to expand the fleet as quickly as possible they turned to the corvette, first producing the sophisticated and powerful Same, and following soon after with the Inoshishi. The Inoshishi (Wild Boar) was designed as a cheaper more easily mass produced alternative to the Same.
Capabilities:
The Inoshishi was the lightest front line corvette deployed in the Human Sphere at the start of the Succession War. Lighter than even the Rim Worlds Republic’s Pinto class Corvette it is an extremely tough and spartan design. The ship’s thick internal structure along with its impressive Improved Ferro-Aluminum armor endows it with unmatched durability for its size. Packing all of this protection into such a small vessel comes at a steep price however. Conditions aboard an Inoshishi are tight to say the least with narrow corridors pervading the entire ship. One of the few luxuries afforded to the crew are the twin 50 meters Grav Decks which give some relief from the otherwise snug insides of this highly durable warship.
Not intended to operate independently the Inoshishi has a relatively small cargo space and only average mobility. Its standard thrust of 2Gs, and maximum thrust of 3Gs, allows it to keep up with most ships so it can use its excellent firepower to swarm opponents as it was intended. Its armament includes eight Naval Autocannon 20s, two Heavy Naval Particle Projection Cannons, two Barracuda Missile Launchers, and twelve Autocannon 5s. This arsenal allows a single Inoshishi, or more typically a squadron, to challenge much larger craft and effectively overwhelm them.
Deployment:
At the start of this new Age of War the Draconis Combine fielded ninety of these valuable warships. Unlike larger warships, which require their own dedicated shipyards, the Inoshishi were small enough to be built at most civilian jumpship yards. Though this practice was limited early on, when the Star League began to crumble, the Combine government quickly moved to shift numerous civilian yards over to military construction, and Inoshishi class ships began pouring into service. In only twenty eight years numerous yards, some of which still have yet to be identified, cranked out more than three vessels a year on average.
After the start of the war production of these ships was stunted by widespread damage to Kurita industry but not completely halted. Approximately thirty more vessels have entered service with the Draconis Combine Admiralty. In fact the Inoshishi is one of the few warships still manufactured in the InnerSphere today thanks to its relatively simple design process. However, construction has been slowed due to a lack of available components and foreign sabotage conducted on all known facilities. It seems only a matter of time before the Inoshishi becomes as endangered as other warship designs no longer produced because of this horrific conflict.
Inoshishis are frequently grouped into squadrons and attached to every major Draconis naval force. Viewed as cannon fodder by their own commanders these corvettes are generally manned by green conscripts. Thanks to their hard charging nature very few Inoshishi crews have time to become battle hardened veterans. Large numbers of these ships have participated in practically every major battle of the Succession War and will likely continue to do so. While some of their losses were replenished from the numerous yards attrition has taken its toll on these ships and their crews.
Same class Corvette
Tech: InnerSphere
Introduced: 2757
In Class: 20
Manufacturer: Wakazashi Enterprises (Dover /Draconis Combine)
Mass: 350,000 tons
Length: 385 meters
Sail Diameter: 800 meters
Fuel: 2,000 tons (5,000)
Tons/Burn Day: 39.52
Safe Thrust: 5
Maximum Thrust: 8
Sail Integrity: 3
KF Drive Integrity: 8
Heat Sinks: 1144 (2288)
Structural Integrity: 60
Armor: (420 tons, Ferro-Carbide)
Fore: 102
Fore-Sides: 56
Aft-Sides: 56
Aft: 46
Cargo:
Bay 1: Cargo (8,146 tons) 2 doors
Bay 2: Small Craft (2) 1 door
Bay 3: Fighters (12) 3 doors
Dropship Capacity: 0
Grav Decks: 0
Escape Pods: 10
Lifeboats: 10
Crew: 165 minimum (29 Officers, 136 Enlisted)
Weapons: (Heat: 2,287)
Nose (Heat: 675)
5 Naval Autocannon 40s
Fore Left/Fore Right (Heat: 1312)
8 Naval Laser 35s
12 Killer Whale Missile Launchers
Left Broadside/Right Broadside (Heat: 120)
6 PPCs
Aft Left/Aft Right (Heat: 120)
6 PPCs
Aft (Heat: 60)
6 PPCs
Ammunition:
300 rounds of Naval Autocannon/40 ammunition
240 Killer Whale Missiles
Overview:
The Same (or Shark) class Corvette was originally engineered by Black Dog Shipbuilding of Fukuroi. A rather eccentric Draconis enterprise run like a pack of competing nerd fraternities rather than a proper business, one could never really be certain what was going to happen next.
And nowhere else was this truer than their Genken division, the division of the company dedicated to warship design. Though the division had turned out some successful designs in its time nobody could really be sure how they were doing it. The Genken division, though packed to the brim with brilliant minds, had no organization, no sense of order at all. Their ideas just seemed to flow spontaneously from out of nowhere or, as some scandalous rumors would have you believe from hallucinations induced by mushrooms.
Still, they did quality work, and their final product, the Same is certainly an excellent example of that, even if the Combine would prefer to forget that she and the Genken division ever existed.
Capabilities:
The Same was conceived as a high speed attack ship meant to engage ships several times her size. Intended to rely on pack tactics the Same did not depend on her considerable maneuverability to keep out of harms way. Quite the contrary in fact. The Same was designed to close with her opponent as quickly as possible and quite simply break it in half.
To do this, the Same depended on a main arsenal of five of the largest naval autocannons available. The Shitsuren (Broken Heart) model 40 naval cannons were built specifically for the Same, and they give her the firepower needed to rip through even the thickest armor.
Long range firepower on the ship was provided by two dozen Killer Whale missile tubes. Though unusual, this did provide the ship with considerable bite at any range for as long as the missiles lasted. A dozen aerospace fighters further added to the ship's offensive firepower.
Designers added sixteen small naval lasers and several PPC turrets to the design almost as an afterthought. Though wishing to pack even more naval missile tubes into the design, they conceded the possibility that the Same might just run out of ammunition and therefore might need something to fall back on.
Close to five hundred tons of Ferro-carbide armor provided protection for the Same. This gave her armor protection that many of the destroyers of her era would be quite happy with.
Small fuel tanks and limited cargo space made the Same ill suited for independent operations. This was not considered a problem, however, as she was designed to operate as part of the main battlefleet, offering a rapid strike force to support the main line of battleships and cruisers.
Deployment:
The Draconis Combine approved construction of the Same in 2757 as part of the public buildup of their House Military in the later days of the Star League (as opposed to the secret buildup that had been going on for decades). Black Dog facilities proved too small to handle production of this complex heavy corvette which was entrusted to Wakazashi Enterprises. Despite her considerable capabilities the ship was neither cheap nor easy to build which resulted in only twenty vessels being built by the start of the Succession War. New construction was halted soon after hostilities broke out because of these same complexities.
The Same's first role was rather unusual to say the least. In early June of 2758, the second ship of the class, the Kasasagi, was "loaned" to the noble Takeda clan, and took part in the festivities surrounding the marriage of the clan's eldest daughter Midori, transporting her on a symbolic journey from Vega to Altair to meet her future husband.
The very nature of the journey (requiring that Lady Midori arrive by July 7th) actually proved just a little dangerous, as the Kasasagi twice had to endure a quick charge of its KF-drive, and jump to a pirate point in the Altair system in order to deliver its passenger on time. Nevertheless, the untested ship made it through in fine style.
[Editor's note: Ridiculously extravagant really, especially when you consider that neither Vega nor Altair were Combine territory at the time. The amount of influence that had to be peddled to allow a heavily armed corvette, especially one that had yet to complete its shakedown cruise, to take this little jaunt through two states was considerable. Still, this gesture, full of romantic symbolism and inspired by classical Japanese legend, was considered incredibly romantic by some. Even today some maidens travel what is called the "lover's crossing" between Vega and Altair as a way of showing their devotion to their lovers].
Unfortunately, the rest of the ship's history has not been so peaceful or clear for that matter. The Combine's twenty Same class warships were on the front lines when the Succession War broke out, and though they scored some very impressive successes early on, many were quickly destroyed. Only a limited number of these warships are still believed to exist but there is a strange discrepancy that continues to puzzle some naval experts. Many sources, including the DCA, insist that only two such vessels continue to serve the Dragon as of today. However, there are some indications that at least one unknown Same still lurks somewhere in Combine space. A vessel spotted by foreign intelligence assets in the Benjamin District at the exact time as the known Same’s appeared elsewhere has raised some interesting questions. Combine authorities however dismiss these reports as attempts to mislead their own war efforts by creating ghosts in their own realm.
* Himeko class Corvette[Raider.hma (5.06 KB - downloaded 5 times.)
* Inoshishi class Corvette.hma (5.34 KB - downloaded 4 times.)
* Same class Corvette.hma (7.1 KB - downloaded 4 times.)
-
Takiro Draconis Destroyers « Reply #22 on: February 13, 2008, 10:10:04 PM »
Kaze class Destroyer
Tech: InnerSphere
Introduced: 2619
In Class: 40
Manufacturer: Stellar Trek (Togura /Draconis Combine)
Mass: 540,000 tons
Length: 600 meters
Sail Diameter: 1,200 meters
Fuel: 2,000 tons (5,000)
Tons/Burn Day: 39.52
Safe Thrust: 5
Maximum Thrust: 8
Sail Integrity: 4
KF Drive Integrity: 12
Heat Sinks: 3760
Structural Integrity: 60
Armor: (647 tons, Standard)
Fore: 50
Fore-Sides: 49
Aft-Sides: 49
Aft: 49
Cargo:
Bay 1: Small Craft (2) 2 doors
Bay 2: Fighters (12) 6 doors
Bay 3: Cargo (28,200 tons) 2 doors
Dropship Capacity: 0
Grav Decks: 0
Escape Pods: 10
Lifeboats: 10
Crew: 206 minimum (36 Officers, 170 Enlisted)
Weapons: (Heat: 3,760)
Nose (Heat: 400)
6 Naval Autocannon 20s
4 PPCs
Fore Left/Fore Right (Heat: 1960)
6 Medium Naval PPCs
6 White Shark Missile Launchers
8 PPCs
Aft Left/Aft Right (Heat: 1360)
4 Medium Naval PPCs
4 White Shark Missile Launchers
8 PPCs
Aft (Heat: 40)
4 PPCs
Ammunition:
600 rounds of Naval Autocannon/20 ammunition
200 White Shark Missiles
Overview:
The Draconis Combine's Kaze (or Wind) class Destroyers were a product of deals brokered between the Combine noble Ryu Mishima and the Taurian naval engineer Gregory Taylor. Though not directly involved in the Taurian campaigns of the Reunification War, the Draconis Combine watched the fighting with keen interest, and the successes the Taurian navy achieved against their enemies left a number the DCA's senior officers desiring to learn their secrets.
This was where Gregory Taylor came in. More or less orphaned by the Reunification War (his father, a naval officer, was captured during a deep raiding mission early on in the war and imprisoned for the duration. His mother died of heart failure soon after) this driven, obsessive man had dedicated his life to designing new warships and technologies that would enable the Concordat to eventually triumph. Unfortunately none of his work could prevent the inevitable, as the war had turned against the Concordat even before he had entered college. Nevertheless, he continued working obsessively. By war's end, he was arguably the Concordat's leading expert in naval technology, especially in the area of high thrust propulsion systems.
How he came to the attention of a Combine noble is anybody's guess. For whatever reason, shortly after the end of the war he was contacted by Ryu Mishima, Duke of the Combine world of Ijima and a DCA flag officer. With the permission of the Coordinator, Mishima arranged for Taylor to travel to the Combine with the expressed purpose of designing a new attack destroyer for the Combine navy.
[Editor's Note: Taylor's initial price for this service included Combine citizenship and a very comfortable life for both himself and his sister at an estate on Ijima. In addition over the next twenty years he was able to arrange for the emigration of thousands of Taurian citizens deemed by the occupying territorial government as dangerous subversives. A couple hundred joined him on Ijima, officially as his design staff, however the vast majority settled in a Combine colony in the near periphery]
After his design work was completed, the Combine constructed four prototypes which became known as the Kagero (or Resolute) class. These four ships (Resolute, Revenge, Ranger, and Rattlesnake) served for the next eighteen years as test vessels, and as the years passed Taylor continued to modify and improve on his basic design, never quite satisfied with it. Finally in 2618, enough people got tired of his ceaseless tinkering to approve the latest modifications for full production as Kaze class Destroyers. The first Wind class vessel, the Kamikaze, was launched in January of 2619.
Capabilities:
Though possessing a formidable battery of naval autocannons in the nose, the Kaze class Destroyer was in overall firepower only marginally better armed than the Combine's standard Kumo class Destroyers. Likewise her armor was only a marginal improvement. Her anti-fighter defenses, on the other hand, were exceptional, including numerous naval missiles, PPCs, and an even dozen aerofighters.
Where the Kaze really shined was in her propulsion system. The sophisticated and powerful propulsion system made it one of the fastest ships of her day, able to easily sustain 2.5 gravities of thrust for as long as needed, and reputedly able to achieve as many as 4.3 Gs at maximum thrust (though this might be an exaggeration). However, this particular capability was generally kept under wraps in order to hide the sophistication of the Combine's engine technology. In fact, it is believed that even some captains didn't know how much thrust their destroyers could produce until long after the ships had been first introduced.
Deployment:
A total of forty Kaze class warships were produced at Togura by Stellar Trek until the Edict of 2650 halted further manufacturing. These swift destroyers were assigned as fast attack ships and screening vessels for the fleet's cruisers and battleships, as well as command ships for large formations of corvettes.
At the start of the Succession War, the four Kaze class Destroyers were assigned to the Draconis' Task Force Biwa. This fast raiding force composed primarily of corvettes was based at Cylene. Their first taste of combat came when a Lyran task force assembled around the Tharkad class Battlecruiser Stalwart raided the world, intent on destroying the BattleMech plant located in the mountains outside the capital city.
Unfortunately, Task Force Biwa was unable to prevent the destruction of the facility or the devastation of the nearby capital by an errant Lyran thermonuclear warhead. They were, however, successful in destroying both of the Stalwart's screening ships. Hungry for revenge (most of Task Force Biwa's mostly conscript crews were drawn from Cylene), the fleet crossed into Lyran space in pursuit of the retreating Stalwart, finally running her down at Alrakis. While the bulk of the task force engaged the Lyran corvettes assigned to defend the system, Cho-Sho Louis Evans, commander of the fleet, committed his destroyers and his two Same class ships against the Stalwart. Engaging at near maximum range, the four Combine destroyers succeeded in drawing the Lyran Battlecruiser's attention long enough for the two Sames (which the Lyran commander seemed to have disregarded as a minor threat. They were, after all, "just corvettes") to close in and deliver a devastating barrage of fire from their forward guns. This attack in itself nearly destroyed the Stalwart, and the Combine forces were able to handily dispatch the crippled Battlecruiser.
Task Force Biwa moved to the Federated Suns front following the battle at Alrakis. There they were all but wiped out at Cholame, counting among its losses all four Kaze class Destroyers. Today only a half dozen of these formidable craft remain in Draconis service.
Kumo class Destroyer
Tech: InnerSphere
Introduced: 2540
In Class: 150
Manufacturer: Various (Draconis Combine)
Mass: 500,000 tons
Length: 570 meters
Sail Diameter: 1,200 meters
Fuel: 2,000 tons (5,000)
Tons/Burn Day: 39.52
Safe Thrust: 4
Maximum Thrust: 6
Sail Integrity: 4
KF Drive Integrity: 11
Heat Sinks: 2,935
Structural Integrity: 60
Armor: (599 tons, Standard Armor)
Fore: 51
Fore-Sides: 46
Aft-Sides: 46
Aft: 41
Cargo:
Bay 1: Small Craft (4) 1 door
Bay 2: Fighters (6) 2 doors
Bay 3: Cargo (56,213 tons) 2 doors
Dropship Capacity: 0
Grav Decks: 1 (65-meter diameter)
Escape Pods: 15
Lifeboats: 0
Crew: 197 minimum (34 Officers, 163 Enlisted)
Weapons: (Heat: 2,934)
Nose (Heat: 730)
10 Naval Laser 45s
2 White Shark Missile Launchers
Fore Left/Fore Right (Heat: 1,412)
10 Naval Laser 45s
2 Autocannon 10s
Left/ Right Broadsides (Heat: 180)
3 Naval Autocannon 10s
Aft Left/Aft Right (Heat: 192)
3 Naval Autocannon 10s
2 Autocannon 10s
Aft (Heat: 420)
6 Naval Laser 45s
Ammunition:
1200 rounds of Naval Autocannon/10 ammunition
20 White Shark Missiles
800 rounds of Autocannon/10 ammunition
Overview:
The Kumo, or Cloud, class Destroyer was authorized by Siriwan McAllister-Kurita during her regency, in order to provide a needed update to the Draconis Combine's often neglected destroyer force during the mid 26th century. This new ship was meant to replace the obsolete Skory and Bird class vessels which had formed the bulk of the Dragon’s “tin can†fleet up until this point. The Kumo class would actually be composed of four destroyer “types†each constructed in separate military districts incorporating refinements to the basic design to better allow each region to support construction. In this way the Combine expected to be able to rapidly update their destroyer fleet to meet any potential threat. Though each class would use locally produced components, in practice the four “types†were functionally identical in performance, and were generally referred to as the Kumo class. These ships became the standard destroyer of the Combine fleet throughout the Star League era.
Capabilities:
Never described as the best destroyer of its age the Kumo would nonetheless go onto prove itself a highly reliable warship throughout its long service life. When it was first constructed this vessel was comparable to any foreign rival fielded by the other Great Houses. Today subsequent classes now consistently outperform this venerable Kurita warship. This is hardly unusual behavior for the Combine which historically neglects their destroyer fleet in favor of their ground forces or heavier naval assets. Rather than commission a new class of ship the Admiralty has saved resources by upgrading the Kumo which has so far held off complete obsolescence.
Best described as well balanced and cost effective the Kumo continues to serve the Dragon well. A truly no nonsense vessel designed to be simple to both build and operate. Using basic and straightforward control systems without any exotic sensors or equipment this ship has proved suitable for nearly any crew. Even the rawest cadets can operate this vessel with little prior instruction. This aspect made the Kumo an excellent training ship in addition to being an exceptional escort. Often Kurita would combine the two roles, and it wasn't uncommon for these warships on patrol to be manned by cadets who had yet to graduate from the academy.
With interplanetary engines that maneuver the ship at 2Gs standard thrust; 3Gs max, the Kumo has good to average speed for a destroyer. Thirty six Medium Naval Lasers and twelve Light Naval Autocannons give the Kumo an impressive array of long range capital weaponry. When it was originally made the destroyer had typical armor protection for a ship of its size. Over time as the naval sciences have evolved this defense has proven to be more and more inadequate. If there is any real flaw in the design, it is in its lack of anti fighter weapons. Eight autocannons in four turrets provide the bulk of the defenses, however these can often prove insufficient against fighters wielding long range missiles. A pair of naval missile launchers is mounted in the nose of the craft, but these have a limited arc of fire. In the end the ship will usually have to depend on its six fighters for defense.
Deployment:
The Kumo class Destroyer served the Dragon well since the end of the Age of War and has widely been deployed throughout Kurita space since its inception some 260 years ago. It is believed as many as one hundred and fifty of these ships were constructed by the Combine since 2540. The secret nature of the Draconis naval operations and the four separate types of this single class make an exact count difficult at best. Typically the Kumo “type†itself was built and served in the Benjamin Military District, while Moons were native to Galedon, Kotlins to Pesht, and Thunders to Rasaulhague. Estimates for each “type†of this class, which look slightly different but in reality are identical, range from thirty five to forty. Some of these vessels were destroyed in combat, scrapped, or cannibalized for spare parts before the start of the Succession War. Long since out of production about 120 vessels of this class are believed to have begun this war in the DCA. While these ships have failed to capture a great amount of prestige many opponents still fail to realize their full potential and often underestimate them in battle. For the most part the class isn't much more than a workhorse and few ships gained anything resembling notoriety in the Draconis Combine.
One dubious exception to this is the Moon class DCS Akizuki, which served as Leonard Kurita's personal ship when he ascended to the Throne in 2591. During the first two months of his reign, the ship ferried him from world to world in what could rightly be described as an interstellar orgy of the highest magnitude. It didn't take long for Lord Kurita's excesses to infect the crew either, and before too long spacers and station managers alike feared the appearance of the Akizuki in their area for the fear that some drunken or stoned helmsman would plow the ship into them (which happened at least once, though it was only a glancing blow off of a recharge station, and the helmsman wasn't drunk or stoned, he was engaged in... umm... deep consultation with the assistant helmswoman). Though order on the ship was restored as soon as Leonard Kurita had a "mysterious accident" and Sanethia Kurita replaced him, the stigma of being Leonard Kurita's personal “pimp-mobile†still hung over the ship for many years after. Even today after amassing an impressive battlefield record this dark past still hangs over the ship and any who serve aboard it.
Nami class Destroyer
Tech: InnerSphere
Introduced: 2577
In Class: 7
Manufacturer: Wakazashi Enterprises (Dover /Draconis Combine)
Mass: 680,000 tons
Length: 600 meters
Sail Diameter: 1,000 meters
Fuel: 5000 tons (12,500)
Tons/Burn Day: 39.52
Safe Thrust: 4
Maximum Thrust: 6
Sail Integrity: 4
KF Drive Integrity: 14
Heat Sinks: 3,466
Structural Integrity: 50
Armor: (644 tons, Standard)
Fore: 48
Fore-Sides: 48
Aft-Sides: 48
Aft: 48
Cargo:
Bay 1: Fighters (6) 2 doors
Bay 2: Small Craft (2) 1 door
Bay 3: Cargo (64,694 tons) 2 doors
Dropship Capacity: 0
Grav Decks: 0
Escape Pods: 20
Lifeboats: 20
Crew: 261 minimum (45 Officers, 214 Enlisted)
Weapons: (Heat: 3,466)
Nose (Heat: 492)
4 Naval Laser-55s
2 Naval Autocannon 10s
4 Large Lasers
4 White Shark Missile Launchers
Fore Left/Fore Right (Heat: 704)
2 Naval Laser-55s
3 Naval Autocannon 10s
4 Large Lasers
4 White Shark Missile Launchers
Left/ Right Broadsides (Heat: 1284)
4 Naval Laser-55s
8 Naval Autocannon 10s
4 Large Lasers
2 White Shark Missile Launchers
Aft Left/Aft Right (Heat: 584)
2 Naval Laser-55s
3 Naval Autocannon 10s
4 Large Lasers
Aft (Heat: 402)
4 Naval Laser-55s
4 Large Lasers
2 White Shark Missile Launchers
Ammunition:
3000 rounds of Naval Autocannon/10 ammunition
180 White Shark Missiles
Overview:
What would one day become the Nami, or Wave class Destroyer, was originally introduced in 2345 as the Lola I by Boeing Interstellar for the Terran Navy. These warships served the Hegemony admirably as escort and picket ships for the main fleet for the next two hundred years, participating in numerous actions.
[Editor's Note: of course it would be more accurate to refer to the Lola I as simply the Lola, since that is actually the proper name for it. However, to avoid confusion with the Lola III, we shall stick with our mildly inaccurate designation]
In the year 2577, with the Reunification War getting into full swing, the Terran Hegemony struck a deal with the Draconis Combine for the sale of seven Lola Is, which by this time were considered rather obsolete. House Kurita immediately renovated these old ships at the Wakazashi Dockyards above Dover.
Renamed at an official ceremony a year later these venerable Heavy Destroyers went onto serve the Dragon with distinction. So renowned was their service that the class managed to survive the "Japanification" of the DCA begun by Urizen II. Even though they were built by the Terrans these ships were not considered gaikoku.
Capabilities:
On the surface there is very little different about the Nami class except for the upgraded and enlarged arsenal. Aside from this added weaponry and modernized external equipment it looks identical to the Lola I Cumbersome old components like the vessel’s fuel tank were replaced by newer more compact models throughout the ship. While living conditions onboard were slightly improved from their “sardine can†like environment by this renovation they can not be described as roomy. However, Draconis crews used to tight quarters fondly referred to this class as cozy homes.
Four Rolls Le Fay interplanetary drives continue to provide the Nami with superior performance. These engines usually intended for larger vessels allow the Destroyer to achieve a maximum thrust of three Gs. Efforts by Draconis engineers to overhaul these superior Terran drives have also paid dividends making them much more reliable. Intense in system burns no longer result in overheating, stress fractures, and breakdowns that occurred at times with the Lola I.
[Editor's Note: There is a persistent legend that the THS Renesco (later the DCS Ayanami) was able to sustain five Gs of thrust for several minutes during the battle of Terra Firma in 2409, which allowed it to escape from Liao pursuers. However, given that the propulsion system isn't even theoretically capable of that much thrust, we have to assume that this story is at least partially a myth. Just another piece of the legend of the Ayanami. However, it was a common tactic for more aggressive Lola captains to tax their engines, risking damage for the sake of gaining a tactical edge.]
The greatest change to the Nami was its weaponry which might have inspired the Lola II design. Only the thirty two Large Lasers from the Lola I remained unchanged. Eight Naval Laser-55s were added to the Kurita design while the dual Naval Laser-45s were removed. Also added were sixteen additional Naval Autocannon 10s which served to augment the Nami’s impressive firepower. Completely new to this design were eighteen White Shark Missile Launchers. To account for the extra heat generated by this staggering upgrade to the ship’s weaponry sufficient heat sinks were also fitted.
Deployment:
When the fighting in the Outworlds Alliance formally began in 2581, three Nami class Destroyers accompanied the DCMS expeditionary force into the Alliance. These warships saw heavy combat as the infamous Pitcairn Legion (Davion troops operating incognito against the Star League and Kurita in the Outworlds Alliance) seemed to single them out for special attention early on, striking at each mercilessly. Both the Isonami and the Shikinami would become victims of the Pitcairn Legion's fighter ambushes, while the Ayanami survived, though she had to withdraw from the theater for extensive repairs.
The hard fighting Nami operated as rather mundane escort ships after the Reunification War came to an end. Their performance while mixed at best still earned the class some degree of notoriety. The Nami might have even inspired the ill conceived Lola II. They continued to patrol the frontier rim of Draconis space until 2650, when they were officially retired from combat duty and declared training vessels. Both the Ayanami and Uranami were briefly reactivated for the Davion War of Succession (which led to the loss of the Uranami), most of the class sat out the next century or so in relative peace.
Some have also linked the Nami to the appearance of the Periphery Lola IIs during the Taurian Uprising. Allegedly the Dragon provided specifications for the Destroyers to the rebels. Supposedly insulted by Blue Nose Clippership’s attempt to rip-off the Draconis design without giving proper credit to Wakazashi Enterprises. While this has never been proven it does make sense to many around the InnerSphere. The Amaris Coup and the subsequent fall of the Star League saw the return of the Nami class to active duty. Two of the surviving four warships, the Makinami and the Onami, have already been destroyed in the Succession War. The renowned Ayanami and the Takanami continue to serve the DCA well to this day.
* Kaze class Destroyer.hma (7.35 KB - downloaded 4 times.)
* Kumo class Destroyer.hma (7.07 KB - downloaded 4 times.)
* Nami class Destroyer.hma (7.21 KB - downloaded 4 times.)
-
Takiro Draconis Cruisers « Reply #23 on: February 13, 2008, 10:15:04 PM »
Atago class Heavy Cruiser
Tech: InnerSphere
Introduced: 2652
In Class: 62
Manufacturer: Matabushi Incorporated (Luthien /Draconis Combine)
Mass: 810,000 tons
Length: 780 meters
Sail Diameter: 1,450 meters
Fuel: 3,000 tons (7,500)
Tons/Burn Day: 39.52
Safe Thrust: 2
Maximum Thrust: 3
Sail Integrity: 4
KF Drive Integrity: 17
Heat Sinks: 5,360
Structural Integrity: 80
Armor: (1199 tons, Standard Armor)
Fore: 88
Fore-Sides: 88
Aft-Sides: 88
Aft: 88
Cargo:
Bay 1: Small Craft (10) 2 doors
Bay 2: Cargo (76,075 tons) 2 doors
Bay 3: Fighters (24) 4 doors
Bay 4: Marines (756 / 36 jump infantry platoons) 1 door
Dropship Capacity: 4
Grav Decks: 2 (120-meter diameter)
Escape Pods: 20
Lifeboats: 10
Crew: 285 minimum (50 Officers, 235 Enlisted)
Weapons: (Heat: 5,360)
Nose (Heat: 340)
4 Naval Autocannon 25s
Fore Left/Fore Right (Heat: 1,230)
5 Naval Autocannon 10s
5 Naval Laser 55s
2 Killer Whale Missile Launchers
Left/ Right Broadsides (Heat: 1,870)
4 Naval Autocannon 25s
5 Naval Autocannon 10s
5 Naval Laser 55s
1 Killer Whale Missile Launcher
Aft Left/Aft Right (Heat: 1,680)
4 Naval Autocannon 35s
4 Naval Autocannon 25s
1 Killer Whale Missile Launcher
Aft (Heat: 240)
2 Naval Autocannon 35s
Ammunition:
1000 rounds of Naval Autocannon/35 ammunition
2000 rounds of Naval Autocannon/25 ammunition
2000 rounds of Naval Autocannon/10 ammunition
320 Killer Whale Missiles
Overview:
Named in honor of Admiral Takeo Kurita’s ancient flagship the Atago was commissioned by Urizen the Second to replace the older Sultan class Heavy Cruisers that until this time had been a bulwark of the DCA. At first, the announcement of Kurita's deployment of a new class of heavy cruiser, coming barely two years after Michael Cameron edict restricting the military strength of house militaries, caused a great deal of a stir. Many accused Kurita of disregarding Cameron's edict, and for a while there was talk that the naval arms race that had tainted the first half of the century would begin again.
However, these fears were quickly put to rest. Built with great fanfare at the Kure Naval Yards by Matabushi Incorporated there was little about this warship that was kept from the public. True to his word, Urizen II ordered the gradual phasing out of older vessels, replacing them with the new Atago class as they became available, and therefore, at least on the surface, staying below the naval limits imposed by the Star League.
[Editor's Note: Actually, the Atago is one of the few times where the Combine didn't try to duck around its obligations to the star league. This is believed to be partially due to the "Japanification" of the Combine first begun by Urizen II. Though Japanese culture had always had an influence over the Combine, it wasn't until his reign that it really took hold. This inevitably spread to the fleet as well, including to wide scale renaming or replacement of so called gaikoku (foreign) ships. Though the Combine already had several classes of ships with japanese names (such as the Hiei class battleships and several destroyer classes), under Urizen II this became policy. Sure the Sultan and other classes were old and would need replacement eventually, but they were also another thing as well. They were gaikoku.]
Capabilities:
The Atago class exemplified the design principles of the heavy cruiser. The ship is slow, and its armor is somewhat subpar for its size. On the other hand it is armed to the teeth. Fifty naval autocannons of varying calibers make up the main firepower, backed up by twenty naval lasers. While eight killer whale capital missile systems and twenty four fighters provide defense against enemy fighter attacks.
Combine naval planners envisioned the Atago as sort of a roving utility man, able to respond to trouble as it arose. With this in mind, the designers included four docking collars in the design, along with barracks space for a full regiment of jump capable marines. This allows the ship to deliver military forces to any trouble spot.
A noticeable difference from smaller Kurita warships is the spacious interior offered by the Atago. They aren’t luxurious by any standard but exceed the meager inside of lesser Draconis vessels. In part the ships’s wider corridors were done to facilitate naval operations but also as a reward to the more valued crews of these vessels.
Deployment:
The Combine constructed sixty two Atago class Heavy Cruisers from 2652 to 2700 and spread them throughout their fleet. They served in a variety of roles which included forming the bulk of the Dragon’s Naval Assault Squadrons as well as commanding smaller frigate and destroyer squadrons. Their service during the Davion War of Succession was limited, but in general they performed well. The sixty surviving Atagos were at the fore front of Kurita advances during the start of the Succession War. They played a major role in the Draconis naval victories at Skondia and Cholame against Steiner and Davion forces respectively. While their impact has clearly been felt the entire class has taken massive damage and could be on the edge of extinction. Only a handful of these Heavy Cruisers now remain.
One of these surviving vessels, the DCS Haguro, has a storied past that includes a female naval commander. Ryoko Igarashii, who commanded the Haguro from 2658 to 2669, was a rarity in the Combine. A woman commanding a major warship was completely unheard of in the Draconis Combine. Descended from a noble linage, that was somewhat unsung, Igarashii was a gifted naval tactician who led with a unique style. Apparently deferring her authority to male underlings, who always under performed without her guidance, she overcame a lingering cultural bias and shot to renown within the Combine. She stepped down in 2669 to settle in as housewife to a rising staff officer Tai-Sa Franklin Nobunaga. The Nobunaga family has continued to serve with distinction in the DCA. Later on the Combine honored the entire Igarashii clan for their service by naming their newest class of battlecruiser after them.
Byakuren class Battlecruiser
Tech: InnerSphere
Introduced: 2781
In Class: 4
Manufacturer: Matabushi Incorporated (Midway /Draconis Combine)
Mass: 950,000 tons
Length: 1,070 meters
Sail Diameter: 1,200 meters
Fuel: 10,000 tons (25,000)
Tons/Burn Day: 39.52
Safe Thrust: 4
Maximum Thrust: 6
Sail Integrity: 5
KF Drive Integrity: 19
Heat Sinks: 2,240 (4,480)
Structural Integrity: 180
Armor: (3420 tons, Lamellor Ferro Carbide)
Fore: 700
Fore-Sides: 614
Aft-Sides: 600
Aft: 400
Cargo:
Bay 1: Cargo (15,578 tons) 8 doors
Bay 2: Small Craft (2) 2 doors
Bay 3: Fighters (36) 6 doors
Dropship Capacity: 4
Grav Decks: 3 (150-meter diameter)
Escape Pods: 60
Lifeboats: 0
Crew: 315 minimum (55 Officers, 260 Enlisted)
Weapons: (Heat: 4480)
Nose (Heat: 600)
60 Particle Projection Cannons
Fore Left/Fore Right (Heat: 1600)
8 Naval Autocannon 30s
Left/Right Broadside (Heat: 1200)
60 Particle Projection Cannons
Aft Left/Aft Right (Heat: 480)
12 Killer Whale Missile Launchers
Aft (Heat: 600)
60 Particle Projection Cannons
Ammunition:
800 rounds of Naval Autocannon/30 ammunition
120 Killer Whale Missiles
Overview:
An experimental design dating as far back as the repeal of the Edict of 2650, the Byakuren (White Lotus) class Battlecruiser was largely regarded as an oddball design that stood accepted naval traditions and protocols on their head, sacrificing almost all of the firepower wielded by her contemporaries such as the Black Lion and Igarashii in favor of speed and armor protection. A lot of armor protection.
In this regard, she wasn't the first ship to follow this design principle, but it had never had much of a following with any naval power, all of which favored offensive armament over armor protection. Even the success of similar designs like the Taurian Navy's Reunification War era Basho wasn't enough to sway most people, and the DCA wasn't an exception, rejecting the radical design out of hand when it was first presented for their approval in 2757. Recent events, however, show that the Byakuren would get the last laugh.
Capabilities:
When a person looks over the Byakuren, the first thing that no doubt sticks out in their mind is that it carries only sixteen heavy guns, an armament barely the equal of a destroyer much less what would be regarded as a typical battlecruiser. The twenty four killer whale tubes, six fighter squadrons, and the truly massive battery of anti-fighter PPCs (which is an almost unheard of design feature) helps brighten the picture a little, but most look no further.
Proponents of the design usually take this moment to slap those who turn away with a copy of Janes Fighting Ships and point out the ship's massive armor belt, thirty four hundred tons of the best armor money could buy and espionage could steal, over twice as thick as that used on the vaunted Texas, and the heaviest confirmable level of armor protection in use on any warship currently in service.
With this in mind, the point of the Byakuren becomes apparent. It is true that most warships her size (or even significantly smaller) outgunned the battlecruiser, often by a significant margin, but all this extra firepower actually doesn't give them a particularly significant advantage over the Byakuren, there is simply too much armor for them to get through, while the Byakuren's more humble broadside is still able to deliver serious damage to a more conventional ship's lighter armor. The ship's designers actually went so far as to claim that the Byakuren's survivability made it at the very least an even match for any ship in the fleets of the Inner Sphere; even the Terran Hegemony's vaunted Mckenna.
Deployment:
Old habits die hard, however, and concerns about the Byakuren's lack of firepower led to its rejection by the DCA. It would take the destruction and chaos of the Periphery Uprising and the Amaris Coup for the design to be revisited. With so much of the SLDF battlefleet being wiped out right and left war planners began to re-evaluate not only their battle tactics, but the design principles of their warships. In far too many battles goliath warships were vaporized rapidly by a variety of innovative tactics. It had become painfully obvious that the light armor protection that had been considered acceptable for centuries simply didn't cut it in true, full scale open warfare, and many warships were actually, as odd as it might sound, a little bit too heavily armed.
Of course the Combine was in no position to begin a massive effort to completely replace and redesign their battlefleet, however, they were in the unique position of having a design already available with the kind of armor protection that some Admirals were clamoring for. The decision was made to begin construction of the Byakuren class as Kerensky was closing in on Amaris. A total of four keels were laid down and eventually completed at the Draconis Fleet Yards above Midway by Matabushi Incorporated. The general scarcity of resources prevented any further construction on a fifth Byaruken which was only partially completed.
Today only one Byakuren class Battlecruiser, the Kakitsubata (Iris), still serves the Dragon. Sadly her sister ships; the Byakuren, the Shakuyaku (Peony), and the Sanshikisumire (Pansy), have all succumbed to the increasing devastation of the Succession War. Even this warship’s impressive armored hull was not enough to stave off the unprecedented destruction of this cataclysm conflict. The DCA has managed to keep the Kakitsubata operational by cannibalizing her unfinished sister ship and judicious use of salvage.
Igarashii class Battlecruiser
Tech: InnerSphere
Introduced: 2708
In Class: 60
Manufacturer: Matabushi Incorporated (Luthien /Draconis Combine)
Mass: 810,000 tons
Length: 775 meters
Sail Diameter: 1,450 meters
Fuel: 4000 tons (10,000)
Tons/Burn Day: 39.52
Safe Thrust: 3
Maximum Thrust: 5
Sail Integrity: 4
KF Drive Integrity: 17
Heat Sinks: 1,500 (3,000)
Structural Integrity: 120
Armor: (1400 tons, Ferro-Carbide)
Fore: 198
Fore-Sides: 199
Aft-Sides: 199
Aft: 198
Cargo:
Bay 1: Fighters (18) 3 doors
Bay 2: Cargo (75,579 tons) 1 door
Bay 3: Small Craft (10) 2 doors
Dropship Capacity: 4
Grav Decks: 2 (65 and 85-meter diameter)
Escape Pods: 20
Lifeboats: 0
Crew: 251 minimum (43 Officers, 208 Enlisted)
Weapons: (Heat: 2,940)
Nose (Heat: 400)
4 Naval Autocannon 30s
Fore Left/Fore Right (Heat: 940)
4 Naval Autocannon 30s
4 White Shark Missile Launchers
1 Barracuda Missile Launcher
Left/ Right Broadsides (Heat: 700)
4 Naval Autocannon 25s
1 Barracuda Missile Launcher
Aft Left/Aft Right (Heat: 700)
4 Naval Autocannon 25s
1 Barracuda Missile Launcher
Aft (Heat: 200)
2 Naval Autocannon 30s
Ammunition:
1400 rounds of Naval Autocannon/30 ammunition
1600 rounds of Naval Autocannon/25 ammunition
80 Killer Whale Missiles
60 Barracuda Missiles
Overview:
In 2691the Star League deployed its fearsome Black Lion class Battlecruiser and the rest of the Human Sphere took notice. This was especially true of the Draconis Combine who allegedly desired this formidable warship design for its own navy. For fifteen years their Internal Security Force (ISF) played a dangerous cat and mouse game with the SLDF eventually acquiring most of the original plans. (Editor’s Note: The House Kurita continues to deny these covert operations and instead plays up the role of its own ship, the Atago, in the design of this ship) While espionage seems to have played a major role in the development of this new Battlecruiser it was not solely responsible for the unique end product. (Editor’s Note: No conclusive proof has ever been uncovered to show that House Kurita stole the Black Lion design despite some pretty convincing accusations) As construction of the impressive Atago class Heavy Cruiser came to an end its proven equipment and capable engineers were dedicated to this growing project. Much of their knowledge and expertise went into the Combine’s Black Lion which became known as the Igarashii. Named in honor of a noted Draconis military family the first ship of its kind launched from the Kure Naval Yards in 2708 becoming one of the finest in the Draconis Combine Admiralty (DCA).
Capabilities:
Even though the Igarashii’s basic design seems to be copied directly from the Black Lion it was apparently intended to defeat its predecessor in a stand-up fight. The debate over how successful the Kurita effort was at overcoming the initial Star League design continues to rage to this day. Both ships look nearly identical as they mass just over eight hundred thousand tons and have almost the same overall length. The Combine model incorporates some aesthetic hull differences and is slightly longer because of its interplanetary engines. The Igarashii uses three Hyperion Starfire engines, originally used on the Atago, to match the Black Lion’s 2.5 Gs of acceleration without the complexity issues that hamper maintenance efforts. These drives actually showcase how much the Igarashii has in common with the Atago which first utilized two Hyperion Starfires for in system transit. Perhaps more interesting might be the fact that both Kurita designs use the same Compact KF Cores and jump sails. While these key features make a compelling case for Draconis advocates who claim the Atago, and not the Black Lion, was the basis for this battlecruiser. However, additional features and their very placement throughout the Igarashii appear to come completely from the Black Lion and almost prove that the design was plagiarized. From the corridors that line the ship to the four docking collars, the fighter bay (with the exception of a single missing door), the small craft bay, the escape pods, and even the grav decks it is almost identically to the Star League Battlecruiser.
Admittedly there are key differences between the Black Lion and its Kurita imitator. First off the Igarashii holds about four times as much fuel as its evident forerunner. The Igarashii has superior armor protection to the Star League Battlecruiser thanks in part to a heavily reinforced hull. The design also makes use of advanced Ferro Carbide plating which was probably obtained by Draconis agents for the express purpose of duplicating the Black Lion’s capabilities. The arsenal of the Igarashii departs from the Black Lion in some important ways. The vessel’s main armament, fourteen Naval Autocannon 30s, is clearly based on Star League ship. However the Igarashii utilizes sixteen Naval Autocannon 25s found on the Atago, rather than 20s found on the Black Lion, to augment the main guns. While this weapons array possessed only two-thirds as much firepower as the Black Lion it requires a smaller crew complement to operate. Also it has superior heat dissipation thanks to double heat sinks and its altered weaponry. Eight Killer Whale Missile Launchers and six Barracuda Missile Launchers appear to be holdovers from the Black Lion. Despite these differences both vessels were clearly able warships that would go onto battlefield success throughout their service in space.
Deployment:
The Igarashii class Battlecruiser first began appearing seventeen years after the launch of the Black Lion. Construction, which was slower than the Star League Battlecruiser, continued until the destruction of the Luthien shipyards in 2787 by the Tamar Tigers. All sixty vessels were battle tested in the early years of the Succession War where they saw extensive combat. During the battle of Dieron the Igarashii finally squared off against the Black Lion but the massive clash failed to resolve the issue of which was the better ship. However, both vessels fought well and proved themselves beyond the shadow of a doubt during this epic struggle. Their fearsome capabilities made them prime targets for nuclear and massed fighter attacks which have taken their toll on this class. They have been nearly wiped out by this conflict and may soon become extinct.
Mogami class Cruiser
Tech: InnerSphere
Introduced: 2725
In Class: 24
Manufacturer: Various (Draconis Combine)
Mass: 700,000 tons
Length: 700 meters
Sail Diameter: 1,150 meters
Fuel: 10,000 tons (25,000)
Tons/Burn Day: 39.52
Safe Thrust: 4
Maximum Thrust: 6
Sail Integrity: 4
KF Drive Integrity: 15
Heat Sinks: 7,180
Structural Integrity: 90
Armor: (1259 tons, Standard)
Fore: 93
Fore-Sides: 93
Aft-Sides: 93
Aft: 93
Cargo:
Bay 1: Fighters (36) 6 doors
Bay 2: Cargo (35,932 tons) 2 doors
Bay 3: Small Craft (2) 1 door
Dropship Capacity: 0
Grav Decks: 0
Escape Pods: 0
Lifeboats: 15
Crew: 290 minimum (51 Officers, 239 Enlisted)
Weapons: (Heat: 7,180)
Nose (Heat: 600)
8 Naval Laser 45s
5 Large Lasers
Fore Left/Fore Right (Heat: 2180)
15 Naval Laser 45s
5 Large Lasers
Left/Right Broadside (Heat: 2180)
15 Naval Laser 45s
5 Large Lasers
Aft Left/Aft Right (Heat: 2180)
15 Naval Laser 45s
5 Large Lasers
Aft (Heat: 40)
5 Large Lasers
Overview:
Though not particularly prevalent in the Draconis Fleet the Mogami class Cruiser has nevertheless earned its own niche, simply because of its clouded origins. Despite intense Kurita secrecy we can today gather from known evidence that there were at least five separate Mogami “classesâ€. Officially, the Draconis Combine deployed only five Mogami class ships, the Mogami, Kuma, Asashio, Nadashio, and Natori. However, records indicate that these five ships (each of which had significant structural differences from one another, suggesting they were built at different yards) were actually the lead warships for a whole series of shadow cruiser.
The official date of the Mogami's launching was in mid 2755, barely two months after the Star League Council passed a resolution allowing the Great Houses to double the size of their private armies. However, careful study does not support this assumption, and despite the official story being that all five ships were built at Chatham, there is no indication whatsoever that the Combine has ever built Mogami class ships there. Careful analysis of freighter traffic (specifically freighters carrying parts needed for warships) seems to indicate that construction of the Mogami and her sisters took place at least five separate shipyards as early as 2725. It is believed that two dozen warships of this type were constructed beginning at least thirty years before their official appearance.
Capabilities:
The Mogami was in essence an illegal warship, built secretly in violation of Star League Edicts regarding the size of private House militaries. This fact in itself is no big deal. Every Great House did at least some stretching or outright breaking of the rules when it came to the strength of their private armies, especially when it became apparent that the League was crumbling. What makes the Mogami unique is the excessive lengths to which this secret was kept (to this day the Combine only admits to building eighteen Mogamis, and they maintain that none of them were built before 2755), and the fact that this ship was built specifically to fight in a post Star League era.
This conclusion becomes inescapable when one examines the Mogami closely. In the first case, the ship is dirt cheap. No lithium fusion battery, no docking collars, no fancy armor, not even a grav deck. The weaponry, a massed battery of nearly a hundred naval lasers and forty large lasers, provides reasonable firepower at the lowest possible price. In the second case, the ship requires very little in the way of logistical support. It carries ten thousand tons of fuel, along with enough supplies to keep operating for a year, and most important of all, does not require ammunition resupply. In the third case, the ship can be operated by practically anyone. The control systems are extremely simple and reliable, meaning that an undertrained crew will be able to control their ship fairly well.
If we take these three things into account, we end up with a relatively cheap ship that can be fueled once, staffed with green recruits, and sent off to battle. Thanks to its weaponry and armor protection, a Mogami might even be expected to last long enough for its replacement to be completed and a new crew trained. The ship is therefore ideal for the bloody ship killing fights that all out war in the InnerSphere would entail.
Deployment:
From confirmed sightings thus far we know that there were at least four Mogamis, three Nadashios, three Kumas, half a dozen Asashios, and two Natoris (the two Natoris in particular are confirmed because they both appeared at the battle of Cholame at the same time), despite claims by Takiro and later Minoru Kurita that they had only ever built five ships. We believe at least seven of these formidable warships are still in service with the Draconis Fleet. However the destruction of the Succession War has effectively ended further construction of this large vessel despite its simplicity.
There are persistent rumors that a sixth Mogami shipyard exists somewhere still in Combine space. These stories may have begun on the vague assumption that there might just be a hidden shipyard somewhere to build this secret warship. Some place Kurama Shipyard (or Hie or Marat or another name used by one of the other hundred legends surrounding this most likely none existent place) along the coreward edge of Combine space. Fantastic tales of how the Combine was researching a new power system called the phase transition engine, or how it was where an incredibly powerful energy weapon was being developed capable of destroying entire planets, or where dealings with a transdimensional alien race broke down, resulting in the Succession War.
Sadly this irrational list seems endless but a few still believe that there is a shipyard out there that used to build these mysterious Cruisers. The evidence for all these theories is of course non existent, and ninety nine percent of them are utterly ridiculous. Nevertheless, a significant number of people have begun to scour the coreward edge of the Combine looking for something, even if it is just a purpose to their own pathetic lives.
That being said, there is of course the possibility that there are additional Mogamis floating around somewhere. It may never be known how many of these warships were built, but the shear amount of time between 2725 (when the first one was believed to have been built) and the start of the Succession Wars suggests that there was plentiful time to produce a large number of these ships, especially at five different shipyards. It is possible that a few of these ships were mothballed, waiting to be utilized, and just forgotten. Of course it is also possible that a sixth shipyard actually does exist. In both cases, there is no evidence to support either assumption.
* Atago class Heavy Cruiser.hma (6.4 KB - downloaded 4 times.)
* Byakuren class Battlecruiser.hma (5.94 KB - downloaded 4 times.)
* Igarashii class Battlecruiser.hma (6.67 KB - downloaded 4 times.)
* Mogami class Cruiser.hma (7.29 KB - downloaded 4 times.)
-
Takiro Draconis Carrier and Battleship « Reply #24 on: February 13, 2008, 10:16:58 PM »
Tone class Carrier
Tech: InnerSphere
Introduced: 2777
In Class: 4
Manufacturer: Stellar Trek (Togura /Draconis Combine)
Mass: 850,000 tons
Length: 950 meters
Sail Diameter: 1,000 meters
Fuel: 2,500 tons (6,250)
Tons/Burn Day: 39.52
Safe Thrust: 4
Maximum Thrust: 6
Sail Integrity: 5
KF Drive Integrity: 17
Heat Sinks: 3,170 (6,340)
Structural Integrity: 80
Armor: (1360 tons, Ferro Carbide)
Fore: 188
Fore-Sides: 190
Aft-Sides: 190
Aft: 188
Cargo:
Bay 1: Fighters (72) 6 doors
Bay 2: Small Craft (6) 2 doors
Bay 3: Marines (12 platoons) 2 doors
Bay 4: Cargo (39,249 tons) 2 doors
Dropship Capacity: 4
Grav Decks: 3 (150-meter diameter)
Escape Pods: 50
Lifeboats: 50
Crew: 291 minimum (51 Officers, 240 Enlisted)
Weapons: (Heat: 6340)
Nose (Heat: 430)
2 Naval Laser-55s
2 Naval Laser-45s
10 Extended Range Large Lasers
Fore Left/Fore Right (Heat: 2160)
4 Naval Autocannon 30s
4 Naval Laser-55s
4 Naval Laser-45s
5 Extended Range Large Lasers
Left/Right Broadside (Heat: 2060)
6 Naval Autocannon 30s
2 Naval Laser-55s
2 Naval Laser-45s
10 Extended Range Large Lasers
Aft Left/Aft Right (Heat: 1260)
2 Naval Autocannon 30s
2 Naval Laser-55s
2 Naval Laser-45s
10 Extended Range Large Lasers
Aft (Heat: 430)
2 Naval Laser-55s
2 Naval Laser-45s
10 Extended Range Large Lasers
Ammunition:
2400 rounds of Naval Autocannon/30 ammunition
Overview:
The Tone class Carrier was the brainchild of Rear Admiral Yugi Nishimura. The Admiral was part of the Draconis Combine Naval Reporting Committee during the Amaris Coup. This Committee was tasked with following the SLDF’s naval operations and using said data to develop improved doctrine for the Combine. Nishimura was thought by many in the DCA to be its best mind even though not he was not its the highest-ranking member.
In 2774 Nishimura used a major committee report to advance his idea for a new warship. He outlined a design that he believed would be able to counter a thick fighter screen. Carrying 72 fighters (2 full wings) and a massive battery of NACs, these ships were designed to power through enemy fighter and dropship screens and tear an enemy capital ship to shreds at close range. Nishimura’s stated plans for the design had it teamed with two destroyers and four assault dropships to give it the added punch to power through any resistance. Despite concern within the DCA over the cost of the design, its outstanding performance in simulations convinced the DCA to order it into production at Togura as the Tone-class, with the first ship completed in 2777. Four Tones were completed by Stellar Trek prior to the start of the Succession War. Their heavy fighter complement prompted the DCA to give them the designation of Carriers.
Capabilities:
In some ways, it is surprising that the Tone class was authorized, since these ships are very different from the formation attack geared cruisers the DCA had been using. The Tone was intended to use its escorts and fighter screen to clean the way while it powered through the enemy to reach broadside range. Twenty-four NAC-30s give it enough hitting power to rapidly destroy any cruiser and most battleships. Forty Naval Lasers give the vessel a powerful anti-Dropship armament. Admiral Nishimura recognized the need for Warships to carry organic anti-fighter defenses and so had the design equipped with seventy extended range large lasers. The ships 3G maximum acceleration ensured that it could easily reach firing range.
Deployment:
By March of 2787, the Star League was no more, the SLDF had left the Inner Sphere, and war was brewing. The DCA fielded four Tone class cruisers: the Tone herself, Chikuma, Ashigara, and Ibuki. The Ibuki, the newest ship, had been assigned along with an understrength destroyer flotilla to protect the DeHuego & Freshet Dropship yards at Proserpina from Davion attack. On March 29th, that attack arrived in the form of the Iron Duke-class battleships Duke of Marlborough, and Benbow supported by four cruisers and five destroyers. Though Ibuki put up a gallant fight and succeeded in damaging the Marlborough and destroying one the cruisers, she was destroyed and the shipyards were crippled.
Revenge would not be long in coming, for her sister Chikuma, along with the Nami class destroyer Onami, picked up the trail of the damaged Marlborough. Chikuma and her destroyer escort caught up to the battleship (along with the Rodney class cruiser Cunningham and the Furious class carrier Courageous) in the Emporia system on May 15th. The fierce engagement that followed nearly destroyed all ships involved except for the Chikuma. The ship and its crew together with survivors from the Onami managed to limp back to Combine space reporting glorious victory for the Dragon. Eventually making its way back to the Togura shipyards where she was constructed the Chikuma was painstakingly repaired. Shorthanded Draconis engineers had to cannibalize a fifth unnamed Tone under construction in order to completely restore the Chikuma.
This was not before the remaining two Tones would see their great hurrah in 2790 at the great bloodbath known as the battle of Cholame. Admiral Nishimura himself commanded the task group containing the two carriers during this battle. Leading from Tone, he took her and Ashigara on a screaming max thrust firing run through the AFFS’ battleship line. Both ships opened fire with their main batteries as they passed through the Davion fleet, each one raking several ships in turn. Ashigara was blown apart by return fire but Tone briefly fought her way clear. As he watched the FSS Churchill (an Iron Duke class Battleship) pull out of the line, Admiral Nishimura saw a chance for another kill and ordered his ship to close what he thought was a cripple. Unfortunately for him, his assessment was wrong: Churchill had pulled out to make a run for a transient pirate point her nav officer had found. She had taken little damage up to this point and now turned to pour no fewer than five broadsides into the hapless Tone. A direct hit on the bridge by the second salvo killed Nishimura and destroyed the ship’s helm, leaving her helpless against the battleship’s shattering fire. The fifth broadside finished off Tone, with only 15 of her crew surviving her loss. The respite proved long enough for Churchill to exit the system.
With the loss of Tone, the only remaining ship of this class is the Chikuma which continues to be supplied by an unfinished sister ship now marooned in the Togura star system. No further construction of these vessels is possible because of their intricate inner workings. With so many high tech systems the Tone may become just another class of ships lost to the Succession War.
Hiei class Battleship
Tech: InnerSphere
Introduced: 2608
In Class: 42
Manufacturer: Matabushi Incorporated (Luthien /Draconis Combine)
Mass: 1,300,000 tons
Length: 1,200 meters
Sail Diameter: 1,500 meters
Fuel: 4000 tons (10,000)
Tons/Burn Day: 39.52
Safe Thrust: 3
Maximum Thrust: 5
Sail Integrity: 6
KF Drive Integrity: 26
Heat Sinks: 8,710
Structural Integrity: 80
Armor: (1500 tons, Ferro-Carbide)
Fore: 208
Fore-Sides: 208
Aft-Sides: 208
Aft: 208
Cargo:
Bay 1: Small Craft (12) 2 doors
Bay 2: Cargo (160,406 tons) 5 doors
Bay 3: Fighters (36) 6 doors
Dropship Capacity: 6
Grav Decks: 2 (90-meter diameter)
Escape Pods: 40
Lifeboats: 30
Crew: 379 minimum (65 Officers, 314 Enlisted)
Weapons: (Heat: 8,710)
Nose (Heat: 480)
4 Naval Autocannon 35s
Fore Left/Fore Right (Heat: 1520)
6 Naval Autocannon 35s
2 Killer Whale Missile Launchers
Left/ Right Broadsides (Heat: 2930)
4 Naval Autocannon 35s
7 Medium Naval PPCs
2 Killer Whale Missile Launcher
Aft Left/Aft Right (Heat: 3780)
14 Medium Naval PPCs
Ammunition:
2400 rounds of Naval Autocannon/35 ammunition
80 Killer Whale Missiles
Overview:
The end of the twenty sixth century was supposed to be the dawn of a new golden age. The Star League stood dominant, the last resistors to its authority defeated. Peace reigned and what would be later known as the good years began. However, in a dramatic counterpoint, one of the first major events of the twenty seventh Century was a new arms race to achieve superiority in battleships.
Historians still debate who started this battleship race. Some place the blame squarely on the Hegemony who introduced new technology to the navies of the InnerSphere during the Reunification War. Terran Admirals also failed to realize the consequences of clinging to the outdated Monsoon class which encouraged proliferation among the Great Houses. The success of Marik’s Atreus class against the Monsoon eventually led the Lyrans to build their monstrously huge Thor class battleships. Davion on the other hand went with a quantity over quality approach, building more of their venerable Iron Duke class Battleships to outnumber any would be competitor.
However, it was House Kurita that has caught the majority of the blame by building their new Hiei class Battleship after the end of the Reunification War. While this act was a clear escalation, especially during peace time, the other Houses all were clearly participating. This formidable warship forced even the cash strapped House Liao to commission their own design, the Sun Tzu in 2616, and shook the SLDF to restore its dominance by fielding the Texas in 2618.
Capabilities:
For its day, the Hiei was one of the largest ships in existence, massing 1.3 million tons. She was from the beginning built to outmatch the Hegemony's vaunted Monsoon class battleship as well as the Davion Iron Duke, and she succeeded admirably in both regards. Both ships were simply outclassed in firepower by the Hiei, and the Iron Duke was further menaced by the Hiei's integral fighter complement, as fighters had always been the bane of the Iron Duke's existence.
The ship's superior armor protection is something of a minor mystery. Though it is known that the Combine was able to acquire the secrets to Ferro Carbide armor through espionage some time in the 27th century, nobody is entirely certain when or how it happened. The battles of the Succession War have proved without a doubt that the Hiei was fitted with this advanced armor. Although nobody can be certain, except for the House Kurita, it is believed that this feature was a refit done sometime after the War of Davion Succession and not part of the ship’s original equipment.
Whatever the case, this advanced armor was an important edge for the Hiei. This gave the ship armor protection comparable to her Davion rival despite the Iron Duke's heavier but less advanced armor, and was a great surprise to the Davion fleet when barrages that should have left a Hiei burning only cratered armor. This is reportedly how the Edward Davion, flagship of the Davion fleet, was lost during the battle of Cholame. Expecting rather light armor protection, the Davion vessel closed in on the Hiei class Tendo and engaged her in a close range slugging match, ultimately falling to the superior firepower and fighter complement of the Tendo.
[Editor's Note: It also helped that the Edward Davion's two escorting Furious class warships were smashed by a trio of Combine battlecruisers. The Davions to this day maintain that the Edward Davion was destroyed not by the Tendo alone, but with the help of those three warships, while the Combine claims that the three battlecruisers stayed out of the fight between the Edward Davion and the Tendo.]
Deployment:
Kurita managed an impressive feat with the Hiei, constructing the ship in large numbers fairly quickly at the Kure Naval Yards. Forty-two vessels existed by 2650; however, given the restrictions placed on house military forces by that time required a rather intricate tap dance by Kurita in order to keep the entire fleet. The battleships were continuously rotated in and out of service, with as much as half of the class officially in mothballs or "decommissioned to serve as museums". The constant rotation of ships (all of these ships were listed as decommissioned and/or mothballed at one point because of this plan) served to confuse the issue so much that some SLDF admirals were freely and openly admitting that they just plain weren't sure how many ships the DCA had active.
[Editor's Note: The correct answer, of course, is all of them. Though the Combine did the bare minimum necessary to look like it was complying with the military restrictions, the fact is that they could, and when the time came, did reactivate all of the ships mothballed and decommissioned by this program with frightening speed. Some naval historians claim that this sort of dirty dealing by the Member States is one of the things that inspired the Mckenna class battleship. Two years after the house military restrictions were put into place, the Terran Hegemony embarked on one of the most incredible naval production programs in history, turning out nearly three hundred of the most powerful warships the Star League had ever seen in a remarkably short time. This was the final act of the battleship race of the 27th century, leaving the SLDF the clear winner and ensuring that they would be able to counter any threat the house fleets posed.]
When the Succession War began, most of these Kurita Battleships were deployed along the Lyran border in order to counter the massively over gunned Lyran fleet. Battles along the Lyran front quickly became brutal ship killing affairs, and though the more mobile Kurita forces were frequently able to gain the advantage, the price was high.
Some of the Hiei class was deployed to the Federated Suns front where they were used as flagships for groups of Igarashii class battlecruisers. These craft proved to be a dangerous team against the Davions. However, like the Lyran front, the fighting was brutal. Much like her Davion rival, the Hiei has become a victim of the Succession War, with only two ships surviving till this day.
* Tone class Carrier.hma (7.19 KB - downloaded 4 times.)
* Hiei class Battleship.hma (7.64 KB - downloaded 4 times.)
-
Takiro Marik Corvettes « Reply #25 on: May 03, 2008, 10:05:34 PM »
Guardian class Corvette
Tech: InnerSphere
Introduced: 2584
In Class: 30
Manufacturer: Various (Free Worlds League)
Mass: 140,000 tons
Length: 266 meters
Sail Diameter: 660 meters
Fuel: 1,000 tons (5,000)
Tons/Burn Day: 19.75
Safe Thrust: 3
Maximum Thrust: 5
Sail Integrity: 3
KF Drive Integrity: 5
Heat Sinks: 800
Structural Integrity: 33
Armor: (90 tons, Improved Ferro-Aluminum)
Fore: 19
Fore-Sides: 18
Aft-Sides: 18
Aft: 17
Cargo:
Bay 1: Fighters (12) 2 doors
Bay 2: Cargo (16,981 tons) 1 door
Bay 3: Marines (3 platoons)
Bay 4: Small Craft (4) 1 door
Dropship Capacity: 0
Grav Decks: 1 (30-meter diameter)
Escape Pods: 20
Lifeboats: 20
Crew: 106 minimum (18 Officers, 88 Enlisted)
Weapons: (Heat: 1,650)
Nose (Heat: 30)
2 Barracuda Missile Launchers
10 Small Lasers
Fore Left/Right (Heat: 624)
2 Medium NPPCs
4 Large Lasers
10 Small Lasers
Left/Right Broadsides (Heat: 624)
2 Medium NPPCs
4 Large Lasers
10 Small Lasers
Aft Left/Aft Right (Heat: 60)
2 Barracuda Missile Launchers
10 Small Lasers
Aft (Heat: 312)
2 Medium NPPCs
4 Large Lasers
10 Small Lasers
Ammunition:
360 Barracuda Missiles
Overview:
The Free Worlds League acquired thirty six Vigilant Corvettes from the Terran Hegemony as part of their agreement to join the Star League. These ships would serve with the League Navy during the Reunification War, where several were lost in combat with the Canopian Navy. In 2582 the FWL Navy began looking for a new escort for is Atreus battleships. While the Atreus was a powerful ship, it was vulnerable to fighter attacks and several were lost to massed fighter attacks by the Canopians. The League Navy began a program in 2581 to build a new light escort, but the ship was not expected to be ready for almost decade. [Editor’s Note: The Free Worlds shipyards were overworked maintaining and repairing the ships of the Free Worlds League and the Star League fleets. As a result there were not enough resources available to develop a completely new ship.] As an interim measure the League began to refit the Vigilants to serve as escorts for the Atreus. The first refitted ship renamed the Guardian was launched in 2584 and all 30 surviving ships had been refit by 2602.
Capabilities:
The refit Vigilant was designed to provide the Atreus with defense against enemy aerospace fighters. In order to reduce the amount of time required for the refit, the design team did not modify the KF Core, engines or structural framework.
The design team started by stripping off all of the weapons carried by the Vigilant. These were replaced with weapons better suited for combat against fighters and dropships. The main guns of the Guardian are ten Medium Naval PPCs. A pair of NPPCs replaced each of the original Luxor Destroyer Naval Autocannons. These weapons proved to be very potent against assault dropships and even small warships.
The remaining weaponry was designed for anti-fighter work. The White Shark missile launchers were replaced with a pair of Barracuda Missile Launchers. The smaller Barracudas, with their advanced targeting systems, were far more effective against fighters then the White Shark. The Guardian also mounts twenty Large Lasers for use against aerospace fighters. To provide defense against the nuclear tipped missiles used by the Periphery States the ship carries eighty small lasers which can be used to target and destroy incoming missiles.
Using the space freed up by removing the need for large ammunition bays, the designers were able to add a second squadron of fighters providing additional fighter defense. The armor protection of the ship was improved by using ninety tons of Ferro Aluminum armor. This provided the ship with marginally better protection then the original model. The biggest problem with the new ship is the heat management system. The design team was unable to increase the heat dissipation capability of the ship. As a result the ship is unable to fire all the NPPCs at the same time, forcing the ship’s Captain to carefully choose his targets.
Deployment:
The Guardian did not enter service until the closing stages of the Reunification War. The ships only saw limited action against the Canopians, but they proved very effective in combat. The ships also saw action during the Free Worlds League Civil War where six were destroyed in combat. During the Succession War the remaining ships served with the League Navy along the Capellan border. The ships have proven effective against the massed Capellan fighter attacks, destroying a large number of fighters. For this reason the ships have come under heavy attack by the Capellan’s Chesterton Destroyers, in an effort to protect the Capellan aerospace fighter forces. Currently nine Guardian class Corvettes remain in service with the Free Worlds League.
Libertad class Corvette
Tech: InnerSphere
Introduced: 2563
In Class: 120
Manufacturer: Various (Free Worlds League)
Mass: 240,000 tons
Length: 347 meters
Sail Diameter: 1,200 meters
Fuel: 3,000 tons (15,000)
Tons/Burn Day: 39.52
Safe Thrust: 4
Maximum Thrust: 6
Sail Integrity: 3
KF Drive Integrity: 6
Heat Sinks: 1700 [Block II], 1400 (2800) [Block III]
Structural Integrity: 50
Block II
Armor: (223 tons, Standard)
Fore: 28
Fore-Sides: 28
Aft-Sides: 28
Aft: 24
Cargo:
Bay 1: Fighters (30) 6 doors
Bay 2: Small Craft (Cool 2 doors
Bay 3: Cargo (16,159 tons) / Marines (1 platoon) 6 doors
Dropship Capacity: 0
Grav Decks: 2 (78-meter diameter)
Escape Pods: 40
Lifeboats: 40
Crew: 121 minimum (21 Officers, 100 Enlisted)
Weapons: (Heat: 2,000)
Nose (Heat: 270)
2 Medium NPPCs
Fore Left/Fore Right (Heat: 740)
2 Medium NPPCs
4 White Shark Missile Launchers
4 PPCs
Left/ Right Broadsides (Heat: 620)
2 Medium NPPCs
4 PPCs
Aft (Heat: 370)
2 Medium NPPCs
4 White Shark Missile Launchers
4 PPCs
Ammunition:
120 White Shark Missiles
Block III
Armor: (227 tons, Improved Ferro-Aluminum)
Fore: 36
Fore-Sides: 36
Aft-Sides: 36
Aft: 32
Cargo:
Bay 1: Small Craft (12) 2 doors
Bay 2: Cargo (14,875 tons) / Marines (1 platoon) 6 doors
Dropship Capacity: 0
Grav Decks: 2 (78-meter diameter)
Escape Pods: 40
Lifeboats: 40
Crew: 121 minimum (21 Officers, 100 Enlisted)
Weapons: (Heat: 2,240)
Nose (Heat: 300)
2 Medium NPPCs
2 White Shark Missile Launchers
Fore Left/Fore Right (Heat: 710)
2 Medium NPPCs
3 White Shark Missile Launchers
4 PPCs
Left/ Right Broadsides (Heat: 890)
2 Medium NPPCs
1 Naval Autocannon 40
4 PPCs
Aft (Heat: 370)
2 Medium NPPCs
4 White Shark Missile Launchers
4 PPCs
Ammunition:
100 rounds of Naval Autocannon/40 ammo
120 White Shark Missiles
Overview:
The peace treaty that ended the Third Andurien War was far from universally popular within the Free Worlds League. Many within the League resented the terms of the armistice, not least of them a number of Anduriens who believed that a seat on Ian Cameron's nascent "Star League Council" was a poor trade for Capellan annexation of their home province. With that in mind, despite the 'outbreak of peace' offered by the Star League and its growing membership, Albert Marik took the precaution of ordering a new round of military modernization, hedging against the chance that Terrence Liao (or any of the Free Worlds League's own myriad secessionist elements) be emboldened by his 'appeasement'.
Further 'outbreaks of peace' in the interim made this move seem increasingly foolish, but increasing Periphery intransigence in the face of the Star League's rise meant that few protests were raised about the modernization.
Part of this modernization policy was a contract for a new design of patrol corvette, intended to police the new borders and remind the Capellans, the Periphery, and the various dissidents that military dominance in the Third Andurien War had firmly rested with the League - and had not wavered in the interim. Events subsequent to the Pollux Proclamation would prove this to be a wise policy, albeit in retrospect.
Capabilities:
Dubbed the 'Libertad' (Liberty) class, the new vessels were meant for relatively short deterrence patrols - often going less than ten weeks between port-visits. One of the keys to their power was their capacious hangar-allowance for parasite craft such as fighters and shuttles. With ample room set aside for fuel, components, and the other supplies needed to keep these parasites operational, each Libertad could deploy a full wing of starfighters - even maintaining room for spare spaceframes to compensate for sometimes lackluster serviceability rates - and several small craft. A Libertad's parasite complement - and thus its operational role - could easily be tailored to a new mission, giving the type exceptional flexibility, allowing it to shift from front-line strike-carrier to Marine assault-transport to customs-enforcement cutter within a few days. (In practice, the 'optimal' mix for a 'strike wing' was soon established as three starfighter squadrons, six 'spare' spaceframes, four gunboat-shuttles for self-defense, and two general-purpose small-craft for customs/boarding operations or the usual utility work.)
However, this same generous allowance of hangar-space required compromises elsewhere. While the Libertad class were stoutly built and well-armored for their size, their onboard armament fits were less than impressive. However, given that the type was intended for patrol work rather than standing in the line of battle, a mix of dual-mount NPPC turrets and banks of White Shark missiles were considered more than adequate against the JumpShips, DropShips and fighters they were expected to deal with most frequently. [Editor’s Note: Details of the Block I which was retired by the mid-twenty seventh century have been omitted from this report as they didn’t survive to see the outbreak of the Succession War.]
The 'Block II' rolling-refits were intended to redress some of the shortcomings of the original Libertads, as revealed by combat experience. A number of the vessels lost during the Reunification War had been caught 'flat-footed' by Canopian strikefighters, with their own parasites elsewhere, and their lack of onboard point-defense weaponry had proven an acute weakness. Moreover, the long deployment-times of the Canopian campaign (long in excess of FWLN guidelines for the class) had seen a disproportionate number of Libertad crewmen succumb to low-gravity complaints, some of them permanently debilitating, and their lack of grav-decks could no longer be tolerated. A revision of the authorized strike-groups saw the hangar reallocated into two dedicated sections, one housing a reinforced fighter-wing and the other devoted to several shuttles; the latter were usually split evenly between gunboats and utility shuttles, since the former had proved a disappointment in wartime situations and the latter were far more useful for the 'workhorse' duties which were the Libertads' peacetime role.
A second SLEP upgrade was instituted at the personal direction of Kenyon Marik shortly after the Amaris Coup, as the specter of widespread warfare once again loomed on the horizon. SAFE operations within the Hegemony shortly before the Coup and turmoil within its borders thereafter brought the League's shipyards a windfall of formerly restricted technologies, a crucial redress of an imbalance which had existed for most of a century. This refit was aimed squarely at countering the danger of the Lyran Commonwealth's Mako class Corvettes - a class whose combination of speed and advanced point-defense weapons gave them the ability to bypass (or destroy) a Block II's fighters and force a close action, where the Lyran vessel held the advantage in raw firepower. Suppressing most of the parasite complement, the Libertad Block III used that room for advanced armor-protection, an overhauled power-management grid and a single (albeit devastating) massive naval autocannon mount in each broadside, offsetting many of the Lyran vessel's advantages. Half of the class was converted to the new standard in the time between the Coup and the start of the Succession War; operational doctrine was that a corvette division (soon known as a 'patrol pair') would always consist of a Block II 'baby carrier' partnered with a Block III 'bodyguard'.
Deployment:
The Libertads saw heavy action sooner than anticipated, for they would play a significant role in Marion Marik's offensive into the Magistracy of Canopus during the Reunification War. Indeed, the fighter-wings and missile-banks of Libertad corvettes did much to break the screen of the Canopian fleet at Thurrock, clearing a path for the League's heavier combatants.
Despite the type's proven utility - both in its design role and elsewhere - and its remarkable ease of construction, procurement of the Libertad class was stopped in 2603. Only one hundred and twenty hulls had been commissioned, and thirteen of those were replacements for vessels lost against the Canopians or in various skirmishes. Navy requests for renewed purchases were rejected in light of the League's rising economic woes, and even when Parliament finally acknowledged the need for a modernization of the Libertad fleet, the introduction of the Star League dollar and the resultant 'cash crunch' meant that this took the form of an overhaul and life-extension program rather than new construction. (The fact that several Navy and independent studies declared that new construction would actually have been significantly cheaper was carefully ignored by the politicians, who 'knew' that renovating old ships was cheaper than making new ones.)
After the Reunification War, the Libertads went on to undergo a System Life Extension Program (SLEP) which enhanced their self-defense and long-deployment capabilities and continued to serve in the usual 'workhorse' tasks of corvettes, mostly as patrol and border-enforcement work. Several were lost to border skirmishes, but it was the Civil War which saw the worst of the losses; by the nature of their work, Libertads were of only marginal use to either faction in the battle-line, but several would participate in deep-strike commando raids by both Loyalist and rebel forces, and when major fleet actions were fought their role as screening elements meant losses of Libertads were all but inevitable. Over the years, various accidents and skirmishes (not to mention the Civil War) whittled down the numbers of the Libertad class, and only eighty remained in FWLM colors by the outbreak of the Succession War.
One of the most notable vessels in this class was the FWLS Matador commanded at the start of the conflict by Captain Carlos Comacho. A native of Cerillos in the 'Southwestern Worlds', Comacho lead his Libertad Block III warship during the 2787 offensive against Bolson and its shipyards. Having twice seen his vessel put in a repair-slip by Lyran Makos, he took a particular satisfaction in the crippling of the yards which had produced those vessels.
Later in that action, a Lyran battlegroup centered on the Tharkad-class battlecruiser LCS Intransigent jumped into the system and attempted to intercept the League main body as it withdrew. Matador was part of the only screening squadron (centered on the destroyer Majestic) which was in a position to intercept the Lyran 'heavies' short of the main fleet of vulnerable assault-transports, and like the rest of Task Force Majestic Captain Comacho did not hesitate to obey Commodore Keegan's order to attack at once. Choosing Intransigent as his target, Comacho boldly closed to the effective range of his own heavy weapons and proceeded to trade broadsides with the battlecruiser for more than an hour, buying crucial time for the main body to withdraw. Despite suffering several brutal direct hits from the Lyrans' main batteries, and witnessing the loss of all her companion vessels (including Majestic), Matador continued to fight and landed a number of telling blows on the Lyran ship before being destroyed with all hands by a full broadside of Intransigent's remaining NPPC mounts. Unable to pursue the Marik forces owing to engine damage sustained during the action, Intransigent instead recovered the few League survivors and withdrew for repairs.
Today of only a dozen Libertads organized into six 'patrol pairs' remain in service with the Free Worlds League.
* Guardian class Corvette.hma (5.35 KB - downloaded 4 times.)
* Libertad II class Corvette.hma (11.08 KB - downloaded 4 times.)
* Libertad III class Corvette.hma (11.03 KB - downloaded 4 times.)
-
Takiro Marik Supplemental Destroyers « Reply #26 on: May 03, 2008, 11:02:58 PM »
Fulbaum class Destroyer
Tech: InnerSphere
Introduced: 2530
In Class: 72
Manufacturer: United Shipwrights (Angell II /Free Worlds League)
Mass: 470,000 tons
Length: 534 meters
Sail Diameter: 1,024 meters
Fuel: 1,000 tons (2,500)
Tons/Burn Day: 39.52
Safe Thrust: 4
Maximum Thrust: 6
Sail Integrity: 4
KF Drive Integrity: 11
Heat Sinks: 729
Structural Integrity: 60
Armor: (564 tons, Standard)
Fore: 45
Fore-Sides: 44
Aft-Sides: 44
Aft: 41
Cargo:
Bay 1: Small Craft (4) 2 doors
Bay 2: Cargo (55,338 tons) 1 door
Bay 3: Fighters (6) 3 doors
Dropship Capacity: 0
Grav Decks: 1 (60-meter diameter)
Escape Pods: 0
Lifeboats: 20
Crew: 169 minimum (29 Officers, 140 Enlisted)
Weapons: (Heat: 828)
Nose (Heat: 183)
6 Naval Autocannon 10s
3 Autocannon 5s
Fore Left/Fore Right (Heat: 366)
6 Naval Autocannon 10s
3 Autocannon 5s
Aft Left/Aft Right (Heat: 186)
3 Naval Autocannon 10s
3 Autocannon 5s
Aft (Heat: 93)
3 Naval Autocannon 10s
3 Autocannon 5s
Ammunition:
2700 rounds of Naval Autocannon/10 ammunition
2400 rounds of Autocannon/5 ammo
Overview:
Unlike the majority of the Free Worlds Navy's larger capital ships, provincial politics played a heavy hand in destroyer design and deployment. Though in theory under the authority of a unified fleet command, in many respects the League's destroyer fleets served essentially as provincial navies: built, staffed, and operated according to the needs or political will of their home province. Among other things, this meant that the Free Worlds League operated a veritable swarm of sometimes radically different destroyer classes, ranging from heavily armed but notoriously short ranged Regulan vessels to the tiny "destroyer-escorts" of Gibson to the sophisticated heavyweight destroyers (sometimes classified as light frigates) operated by Oriente. [Editor’s Note: These various warships were replaced by the ubiquitous Themistocles during the Star League era reducing cost and easing maintenance throughout the fleet. However even after this consolidation House Marik still maintained the greatest number of destroyer classes under its flag right up until the Succession War began. Some debate whether this policy was a holdover of provincial politics or the consequence of the League’s growing carrier philosophy which required several different escorts.] The Fulbaum was one of these classes, designed and operated by the Marik Commonwealth in the years before the founding of the Star League. Though not the most numerous destroyer class in service, given the Commonwealth's ties to the Captain-General, it was one of the most widely deployed during its term of service, one of the few classes to see service throughout the Free Worlds League.
Capabilities:
The Fulbaum was a fairly typical destroyer for her day, though, like much of the Free Worlds League destroyer fleet, she was a fairly small vessel, massing less than half a megaton. Twenty seven light naval autocannons provide the offensive firepower, while twenty four conventional autocannons and a squadron of aerofighters handle anti-fighter defense. Though this entirely ammunition based armament on the surface limited the ship's endurance, the Fulbaum's not inconsiderable cargo capacity allowed the ship to carry all the extra ammunition it might need for extended operations.
Deployment:
Unlike many of the Free Worlds League's destroyer classes, the Fulbaum was fairly evenly deployed throughout the League, primarily operating as a picket ship for the League battlefleet. Seventy two of this reliable, if ordinary warships, would serve the Free Worlds Navy right up to the Succession War despite the introduction in the updated Vester class Destroyer in the 28th century which was originally intended to replace them.
One of the most notable vessels of this class is the FWLS O'Reilly which was launched in 2537. Despite constant minor mechanical problems, including a defective grav deck, this warship served with distinction during the Reunification War against the ships of the Canopian navy. Roughly a hundred years later, she participated in the battle at Hellos Minor, aiding in the destruction of the renegade Battlecruiser Stewart and the capture of the Amity. Early in the 28th Century she would once again be called upon to face her bretheren in the first Marik Civil War, earning battle honors at Atreus and Ariel.
The O'Reilly is best perhaps best remembered for her last stand during the opening phases of the Succession War. Cut off from the rest of her fleet, the O'Reilly was forced into a hit and run battle against three Capellan destroyers. Though she was outclassed in every conceivable way, the plucky little destroyer still managed to hold out, and even delay the Liao warships for several hours. Though the O'Reilly was eventually destroyed, the Capellans paid a high price for their victory, including the loss of a Chesterton class Destroyer to an asteroid collision and severe damage to a second ship caught unaware by the O'Reilly.
Fifty of these Destroyers began the Succession War in the Marik fleet along with the FWLS O'Reilly. Today only eight of these vessels survive.
Vester class Destroyer
Tech: InnerSphere
Introduced: 2755
In Class: 65
Manufacturer: Various (Free Worlds League)
Mass: 470,000 tons
Length: 534 meters
Sail Diameter: 950 meters
Fuel: 2,000 tons (5,000)
Tons/Burn Day: 39.52
Safe Thrust: 4
Maximum Thrust: 6
Sail Integrity: 4
KF Drive Integrity: 11
Heat Sinks: 1629
Structural Integrity: 60
Armor: (564 tons, Standard)
Fore: 45
Fore-Sides: 44
Aft-Sides: 44
Aft: 41
Cargo:
Bay 1: Small Craft (4) 2 doors
Bay 2: Cargo (52,475 tons) 1 door
Bay 3: Fighters (6) 3 doors
Dropship Capacity: 0
Grav Decks: 2 (150-meter diameter)
Escape Pods: 30
Lifeboats: 30
Crew: 160 minimum (27 Officers, 133 Enlisted)
Weapons: (Heat: 1,620)
Nose (Heat: 355)
4 Naval Autocannon 25s
3 LRM 15s
Fore Left/Fore Right (Heat: 710)
4 Naval Autocannon 25s
3 LRM 15s
Aft Left/Aft Right (Heat: 370)
2 Naval Autocannon 25s
3 LRM 15s
Aft (Heat: 185)
2 Naval Autocannon 25s
3 LRM 15s
Ammunition:
1800 rounds of Naval Autocannon/25 ammunition
1440 rounds of Long Range Missile
Overview:
Design work on the Marik Commonwealth's Vester class destroyer began in 2750 as a replacement for the Fulbaum. In basic principle an upgrade of the older destroyer, development was nonetheless delayed repeatedly by a combination of technological and political considerations. In the end, the new destroyer wasn't ready for construction until 2755, just in time for the repeal of the Edict of 2650 and the massive military buildups this entailed.
Capabilities:
With a similar hull design and speed capabilities to the Fulbaum, visually at least, the Vester does not seem to offer much more than her older sister. Nevertheless, though carrying fewer naval cannons than the Fulbaum, the Vester's heavier guns give it a substantially greater bite, though veteran gun crews generally complained that the class 25 cannons were too unreliable and maintenance intensive. The anti-fighter defenses were switched from conventional autocannons to long range missile racks. This gave the ship more firepower against aerofighters, but reduced its total ammo load.
Unlike many warships, special emphasis was placed on crew comfort and safety on the Vester. The loss of the Fulbaum class FWLS Dhue and her entire crew complement to an accident in 2753 led to a lobby in the Marik Commonwealth for increased crew safety, eventually leading to changes in the design of the Vester. In addition to reducing the crew complement by a full third, designers greatly expanded the ship's complement of lifeboats and escape pods, making the Vester one of the few ships whose escape systems can completely accommodate her crew.
Deployment:
Though it was eventually decided to retain the Fulbaum in service, new Vester class destroyers were nevertheless built for the Free Worlds League Navy in the years leading up to the fall of the Star League. As with the Fulbaum, Vester class destroyers saw service throughout the League. Their performance during the Succession War along with the rest of Mark’s diverse destroyer force has been excellent. However, this intense conflict has taken a large toll on the class as a whole leaving only ten vessels in active service.
Stewart class Destroyer
Tech: InnerSphere
Introduced: 2469
In Class: 10
Manufacturer: United Shipwrights (Angel II / Free Worlds League)
Mass: 520,000 tons
Length: 530 meters
Sail Diameter: 1,031 meters
Fuel: 3,500 tons (8,750)
Tons/Burn Day: 39.52
Safe Thrust: 4
Maximum Thrust: 6
Sail Integrity: 4
KF Drive Integrity: 11
Heat Sinks: 1,594
Structural Integrity: 82
Armor: (389 tons, Standard)
Fore: 36
Fore-Sides: 34
Aft-Sides: 34
Aft: 32
Cargo:
Bay 1: Fighters (6) 6 doors
Bay 2: Small Craft (2) 2 doors
Bay 3: Cargo (73,836 tons) 4 doors
Dropship Capacity: 1
Grav Decks: 1 (80-meter diameter)
Escape Pods: 12
Lifeboats: 8
Crew: 174 minimum (29 Officers, 145 Enlisted)
Weapons: (Heat: 1,593)
Nose (Heat: 405)
3 Medium NPPCs
Fore Left/Fore Right (Heat: 364)
1 Naval Autocannon 10 (100 rounds)
2 Naval Laser 45s
2 LRM 20s (36 rounds)
Left/ Right Broadsides (Heat: 460)
2 Naval Autocannon 10s (200 rounds)
2 Naval Laser 55s
Aft Left/Aft Right (Heat: 224)
1 Naval Autocannon 10 (100 rounds)
1 Naval Laser 45s
2 LRM 20s (36 rounds)
Aft (Heat: 140)
2 Naval Laser 45s
Ammunition:
800 rounds of Naval Autocannon 10 ammunition
144 rounds of LRM 20 ammunition
Overview:
After being crushed to death beneath the foot of a Lyran 'Mech on the world of Loric in 2459, Captain-General Gerald Marik was replaced by his daughter, Simone Marik. Only nineteen when she took office in 2462, Simone Marik - at that time the youngest Captain-General ever appointed by Parliament - was unlike her vainglorious father and his predecessors had no desire to be covered in glory. Though a competent military commander, Simone is best known for her economic foresight (akin to that of her great-grandfather) and her dedication to strengthening the entire Free Worlds League though technology and education rather than concentrating on the military.
Though her forthright manner and lack of charisma did not usually sit well with a League Parliament itching for a renewed war with the Lyrans, for a short period of time her goals were undeniable; especially when those goals were aimed at the betterment of not just the entire League but also the Free Worlds Military. Using her economic renovations as the backdrop to her naval revival, Captain-General Marik's efforts, though short lived, would produce the long serving Stewart class Destroyer.
Capabilities:
The Stewart class Destroyer, named in homage to one or the founding war-like states of the Free Worlds League, highlighted a number of new League advancements as an heir to Simone Marik's economic revival program. Benefiting from advancements in metallurgy and armament development, the new Destroyer Class was to herald a new age in League warship manufacture. In many ways this was the first Free Worlds League Destroyer to be built as prior craft of this type had traditionally been made and staffed by the Provinces rather than the nation as a whole.
Weighing 520,000 tons, and with a length of 530 meters, the Stewart class faired favorably with other contemporary Terran Destroyer Classes like the Block I Lola. In 2468 when the League began their design work on the new Destroyer class that would eventually become the Stewart; careful attention was given to the latest design philosophies of the Terran Hegemony, and by default, the Lyran Commonwealth. Considering the importance of the project, Captain-General Simone Marik made it one of SAFE's highest priorities to accurately catalogue and decipher all of the HAF's existing warships, while to also engage in clandestine espionage for information on future designs. It was a risky operation that if compromised could possibly incite armed hostilities between the Hegemony and the League. For the next two years, SAFE operatives infiltrated the HAF navy with the express purpose of transmitting design and technical information. When the operation concluded in 2470, the operation had garnered enough data to be considered a success.
Unlike the slower Destroyers of the era, the new Stewart featured four state-of-the-art Atrean Mk III Pushers as its Interplanetary Fusion engine. These reliable interplanetary drives could sustain a 2G cruising speed for extended periods of time and a quick 3Gs of acceleration for maneuvers during combat. 3,500 tons of fuel fed the Atrean Pusher drives, which provided the destroyer with the ability to operate in the field for over three months before refueling. The Stewart also featured a heavily reinforced internal structure. Learning from earlier warships, the bulkheads of the Stewart were strengthened considerably, allowing the craft to support 389 tons of resilient crystal-embedded armor in stark contrast to most destroyers of the same weight class, which often featured an armor sleeve of half the weight.
For the Stewart's offensive suite, the best capital weapons the Free Worlds League could provide were utilized on the Destroyer. Centerpiece to this impressive armament was a trio of medium NPPC mounted in a nose turret which was capable of vaporizing smaller vessels with a single salvo. This warship also mounted a collection of NAC/10s that were mounted prominently along the warship's sides in turret mounts, giving the weapons maximum fields of fire. Pairs of NL/45s and NL/55s were mounted all along the ship as support to the larger main guns. The Stewart was also armed with four batteries of LRM 20s to provide the Destroyer with some protection against swift aerospace fighters and small craft. Although the LRM additions were minimal, they attempted to correct a critical oversight found in warships of the era, though almost without exception, the Stewart followed accepted standard naval doctrine of the time.
Beneath the destroyer's thick exterior hid the cutting edge of League naval ideology of the 2460s, namely advanced targeting and tracking gear, the inclusion of a six fighter squadron, and two platoons of ship marines for boarding actions. Avoiding the pitfall of other vessels the Stewart's crew were given the benefit of spacious crew quarters and access to other amenities, including a single 80-meter Grav Deck. Also unlike older vessels of equal tonnage, the Stewart featured an expensive Docking Collar. The inclusion of the docking collar allowed the ship to support a single Dropship while on extended patrol duty. The final notable feature of the destroyer was its single 73,836 ton cargo bay. This mammoth bay, large even by modern standards provided an unexpected boon to the Stewart, which could enjoy enough supplies to remain in the field for an extended period, or be used to supplement a League patrol group.
Deployment:
When Simone Marik stepped down as Captain-General in 2475 after a number of negotiations failed between the Capellan Confederation and the League over a mutual alliance to attack the Terran Hegemony, she was replaced by her brother, Carlos Marik, as the thirteenth Captain-General. As Simone stepped down, she left behind a Free Worlds League stronger than it had been in more than fifty years. A total of ten Stewart class Destroyers were built for the Free Worlds Navy and quickly spread throughout the fleet as patrol vessels.
However, during her revival of the League, focus had shifted from the Lyran Commonwealth to the Terran Hegemony, as the main enemy of the state, prompting increased paranoia directed towards the Terran-state. When the thirteenth Captain-General ascended the throne in 2475, he wasted no time stewing over the defunct dual alliance between the Confederation and the League and how if failed to come to fruition. Instead, the newly appointed ruler of the Free Worlds League, Carlos Marik gathered a large portion, including three-fourths of all active Stewarts, of the Free Worlds Navy to Oriente. Carlos planned to strike the Terrans quickly and lethally, using his Warships and stockpiles of atomic weapons to smash the Terran military before the Hegemony could unleash it on the Marik domain.
Ironically, Carlos' plans triggered the very military action he feared when a spy passed details of the operation to Hegemony leaders. Hegemony forces launched a lightening raid against Oriente to destroy the Free Worlds League fleet while it lay at anchor. With over half of their respective crew on-planet for R&R, the outcome of the battle was never in doubt, with the Hegemony handily defeating the unprepared League forces. However, given the circumstances, some of the Free Worlds League ships presented themselves admirably. One such vessel, the Stewart class FWLS Fire of Constance, despite sustaining damage, managed to limp away from the battle. Spending only enough time recover casualties, the Fire of Constance boldly charged back into the heart of the battle where she was able to destroy a Terran Cruiser by ramming the wounded vessel and detonating her own fusion core.
Only three ships of the Stewart class survived the battle and damage sustained to the Marik fleet during the attacked precluded any additional vessels being built for years to follow. During this time the League returned to its Provincial Destroyer force and found further production of the Stewart pointless. The normalization of relations between the Free Worlds League and the Terran Hegemony in 2478 and the military detente that followed until the formation of the Star League a century later, ended any hope for renewed production of this warship.
The remaining vessels of this class, the FWLS Icarus, the FWLS Ajax and the FWLS Merak's Honor served admirably with the League military for almost two centuries. Despite their age these vessels were widely regarded as House Marik’s finest Destroyers. In 2745 the Icarus was lost to a catastrophic misjump over the world of Helm. (Editor’s Note: While that is the official story but many continue to claim that the Icarus was a causality of the Hidden War with the Marik’s “alliesâ€) That left only two Stewart class Destroyers to start the Succession War and one was among the first causalities in this brutal war.
The FWLS Merak's Honor, named after a militaristic proto-nation, single handedly defended the world of Bolan from a Lyran strike force. Faced with the overwhelming odds and firepower of a Lyran naval assault group, the Merak's Honor faced her foes full on, charging directly into the teeth of the attackers. Using a combination of superior speed and the strength of three NPPCs, the Merak was able to cripple one Mako Corvette, and to seriously damage another before being destroyed. Only the FWLS Ajax, the last ship in a proud line, continues to endure to this day.
Alexander class Destroyer
Tech: InnerSphere
Introduced: 2700
In Class: 60
Manufacturer: Various (Free Worlds League)
Mass: 600,000 tons
Length: 638 meters
Sail Diameter: 900 meters
Fuel: 4,000 tons (10,000)
Tons/Burn Day: 39.52
Safe Thrust: 4
Maximum Thrust: 6
Sail Integrity: 4
KF Drive Integrity: 13
Heat Sinks: 3600 (7200)
Structural Integrity: 80
Armor: (939 tons, Standard Armor)
Fore: 72
Fore-Sides: 71
Aft-Sides: 70
Aft: 70
Cargo:
Bay 1: Small Craft (Cool 4 doors
Bay 2: Fighters (24) 4 doors
Bay 3: Cargo (5,066 tons) 5 doors
Dropship Capacity: 0
Grav Decks: 3 (100-meter diameter)
Escape Pods: 0
Lifeboats: 30
Crew: 225 minimum (39 Officers, 184 Enlisted)
Weapons: (Heat: 7,184)
Nose (Heat: 3,600)
16 Heavy NPPCs
Fore Left/Fore Right (Heat: 892)
3 Naval Autocannon 10s
4 Naval Laser 55s
8 Ultra Autocannon 5s
Aft Left/Aft Right (Heat: 892)
3 Naval Autocannon 10s
4 Naval Laser 55s
8 Ultra Autocannon 5s
Aft (Heat: 1,800)
8 Heavy NPPCs
Ammunition:
1200 rounds of Autocannon 10 ammunition
6400 rounds of Ultra Autocannon/5 ammo
Overview:
The Alexander has been described as the space going Charger class BattleMech. A ship built to so specifically emphasize a single specific role that its design is actually compromised in practically every other way. The design originated in the Free Worlds League as part of the ICB (Integrated Carrier Battlegroup) doctrine. This doctrine was based on a combined force of carriers and fast destroyers and frigates. In theory the carriers could operate as the main punch while the fast ships acted as a maneuver element, both screening the otherwise vulnerable carriers and acting as a mobile hammer to deliver a fast, cavalry style charge where needed. In theory it looked like a good strategy and it has worked well during the Succession War. However, when the success of that strategy is talked about, very rarely does the Alexander come up.
Capabilities:
Actually, at first glance the Alexander doesn't look all that bad. In fact, it looks down right intimidating with its massive battery of naval PPCs and its fairly high thrust capability. The only problem is that that's only at first glance.
The Alexander was built to carry as much firepower as possible with as big a propulsion system as possible. All other concerns were secondary, and it shows. The most immediate flaw is that the ship is an almost pure bow-fighter. Its heaviest batteries are mounted in four forward turrets with a very narrow arc of fire. Though this gives the advantage of being able to project the maximum volume of fire in one direction, it also leaves the ship highly vulnerable to attacks from the side, with only a light battery of naval autocannons and lasers providing cover. This made a direct "cavalry charge" at the enemy almost essential if these warships were to expect any success. Against a full battle line of warships, this could be down right suicidal, while one on one an Alexander would have trouble keeping a bead on his opponent.
Most crews weren't all that reassured by the aft armament either, which happened to be the ship's second most heavily armed arc. All this really meant to most was the ship had something to cover its retreat.
Anti-fighter defenses were fairly sparse. Thirty two rapid fire autocannons, copied from the Lyran developed Ultra autocannon first deployed on the Sentinel BattleMech, provide a barely adequate defense system, and in fact it was usually the ship's integral complement of four aerofighter squadrons that were usually key to the ship's anti-fighter defenses.
The biggest flaw in the design, however, was its lack of cargo capacity. With barely more than five thousand tons of cargo space, the Alexander was utterly incapable of operating on its own for more than a week. This meant the ship had a very narrow role in the Free Worlds Navy. They either operated as part of a fleet, or they served exclusively as system defense craft.
Deployment:
Okay, all complaints aside, the Alexander wasn't a bad ship for its intended role as the maneuver element of an ICB, and though she would be overshadowed by the slightly older Dido class frigates that she fought beside, she nevertheless performed admirably for her first few years. Then the Free Worlds League Civil War began in 2729. When the Civil War began, many of the Alexanders in service pledged loyalty to Parliament, where they became casualties of war. With the entire fleet thrown into chaos, and with many Alexander class ships caught far from friendly territory without the supplies needed to get to a friendly world, many were seized or destroyed almost immediately. Roughly a full third of the class was lost within the first few months of the war. Even more would be destroyed during the course of the war. During the battles of Atreus and Ariel alone a total of twenty six Alexander class Destroyers were lost. By the time the Treaty of Verona was signed, there were a mere fourteen Alexanders still in service. This handful of warships was divided among the Integrated Carrier Battlegroups (ICB) and saw a great deal of action during the opening year of the Succession War, where ten were lost early on. However, their inferior cargo capacity would do the last few in far more completely than the Steiners or Liaos could. With the collapse of much of the logistical system as a result of the brutal fighting of the war, the League was forced to bring its four surviving Alexanders home, assigning them to the defense of Irian alongside a number of other heavily damaged warships. There they have endured numerous attacks by many of the Great Houses. Today only two Alexanders remain to defend Irian which remains in League hands.
* Fulbaum class Destroyer.hma (5.56 KB - downloaded 4 times.)
* Vester class Destroyer.hma (3.72 KB - downloaded 4 times.)
* Stewart class Destroyer.hma (10.81 KB - downloaded 4 times.)
* Alexander class Destroyer.hma (6.21 KB - downloaded 4 times.)
-
Takiro Marik Heavy Weights « Reply #27 on: May 03, 2008, 11:19:30 PM »
Themistocles class Destroyer/Carrier
Tech: InnerSphere
Introduced: 2653
In Class: 141
Manufacturer: Various (Free Worlds League)
Mass: 500,000 tons
Length: 690 meters
Sail Diameter: 800 meters
Fuel: 14,000 tons (35,000)
Tons/Burn Day: 39.52
Safe Thrust: 3
Maximum Thrust: 5
Sail Integrity: 4
KF Drive Integrity: 11
Heat Sinks: 736
Structural Integrity: 40
Armor: (399 tons, Standard Armor)
Fore: 30
Fore-Sides: 31
Aft-Sides: 31
Aft: 30
Cargo:
Bay 1: Small Craft (20) 2 doors
Bay 2: Fighters (108) 4 doors
Bay 3: Cargo (93,352 tons) 2 doors
Dropship Capacity: 0
Grav Decks: 1 (65-meter diameter)
Escape Pods: 10
Lifeboats: 0
Crew: 169 minimum (28 Officers, 141 Enlisted)
Weapons: (Heat: 736)
Fore Left/Fore Right (Heat: 368)
4 Naval Autocannon 10s
2 Large Lasers
2 PPCs
4 Autocannon 5s
4 LRM 20s
Aft Left/Aft Right (Heat: 368)
4 Naval Autocannon 10s
2 Large Lasers
2 PPCs
4 Autocannon 5s
4 LRM 20s
Ammunition:
800 rounds of Naval Autocannon/10 ammunition
640 rounds of Autocannon/5 ammo (32 tons)
384 rounds of LRM /20 ammo (64 tons)
Overview:
The naval restrictions of 2650 hit the Free Worlds League Navy very hard. The ambitious Frost Program, which was supposed to give the League a massive fleet of battleships, battlecruisers, and a new breed of super carriers, soon proved impossible under the current naval restrictions, and much of the program, including the new supercarrier, had to be abandoned.
However, the Captain-General still valued the fighter carrier concept, and work continued on a dramatically more humble design, which would become the Varyag. However, from the beginning it was realized that the Varyag could never be produced in large enough numbers to fill the needs of the Free Worlds League fleet, at least not under current naval restrictions. With all future Varyags already slated to form independent fleets (which would eventually become the Integrated Carrier Battlegroups) it was decided that a more quickly and easily produced ship was needed to provide fighter support to the main battle fleets. Thus was born the Themistocles.
Capabilities:
A combination of interstellar politics and interservice rivalry would have a radical affect on the final design for the Themistocles. Even though a truly multi-role carrier able to transport numerous fighter craft and engage successfully in direct combat was not only possible but extremely feasible (the concept was used effectively by the Periphery States during the Reunification War), many Admirals in the Free Worlds League fleet considered the idea of such a ship a threat to the traditional role of the battleship. As a consequence, they lobbied successfully for severe restrictions on carrier design, limiting the naval weaponry carried by these vessels and leaving them dependent on escorts to fend off most warship attacks.
While the Themistocles was categorized as a Destroyer by these traditionalist minded elements of the Navy because of its overall mass it was more akin to a Transport. The design, based largely on the civilian built Aristotle class Compact Core Transport in order to reduce cost, carries only a minimal armament of sixteen small naval autocannons in four quad turrets, backed up by a moderately extensive mix of anti-fighter weaponry. This arsenal is barely sufficient to fend off most corvettes, and furthermore does not provide anything even resembling total coverage. The light armor of the ship further provides poor protection against most attackers, and the civilian spec hull is simply incapable of standing up to heavy combat.
[Editor's Note: Though the Free Worlds League might be considered to be the most extensive practitioner of carrier tactics during the Star League years, this tendency to consider the carrier as little more than a transport for fighters would actually cause them to fall dramatically behind in carrier design by the mid twenty eighth century. By that time several powers had multi-role carriers, such as the Hegemony's Riga, the Lyran Commonwealth’s ill considered Banshee, and the Federated Suns' venerable Furious, and it was only a matter of time before other powers jumped on the bandwagon. Though no state employed nearly as many carriers as the Free Worlds League, this deficiency in their carrier force was eventually considered a serious problem, leading to the crash development of the Nemesis class Carrier in 2755.]
The only real bright spot in the design is its massive hangar capacity. Though classified as a Destroyer/Carrier, the Themistocles can carry just as many fighters as the Varyag class Battlecruiser/Carrier. However, the typical Themistocles generally did not carry anything close to a full complement. Furthermore, while a Varyag would usually carry a good mix of the best fighters available, the humble Themistocles often carried a castoff mix of cheap, lightweight aerofighters manned by green pilots, meaning that even at full strength the ship's aerowing was no match for that of a Varyag.
On the other hand, the Themistocles, based as it was on a cargo hauler, had much roomier hangar bays than the Battlecruiser based Varyag. Most flight crews loved the carrier as a result for the superior work space she provided them.
Deployment:
The total number of Themistocles class warships produced by with the Free Worlds League and its various provinces is believed to be one hundred and forty one. Admittedly this is only an estimate based on confirmed information. Some experts believe other ships of this class remain unaccounted for. Unfortunately it is hard to tell because exactly Because of the very nature of this ship's design. Based as it was on a civilian ship, the vessel was extremely inexpensive for its potential punch, meaning that even the minor provinces could field a number of carriers. Even more importantly, though, there was precious little at first glance to distinguish the Themistocles from a standard Aristotle class CCT. The only thing that gives the ship away is its naval autocannon turrets. Some provinces, trying to keep the strength of their private forces a secret, were known to strip the naval guns off of their carriers and claim them to be standard cargo haulers. Though bye and large willing to play along with naval restrictions imposed by the Star League, most Captain-Generals turned a blind eye to this practice, giving the League extra fighter carriers to call upon in emergencies.
Roughly half of the "official" Themistocles class was assigned to support the main battle fleet, providing additional fighter support to the Battleships and Battlecruisers that made up the fleet. A number were assigned as training carriers, while the remainder was assigned patrol and escort duty throughout the League, where their large fighter complement made them a true terror for practically any pirate band. Though numerous Themistocles class vessels were lost during the infighting that plagued the League, the relatively cheap cost of the ships made them extremely easy to replace, and their numbers diminished only slowly.
As with many things this situation has changed dramatically during the Succession War. At the start of this horrific conflict the Free Worlds League Navy fielded one hundred of these able vessels. The disasters of this new war have torn the heart out of the Free Worlds League's military and industry. Some of the hardest hit forces in the Free Worlds League fleet were the Integrated Carrier Battlegroups. Though they scored numerous impressive victories against House Steiner during the war, they likewise suffered extensive losses. With their frontline carrier forces depleted, the League made the decision to reinforce the surviving ICBs with Themistocles class ships, which were never designed for the direct confrontations an ICB faced. This has allowed the League to keep its carrier operations afloat for a while longer, the loss of so many of the fleet's best fighter units, and the general inferiority of the Themistocles to the Varyag and Nemesis class Carriers that it was replacing, meant that the golden years of the ICB were finished. Today only a dozen of these craft remain operational with the Marik Navy.
Dido class Frigate
Tech: InnerSphere
Introduced: 2689
In Class: 112
Manufacturer: Various (Free Worlds League)
Mass: 760,000 tons
Length: 702 meters
Sail Diameter: 950 meters
Fuel: 5,000 tons (12,500)
Tons/Burn Day: 39.52
Safe Thrust: 4
Maximum Thrust: 6
Sail Integrity: 4
KF Drive Integrity: 16
Heat Sinks: 4400
Structural Integrity: 50
Armor: (747 tons, Ferro Carbide)
Fore: 128
Fore-Sides: 115
Aft-Sides: 90
Aft: 90
Cargo:
Bay 1: Small Craft (6) 2 doors
Bay 2: Fighters (18) 3 doors
Bay 3: Cargo (70,430 tons) 5 doors
Dropship Capacity: 4
Grav Decks: 2 (90-meter diameter)
Escape Pods: 10
Lifeboats: 20
Crew: 252 minimum (43 Officers, 209 Enlisted)
Weapons: (Heat: 4,320)
Nose (Heat: 930)
4 Naval Autocannon 30s
2 Heavy Naval PPCs
4 Barracuda Missile Launchers
5 Large Lasers
Fore Left/Fore Right (Heat: 960)
4 Naval Autocannon 30s
4 Barracuda Missile Launchers
5 Large Lasers
Left/ Right Broadsides (Heat: 960)
4 Naval Autocannon 30s
4 Barracuda Missile Launchers
5 Large Lasers
Aft Left/Aft Right (Heat: 980)
2 Heavy Naval PPCs
5 Large Lasers
Aft (Heat: 490)
4 Heavy Naval PPCs
5 Large Lasers
Ammunition:
2000 rounds of Naval Autocannon/30 ammunition
200 Barracuda Missiles
Overview:
The Dido was conceived as a replacement for the older Stewart and Oriente class warships that had been in service since the early 25th century. Though most of the Oriente class was less than a hundred years old at the time of the Dido's development and was still a match for its most likely opponents, like the Lyran Commonwealth's Valkyrie class destroyer and Victory class frigate, Captain General Gerald Marik wanted a larger, more heavily armed ship that in addition to handling general patrol duty could also act as a fast screening vessel to the Varyag class carrier. Drawing some inspiration from the Star League's Kimagure class pursuit cruiser, designers unveiled the Dido.
Capabilities:
The Dido is an agile frigate, capable of three Gs of acceleration at maximum thrust. Though on its face this is only a marginal improvement over the Oriente, in practice it provides a significant advantage, giving the ship a significantly tighter turning radius at high velocity.
The influence of the Kimagure is clearly visible in the ship's weapons as the Dido's armament is largely oriented towards the front. The aft quarter is under gunned, providing a rather narrow but still present gap where the ship can be attacked with a minimum of return fire.
The Dido is also well protected against fighters by twenty advanced barracuda missile tubes and forty large lasers. Additionally these weapons are supported by a full wing of aerospace fighters. On top of that four docking collars were added to the design, and it wasn't uncommon for a Dido to carry assault dropships to supplement its firepower even further.
Between all of the weapons mounted on the Dido and its large propulsion system, designers were forced to skimp a fair amount on the ship's structure and armor. The hull is lightly constructed for a frigate (its structural strength is actually only about half that of the Oriente), and only seven hundred and sixty tons of armor cover that. However, in order to counter this problem, designers included expensive Ferro Carbide armor, which greatly enhanced the protection of the ship.
Deployment:
Members of Parliament were always skeptical of the Dido from the beginning, if for no other reason than the ship cost more to build than a Sian class Battlecruiser. However this class had a powerful political ally in the Marik family who staunchly supported construction of this warship. The traditional ruling clan of the Free Worlds League, ever politically able, was able to convince enough skeptics to sign off on the project. By utilizing a wide variety of maneuvers, which included the production of this frigate by multiple shipbuilders throughout the League, the Marik’s were able to garner enough support for the Dido. So despite the high cost of this vessel it would go onto phase out several other older vessels during the Star League era. Incredibly the Captain-General’s eventually succeeded in pushing through the funding needed to build one hundred and twelve of these Frigates.
The Dido ultimately went onto prove itself in the Marik Civil War and the 3rd Hidden War but lost eighteen of its number in these conflicts. About one-half of all Didos in service were assigned to Integrated Carrier Battlegroups (ICBs) alongside the Varyag class Carriers and the Alexander class Destroyers. In that role they were used as the maneuver element of the task force, screening the carriers and transports from attack and acting as a mobile hammer to back up the carrier's fighters. This tactic has proven very successful against the Lyrans during the Succession War but was extremely hard on the class as a whole. The first brutal battles of the war claimed most of them quickly. On the Liao front, Didos were used as part of hunter killer battlegroups tasked with searching out and destroying elusive Liao warships. As these ships weren't subjected to the same sort of punishing ship killing action that the Didos on the Steiner front faced, they tended to last much longer. However, as the war has dragged on it has become increasingly difficult to repair these complex ships and their advanced ferro carbide armor. Today only fourteen of these warships continue to survive in the service of the Free Worlds League Navy.
Aeneas class Cruiser
Tech: InnerSphere
Introduced: 2595
In Class: 60
Manufacturer: United Shipwrights (Angell II / Free Worlds League)
Mass: 850,000 tons
Length: 950 meters
Sail Diameter: 1,200 meters
Fuel: 4,000 tons (10,000)
Tons/Burn Day: 39.52
Safe Thrust: 4
Maximum Thrust: 6
Sail Integrity: 5
KF Drive Integrity: 17
Heat Sinks: 2020 (4040)
Structural Integrity: 80
Armor: (1,309 tons, Ferro Carbide)
Fore: 200
Fore-Sides: 180
Aft-Sides: 180
Aft: 175
Cargo:
Bay 1: Fighters (24) 6 doors
Bay 2: Small Craft (4) 2 door
Bay 3: Cargo (74,838 tons) / Marines (2 platoons) 1 door
Dropship Capacity: 6
Grav Decks: 2 (90 and 150-meter diameter)
Escape Pods: 22
Lifeboats: 22
Crew: 263 minimum (45 Officers, 218 Enlisted)
Weapons: (Heat: 4,040)
Nose (Heat: 660)
2 Naval Autocannon 25s
2 Heavy NPPCs
2 Killer Whale Missile Launchers
Fore Left/Fore Right (Heat: 720)
2 Naval Autocannon 20s
2 Naval Autocannon 35s
Left/ Right Broadsides (Heat: 1,880)
2 Naval Autocannon 25s
2 Heavy NPPCs
4 Naval Laser 45s
2 Killer Whale Missile Launchers
Aft Left/Aft Right (Heat: 340)
2 Naval Autocannon 25s
Aft (Heat: 440)
2 Naval Autocannon 20s
4 Naval Laser 45s
4 Barracuda Missile Launchers
Ammunition:
400 rounds of Naval Autocannon/35 ammunition
1000 rounds of Naval Autocannon/25 ammunition
600 rounds of Naval Autocannon/20 ammunition
60 Killer Whale Missiles
40 Barracuda Missiles
Overview:
The Aeneas class Cruiser stems from harsh lessons learned during Marion Marik's advance into the Magistracy of Canopus during the War of Reunification. The fleet arm of the SLDF's VII Corps was constructed to focus on larger craft, with its backbone being the venerable Monsoon-class Battleships and buttressed by the Free World League's new Atreus class Battleship. Marion believed that sheer weight of fire would cow the Canopians into submission without an overabundance of bloodshed. This was not to be.
The lighter, faster units of the Magistracy fleet repeatedly engaged in high-speed passes against SLDF forces. They would build up velocity far out of the heavier ships' maximum range, streak in, and let loose only one or two volleys, score what damage they could, and be out of range again before the SLDF forces could respond. When Marik's forces could bring the Canopian fleet assets to fight, they would drive at high speed to point-blank ranges and use their superior tactical maneuverability to engage the SLDF ships in their damaged or more lightly-defended arcs of fire, causing damage all out of proportion to their size.
After the Reunification War, as the highest-profile Marik with recent combat experience, Marion used her position to lever the Free Worlds League Admiralty into creating, essentially, a "Pocket Atreus" with the advantages of much greater maneuverability and combat endurance. With peace breaking out across the Inner Sphere, the Aeneas was given the label of "Cruiser", so as not to seem overly-aggressive to the League's restless neighbors.
Capabilities:
While the primary focus of the Aeneas class is the high-powered engine suite, the vessel featured many state-of-the-art systems when it was introduced.
The weapons systems mostly match and exceed the weapons found on the Atreus Battleship. Indeed, the systems are practically identical, with only a few adjustments. The Aeneas mounts no dedicated anti-fighter weapons, following the trend started by Star League vessels, instead relying on its fighter complement to keep the "bugs" off its back. To the heavy gun complement, it adds several capital missile systems for range and nuclear-strike capability. Finally, the famously short magazines of the Atreus that led to such problems during the Canopian campaign are increased by 50%.
As in most League ships, the aerospace fighter complement is not an overlooked branch of the black-water navy. A full wing of 18 fighters is included, and each squadron has two spare fighters in their own dedicated bays for easy replacement of battle-damaged spaceframes. The pilots also enjoy top-quality crew accommodations, making an Aeneas Cruiser a sought-after duty station.
The Aeneas is also the first League vessel to mount advanced Ferro-Carbide Armor. League scientists studied the compound, which first appeared on the Terran Hegemony's Farragut class battleships in 2448, for 150 years before being able to match and produce it in any real quantity.
Deployment:
Derided by critics as "a vessel designed to fight the last war" at the time of its launch in 2595, the FWLS Aeneas showed the flag and engaged in anti-piracy patrols early in its history. Not too surprisingly the Cruiser stomped flat any pirates unfortunate enough to encounter it earning quite a reputation in the process. The Aeneas was the first of seventy five planned vessels when it was originally launched with a planned deployment of two per year. However issues with the Ferro Carbide logistic train meant the next vessel, the FWLS Hector, wasn't launched until 2599. Ultimately various budget cutbacks limited the class to only sixty vessels in total.
These warships would go largely unchallenged until the onset of the Marik Civil War in 2729. In March of that year Oliver Marik made his way to Calloway IV in a heavily-armed convoy, of which the FWLS Menelaus, an Aeneas-class Cruiser, was the heaviest vessel. On their journey, they were intercepted by a loyalist task force centered around the Ivanhoe, an ancient SLDF Monsoon class Battleship that had been sold off to the League during the class's retirement in 2668. The lighter craft paired off as Oliver's ship ran for it, and the final pairing came down to the Menelaus and the Ivanoe. Obsolete though the Monsoon was, the Menelaus gave away near-on a half-million tons displacement to the vessel, and was in for the fight of its life.
Captain Alistair McKeon ordered the Menelaus's throttles shoved to the stops, and the cruiser bored in on a high-speed pass that left the Ivanhoe damaged enough that it stopped its pursuit of Oliver Marik's ship and lumbered around to engage its tormentor. The Menelaus roared back in towards the massive foe at a barely-controlled velocity (momentarily causing the Ivanhoe's capatin to wonder if they were going to ram), spinning madly in an attempt to take the Ivanhoe's fire in as many arcs as it could. Reaching close range, McKeon cut the vessel's speed sharply and swung in behind the Ivanhoe, riding its six o'clock arc much like a massive aerospace fighter. The lighter vessel used its greater maneuvering capacity to dog the Ivanhoe's tail for several minutes, sleeting fire into the back of the vessel, until critical damage to the engines left the Ivanhoe dead in space.
Forty four Aeneas class Cruisers survived the Marik Civil War and the Third Hidden War only to face the total destruction of the Succession War. Due to their impressive capabilities these Aeneas class Cruisers became a high-priority target for the enemies of the League. As a result more Aeneas’ have been destroyed by nuclear weapons than any other Marik ship class in the Succession Wars. Only six survive today.
Sian class Battlecruiser
Tech: InnerSphere
Introduced: 2623
In Class: 52
Manufacturer: Various (Free Worlds League)
Mass: 800,000 tons
Length: 852 meters
Sail Diameter: 1,200 meters
Fuel: 3,000 tons (7,500)
Tons/Burn Day: 39.52
Safe Thrust: 3
Maximum Thrust: 5
Sail Integrity: 4
KF Drive Integrity: 16
Heat Sinks: 3840
Structural Integrity: 100
Armor: (1600 tons, Standard Armor)
Fore: 116
Fore-Sides: 117
Aft-Sides: 117
Aft: 116
Cargo:
Bay 1: Small Craft (10) 2 doors
Bay 2: Cargo (57,411 tons) 2 doors
Bay 3: Fighters (18) 2 doors
Dropship Capacity: 4
Grav Decks: 2 (70-meter diameter)
Escape Pods: 30
Lifeboats: 30
Crew: 269 minimum (46 Officers, 223 Enlisted)
Weapons: (Heat: 3,840)
Nose (Heat: 100)
5 Killer Whale Missile Launchers
Fore Left/Fore Right (Heat: 600)
2 Naval Autocannon 30s
5 Killer Whale Missile Launchers
Left/ Right Broadsides (Heat: 1,360)
6 Naval Autocannon 30s
4 Killer Whale Missile Launchers
Aft Left/Aft Right (Heat: 1,720)
8 Naval Autocannon 30s
3 Killer Whale Missile Launchers
Aft (Heat: 60)
3 Killer Whale Missile Launchers
Ammunition:
3200 rounds of Naval Autocannon/30 ammunition
320 Killer Whale Missiles
Overview:
Despite its name there is no mistaking the fact that the Sian class Battlecruiser is a Free Worlds League ship of the line. Many, especially those outside Marik space, fail to realize that this vessel was named in honor of the decisive battle of the 1st Andurien War that began the Age of War. This pivotal naval victory which is still well remembered by the League Navy was reason enough to name a Marik warship after the Capellan capital system. No doubt the Confederation’s anger over the entire issue also played a small part in this decision. [Editor’s Note: House Liao issued numerous protests over this openly hostile and disrespectful act to everyone that would listen and has refused to recognize this warship as the Sian, instead referring to it as the Marik class Battlecruiser]
The design itself was created as a stopgap to meet the needs of the Free Worlds League during the arms race of the early twenty seventh century. Though the League initially attempted to match the battleship construction of their neighbors’ measure for measure with their Atreus class Battleships, it soon became readily apparent that the Atreus, though big and powerful, had its flaws. With the economy of the League beginning to falter by 2620, Parliament decided to greatly slow production of the Atreus, seeking instead to concentrate production on a smaller, simpler, and less expensive alternative that could effectively supplement its flagship. The end result was this formidable Battlecruiser.
Capabilities:
The Sian is pretty much your garden variety Battlecruiser. Though not as cost effective as Parliament had hoped it would be, the ship is certainly simple, straightforward, and to the point.
The Sian's primary armament is thirty six heavy naval autocannons. These cannon are arranged in eighteen dual turrets along the sides of the ship, presenting a pure broadside fighter. Though this can limit the tactical options of a lone ship, when operating in a massed battlegroup these ships are more than capable of covering each other's exposed arcs.
The Sian's secondary armament is surprising, as the ship carries one of the heaviest batteries of naval missiles ever mounted on a ship. This massed battery makes fighter attacks against a Sian very dangerous indeed, and in fact many Sians served a secondary role as AA ships escorting Atreus class battleships and Varyag class carriers.
Though relying on standard plate in order to cut costs, the Sian is reasonably well protected. Sixteen hundred tons of armor covers an extremely strong hull making for a ship that can stand a remarkable amount of punishment.
Rounding out these exceptional offensive and defensive capabilities is a full wing of aerospace fighters and space for ten small craft.
Deployment:
As with many Marik warships production of the Sian was diversified by federal authorities. Several different naval manufacturers worked on building multiple vessels at once. This allowed for the construction of fifty two Battlecruisers by 2650 when further shipbuilding was discontinued. Twelve of these vessels were placed into reserve status following the restriction of House Militaries by Star League law.
In one of the tragic ironies of naval history, the first major battle the Sian and her sisters would see was against each other. After three members of Regulus' ruling Selaj family were implicated in an attempt to slaughter the Marik family, Captain-General Gerald Marik moved to deal with the traitors, leading to a major battle on Hellos Minor at the end of 2679. During the campaign, a pair of Sian class Battlecruisers (the Stewart and Amity) which had sided with the traitors attempted to lead a convoy of reinforcements to the world. In the battle that followed, the convoy was routed from the system, the Stewart was destroyed and the Amity was captured. After the successful conclusion of the campaign, the Captain General ordered the Amity renamed the Hellos Minor.
Unfortunately, this would not be the last time these ships would face each other. Much like the rest of the League, the fleet split pretty evenly when the League was wracked by civil war in 2729. Both sides in that conflict tended to use their Battlecruisers as shock forces, and as a consequence many were lost before the Treaty of Verona was signed, ending the fighting.
The thirty two remaining ships of this class have been called into action again during the Succession War. Much as had been done during the Civil War, the Sians were used primarily as shock troops, leading the way into the Terran Republic, the Capellan Confederation, and the Lyran Commonwealth in various League campaigns. This proved disastrous in many cases, however. During an attack on Hesperus II, Lyran defenders accounted for all twelve surviving Sians on the Lyran front destroyed, a loss that forced Marik to completely rethink their strategies against House Steiner.
Today only five of these Battlecruisers continue to operate in Marik service. As luck would have it one of the last ships of her class to survive is also the first ship. The Sian has been operating along the Capellan frontier since the start of the war, and the Confederation holds a special dislike for the ship. Barbara Liao herself is reported to have said "If I accomplish nothing else during this damn war I will see that ship destroyed!" So far the Sian has managed to frustrate the Capellans by its continued existence.
* Themistocles class Destroyer-Carrier.hma (8.54 KB - downloaded 5 times.)
* Dido class Frigate.hma (5.95 KB - downloaded 4 times.)
* Aeneas class Cruiser.hma (7.47 KB - downloaded 4 times.)
* Sian class Battlecruiser.hma (7.01 KB - downloaded 4 times.)
-
Takiro Marik Carriers « Reply #28 on: May 03, 2008, 11:25:29 PM »
Varyag class Battlecruiser/Carrier
Tech: InnerSphere
Introduced: 2651
In Class: 40
Manufacturer: Various (Free Worlds League)
Mass: 800,000 tons
Length: 892 meters
Sail Diameter: 1,200 meters
Fuel: 10,000 tons (25,000)
Tons/Burn Day: 39.52
Safe Thrust: 3
Maximum Thrust: 5
Sail Integrity: 4
KF Drive Integrity: 16
Heat Sinks: 582
Structural Integrity: 100
Armor: (1600 tons, Standard Armor)
Fore: 110
Fore-Sides: 120
Aft-Sides: 120
Aft: 110
Cargo:
Bay 1: Small Craft (12) 2 doors
Bay 2: Cargo (140,632 tons) 2 doors
Bay 3: Fighters (108) 6 doors
Dropship Capacity: 2
Grav Decks: 2 (250-meter diameter)
Escape Pods: 0
Lifeboats: 100
Crew: 221 minimum (37 Officers, 184 Enlisted)
Weapons: (Heat: 1,216)
Nose (Heat: 36)
6 LRM 20s
Fore Left/Fore Right (Heat: 272)
1 Naval Autocannon 30
6 LRM 20s
Left/ Right Broadsides (Heat: 400)
2 Naval Autocannon 30s
Aft Left/Aft Right (Heat: 472)
2 Naval Autocannon 30s
6 LRM 20s
Aft (Heat: 36)
6 LRM 20s
Ammunition:
1000 rounds of Naval Autocannon/30 ammunition
1080 volleys of LRM 20 ammunition (180 tons)
Overview:
The Varyag was a product of the restrictions placed on the house fleets by the Star League in 2650. At the time, the Free Worlds League was operating on a building plan tagged the Frost Program, which ultimately called for an enormous fleet of some one hundred Sian class Battlecruisers alongside a nearly equal number of Atreus class battleships operating as the main punch of the fleet. Backing these up would be an ambitious (if as yet unrealized) carrier design capable of carrying as many as eight regiments of fighter craft.
Then the new restrictions hit, and the League was forced to make some difficult choices. With the limits imposed on the Marik fleet by the Star League, the Frost Program became simply impossible. However, unwilling to give up on the underlying principles of the project, the League instead embarked on a revised program (which some, with a sense of really bad humor, tagged as the Mildly Cold Dew Program). Under this program the twelve Sian class Battlecruisers currently under construction would be completed as fighter carriers, though they would be much more humble than the originally planned design.
Capabilities:
The Varyag actually suffers a great deal as a result of military politics. Many naval officers (especially the so called "Battleship Admirals") saw carriers as a serious threat to the status quo. As a result, the Varyag (as well as the Themistocles class Destroyer/Carrier) was something of a compromise design.
The main compromise was a rather light armament. Ten heavy naval cannons make up the sum total of the ship's naval weaponry, and this is further hampered by an insufficient cooling system. This armament is adequate to fend off some destroyers and most smaller ships, however against a larger opponent the Varyag can quickly find itself outmatched. This was justified on the theory (heavily espoused by the battleship admirals) that carriers were meant to serve as launch platforms for fighters, not as front line combatants. It is worth noting that the Varyag could actually accommodate another ten heavy guns easily without compromising its ability to conduct carrier operations one bit. It is clear, however, that such an armament would have been completely unacceptable to many in the FWL fleet.
The principle weapon of the Varyag is without a doubt its fighter complement. Space for two full regiments of fighters was included in the design, giving the ship an exceptional strike capability. For defense against hostile fighters, a network of LRM 20 racks was added to the design. The Varyag has the same hull as the Sian, and as a consequence is similarly armored, though for unknown reasons the armor was redistributed somewhat.
What the ship does have in abundance is space for supplies. Ten thousand tons of fuel not only amply supplies the ship's needs, but those of its fighter complement as well. Just over one hundred and forty thousand tons of cargo space likewise leaves plenty of room for stores, not only to meet the Varyag's needs, but those of her escorts. [Editor's Note: that was one of the justifications for the limited cargo space of the Alexander class destroyer. Since the ship would be operating alongside Varyag class carriers, a large cargo capacity was considered unnecessary] [On an unrelated note, nobody is really sure why the Varyag happens to carry so many lifeboats. One popular theory was that the Free Worlds League had perfected some kind of guided weapon system similar to the Star League's Adcap, which would be launched from a modified lifeboat bay. However there is no evidence of such a weapon ever being used by the League. Another theory espoused by Rear Admiral Phillip Montague of the SLDF was that should a good sized ship get past the Varyag's escorts, every man in the crew would almost certainly start looking for lifeboats, so the designers made sure to include as many as possible.]
Deployment:
The first twelve Varyags were completed in fairly rapid succession starting in 2651. Ironically, the first combat action the class would see was against the SLDF.
In 2664, a task force centered around the carrier Moskva in the Leyda system recieved a distress signal from the destroyer Alkyon, reporting that it was under attack by an unknown enemy warship. The task force quickly moved in to aid the Alkyon, but failed to arrive in time to prevent the crippling of the warship. The attacker, identified as an SLDF Naga class destroyer, did not respond to the hails of the approaching ships, instead executing a high G burn directly at the Moskva. The unidentifed Naga was able to deliver a punishing barrage of naval gauss and PPC fire and slip out of range before the Moskva could launch fighters, inflicting moderate damage to the carrier's port side.
It was only after about another ten minutes of skirmishes between the Naga and one of the Moskva's escorting frigates that communications between the ships were established. The Naga identified herself as the SLS Amelia (Captain Phillip Montague commanding), and reported that the Alkyon had been covertly conducting acts of piracy against the Magistracy of Canopus and Free Worlds League (a later investigation would reveal that the commander of the Alkyon was in the pocket of the Selaj family). With this information in hand, the Amelia had moved in to deal with the problem. When the Moskva and her escorts had moved in to help the Alkyon, the captain of the Amelia had assumed that they too were part of the conspiracy and acted accordingly.
Ultimately, both the SLDF and Free Worlds League decided to quietly let the incident pass, though the colorful Phillip Montague was promoted right off of the Amelia and assigned to the planning and strategy division where he couldn't do any more immediate damage. [Editor's note: The very fact that the SLDF didn't fire the infamous Captain Phil for that incident speaks volumes. Many believed that Phillip Montague had such a knack for combat tactics that he was simply too valuable for the SLDF to loose no matter what messes he tended to cause. Recently, however, reports filed about the incident and quietly shoved aside have indicated that he was probably right about the Moskva. There are indications that the Moskva's captain and most of her crew were in fact in league with the Selaj family. If Montague had known about this in advance, then it casts the whole incident in a completely different light. Did Captain Phil know? And more importantly, did the Free Worlds League? Nobody can really be sure. It is worth noting, however, that in 2695 the Captain-General christened the newest Dido class frigate the Phillip Montague, "in honor of the man's twenty years of service in protecting the League from pirates and seperatist forces." An interesting decision considering he is best known in the League for shooting at one of their carriers.]
Despite a rather poor showing against the Amelia, the League was pleased with its new carrier and continued production, ultimately producing forty vessels. These craft proved to be a dangerous advantage for the Captain-General during the Free Worlds League Civil War when the majority sided with her against Oliver Marik. It was during this conflict that a new concept, the Integrated Carrier Battlegroup (ICB), received its first trial by fire. This force was composed of two Varyag class Battlecruiser/Carriers, an escort squadron of Dido class Frigates and a squadron of Destroyers, usually an Alexander class. The ICB proved to be a powerful and flexible force, scoring several impressive victories over more traditional Battleship formations. This conflict and later skirmishes during the Hidden Wars cost the League a total of eight Varyags. The remaining thirty two Battlecruiser/Carriers were deployed in sixteen ICBs by the start of the Succession War. Shifted almost exclusively to the Lyran front after the outbreak of hostilities they proved vital in dealing with House Steiner’s huge warships. However, this conflict took a massive toll on the class reducing it to only four surviving vessels today.
Nemesis class Carrier
Tech: InnerSphere
Introduced: 2755
In Class: 20
Manufacturer: Various (Free Worlds League)
Mass: 900,000 tons
Length: 1,085 meters
Sail Diameter: 1,100 meters
Fuel: 10,000 tons (25,000)
Tons/Burn Day: 39.52
Safe Thrust: 4
Maximum Thrust: 6
Sail Integrity: 5
KF Drive Integrity: 18
Heat Sinks: 2972
Structural Integrity: 80
Armor: (1440 tons, Improved Ferro Aluminum)
Fore: 152
Fore-Sides: 152
Aft-Sides: 152
Aft: 152
Cargo:
Bay 1: Small Craft (20) 2 doors
Bay 2: Fighters (108) 6 doors
Bay 3: Cargo (34,919 tons) 2 doors
Dropship Capacity: 4
Grav Decks: 1 (250-meter diameter)
Escape Pods: 30
Lifeboats: 20
Crew: 290 minimum (50 Officers, 240 Enlisted)
Weapons: (Heat: 4,412)
Nose (Heat: 412)
4 Naval Autocannon 30s
3 LB-10X Autocannons
6 Autocannon 5s
Fore Left/Fore Right (Heat: 824)
4 Naval Autocannon 30s
3 LB-10X Autocannons
6 Autocannon 5s
Left/ Right Broadsides (Heat: 1,400)
6 Naval Autocannon 20s
4 Naval Laser 55s
Aft Left/Aft Right (Heat: 1,424)
6 Naval Autocannon 20s
4 Naval Laser 55s
3 LB-10X Autocannons
6 Autocannon 5s
Aft (Heat: 352)
4 Naval Laser 55s
3 LB-10X Autocannons
6 Autocannon 5s
Ammunition:
1200 rounds of Naval Autocannon/30 ammunition
2400 rounds of Naval Autocannon/20 ammunition
1800 rounds of LB-10X Autocannon ammunition
3600 rounds of Autocannon/5 ammunition
Overview:
The Nemesis class Carrier has been the focus of controversy since its launch on April 19, 2755. Many continue to debate if this warship is an expensive boondoggle, an ill conceived chimera directly responsible for the collapse of the Free Worlds League's Navy during the Succession War. Others claim the class is simply poorly utilized and poorly understood by inflexible commanders. The truth may actually be a little bit of both. The Nemesis can be thought of as the right ship built at precisely the wrong time for entirely the wrong reasons.
The Nemesis was House Marik’s first true aerospace carrier designed from keel up to both transport massive numbers of fighters and engage enemy warships directly. This was a radical deviation from accepted naval design principles, which until this point had maintained a clear delineation between fighter carriers and front line combat vessels. During the Star League era this well established practice began to be questioned in earnest especially within some circles of the Free Worlds League. Maverick engineers and certain aerospace industries ran with the idea and began to lobby for the creation of such a revolutionary new craft. After many years of consideration Parliament authorized funding for the construction of a prototype carrier that forced its fleet to take a hard look at this concept.
This political decision caused an immediate uproar among the Navy. Nobody liked the idea. The carrier commanders knew the League's naval aerospace arm was already stretched to the limit with the existing carrier fleet and didn't want a new carrier, especially an untried multi-role design like the Nemesis which might very well take away some of the funding for their beloved Integrated Carrier Battlegroups. Traditional battleship commanders on the other hand considered the Nemesis an encroachment on their own sacred territory. Despite fierce protests League authorities were impressed by its potential and ordered the warship into mass production.
Capabilities:
The Nemesis is a solid front line carrier. Her main armament, two dozen medium and heavy naval cannon backed by nearly as many lasers, certainly gives the ship much greater firepower than the Varyag class that served as the mainstay of the carrier forces, and her fighter complement is (in theory at least) just as big. In addition superior thrust capability and armor protection nominally give this ship the edge, and her massed batteries of autocannons (including an analogue of the Hegemony's LB-10X) provide a roughly comparable anti-fighter defense. All this combined allowed the Nemesis to operate as a quick striking hammer, able to follow up a massed fighter attack with a barrage of heavy gunfire. In theory this made the ship a potent weapon but in practice the results were far different.
Deployment:
Though the Nemesis' trials were enough to demonstrate the potential of the class, it was the reversal of the Edict of 2650 that really spurred a burst in construction. With all of the Great Houses engaged in a downright massive naval buildup, and with the new Nemesis proving to be every bit the better of the older Varyag class, the League Central Command authorized the construction of a total of twenty Nemesis class vessels. Today many regard this decision as a costly and foolish mistake.
The Free Worlds League's naval aerospace forces had been horribly mauled during the recent Civil War (estimates place losses at anywhere from 50 to 70 percent among carrier wings), which had ended barely twenty one years earlier. Though the carrier forces were well on their way to recovery in the two decades since the war, the League's aerospace assets were still stretched to the limit supporting the existing fleet. When the first new Nemesis class ships began entering service, League Admirals suddenly realized that they had few or no new fighters to give them, a situation that might take years or even decades to completely rectify.
In order to properly equip the new carriers, it was decided to strip fighters from other warships in the fleet. Hardest hit by this decision were the Integrated Carrier Battlegroups, each of which lost several of their best fighter squadrons to the new ships. This, to some degree, blunted the striking power of the battlegroups, a situation that was never really rectified. Ships in the main battlefleet lost fighter squadrons as well, increasing the dependence on dedicated carriers like the poorly armed and protected Themistocles to provide the main defensive fighter screen for battleships and other major fleet units.
The biggest tragedy of the Nemesis' career, however, was that it was almost never really utilized well. Nemesis class ships were grouped into their own independent battlegroups, supported by a mixed bag of destroyers for escort and screening duty. These battlegroups were something of a cross between a battlecruiser squadron and an integrated carrier battlegroup, and in theory they offered the best of both worlds. In practice however, their performance was far below what was hoped for. Most Nemesis commanders, especially those with previous command experience on either Sians or Varyags, never really got the hang of the idea that BOTH the ship's formidable arsenal and its fighters were offensive weapons. Some captains preferred to keep their ships well away from the fighting, relying on their fighters to strike at the enemy. Others tended to plunge into battle with cannons blazing, relegating an enormous number of fighters to a rather needless defensive screen, or even worse, ignoring their own fighters entirely.
[Editor's Note: Inter-service rivalry at work. For a century League naval tactics had been built on the idea that the Sian class Battlecruiser fight close in and Varyag class Battlecruiser/Carrier stay back and send fighters into the fray. A ship that was essentially able to fill both roles just didn't fit into this tactical doctrine. Those who did best commanding Nemesis class warships were generally mavericks that spent their careers doing things the "wrong way". It was only a rare few who could get bye on bucking the system and still rise to command of a major front line warship like the Nemesis. Those few that did built the framework for whole new naval doctrine which likely would have greatly advanced naval tactics in the League and would have turned the Nemesis squadron into a weapon to be reckoned with. Unfortunately the horrors of the Succession War have devastated the League fleet and made such developments pointless.]
Despite their less that hoped for performance, the League sent all of its Nemesis squardons into the fray right from the start of the Succession War. Today only two of these Carriers remain in the service of the Free Worlds League Navy.
* Varyag class Battlecruiser-Carrier.hma (9.46 KB - downloaded 6 times.)
* Nemesis class Carrier.hma (8.51 KB - downloaded 5 times.)