Did the future of a trillion-dollar weapons program depend upon how a jet appeared? In the loftiest Joint Strike Fighter battle between Boeing’s X-32 and Lockheed Martin’s X-35, the solution was governed as much by engineering constraints as image and the X-32 lost on both accounts.

The X-32, built with a philosophy of manufacturing efficiency and commonality in mind, entered the late-1990s competition. Its single-piece delta wing and carbon-composite fuselage guaranteed fewer parts to move, easier production, and lower life-cycle expenses. The airframe was designed to fit all three U.S. services with minimal variation, as opposed to the X-35’s custom wing and fuselage modifications between variants. But simplicity of structure had its cost: the rigid geometry restricted aerodynamic flexibility and precluded future modifications, a disadvantage in a program designed to change over decades.
The final nail was hammered in with the Short Take-Off and Vertical Landing (STOVL) requirement, essential to the Marine Corps. Boeing went after an initial direct-lift system like the Harrier’s vectored thrust from a single engine with swiveling exhaust and roll posts for stability. Halfway through development, the firm turned to a shaft-powered lift fan again following Lockheed’s lead but the demonstrator never successfully executed a full, unaltered STOVL transition. As retired Navy Cmdr. Phillip “Rowdy” Yates, chief test pilot of the X-32, remembered, “That was probably the one where we kicked the dirt a little bit and said ‘damn.’” The X-35, on the other hand, performed a flawless sequence: vertical takeoff, supersonic acceleration, and vertical landing in the same configuration.
Lockheed’s lift-fan concept, built in partnership with Rolls-Royce, employed a 48-inch fan powered by a shaft off the main engine, blowing cool air from behind the fuselage to beneath for lift and a rotating rear exhaust. This configuration bypassed the X-32’s hot-gas ingestion issue, in which recirculated exhaust compromised thrust and could overheat. Boeing’s STOVL version even necessitated transfer to sea-level test at Patuxent River in order to provide sufficient lift margin for hover, but Lockheed’s was able to perform at Edwards Air Force Base’s higher elevation.
Aside from STOVL, the design of the X-35 was closer to that of a traditional fifth-generation fighter, its planform shaping and proportions reminiscent of the F-22. Yates admitted the “cosmetic vanity piece,” noting that “the X-35 looked more like a fighter than the X-32.” Aesthetics should not drive procurement, but the Pentagon’s decision-making climate open to congressional oversight, interservice competition, and public opinion meant that appearances could reinforce support for a program’s survival.
The competition was not a fly-off per se; each contractor built to its own test program to the baseline standards. Boeing’s demonstrator achieved carrier approach handling objectives Yates reported after initial testing that he “would take that aircraft to the ship tomorrow” but the inability to show a production-representative STOVL system weighed heavily. Lockheed’s prototype was closer to its proposed final configuration, reducing perceived risk. As Yates put it, “What they demonstrated was not their proposed final design. Lockheed’s was.”
In engineering terms, the X-32’s production philosophy foresaw contemporary demands for modularity and efficiency in sustaining. Its common engine architecture and structural simplicity potentially could have given greater sortie rates and reduced sustainment costs than the F-35, which now has just 27% to 40% commonality between variants, a far cry from the initial 70–90% target. But in 2001 the Pentagon preferred the X-35’s proven capability and perceived flexibility over the long-term cost savings offered by Boeing.
Twenty years after the fact, the F-35 program grapples with exorbitant sustainment expenses and chronic software slips, and the X-32 resides in museums as a warning relic. The tragedy highlights a conflict in defense procurement: the tension between documented short-term capability and designs optimized for industrial scalability and life-cycle affordability. In the JSF competition, the former won out guided by engineering milestones, strategic risk management, and, however subtly, the shape of the airplane itself.

