Skip to main content
The Imagined Battlefield — Military History Beyond Reality Lorecasts + Wiki

Sitewide search

Search lorecasts and the wiki

Search 1000 wiki articles, 1000 episode records, and all universe pages.

Begin typing to search the site.

BattleMech hall of fame

Locust, Wasp, and Stinger

The Locust, Wasp, and Stinger became three of the most widespread light BattleMechs in human space because they solved ordinary military problems efficiently.

The Locust emphasizes exceptional ground speed, making it valuable for reconnaissance, screening, pursuit, and communications work. The Wasp and Stinger add jump capability, allowing them to cross broken terrain, urban obstacles, forests, and elevation changes that complicate movement for conventional vehicles. This episode compares how these 20-ton machines survived centuries of warfare despite limited armor and modest weaponry. Their longevity came from relatively straightforward designs, widespread production, established maintenance knowledge, and roles that every army continually needed filled. Light ’Mechs are often portrayed as disposable, but experienced pilots understand that survival depends on avoiding the kind of engagement heavier machines were built to win. The Locust, Wasp, and Stinger became ubiquitous not because they dominated battlefields, but because armies always need something fast enough to find the battlefield first.

01

Design origins and battlefield requirement

A reconnaissance lance does not need to destroy the enemy to change a battle. It only needs to find the enemy first, identify the direction of movement, and survive long enough to report. For centuries, that mission often fell to a twenty-ton BattleMech with light armor, modest weapons, and a pilot who understood that curiosity could be fatal. The machine might be a Locust racing across open ground, a Wasp jumping onto a ridge, or a Stinger clearing a treeline in a single bound. None looked impressive beside an Atlas or a Marauder. Yet commanders who ignored these light machines often discovered that their own heavy units were marching toward an ambush already measured, mapped, and reported.

The Locust, Wasp, and Stinger became three of the most common BattleMechs in human history because they solved a problem every military shared. Armies needed scouts in numbers greater than they needed prestige machines. They needed couriers when communications failed, raiders that could cross difficult ground, rear-area security, and BattleMechs that smaller states could build and maintain. These designs were fragile and often assigned missions meant for heavier machines because none were available. Their survival did not prove that twenty tons was ideal for every battlefield. It proved that a useful design, produced widely enough, can outlive both doctrine and the governments that created it.

The demand appeared during the Age of War, after the Mackie demonstrated that BattleMechs could dominate terrain inaccessible to conventional armor. The first BattleMech was enormous, expensive, and strategically valuable, making it a poor answer to routine reconnaissance. A commander did not need one hundred tons of armor to inspect a river crossing or follow a withdrawing enemy. The Terran Hegemony needed machines that could range ahead of the main force and be produced in numbers large enough to cover multiple axes. The result was a family of competing ideas. The Wasp emphasized jumping mobility. The Stinger refined that approach for mass production. The Locust sacrificed jumping capability for raw ground speed.

General Mechanics introduced the first Wasp on Mars in the year twenty-four sixty-four. It was a primitive machine, but it achieved something no earlier BattleMech had done successfully. It used jump jets to lift itself over obstacles and reposition without following the ground beneath it. The early system was limited, and the first model carried primitive components that reduced speed, protection, and weapon capacity. Continued development produced the Wasp one A in the year twenty-four seventy-one. That model established the configuration recognized across later centuries: a twenty-ton scout with a medium laser, a two-tube short-range missile launcher, and enough jump capability to clear roughly one hundred eighty meters under favorable conditions.

The Wasp’s ground speed was respectable rather than exceptional. Its advantage was choosing routes unavailable to wheeled vehicles, tracked armor, and many BattleMechs. A Wasp could jump a stream, clear a wall, move between ridges, or escape a firing lane without retracing its path. In cities, forests, broken hills, and industrial districts, that vertical mobility complicated enemy planning. The pilot could observe, drop behind cover, and emerge elsewhere. The price was weight. Six jump jets occupied space and mass that might have supported armor, weapons, or a larger engine. The Wasp was mobile because it accepted that it would never be heavily protected.

02

Chassis, mobility, and protection

