Sarna News: Bad 'Mechs - Icestorm

Difference between revisions of "Zephyr (Combat Vehicle)"

(Created page with '{{InfoBoxCombatVehicle | image = Zephyr.gif | name = Zephyr | manufacturer = Grumman Industries | Mission = Artillery Support | Type = Hover | Cost = ??? | mass = 40 | armor …')
 
(added mission, BV1, citations)
Line 3: Line 3:
 
| name = Zephyr
 
| name = Zephyr
 
| manufacturer = [[Grumman Industries]]
 
| manufacturer = [[Grumman Industries]]
| Mission = Artillery Support
+
| Mission = Dragoon / Cavalry
 
| Type = Hover
 
| Type = Hover
 
| Cost = ???
 
| Cost = ???
Line 10: Line 10:
 
| engine = [[GM]] 185 [[Fusion Engine]]
 
| engine = [[GM]] 185 [[Fusion Engine]]
 
| speed = 146
 
| speed = 146
| Crew = 2
+
| Crew = 3
 
| armament = 3 x [[Medium Laser]]s <br> 1 x [[SRM-6]] <br> 1 x [[Small Laser]]
 
| armament = 3 x [[Medium Laser]]s <br> 1 x [[SRM-6]] <br> 1 x [[Small Laser]]
| BV (1.0) = ???
+
| BV (1.0) = 640<ref>''Combat Operations'', p. 106</ref>
| BV (2.0) = 889
+
| BV (2.0) = 889<ref>''Technical Readout: 3050 Upgrade, p. 163</ref>
 
}}
 
}}
  
 
==Description==
 
==Description==
Originally designed in [[2620]] as a medium duty fast response [[infantry]] support tank, the [[SLDF]] instead saw the '''Zephyr''' as the prefect support vehicle for its [[Chaparral]] [[Arrow IV]] artillery tank.
+
Designed in [[2620]] to be a medium-duty, fast response, [[infantry]] support tank; the [[SLDF]] instead saw the '''Zephyr''' as the perfect support vehicle for its [[Chaparral]] [[Arrow IV]] artillery tank.
  
 
When the SLDF's Quartermaster Command was considering accepting the Zephyr for service, the SLDF vehicle corps was looking for a ground based design that could carry the successful [[Guardian ECM Suite]] to assist in setting ambushes for the Chaparral, with the SLDF ordering Grumman to add the system to tank. Powered by a [[GM]] 185 rated [[Fusion Engine]] and clad in seven tons of a Grumman CRT [[Ferro-Fibrous]] armor, the Zephyr boasts above average armor and speed for its weight and support role. <ref name=TRO2750>''Technical Readout: 2750'', p. 98</ref>
 
When the SLDF's Quartermaster Command was considering accepting the Zephyr for service, the SLDF vehicle corps was looking for a ground based design that could carry the successful [[Guardian ECM Suite]] to assist in setting ambushes for the Chaparral, with the SLDF ordering Grumman to add the system to tank. Powered by a [[GM]] 185 rated [[Fusion Engine]] and clad in seven tons of a Grumman CRT [[Ferro-Fibrous]] armor, the Zephyr boasts above average armor and speed for its weight and support role. <ref name=TRO2750>''Technical Readout: 2750'', p. 98</ref>
Line 35: Line 35:
 
<references/>
 
<references/>
  
==Biblogary==
+
==Bibliography==
 +
*''[[Combat Operations]]''
 
*''[[Technical Readout: 2750]]''
 
*''[[Technical Readout: 2750]]''
 
*''[[Technical Readout: 3050 Revised]]''
 
*''[[Technical Readout: 3050 Revised]]''
Line 47: Line 48:
 
[[Category:SLDF Combat Vehicles]]
 
[[Category:SLDF Combat Vehicles]]
 
[[Category:SLDF Royal Combat Vehicles]]
 
[[Category:SLDF Royal Combat Vehicles]]
 +
[[Category:Dragoon Combat Vehicles]]

Revision as of 16:42, 24 April 2010

Zephyr.gif
Zephyr
Production information
Manufacturer Grumman Industries
Mission Dragoon / Cavalry
Type Hover
Technical specifications
Mass 40
Armor Grumman CRT Ferro-Fibrous
Engine GM 185 Fusion Engine
Speed 146 km/h
Crew 3
Armament

3 x Medium Lasers
1 x SRM-6
1 x Small Laser

BV (1.0) 640[1]
BV (2.0) 889[2]


Description

Designed in 2620 to be a medium-duty, fast response, infantry support tank; the SLDF instead saw the Zephyr as the perfect support vehicle for its Chaparral Arrow IV artillery tank.

When the SLDF's Quartermaster Command was considering accepting the Zephyr for service, the SLDF vehicle corps was looking for a ground based design that could carry the successful Guardian ECM Suite to assist in setting ambushes for the Chaparral, with the SLDF ordering Grumman to add the system to tank. Powered by a GM 185 rated Fusion Engine and clad in seven tons of a Grumman CRT Ferro-Fibrous armor, the Zephyr boasts above average armor and speed for its weight and support role. [3]

Restarting production of the design after the unveiling of ComStar's Com Guards, after the Word of Blake took control of Terra Grumman received a large infusion of capital to develop a revamped C3i version in 3062. Further funding also resulted in Grumman expanding production via a new plant opened on New Earth in 3066 to keep up with increasing demand from the Word of Blake's Militia and Protectorate forces. [4]

Armament

Not intended for front-line combat, the primary weapons of the Zephyr are a trio of Sorenstein IV Medium Lasers mounted alongside the Alloran Target Acquisition Gear in the turret. Supporting firepower comes from from a Shannon SRM-6 rack mounted in the vehicle's nose supplied with two tons of reloads and a single rear mounted Harmon Small Laser to provide cover when fleeing combat. The Clan Invasion era model utilized different brands (a Thor SRM-6, Bundersweyth TAG and Bowie Electronics brand lasers) but otherwise carried identical weaponry to the Star League era models. [4]

Variants

  • Original - The original pre-Guardian Zephyr an carried extra half-ton of armor and an additional rear-facing SRM-2 with a ton of missile reloads. [3] [5]
  • Royal - The upgraded model used by the SLDF Royal units enhances the tank's support role by replacing the Short Range Missile launcher with a Narc Missile Beacon and two tons of ammunition. [6]
  • C3i - The first of the Blakist commissioned variants downgrades the SRM-6 rack for a Streak SRM-2 launcher, freeing up weight for C3i Computer.[4]
  • Pug - A less common variant among the Blakist's Protectorate forces, it drops all the standard equipment and weapons in exchange for a C3i system, a pair of turret mounted ER Medium Lasers and two nose mounted LRM racks. Its designation of Pug stems from the blockier appearance borne of these missile launchers. [4]

References

  1. Combat Operations, p. 106
  2. Technical Readout: 3050 Upgrade, p. 163
  3. 3.0 3.1 Technical Readout: 2750, p. 98
  4. 4.0 4.1 4.2 4.3 Technical Readout: 3050 Upgrade, p 162
  5. Technical Readout: 3050 Revised, p 202
  6. Technical Readout: 3075, p 169

Bibliography