The Unstoppable Force and the Immovable Object

What happens when an unstoppable force meets an immovable object? The riddle is usually posed as a logic problem. And in 2018, the United States Air Force ran this experiment. The unstoppable force was innovation: endorsed from the Secretary of the Air Force down, funded, and in a hurry. The immovable object was the bureaucracy that buys things, procurement. And the collision point, improbably, was the fixed-wing aircrew helmet.

One idea before the story begins, because it is the point of the story: the immovable object is not the villain. Procurement bureaucracies are an organization's immune system. They are skilled, careful, and built to protect the institution from exactly the kind of enthusiasm that innovation programs generate. The people inside them are good at what they do. What follows is not an account of bad actors. It is an account of what happens when the rules of the game change faster than the toolkit.

On any given day, tens of thousands of Air Force pilots and aircrew put on a helmet whose basic design had not been overhauled since 1981. Around that helmet, everything changed. The F-22 and F-35 arrived (fighters got the headlines, but bombers, tankers, and transports were adding mission systems of their own). Night-vision goggles, helmet-mounted displays, and cueing systems (the aiming technology that lets a pilot target a weapon by looking at something) migrated onto the pilot's head. Bolted, strapped, and counterweighted onto a shell that was never designed to carry them. A 2.2-pound helmet becomes roughly twenty-seven pounds of effective load in a 9G turn (nine times the force of gravity, a routine number in a fighter); the equipment hanging off it made the arithmetic worse, and decades of neck and back injuries followed. The fleet's fit range failed a changing force: as one Air Combat Command analyst later put it, the legacy helmet "was not originally designed to support advances in aircraft helmet-mounted display systems, causing pilots to fly with equipment not optimized for them, especially our female aircrew."

The Air Force knew all of this. Knowing was never the problem. For years the acquisition system tried to buy a replacement the way it knew how: study the problem, interview the users, write the requirements, publish the solicitation. An Air Force program manager for aircrew equipment summarized the helmet market this approach produced: "For years, the Air Force only had one vendor." The Air Force Research Laboratory's own account of the era is drier still: previous attempts at defining the aircrew helmet's requirement had "failed to gain much altitude." The helmet was not stuck because nobody cared. It was stuck because the process itself could not produce a buyable answer in a market it had never invited in. Technology was moving faster than specifications. That is not a helmet problem. That is a process problem wearing a helmet.

In August 2018, the AFWERX Vegas hub in Las Vegas, Nevada, helped the Air Force to invert the process.