Its weapons supported escape and self-defense rather than prolonged combat. The arm-mounted medium laser provided reliable fire without consuming ammunition. The short-range missile launcher added a limited burst of destructive power and allowed specialized ammunition when available, but the launcher also tied the machine to a supply chain. Three tons of armor protected the chassis. That was enough to defeat fragments and light fire, but repeated hits in the same location could reach internal systems quickly. Heat was rarely the Wasp’s principal problem. A pilot could use the laser and missile launcher without overwhelming the cooling system, although repeated jumping and firing still demanded judgment. The larger problem was remaining close enough to shoot without remaining close enough to be hit.

Wasp pilots developed aggressive methods to compensate for limited weapons, including physical attacks after a jump. That practice exposed a serious design flaw at the Battle of Imbros the Third in the year twenty-five eighty. Early lower-leg actuators lacked the stress-resistant materials needed to survive repeated jump-kicks. Machines that attempted the maneuver could suffer catastrophic leg failure. The defect was eventually corrected across the surviving fleet, but the incident revealed a recurring truth about light BattleMechs. Their mobility encouraged pilots to attempt maneuvers that placed extraordinary stress on structures built with very little reserve. A successful jump could save the machine. A badly judged landing could turn a scout into salvage before the enemy fired.

The Wasp nevertheless spread farther than almost any BattleMech ever built. General Mechanics created the concept, but production migrated across the Inner Sphere and Periphery. Plants tied to the Free Worlds League, Lyran Commonwealth, Federated Suns, Taurian Concordat, Magistracy of Canopus, and Outworlds Alliance produced Wasps or local versions. Even after centuries of industrial destruction, factories kept building them. The design was established, repair knowledge was widespread, and customers ranged from major armies to planetary forces unable to afford better scouts. A procurement officer rarely receives praise for ordering another Wasp. The officer does receive questions when no scout is available.

Earthwerks introduced the Stinger in the year twenty-four seventy-nine as a direct competitor to the Wasp. The resemblance was close enough that General Mechanics pursued a copyright case. The dispute lasted roughly two decades while Stinger production continued, which may be the most BattleTech outcome possible. Lawyers argued over intellectual ownership while factories delivered the machine by the thousands. General Mechanics eventually abandoned the case as costs rose. The Terran Hegemony accepted both designs because its need for scouts exceeded the distinction between them, and two production streams were more useful than one legally tidy monopoly.

The standard Stinger three R matched the Wasp’s basic mobility. It could run at roughly ninety-seven kilometers per hour and jump about one hundred eighty meters. Its armament replaced the Wasp’s missile launcher with two machine guns supporting a single medium laser. That reduced its ability to damage armored targets, but it made the Stinger effective against exposed infantry and soft vehicles. The machine guns generated little heat, and the standard cooling system easily supported the weapons. A Stinger pilot therefore spent less time negotiating thermal limits and more time deciding whether the target justified closing to machine-gun range. Against infantry, that could be devastating. Against a heavier BattleMech, it was usually an invitation to reconsider the mission.

03

Weapons and tactical role

Three tons of armor gave the Stinger no more tolerance for concentrated fire than the Wasp. Survival depended on movement, terrain, and the enemy’s inability to spare serious weapons for a minor target. The cockpit was notoriously cramped, and some pilots needed help climbing out after a mission. As purpose-built trainers became scarce during the Succession Wars, Stingers increasingly served in academies. Simple weapons, forgiving heat, hand actuators, and jump jets exposed students to essential skills. The cockpit taught one more lesson: military procurement does not promise comfort merely because a machine may remain in service for centuries.

The scale of Stinger production explains its endurance. More than two hundred thousand were reportedly built between its introduction and the end of the Amaris Civil War. It became the second-most-produced BattleMech after the Wasp. The Succession Wars consumed that inheritance with astonishing efficiency. By the year thirty twenty-five, estimates placed only about five thousand Stingers in service. That was a catastrophic reduction, yet five thousand surviving machines still made the design common by the standards of an age in which entire factories and technical traditions had vanished. Earthwerks remained a major producer, while factories in the Lyran Commonwealth and several Periphery states continued to support the design. Quantity had become a strategic form of protection.

Bergan Industries introduced the Locust one V in the year twenty-four ninety-nine. It was another twenty-ton reconnaissance BattleMech, but its shape and method differed sharply from the humanoid Wasp and Stinger. The Locust used a compact, birdlike chassis without hand actuators and carried a larger engine. It could reach roughly one hundred thirty kilometers per hour, making it much faster on the ground than its rivals. It could not jump. On plains, roads, rolling terrain, and wide valleys, it could cover distance rapidly and withdraw before heavier units closed. In dense cities or broken mountains, a Wasp or Stinger could cross obstacles that forced the Locust to detour.

