- Did You Know? - Fan made TRO 3028 is better than the originals!
- BattleTech Technology - Today!
- Someone did the math on how many 'Mechs you kill in MechWarrior 3
- A chat with MechWarrior Online Champs: Empyreal's prtNspz - Full Interview
- Unstoppable: A chat with MechWarrior Online Champs, Empyreal's prtNspz
- Read more →
|Tech Base||Star League|
|Sail Diameter||1.150 m|
|Safe Thrust||1 g|
|Top Thrust||1.5 g|
|KF Drive Integrity||11|
|Armament|| 19 x NL35s |
4 x NAC/10s
4 x White Shark Launchers
|Armor||256 tons of Improved Ferro-Aluminum|
|Crew||275 + 30 passengers|
|Grav Decks||1 x 65 meter diameter|
|Escape Pods/Life Boats||38/13|
The Baron-class destroyer was a moderately effective design that suffered due to protracted development and construction.
With initial construction beginning in 2515 in the midst of a massive arms race intended to allow the Terran Hegemony to maintain its edge against the Great Houses, flaws were discovered with the then-revolutionary Palenkov-Reese interplanetary engines used by the Baron. While the fault was correctable, it took 2 years and greatly reduced their performance, by which point naval design had marched steadily onward and the Baron-class was considered out of date before the first ship had slipped its moorings in 2520. In 2582 the Star League presented over half the constructed Barons to Star League member states; the remainder were retained by the Star League Defense Force and though it would see action in the Reunification War, their performance was considered lacklustre. The Federated Suns had five Barons lost or destroyed to the Taurian Concordat during the Case AMBER ambush at Tentativa alone.
The design’s sole saving graces were its generously-sized fuel bunkers and accommodations for thirty extra passengers, which caused many high ranking Star League diplomats to select ships of the Baron-class as heavily armed transports into high risk areas, including the Periphery. However by 2720, the SLDF had decommissioned and sold off the remaining Barons to the Great Houses; the Capellan Confederation kept three Barons in their active fleet until at least 2765 while the Draconis Combine was operating five the Federated Suns three and the Lyran Commonwealth one at the same point in time. The Succession Wars would see even mothballed Barons restored to combat status; the last active Baron in the Inner Sphere was believed to have been a Draconis Combine destroyer restored to active service and destroyed in 2853 in battle over Hesperus II, but at least one Baron would survive in a Clan naval cache until the Wars of Reaving. In the buildup to the Jihad the Word of Blake would restore three Barons to working order, subsequently deploying them in various battles around the Inner Sphere, with the last being destroyed in 3077.
Mounting a large array of NL35 capital Lasers, the Baron boasts impressive endurance on longer patrols, with six mounted in the nose, ten carried in each broadside with a further three directly aft. A mix of capital-grade autocannons and missile launchers provide support, with two NAC/10s and White Shark missile launchers in each forward angle, two more NAC/10s on each rear angle and two White Shark tubes directly rearward.
- MUL online date for the Baron
- Jihad Turning Points: Luthien, p. 15, "Baron [Destroyer]"
- Technical Readout: 3057 Revised, p. 200, "Baron (Destroyer"
- Historical: Reunification War, p. 69, "Battle for Tentativa"
- Field Report: Capellan Confederation 2765, p. 5, "Guarding the Vault of Heaven"
- Official Errata Thread
- Field Report: Federated Suns 2765, p. 6, "Naval Defense Doctrine"
- Field Report: Lyran Commonwealth 2765, p. 5, "The Vacuum Fleet"
- Tactics of Desperation, Part 1 (BattleCorps Scenario)
- Wars of Reaving, p. 112-113, "Constriction"
- Jihad: Final Reckoning, p. 128, "Word of Blake Naval Assets"