Instead of writing requirements and then soliciting industry, it put thirty-five people in a room for three days to define the problem together. At the meeting were the program office and its engineers, fighter pilots and flight-equipment chiefs, the incumbent manufacturer (Gentex, which had supplied the fleet's helmets for decades), avionics firms, academics, and a contingent no traditional solicitation would ever have reached: motorsport and bicycle helmet makers, impact-science startups, even a sports-medicine expert from the NHL's Vegas Golden Knights, there to explain how a different industry thinks about protecting heads. The workshop produced the four problem areas that would define everything downstream: weight, stability under multiple interfaces, thermal management, and fit. And it produced a set of deliberate constraints: upgrade the helmet, not the aircraft; specify performance, not design.

After the workshop, instead of trying to generate a third several-hundred-page request for proposals, the AFWERX Challenge team produced a roughly thousand-word solution framework. The USAF New Helmet System Open Challenge read less like a solicitation than an invitation ("You may not even know at this stage if your technology could be used in a USAF helmet, please still submit your ideas"). It ran in public, on afwerxchallenge.com, where every submission was visible to every competitor. Five weeks later there were more than a hundred solutions on the board, from defense primes, universities, and companies that had never sold the government anything. An expert panel screened them against the program's formal performance parameters: openness and rigor, running together. Thirty-eight were invited to Las Vegas for a showcase event.

As one AFWERX Vegas facilitator put the contrast at the time: "Previously, it had taken the Air Force years to fully articulate a requirement and launch an RFP. It took us just a few weeks."

The program office had never believed a word of it.

Long before the showcase, in the early planning that preceded even the workshop, the proposed approach was so foreign to the program office that its people could barely contain their disbelief. A leader for the program office said so, directly, to the AFWERX Vegas team: "I don't believe in this process. It won't work." And: "The only reason I'm here is because the last two times we failed, and we can't take the blame for the next failure." The plan, from their side of the table, was refreshingly cynical: "I don't care about those other companies, just get me into a room with the top three so that I can beat them up on price." One manager offered a modest definition of success: "We've tried for years to get Bell Helmets to the table. If you even pull that off, I would consider this a success." And end users? "We've already talked to the end-users. We already know the requirements. We don't need new requirements."

Every one of those sentences is the immune system talking: an institution that had been burned twice, protecting itself the only way it knew. The challenge's designers made a choice that mattered more than any piece of process. They did not fight the skepticism. They designed a process that would let the evidence argue.

The showcase, held that November at an event space off the Las Vegas Strip, did not look like defense procurement. Thirty-eight solutions set up science-fair booths (no PowerPoint presentations, by design). Pilots, program-office engineers, testers, and decision-makers walked the floor. So did the public. A hedgehog-quill impact liner sat near a microphone mounted on a tooth; a Formula 1 helmet maker exhibited across from a biometric-sensor startup and a bicycle company's micro-adjustable fit system.

The format's designers called it a collision space, and the collisions were the product. Vendors who had arrived as competitors walked the floor as collaborators, asking each other questions no private proposal process would ever permit. In the days after the event, companies began signing non-disclosure agreements with one another to explore teaming. As the challenge's own record put it: "Teaming opportunities like this would not be possible in the traditional acquisition process by the U.S. Air Force, where proposals are submitted privately."

The government's evaluation team made its decisions immediately after the showcase. Not in months. In days, with initial prototyping awards measured in the hundreds of thousands of dollars (not millions). Ten companies were selected, organized into three teams. The incumbent, Gentex, would build one prototype. Aviation Specialties Unlimited partnered with Bell Racing (the same Bell the program office had spent years failing to reach) to build another. And seven companies that had entered the challenge as strangers (an aviation-helmet upstart out of the motocross world, the Rockwell Collins and Elbit display houses, a football-helmet company, a biometrics startup, a hearing-protection firm, and Specialized, the bicycle maker) merged into a single team to build a composite of the best technologies on the floor: a project the AFWERX Vegas team lovingly called the Franken-helmet.

Twenty weeks after the workshop, the program office's aircrew performance lead assessed the same process her office had doubted, on the record: "We have been able to reach many non-traditional defense companies, that until now have been unresponsive to traditional market research methods... We are executing our leadership's rapid-prototyping direction and bringing the future faster." Nine months after the workshop (a timeline in which, by the program's own history, a traditional effort would still have been drafting its RFP), twelve proof-of-concept helmets were delivered for testing.

Then the challenge did what a good front end should do: it handed off. Testing and evaluation for flight equipment is a known, rigorous, and largely necessary process (sled tests, windblast, ejection geometries, altitude chambers), and nothing about the challenge was designed to shortcut it. What the challenge changed was what entered that process: not a single incumbent bid deemed unviable, but a competed field of funded prototypes.

The field narrowed the way rigorous processes narrow things. By late 2021 two teams remained: the incumbent, and the coalition. In 2022, the Air Force selected the coalition's helmet: LIFT Airborne Technologies' AV2.2. Carbon-shelled, jaw-activated lighting, sized for the aviators the old fleet fit worst. In 2023 F-22 pilots flew with it. It went on to pass more than fifty environmental test events, including the first 600-knot ejection sled test ever passed by a fixed-wing helmet, and by 2025 it was operational with Air Force Special Operations Command crews. Its carbon shells came from Bell Racing's parent company (a detail the skeptics of 2018 could not have invented). The vendor the program office once defined victory as merely reaching is now in the fielded helmet's supply chain.

And the incumbent? Gentex took the next-generation design it built for the challenge to the Navy. And in 2026 it won that service's parallel helmet program. A market that two failed solicitations could not move now has two services fielding next-generation helmets from two challenge-shaped competitors. The challenge did not pick a winner at the incumbent's expense. It rebuilt the market for everyone in it.

The program office noticed. The same team that opened with "I don't believe in this process" closed by recommending the model to its leadership for wider use. One of its chiefs found the plainest words for what had changed: "AFWERX was able to leverage non-traditional industry partners that someone like me would not have the opportunity to interact with... AFWERX provided a collision space."

So what does happen when an unstoppable force meets an immovable object? Neither wins. That is the answer the helmet gave. Done with courage and conviction, the collision produces something better than either force alone: the institution's rigor, pointed at a field of options the institution could never have assembled by itself.

None of it was luck. Every beat of the story was designed: the problem defined with outsiders in the room before a single requirement was written; the invitation published where a specification would have stood; the evaluation mapped to formal performance parameters; the showcase engineered to force collisions; the awards made in days while conviction was hot. Change the nouns (helmet, hangar, hospital, warehouse) and the design holds. It is not a procurement trick. It is a structured and operated system of change, run once, in public, on one of the hardest buyers on earth.

At the showcase, a camera crew asked participants what was really happening on that floor. The last voice on the tape gave the answer that outlasts the helmet: "At the end of the day... we're going to produce a prototype helmet. But the real thing that's going on here is an idea of changing mindsets. It's about changing culture. And it's about being able to do significantly better when it comes to a world in which technologies continuously disrupt us."