Another day, another defense contractor popping champagne over a multi-million-dollar concrete pour in the American Heartland.
The media treats every newly announced military construction contract like an economic miracle. Headlines beam with local pride whenever a base or a classified hangar lands in a rural zip code. A contractor wins a deal to build a classified F-35 facility in Arkansas, local politicians cut ribbons with oversized shovels, and everyone assumes regional prosperity is guaranteed. Meanwhile, you can find similar stories here: Why David Friedberg is Wrong About Mamdani and the Grocery Store Spectacle.
It is a comforting illusion. I have watched defense firms blow millions on specialized footprint expansions that solve yesterday's operational headaches while ignoring tomorrow's structural obsolescence.
We are pouring reinforced concrete for a physical footprint that weapon systems are rapidly outgrowing. The lazy consensus says more square footage for the Joint Strike Fighter program equals industrial strength. The reality is far uglier. We are locking ourselves into a bricks-and-mortar mindset while software eats the aerospace supply chain. To explore the full picture, check out the detailed analysis by Harvard Business Review.
The Physical Obsession Trap
Defense procurement suffers from a dangerous nostalgia. When people picture a fifth-generation fighter program, they picture sprawling tarmac, climate-controlled bays, and armed guards standing outside heavy blast doors.
That imagery sells newspapers and secures congressional appropriations. It also blinds stakeholders to how modern military aviation actually functions.
The F-35 is not merely an airplane with wings and an engine. It is a flying data center. Its primary tactical advantage relies on the Operational Data Integrated Network, or ODIN, which replaced the notoriously clunky Autonomic Logistics Information System. When a contractor builds a classified maintenance or integration facility today, they are rarely building space for a wrench-turning mechanic to swap out a turbine blade. They are building secure server farms, tempest-shielded communications rooms, and classified processing nodes.
Yet, regional economic development boards evaluate these projects through a 1950s lens. They count jobs by the head rather than output by the byte.
Let us look at the mechanics of these facility awards. A prime contractor wins a competitive bid under federal acquisition regulations, promising local hiring spikes, specialized trade employment, and long-term economic stability. But specialized military construction projects are notoriously insulated from the local economy. The high-value engineering, specialized electronics integration, and cryptographic security installations are routinely imported. The local community gets the short-term payroll bump for earthmovers and drywall hangers, followed by decades of maintenance overhead on a building designed for a hardware-heavy paradigm that is already sunsetting.
Why the Classified Construction Model is Broken
To understand why this Arkansas facility win is being cheered for all the wrong reasons, we need to examine how the Pentagon defines infrastructure requirements.
Defense bureaucracy operates on linear projections. If the fleet size expands by a specific percentage, the required maintenance square footage must expand by a matching ratio. This model ignores efficiency gains, modular software updates, and predictive maintenance algorithms that reduce physical depot time.
Imagine a scenario where a software patch deployed overnight eliminates the need for a physical depot-level inspection sequence entirely. Suddenly, that multi-million-dollar specialized hangar sits underutilized for months.
Defense insiders know this dirty little secret. Utilization rates for classified facilities across the defense industrial base are often abysmal. Contractors love winning capital expenditure contracts because they guarantee a steady profit margin regardless of whether the building becomes a white elephant five years down the line. Cost-plus contracting models incentivize building bigger, not building smarter.
When a contractor secures a classified footprint project, they lock in revenue streams for construction management, security compliance infrastructure, and environmental remediation. They are monetizing the barrier to entry. Every layer of security classification required for a facility acts as a moat against competition, allowing the primary contractor to inflate subcontracting costs without fear of market correction.
The public thinks this is about national defense capability. It is often about corporate revenue maintenance.
The Supply Chain Delusion
Proponents of these regional defense investments argue that dispersing sensitive infrastructure across states like Arkansas protects the defense industrial base from localized disruptions.
This argument falls apart under basic logistics scrutiny.
An F-35 facility is not an independent island. It relies on a hyper-concentrated supply chain where single-source vendors provide everything from specialized composite materials to proprietary turbine cooling coatings. Building a classified hangar in the middle of Arkansas does nothing to solve the fragility of a supply chain where a single factory fire in Ohio can halt final assembly lines nationwide.
Worse, geographic decentralization without digital integration creates information silos. When maintenance data, telemetry, and diagnostic logs are funneled through localized classified facilities with legacy hardware architectures, the feedback loop between the flight line and the software developers slows down.
In modern air combat, the speed of code deployment matters infinitely more than the thickness of the concrete bunker housing the jet. If an adversary can iterate electronic warfare algorithms in weeks while our maintenance infrastructure requires months of physical security clearance processing and bureaucratic sign-offs to update a test bench, the concrete is just an expensive tombstone.
Dismantling the Economic Development Myth
Local officials view defense contracts as free money. Tax incentives, infrastructure write-offs, and municipal support are rushed out to lure contractors.
Let us be brutally honest about the return on investment.
Specialized defense construction creates temporary economic distortion rather than sustainable growth. Once the ribbon is cut, the specialized labor force moves on to the next project. The remaining permanent staff consists of high-clearance technicians and administrative personnel whose salaries are funded entirely by federal tax dollars. This does not seed a vibrant, self-sustaining regional economy; it creates a company town dependent on the federal budget cycle.
When federal defense priorities shift—as they inevitably do when the Pentagon pivots toward peer-to-peer conflict doctrines, uncrewed autonomous systems, and distributed maritime operations—those specialized facilities become liabilities. You cannot easily repurpose a tempest-shielded, classified vault for commercial manufacturing or logistics. It sits vacant, a monument to poor strategic foresight, while local taxpayers are left holding the bag for municipal infrastructure upgrades built to service a transient workforce.
The Contrarian Playbook
If we want to fix how defense infrastructure is planned, we have to stop celebrating square footage.
First, tie facility contracts to modularity metrics. If a contractor cannot demonstrate that a building can be reconfigured for dual-use technology or updated without tearing down reinforced interior walls, disqualify them.
Second, prioritize edge-computing mobility over fixed-site construction. The future of tactical aviation support is expeditionary. Instead of sinking hundreds of millions into monolithic installations in fixed locations, the defense budget should reward agile, containerized, rapidly deployable maintenance nodes that can be moved at a moment's notice.
Third, stop letting contractors grade their own homework on capacity utilization. Independent defense analysts need to audit the actual throughput of these classified facilities against their projected utility.
We do not need another fortified hangar in the Ozarks. We need an industry that stops building physical monuments to yesterday's wars while our adversaries out-software us in the present.
Stop cheering for the concrete. Start asking what happens when the software makes the building obsolete.
