- Lead Developer Brent Evans Answers Big Questions On The Future Of BattleTech
- Was the Early Portrayal of the Capellan Confederation an Example of Yellow Peril?
- Mechwarrior Online World Championship Semi-Finals Seeding Games
- New Campaign Begins on MegaMekNET
- BATTLETECH Multiplayer Review - A Battle Of Titans
- Read more →
|Manufacturer||Krauss-Liemann Incorporated |
|Mass||50 tons[[Category:50 ton BattleMechs]]|
|Armor||PanzerSlab Type 3|
|Communications System||Vex/Holden TriComm Plus|
|Targeting Tracking System||Dillon QuadTrac w/Particle Cannon Suite|
|Jump Jets||Gerard Special A|
The Phoenix was the Rim Worlds Republic's first effort to design a jump-capable BattleMech designed and produced by Krauss-Liemann Incorporated. Terens Amaris was convinced that the Wasp and its jump jets heralded a sea-change in tactics and was determined to build a 'Mech larger than the Wasp that incorporated them. Unfortunately, the Republic lacked jump jets, so the project stalled while technicians reverse-engineered the technology. Terens insisted on "quality over quantity" in the Republic's BattleMech program, delaying production until well after the Terran Hegemony had fielded the Griffin and Shadow Hawk. The First Consul diverted resources away from other production efforts to accomplish this which became a massive boondoggle. Nonetheless, the Phoenix and its jumping capability did allow the Republic to execute new battle plans, including combat drops from DropShips. No other power produced or salvaged the Phoenix and it was believed to have become extinct following Aleksandr Kerensky's conquest of the Rim Worlds Republic. It was surprising, then, when a ComStar report indicated that the Hanseatic League was deploying a number of them.
The earliest prototypes of the Phoenix underwent numerous changes throughout its long development history. Having nearly reached completion of a prototype in 2470, Terens Amaris ordered the design team to implement jump jet technology for immediate testing - information that had been acquired by the Republic's intelligence agency. They quickly scrambled to redesign a machine that was essentially complete as a result. The design philosophy had been intended to create a front-line "trooper" BattleMech that would engage enemies at all ranges and so had mounted a PPC and a two SRM-4 launchers. In order to reconfigure it as jump-capable, the launchers were downgraded to twin SRM-2s, but received slightly better armor protection. Ultimately Krauss' engineers encountered the same problems as the Terran Hegemony with their earlier Wasp and it took an additional 4 years until the redesigned prototype was unveiled and another 6 before it was production ready. It was mired by constant problems including electronics interference when the particle cannon was fired, with pilots giving it the name "Sparkly Bird." The legs were also too weak to deal with the stress of landing a 50 ton BattleMech, resulting in fractured or shattered leg and torso structural components. These were eventually corrected after 33 years, just 13 years before Krauss-Liemann Incorporated designed the modern PX-3R Phoenix. 
The main feature of the medium-class Phoenix is its ability to jump up to 150 meters. Capable of attaining 86 km/h, the Phoenix is protected by nine tons of armor.
Weapons and Equipment
- Technical Readout: 3075, pp. 298-299, "PX-3R Phoenix"
- Field Report 2765: Periphery, p. 11, "Infrastructural Integrity"
- MUL online entry for the Phoenix (BattleMech)
- Era Digest: Age of War, p. 11
- Record Sheets: 3075 Unabridged, p. 272
- Record Sheets: 3075 Unabridged - Age of War, p. 217
- Experimental Technical Readout: Primitives, Volume 5, p. 4 "PX-1R Phoenix 'Mech Profile"
- MUL online entry for the PX-1R Phoenix varinat
- Record Sheets: 3075 Unabridged, p. 273
- MUL online entry for the PX-4R Phoenix varinat
- Record Sheets: 3075 Unabridged, p. 274
- Record Sheets: 3075 Unabridged - Age of War, p. 218