Difference between revisions of "Phoenix (BattleMech)"
Sarna News
(Update Notice) |
(XTROPv5 adds) |
||
| Line 1: | Line 1: | ||
| − | + | ||
{{InfoBoxBattleMech | {{InfoBoxBattleMech | ||
|image=Phoenix.jpg | |image=Phoenix.jpg | ||
| Line 26: | Line 26: | ||
== Description == | == Description == | ||
| − | The '''''Phoenix''''' was the [[Rim Worlds Republic]]'s first effort to design a jump-capable [[BattleMech]]. [[Terens Amaris]] was convinced that the ''[[Wasp]]'' and its [[jump jet]]s 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]]''. Nonetheless, the ''Phoenix'' and its jumping capability did allow the Republic to execute new battle plans, including combat drops from [[DropShip]]s. 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.<ref name="TRO:3075p298+"/> | + | The '''''Phoenix''''' was the [[Rim Worlds Republic]]'s first effort to design a jump-capable [[BattleMech]] designed and produced by [[Krauss-Liemann_Incorporated|Krauss-Liemann Incorporated]]. [[Terens Amaris]] was convinced that the ''[[Wasp]]'' and its [[jump jet]]s 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 [[DropShip]]s. 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.<ref name="TRO:3075p298+"/> |
| + | |||
| + | 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 [[SRM2|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 the company designed the modern PX-3R ''Phoenix''. <ref name=XTROPv5>''Experimental Technical Readout: Primitives, Volume 5'', p. 4 "PX-1R ''Phoenix'' 'Mech Profile"</ref> | ||
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.<ref name="TRO:3075p298+"/> | 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.<ref name="TRO:3075p298+"/> | ||
| Line 34: | Line 36: | ||
== Variants == | == Variants == | ||
| − | *;PX-1R : The original prototype of the ''Phoenix'' introduced in [[Introduction Year::2474]]<ref name="MUL2"/>, the 1R was slower and had fewer heat sinks<ref name="TRO:3075p298+"/>. BV (1.0) = ??, BV (2.0) = 900<ref>''Record Sheets: 3075 Unabridged'', p. 273</ref><ref name="MUL2">''[http://www.masterunitlist.info/Unit/Details/2488/phoenix-px-1r/ MUL online entry for the PX-1R Phoenix varinat]''</ref> | + | *;PX-1R : The original prototype of the [[Primitive Technology|primitive] ''Phoenix'' introduced in [[Introduction Year::2474]]<ref name="MUL2"/>, the 1R was slower with a top speed of 64 km/h and had fewer heat sinks<ref name="TRO:3075p298+"/><ref name=XTROPv5/>. BV (1.0) = ??, BV (2.0) = 900<ref>''Record Sheets: 3075 Unabridged'', p. 273</ref><ref name="MUL2">''[http://www.masterunitlist.info/Unit/Details/2488/phoenix-px-1r/ MUL online entry for the PX-1R Phoenix varinat]''</ref> |
*;PX-4R : This variant developed in [[Introduction Year::2581]]<ref name="MUL3"/> was highly anticipated, but it proved to be so unpopular that production was canceled. The decision to switch to an ammunition-fed [[Autocannon/10]] instead of the PPC is blamed<ref name="TRO:3075p298+"/>. BV (2.0) = 996<ref>''Record Sheets: 3075 Unabridged'', p. 274</ref><ref>''Record Sheets: 3075 Unabridged - Age of War'', p. 218</ref><ref name="MUL3">''[http://www.masterunitlist.info/Unit/Details/2490/phoenix-px-4r/ MUL online entry for the PX-4R Phoenix varinat]''</ref> | *;PX-4R : This variant developed in [[Introduction Year::2581]]<ref name="MUL3"/> was highly anticipated, but it proved to be so unpopular that production was canceled. The decision to switch to an ammunition-fed [[Autocannon/10]] instead of the PPC is blamed<ref name="TRO:3075p298+"/>. BV (2.0) = 996<ref>''Record Sheets: 3075 Unabridged'', p. 274</ref><ref>''Record Sheets: 3075 Unabridged - Age of War'', p. 218</ref><ref name="MUL3">''[http://www.masterunitlist.info/Unit/Details/2490/phoenix-px-4r/ MUL online entry for the PX-4R Phoenix varinat]''</ref> | ||
| + | |||
| + | ==Design Quirks== | ||
| + | The ''PX-1R Phoenix'' variant is subject to the following [[Design Quirks]]:<ref name=XTROPv5/> | ||
| + | * [[EM Interference]] | ||
| + | * [[Obsolete]] (2525) | ||
| + | * [[Poor Workmanship]] | ||
| + | * [[Weak Legs]] | ||
== References == | == References == | ||
| Line 43: | Line 52: | ||
== Bibliography == | == Bibliography == | ||
* ''[[Era Digest: Age of War]]'' | * ''[[Era Digest: Age of War]]'' | ||
| + | * ''[[Experimental Technical Readout: Primitives, Volume 5]]'' | ||
* ''[[Field Report 2765: Periphery]]'' | * ''[[Field Report 2765: Periphery]]'' | ||
* ''[[Master Unit List: Battle Values]]'' | * ''[[Master Unit List: Battle Values]]'' | ||
Revision as of 13:10, 30 July 2017
| |
| Phoenix | |
|---|---|
| Production information | |
| Manufacturer | Krauss-Liemann Incorporated[1] Diplass BattleMechs[2] |
| Production Year | 2520[3][4] |
| Model | PX-3R[1] |
| Class | Medium[1][[Category:Medium[1] BattleMechs]] |
| Cost | 4,234,250 C-bills[3] |
| Technical specifications | |
| Mass | 50[1] tons[[Category:50[1] ton BattleMechs]] |
| Chassis | 12b Krauss-Liemann |
| Armor | PanzerSlab Type 3[1] |
| Engine | Magna 250[1] |
| Communications System | Vex/Holden TriComm Plus |
| Targeting Tracking System | Dillon QuadTrac w/Particle Cannon Suite[1] |
| Heat Sinks | 14[1] |
| Speed | 86[1] km/h |
| Jump Jets | Gerard Special A[1] |
| Armament | |
| BV (1.0) | ??? |
| BV (2.0) | 1,106[1][3][5][6] |
Contents
Description
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.[1]
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 the company designed the modern PX-3R Phoenix. [7]
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.[1]
Weapons and Equipment
Primarily a sniper, the Phoenix mounts a Stolz Harbinger 2 PPC. To back it up, the 3R carries a pair of SRM-2 launchers. Two ammo bins enable the use of different munitions, including Infernos.[1]
Variants
Design Quirks
The PX-1R Phoenix variant is subject to the following Design Quirks:[7]
References
- ↑ 1.00 1.01 1.02 1.03 1.04 1.05 1.06 1.07 1.08 1.09 1.10 1.11 1.12 1.13 1.14 1.15 1.16 1.17 Technical Readout: 3075, pp. 298-299, "PX-3R Phoenix"
- ↑ Field Report 2765: Periphery, p. 11, "Infrastructural Integrity"
- ↑ 3.0 3.1 3.2 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
- ↑ 7.0 7.1 7.2 Experimental Technical Readout: Primitives, Volume 5, p. 4 "PX-1R Phoenix 'Mech Profile"
- ↑ 8.0 8.1 MUL online entry for the PX-1R Phoenix varinat
- ↑ Record Sheets: 3075 Unabridged, p. 273
- ↑ 10.0 10.1 MUL online entry for the PX-4R Phoenix varinat
- ↑ Record Sheets: 3075 Unabridged, p. 274
- ↑ Record Sheets: 3075 Unabridged - Age of War, p. 218