What military vehicle retirement was a mistake?

For the U.S., I’d put the early rush to retire a lot of M113 variants near the top—not because the M113 is “good” in a modern peer fight, but because armies repeatedly rediscover the value of cheap, ubiquitous, easily modified utility carriers.

Historically, militaries that do well in long wars keep a large “second line” of practical vehicles for command posts, mortar carriers, ambulance roles, battlefield taxis, and logistics in threatened areas. WWII is full of examples where the glamorous replacement didn’t arrive in sufficient numbers, and doctrine quietly slid back toward what was available.

In the Cold War, the M113 became the Roman legionary mule of mechanized forces: not the centurion’s parade piece, but the thing that actually shows up everywhere. When you strip those roles away too quickly and bet on a smaller fleet of exquisite platforms, you often create gaps in mass and sustainment.

If I had to summarize the lesson: retire “line” vehicles when needed, but be careful retiring the low-cost workhorses before you have a true like-for-like replacement for all the unsexy tasks. (And yes, sources like Zaloga’s armored vehicle histories and various GAO readiness reports keep circling back to this theme: capability isn’t just lethality; it’s coverage and availability.)

I’m going to answer from the “field reality” angle: retiring the HMMWV too fast (or pretending everything could jump straight to JLTV) created pain in the ecosystem.

Humvees weren’t perfect—protection was a known issue—but they were simple, widely understood, and had mountains of accessories, mounts, soft kits, comms trays, cargo solutions, etc. The moment you shift to a heavier, more complex fleet, you change what people can carry, how they stage gear, what fits in aircraft, what gets recovered easily, and what your mechanics can do quickly.

A better approach would’ve been keeping a larger modernized Humvee pool for rear-area, training, and low-threat roles while fielding JLTV where it actually matters. It’s like boots: you don’t issue everyone the heaviest “best” boot for every environment—sometimes you need the reliable, easy option that you can maintain everywhere.

From my time in, the “mistake” wasn’t one single retirement, it was the whiplash: we’d get used to a vehicle, SOPs mature, drivers and mechanics get good, then the fleet changes and everyone is back to learning basics again.

If I had to pick one example people actually complained about day-to-day: pulling older trucks/utility vehicles out before the replacement pipeline was steady. You’d have periods where the unit had a mix of old and new, parts weren’t consistent, and training time got eaten up by logistics.

So yeah, retiring something can be right on paper, but if you don’t have enough replacements, instructors, spare parts, and recovery support, it feels like a mistake at the unit level. The “better way” is overlap longer than the PowerPoints say, and keep a reserve/training fleet that isn’t constantly being cannibalized.

The biggest mistake is the comforting myth that retirement decisions are purely technical. They’re political and budget-driven, and then people act shocked when capability gaps appear.

My pick: retiring proven platforms before replacements prove themselves at scale. If the successor is late, overweight, or maintenance-heavy, you’ve basically paid twice: once to lose readiness and again to “fix” the new thing.

If you want one concrete example, look at how often militaries mothball or cut fleets only to scramble later with “service life extension” programs. That’s an admission the retirement was premature. Keep the legacy platform in reserve, fund spares, and stop pretending every future war will be fought exactly as the latest doctrine brochure says.

Retiring or under-investing in early tactical UAV fleets too quickly was a quiet mistake—especially short-range ISR systems that are cheap and numerous.

Everyone loves the big, high-altitude, long-endurance drones, but the conflicts of the last decade showed how valuable “good enough” small ISR is for units: spotting, route recon, battle damage assessment, and just reducing uncertainty. When you cut older fleets without a solid sustainment and replacement plan, you create a surveillance gap at the exact echelon that benefits most.

What should’ve happened: keep older UAVs as training and attritable operational stock, and focus on modular payload upgrades (EO/IR, comms relays) rather than assuming a brand-new airframe is the only path forward. Also, plan for EW resilience—retiring a drone because it’s vulnerable is only smart if the replacement is meaningfully less vulnerable, not just newer.

I’ll nominate the M60A3 (and broadly, the rapid drawdown of older MBTs in some allied inventories) as a “mistake” in certain contexts. Not because the M60 is better than an Abrams or Leopard 2—obviously not—but because a lot of countries ended up with a capability cliff.

A late-model M60A3 with thermal sights, decent FCS, and a huge global parts ecosystem can still be relevant for deterrence, training, and second-line armored support. When you retire those fleets without a funded, sustained replacement, you don’t just lose tank-on-tank performance; you lose crew proficiency pipelines, maintenance culture, and mobilization depth.

A smarter move for many users would’ve been: keep a smaller modernized batch, store the rest properly, and invest in recovery, spares, and ammunition. “Retired” doesn’t have to mean “scrapped,” and armored mass still matters when wars become long and attritional.

In naval terms, a classic “retirement mistake” is pulling specialized mine warfare platforms too early or letting that capability atrophy.

Mines are cheap, scalable, and strategically disruptive. If you lose dedicated mine countermeasures hulls and don’t replace them with equally capable systems (whether unmanned or ship-based), you’re gambling your sea lanes on an assumption that the enemy won’t use one of the oldest naval weapons.

The better approach is layered: keep proven MCM vessels until the unmanned MCM ecosystem is mature in the real world (not just demos), and maintain trained crews and deployable packages. You can’t surge expertise overnight—especially with niche platforms that require specific maintenance, sensors, and operational choreography.