The standard Locust carried a medium laser in a forward turret and two machine guns supplied from a common ammunition reserve. Four tons of armor gave it slightly more protection than the Wasp or Stinger, but the difference did not transform it into a line fighter. A direct hit from a major weapon could still cripple the machine. The Locust’s speed was therefore not an enhancement to its defense. Speed was its defense. The pilot had to keep moving, avoid predictable routes, and resist the urge to exchange fire simply because a target appeared on the display. The medium laser could discourage another scout. The machine guns could break up infantry in the open. Neither justified remaining in front of a heavy BattleMech whose gunner had solved the firing problem.

A Locust was most dangerous when its pilot understood timing. Three machines could harass an isolated opponent, force it to turn, threaten vulnerable rear armor, or delay it until friendly support arrived. A single Locust could draw attention away from another axis, chase down a convoy, screen a retreat, or maintain contact with an enemy column. These were useful tasks, but none required the Locust to win a fair duel. Fair duels are generally an avoidable luxury for reconnaissance forces. The design’s lack of hands also limited physical interaction with equipment and made close combat less flexible than in the Wasp or Stinger. The Locust was built to arrive, observe, strike briefly, and leave. Problems began when a commander remembered only the striking.

04

Variants, operators, and campaign use

Bergan produced Locusts from several factories before the fall of the Star League, and more manufacturers joined during the Succession Wars. Plants across major states and the Periphery built the machine, while pirates, corporate security forces, militias, mercenaries, and national armies bought or salvaged examples. Wide production lowered costs and made components easier to find. A Locust far from its original factory could often be restored with familiar parts and local substitutions. Continuous production mattered more than theoretical excellence. A superior scout in one regiment is an interesting capability. A good-enough scout supported by factories across known space becomes part of the military landscape.

Placed side by side, the three machines represented different answers to the same problem. The Locust was the fastest over favorable ground and carried the most armor of the standard models, but obstacles could channel it. The Wasp had the most flexible standard weapons mix, combining an energy weapon with short-range missiles, while accepting ammunition dependency. The Stinger emphasized simple anti-infantry firepower and shared the Wasp’s jumping mobility. Both humanoid machines could use their hands for tasks beyond firing weapons, an advantage in recovery, field engineering, and improvised operations. None carried sophisticated reconnaissance electronics by later standards. Their most important sensor remained the pilot’s judgment, supported by communications equipment and whatever intelligence network the unit could maintain.

Reconnaissance is not simply seeing something. It is converting observation into useful information. A Locust behind enemy lines accomplished little if terrain blocked its transmitter or headquarters mistook a real report for a decoy. A Wasp on a ridgeline needed to identify unit type, direction, and timing rather than merely announce contact. A Stinger shadowing a retreat had to know when continued pursuit risked capture. The light BattleMech was one link in a chain including maps, signals personnel, analysts, commanders, artillery, aerospace patrols, and the troops expected to act. The machines were common because armies needed many links. Their pilots survived when commanders remembered the chain.

In combined-arms operations, these scouts performed work that heavier BattleMechs could do only at greater cost or with less flexibility. They screened flanks, checked bridges, escorted headquarters, hunted infiltrators, and provided security for artillery positions. They carried messages when jamming or damaged communications made radio unreliable. They raided supply points whose defenders were too weak to justify a heavier commitment. They pursued infantry and vehicles that could otherwise escape. They also served as forward observers, although doing so required communications discipline and a clear understanding of friendly artillery plans. A twenty-ton scout could create disproportionate effects by placing the right information in the right command post. It could also disappear in one artillery correction if it remained in the wrong observation post.

05

Strengths, limitations, and historical legacy

The logistical argument was equally important. These machines used mature components, modest weapons, and designs understood by generations of technicians. Standard engines and armor were less demanding than advanced systems used by later elite scouts. Ammunition needs were limited, especially for energy-focused variants. Recovery remained difficult because even twenty tons was beyond ordinary field towing, but a light chassis strained bridges, recovery equipment, and rough transport less than a heavy machine. DropShip capacity still depended on BattleMech bays, so a Locust did not create extra berths. It did reduce the mass technicians had to lift, brace, and repair. Logistics rarely makes a machine famous, but it often decides whether the machine returns to service.

