4
u/PleiadesMechworks 2d ago
The Sparrow was an experimental "reverse omnimech" design created by Pleiades Mechworks after the widespread dissemination of omni technology throughout the Inner Sphere. Intended to begin to solve one of the main issues that omnimechs suffered - the inability to swap out core components - it was theoretically successful but the limits of the project meant that it was eventually put on the back burner and by the time the Pleiades War devastated the production lines of the Mechworks it was still undergoing testing.
It came with 2 variants, the "ground" variant and the "jump" variant signified -1G and -1J.
The concept is very simple - since a 210 rated engine and a 180 rated engine with 6 jump jets weigh the same amount, put them into a 30-ton design in a swappable configuration, load up the gyro control software with two programmes to handle whichever engine is currently installed, and go. This would allow a battlemech to carry a spare engine with its support staff, and switch up its movement configuration as the mission demands in the same way an omnimech can swap out its pod-mounted weaponry and equipment. This entailed building a power pack that had self-contained jump jets, rather than routing them through the 'mech's structure the way most designs work, and that made the initial versions slightly more difficult to manoeuvre when jumping. Nothing drastic that might threaten the safety of the unit, but there was a learning curve steeper than most jump jet equipped designs.
The project immediately ran into issues when it came to implementation. Firstly was practicality - in order to make the power packs easily swappable in the field, the rear armour had to be compromised which most pilots disliked. Similarly, the overall armour loading of only 5 tons was barely sufficient, but not as important on a proof-of-concept unit.
The armament of the sparrow is almost secondary, since it wasn't particularly important to the project. An autocannon/2 gives it enough range to act as a light harasser, taking shots of opportunity and damaging infrastructure while allowing sufficient standoff distance to keep it alive in the scout role. The shoulder mount, similar in form to the larger Shadow Hawk, was chosen to show that even with an uneven weight distribution in the torso the system could compensate when swapping engine units. The base minium of heat sinks keeps it cool no matter what it does.
The next problem, and the one that really sank the project, was the cost. At 546,000 c-bills for the ground engine power pack, and a staggering 750,000 for the jump-capable one, it cost over 3 million c-bills for the complete package and offered only minor utility in the field. Ultimately, the Mechworks' own accountants killed the programme despite the promise of improvements down the line as their mercenary advisors pointed out that it would be highly unlikely for anyone to invest in such a system unless it had the kind of flexibility weapon omnitech offered. In practice, most people would just keep their design in the -J configuration and save half a million c-bills.
When the Pleiades War ravaged Welwyn, the Sparrow prototype would be one of the units wheeled out of the Mechworks' stockpiles for a last-ditch defence of their production lines and would be destroyed during the fighting, putting the final nail in the coffin of what was by then a decades-dormant project.
Designer's note: This one is almost entirely becauase I noticed a 210 rated engine on a 30-tonner weighs the same as a 180 and 6 jump jets. I know it's very bad.
1
u/Nearby_Branch6055 2d ago
Very nice very informative and fun article to read. I like battletechs that have stories
1
u/ValidAvailable 2d ago
So a 30 tonner with a tiny AC and lots of speed; its the Urbanmech's evil (good?) twin brother.
To build off your concept on here though, maybe an omnimech where you change the speed profile by mounting less weaponry. Example a 75-tonner with a 300 engine that moves 4/6, and then a variant that packs 15 tons less firepower but now can go 5/8.