Ravenclaw VTOL

Pages: 1
Foxhound
06/08/03 01:04 PM
67.74.153.186

Edit Reply Quote Quick Reply
BattleTech Vehicle Technical Readout
VALIDATED

Type/Model: Ravenclaw
Tech: Inner Sphere / 3060
Config: V.T.O.L.
Rules: Level 2, Standard design

Mass: 30 tons
Power Plant: 70 Ceres I.C.E.
Cruise Speed: 75.6 km/h
Maximum Speed: 118.8 km/h
Armor Type: Durallex Standard
Armament:
1 Valiant Catapult Arrow IV System
Manufacturer: Ceres Metals Industries
Location: Victoria
Communications System: Ceres SuperComm 3
Targeting & Tracking System: Ceres/Maladev 3

==Overview:==
One of the most effective weapon systems on the battlefield today is the Arrow IV Missile System. Essentially a large guided missile that relies on a spotter, the Arrow IV represents some of the most accurate artillery available to commanders. The launchers are typically found on support vehicles far behind the frontlines. However, the vehicles are unable to deal with rough terrain as the forces they support, at least without becoming bogged down or relying totally on a road system.

With the unlocking of the secrets of the Helm Memory Core, the Arrow IV once again found its way onto the battlefield. Capellan Confederation engineers first saw the advantages of mounting such an effective weapon system on a BattleMech, and put the Arrow IV on a Catapault chassis. Other houses followed suit, (e.g. House Kurita's O-Bakemono). While the BattleMech is an ideal platform given its versatility, but it has been noted that BattleMechs are very expensive and resource intensive.

At the same time Sun-Tzu Liao instituted his reforms in the military and civil sectors, Capellan military planners began looking at way to get the most out of their meager resources. As much as it pained the BattleMech-minded upper eschelons, even they had to admit that BattleMechs are wasted in the role that Arrow IV carriers have. It was put to the military contractors to find a solution.

Ceres Metals put forth the most unusual, yet winning, idea. While other companies attempted to mate the Arrow IV with hover, tracked, or wheeled vehicles, all new comers either ended up being too expensive, or faced the same limitations from terrain as their currently manufactuered cousins. However, VTOLs face few terrain obsticles, giving them superior ability to deploy immediately to trouble spots.

When the head of the design team presented the design to the Military Procurement Selection Board, he stated that the VTOL would "give claws to the Raven", referring to the light BattleMech that Capellan forces would use as the primary spotter for the incoming Arrow IV strikes.

==Capabilities:==
The Ravenclaw is built around the Valient Catapault Arrow IV Missile System. This system has a proven battlefield record, and with the new submunitions now available to CCAF troops, is just that much more of a threat to enemies of the Capellan Confederation. With the ability to carry ten salvos of Arrow IV strikes before needing to reload, the Ravenclaw can stay on station for extended periods in support of frontline troops.

Of course being a support weapon, this means the Ravenclaw did not need much armor, with the thinking being that the Ravenclaw will seldom be a target. As a result, only 1.5 tons of standard armor is mounted. Although Ferro-Fibrous Armor was available, the desire to cut costs and use fewer resources meant that standard armor was chosen. As with nearly all other systems, Ceres used their own designed and built armor rather than contract out for a different manufacturer.

The top speed of nearly 120 Kilometers Per Hour allows the Ravenclaw to follow the rapidly changing battlefield, and to act as a "fire brigade" of sorts. Commanders can send Ravenclaws to where they are needed and then rapidly shift them to another sector if necessary. The speed also allows the Ravenclaw to escape from any trouble spots.

Coupled with the high speed, the VTOL capabilites make terrain almost a non-issue for CCAF planners when tasking Ravenclaw missions. With the ability to cross over woods, rivers, rocky, and other terrain unsuitable for ground vehicles, the Ravenclaw can go almost anyplace BattleMechs can go.

Even with the advantages of the Ravenclaw, mission planners need to take into account weather. Ravenclaws have proven highly suceptable to crashing in bad weather. This is most likely due to the Arrow IV launcher's sheer size. Tests and simulations show that the launcher acts almost like a sail when hit by wind and can cause the pilot to lose control when he tries to over-compensate for wind resistance. Another issue is the use of an internal combustion engine. This limits overall effective range, and requires planning for refueling. This also effects crash survivability when the Ravenclaw bursts into flames or explodes following an otherwise survivable crash.

One quirk that has arisen in early production models is that whenever the Arrow IV launcher is used a burst of static emits from the communications system for approximately ten seconds. While the problem seems to have been corrected in later models, the refit kits sent to correct the initial runs have only a 45% rate of correcting the problem. Ceres is investigating.

==Battle History:==
Despite the material support and intelligence the Word of Blake gave the Capellan Confederation, House Liao did not feel so obliged to allow the Blakists to simply run rampent at will. In June 3065 the Maskerovka found out that a large supply cache was being hidden in an uninhabited system within the Confederation borders. The Third MacCarron's Armored Cavalry was sent to deal with the Blakists. Along with them was a full battery of Ravenclaws.

The Ravenclaws were kept in reserve, mostly waiting for targets of opportunity. When a spotter unit would need it, a few Arrow IV missiles woul be fired to break up a concentration of WoB troops, or eliminate some point of resistence. Given the terrain difficulties, the normal Arrow IV support vehicles would not have been able to keep up.

On the 3 July, elements of the 1st Battalion of the 3rd MAC stumbled into a main body of WoB Battlemechs trying to flank the MAC forces by using the mountainous terrain as cover. Depsite being some 50 kilometers away, the detachment of Ravenclaws were dispatched in the direction of the 1st Battalion. While the 1st Battalion was taking moderate casualties while keeping the WoB forces from advancing, the Ravenclaws were able to get into position. Once the Ravens and other TAG equipped Battlemechs began to direct their fire, the sheer volume of Arrow IVs the Ravenclaws unleashed simply devestated the WoB troops. While the survivors broke at the time, they eventually surrendered. the Blakist commander told his Maskirovka interrogator that he believed he had been faced by at least a regiment of Arrow IV equipped vehicles, never believing it was only a swift-moving battery.

==Variants:==
Due to the specialized nature of the Ravenclaw, no varients are planned.

Several Ravenclaws have been lost in combat or accidents with salvage ending up in the hands of enemy states. All of the Successor States, as well as the three major Periphery states, and ComStar/Word of Blake are expected to field their own versions shortly. While their versions are just now going through the field trial process, they are expected to be deployed shortly. Any differences between the Ravenclaw and enemy versions is likely to be minimal. While the designations of most are unknown, the Davion version is known as the Catapault.

==Notable Vehicles & Crew:==
Mosquito 3
This Ravenclaw, currently attached to Warrior House Dai Da Chi is remarkable for being known as a crew killer. So far it has killed three crews in crashes that were not bad enough to scrap the vehicle (in fact all three times recovery crews were suprised it had any damage at all) and three crews in cabin fires that were started without an anttributable reason. While no commander would dare scrap the vehicle for being haunted, several members of the warrior house have suggested it meet with some kind of accident (one said it should fall off the dropship the next time the unit deployed).

==Deployment==
Given the speed and ability to conquer terrain, it seems suprising that the Ravenclaw is not issued to battalions, but rather kept as a regimental asset. Standard Arrow IV artillery batteries are being replaced on a one to one basis. Individual lances are then attached at the battalion level with control remaining at the regimental level in case the Ravenclaws need to be rapidly redeployed. Often, a lance of TAG-equipped BattleMechs or vehicles are mated with the Ravenclaws, but spread around the battalion (normally attached to each company).

With the Ravenclaw being a relatively new unit, it is becoming suprisingly common in frontline units. While none have yet been spotted in reserve or militia units, most frontline BattleMech regiments have at least a lance worth. The highest concentration is in the MacCarron's Armored Cavalry, with each regiment having a whole battery of Ravenclaws and each battalion having at least one dedicated Ravenclaw.

None are currently in mercenary units, but Ceres has recently been granted permission to begin selling Ravenclaws to long-term Capellan mercenaries once all frontline Capellan units are equipped. Rumors abound of several Ravenclaws being in the armies of the other Trinity Alliance states.

--------------------------------------------------------
Type/Model: Ravenclaw
Mass: 30 tons

Equipment: Items Mass
Int. Struct.: 15 pts Standard 0 3.00
Engine: 70 I.C.E. 0 4.00
Cruise MP: 7
Flank MP: 11
Heat Sinks: 0 Single 0 .00
Cockpit & Controls: 0 1.50
Crew: 2 Members 0 .00
Rotor Equipment: Main/Tail Rotors 0 3.00
Armor Factor: 24 pts Standard 0 1.50

Internal Armor
Structure Value
Front: 3 8
Left / Right Sides: 3 5/5
Rear: 3 4
Rotor: 3 2

Weapons and Equipment Loc Heat Ammo Items Mass
--------------------------------------------------------
1 Arrow IV System Front 0 10 2 17.00
--------------------------------------------------------
TOTALS: 0 2 30.00
Items & Tons Left: 9 .00

Calculated Factors:
Total Cost: 1,370,000 C-Bills
Battle Value: 654
Cost per BV: 2,094.8
Weapon Value: 104 / 104 (Ratio = .16 / .16)
Damage Factors: SRDmg = 12; MRDmg = 12; LRDmg = 12
BattleForce2: MP: 7V, Armor/Structure: 0 / 1
Damage PB/M/L: 1/2/2, Overheat: 0
Class: VA; Point Value: 7
Specials: artA
CrayModerator
06/08/03 03:38 PM
65.32.253.120

Edit Reply Quote Quick Reply
VTOLs and Arrow IVs always mix well, though the result tends to be fragile and slow as far as VTOLs go. Good, cheap design.
Mike Miller, Materials Engineer

Disclaimer: Anything stated in this post is unofficial and non-canon unless directly quoted from a published book. Random internet musings of a BattleTech writer are not canon.
Karagin
07/24/07 05:52 PM
24.26.220.4

Edit Reply Quote Quick Reply
Nice any chance of getting the HMVee file for this one?
Karagin

Given time and plenty of paper, a philosopher can prove anything.
Tripod
07/25/07 01:16 AM
192.91.75.29

Edit Reply Quote Quick Reply
does anyone ever do artwork for the units they design? i'd love to see what this thing looked like...
TBA
Karagin
07/25/07 01:49 AM
24.26.220.4

Edit Reply Quote Quick Reply
I would for mine, but my drawing skills aren't up too it.
Karagin

Given time and plenty of paper, a philosopher can prove anything.
Pages: 1
Extra information
0 registered and 182 anonymous users are browsing this forum.

Moderator:  Nic Jansma, Cray, Frabby, BobTheZombie 

Print Topic

Forum Permissions
      You cannot start new topics
      You cannot reply to topics
      HTML is disabled
      UBBCode is enabled

Topic views: 5951


Contact Admins Sarna.net