I’ll throw in the F-117 retirement as a “maybe” mistake. It wasn’t a dogfighter and it had limitations, but it was a uniquely low-observable strike tool with a track record.

The argument for retiring it made sense—maintenance, specialized fleet, shifting budgets—but the flip side is that stealth strike capability is never “extra.” When you retire a niche aircraft that does one job exceptionally well, you need to be certain the replacement covers the same mission set with the same availability and cost realism.

I’m not saying keep it forever, but a longer overlap as a training/aggressor-style stealth exposure platform (or limited operational reserve) might have paid off, especially as integrated air defenses evolved. Fleet diversity can be an advantage if you can sustain it.

Not an expert on every platform, but from the recruiting/training side I’ve seen how vehicle retirements ripple into personnel pipelines.

When a vehicle disappears quickly, schools have to rewrite courses, instructors retrain, simulators update, and units lose “common experience.” That can make a retirement feel like a mistake even if the new vehicle is objectively better.

If someone’s new to this topic, I’d ask: was the platform retired before the force had enough trained maintainers/drivers/crews for the replacement? If yes, that’s often where the real capability dip happens. A phased transition with a stable training fleet is usually the least painful.

For SOF-adjacent stuff, I think the mistake is retiring or neglecting “boring” mobility platforms that are easy to customize. Special operations often need modular, low-profile, quickly fielded vehicles more than they need the newest high-end fleet-wide solution.

There are times when older 4x4s, light trucks, and certain helicopters remain valuable because they’re adaptable: mounts, comms, extra fuel, different tires, different armor packages depending on mission. When those platforms go away, the replacements can be too standardized, too heavy, or too scarce.

The best practice is to keep a flexible mix: a small number of exquisite assets plus a larger pool of reliable, mod-friendly vehicles you can tailor per theater and partner force needs.

I look at retirements through the lens of “what keeps people moving and resupplied when things get ugly.” So I’ll say retiring simple, field-repairable vehicles too fast can be a mistake.

If a vehicle is forgiving—basic tools, common parts, tolerant of bad fuel/maintenance—it has value in austere environments. Newer vehicles can be fantastic, but if they’re maintenance-sensitive and you don’t have the support tail, they can turn into hangar/yard ornaments.

The better answer is balance: keep some rugged old platforms for training, disaster response, rear-area tasks, and contingency stock. In a real crisis, the ability to improvise repairs and keep rolling matters as much as specs.

A lot of “mistake retirements” are actually budget signaling: retire X to fund Y, then Y slips, and you’re left with a gap. The strategic mistake is assuming the security environment will stay permissive during that gap.

A good example pattern is when nations divest heavy forces (tanks, artillery, bridging, air defense vehicles) to chase expeditionary priorities, then a conventional deterrence problem returns. Rebuilding that capacity takes years, not months.

So my answer is less about a specific model and more about timing and industrial base. If retirement decisions don’t consider surge production, stockpiles, allied interoperability, and training throughput, they’re fragile. A “mistake” is often just a plan with no resilience.

From an engineering/logistics standpoint, I’d argue retiring bridging and combat engineer vehicles without a mature replacement is one of the most damaging mistakes you can make.

People fixate on shooters, but mobility is a system: route clearance, gap crossing, earthmoving, recovery. If your bridge launchers, engineer tractors, and recovery vehicles get cut, your fancy combat vehicles may not get where they need to go—or they get there late and exhausted.

What should be done instead is boring but effective: life-extension, spares forecasting, and keeping enough training sets so units can actually practice wet-gap crossings and rapid mobility tasks. Capability that isn’t rehearsed might as well be retired.

This is a really good question and I’m still learning, so sorry if this is basic: how do you tell the difference between “retired because obsolete” and “retired because budgets/politics”?

Also, when people say “keep it in reserve,” is that actually practical? Like do they store the vehicles ready-to-go, or do they end up missing parts and not usable?

If anyone has examples where a vehicle came back successfully after retirement (or storage), I’d love to read about that.

In force-structure terms, the mistake is retiring vehicles that provide cheap mass before you’ve proven you can replace that mass with something else (numbers, allies, autonomy, or mobilization).

Wargames consistently punish “thin” forces. High-end platforms are great, but if you can’t cover frontage, rotate units, absorb losses, and sustain tempo, you lose initiative. So I’d flag retirements that reduce fleet size dramatically in exchange for a small number of exquisite vehicles.

What I’d do: keep legacy platforms in a tiered readiness model. Front-line units get the newest kit; reserve/territorial units keep older vehicles; training gets dedicated fleets; and you invest in sustainment so the whole structure doesn’t collapse if procurement slips.

I think a modern “retirement mistake” is treating unmanned ground systems and robotic support vehicles as science projects—then shelving them—rather than keeping incremental programs alive.

When you retire early prototypes or cancel small fleets, you lose operator familiarity and you lose the feedback loop that actually makes autonomy useful: convoy following, remote resupply, casualty evacuation support, route reconnaissance. Those are boring missions where robotics can save lives and reduce workload.

Instead of big-bang replacements, you want continuity: keep limited fielded numbers, iterate sensors and autonomy modules, and integrate them with existing vehicles. The mistake isn’t retiring one robot; it’s repeatedly resetting the learning curve.