Variants reveal how users adapted each chassis to local wars. Some Locusts traded machine guns for lasers to reduce ammunition dependence. Others carried long-range missiles for harassment or short-range missiles for close attacks, often sacrificing armor to make the weapons fit. Wasp variants replaced missiles with lasers, flamers, or machine guns according to faction needs. Stinger variants commonly exchanged the machine guns for a second medium laser, improving performance against armored targets while increasing heat and reducing anti-infantry utility. Later models used rediscovered Star League technology, improved armor, advanced electronics, and more capable weapons. The names remained familiar, but the mission packages changed. A designation could survive because the factory tooling survived, even when the battlefield around it had become unrecognizable.

The Succession Wars made all three designs symbols of scarcity as much as abundance. A newly assigned pilot might receive a machine older than the pilot’s family line, repaired with components from several manufacturers and carrying modifications never shown on the original plans. Light BattleMechs were often given to inexperienced MechWarriors because they were available, not because the assignment was safe. Speed and jump capability demanded judgment that beginners had not yet developed. Veterans knew when to break contact, how to use terrain, and how long an enemy gunner needed to settle a shot. Novices often discovered that a fast machine reaches a bad decision sooner. The designs were forgiving to maintain. They were not forgiving when employed as miniature assault BattleMechs.

Their commonness also shaped military culture. Heavy BattleMechs attracted noble heirs, famous mercenaries, and official portraits. Locust, Wasp, and Stinger pilots more often performed patrols that produced no dramatic story. They watched roads, checked settlements, escorted convoys, and returned with reports that prevented battles rather than won them. No single personality defined these designs. Their history belongs to thousands of anonymous MechWarriors and technicians. Wars are not sustained only by rare machines and famous commanders. They are sustained by ordinary units completing repetitive missions until one missed patrol, failed sensor check, or delayed report becomes the most important event on the map.

06

Military historian’s assessment

The technological renaissance after the Helm Memory Core did not make the three obsolete. It gave manufacturers new ways to update them. Endo steel structures, ferro-fibrous armor, improved lasers, electronic warfare systems, advanced missiles, and more efficient engines created models that were faster, harder to detect, or more dangerous. Some upgrades were sensible. Others placed expensive technology inside a chassis still vulnerable to a single heavy hit. The logic depended on the customer. A major state might prefer a purpose-built modern scout. A Periphery government with an existing production line could gain more by improving a familiar design. A mercenary command might accept any variant supported by available parts. Technical elegance remained subordinate to budgets, factories, and the machines already standing in the hangar.

Advanced enemies did not erase the need these BattleMechs served. Clan scouts and later Inner Sphere designs carried better sensors, firepower, and protection. They also cost more, required different parts, and were unavailable to many militias and border garrisons. The old machines remained useful because most military activity occurs below celebrated campaigns. A planetary commander still needed someone to inspect a canyon. A merchant consortium needed mobile security. A raiding force needed a rear guard. An academy needed machines students could operate and technicians could keep running. Strategic planners prefer standardized modern fleets. History usually provides mixed formations assembled from whatever survived the last budget cycle and invasion.

The reputation of the Locust, Wasp, and Stinger suffers when they are judged by the wrong standard. None was designed to trade fire with a heavy BattleMech. None could hold ground against determined combined-arms opposition. Their armor was thin, their weapons were limited, and their pilots lived close to the consequences of one accurate shot. Yet they were not failed combat machines. They were successful reconnaissance systems repeatedly misused as line combatants because war creates shortages faster than industry corrects them. Their wide availability encouraged commanders to spend them freely, while their low prestige made losses easier to accept on paper. The casualty report was less impressed by the distinction between an inexpensive scout and a valuable human pilot.

These three designs appeared everywhere because the mission appeared everywhere. Every state needed eyes forward, security behind, and mobility along the flanks. The Wasp brought jumping reconnaissance into practical service. The Stinger proved that a closely related machine could be produced on an immense scale and adapted for training and anti-infantry work. The Locust demonstrated the enduring value of speed, simplicity, and broad industrial support. Their greatest contribution was rarely the damage recorded after battle. It was the contact report that arrived in time, the ambush identified before the column entered it, and the enemy movement tracked long enough for someone else to act. The assault BattleMechs decided many engagements. The light scouts often decided where those engagements would occur.