dailynewsnblog
Lockheed Martin built a fighter jet intended to serve three US military branches, then gave every version of it a single engine. On a conventional fighter, that might look like a straightforward choice; on the Lockheed Martin F-35B, which has to transition from conventional flight to short takeoff and vertical landing, it looks almost counterintuitive. Yet the engine count was not an isolated propulsion decision. It was tied to the way the entire Joint Strike Fighter was supposed to share parts, systems, weight, and cost.
That makes the more interesting question less about whether a fifth-generation fighter can fly on one engine and more about why the Joint Strike Fighter program accepted that architecture in the first place. Lockheed Martin’s pursuit of commonality, the demonstrator that introduced the shaft-driven lift-fan concept, and the difficult F-35B redesign all point to the same decision, but each also exposes another constraint the engineers had to solve.
What The Joint Strike Fighter Program Actually Asked For
The starting point was not the engine itself. Lockheed Martin’s 2002 program announcement described affordability and a high degree of common parts and systems across the three F-35 variants as a project milestone. That requirement pushed the designers toward an architecture that could serve the United States Air Force‘s F-35A, the US Navy‘s F-35C, and the US Marine Corps’ F-35B without creating three essentially separate aircraft underneath the common name.
Propulsion became part of that commonality equation. A separate engine for each variant would have made the architecture harder to share, but the pressure was strongest in the F-35B, where the aircraft had to accommodate a propulsion system capable of supporting short takeoffs and vertical landings. The solution therefore had to do more than provide thrust for a fighter: it had to fit inside an airframe being designed around common systems while also supporting an entirely different landing method. For a wider view of how modern fighter fleets are changing, see Simple Flying’s analysis of NATO fighter fleets.
That is why the single-engine layout should not be read simply as a decision to save the weight of one engine. It was part of a larger attempt to make three aircraft behave as one program from an engineering and affordability standpoint. Pratt & Whitney‘s F135 became the single-engine family for all three F-35 variants, giving the Joint Strike Fighter something unusually valuable for a program built around three different operating requirements: a common engine at the heart of the F-35A, F-35B, and F-35C. The next question is where the F-35B’s unusual vertical-lift system came from, and why it made that common goal so difficult to execute.
Why The F135 Became The F-35’s Common Powerplant
Lockheed Martin’s own design history traces this back to an early design concept, internally numbered 220-2, which introduced what the company calls a shaft-driven lift-fan design. That was a first-of-its-kind piece of engineering , as described by Lockheed Martin, that helped the company win the demonstrator phase of the JSF competition in the first place.
Instead of adding a second engine solely for vertical lift, the aircraft could use the main engine as the source of propulsion while mechanically driving a lift fan positioned forward of it. The concept lets one powerplant support both conventional flight and the vertical-lift system without abandoning the common propulsion architecture.
That arrangement matters because the lift fan is mechanically linked to the aircraft’s main engine, which means the propulsion system has to perform several jobs within one integrated arrangement. The rear exhaust system provides the conventional thrust path, while the lift fan contributes vertical force during STOVL operations. The engineering trade-off was substantial. The F135 had to provide enough power for a conventional fifth generation fighter while also accommodating the mechanical and thermal demands created by the F-35B’s STOVL system. That made the engine one of the central pieces around which the B variant’s entire propulsion architecture was organized.
The result is a solution that preserves the single-engine philosophy while introducing substantially more mechanical complexity than a conventional fighter’s propulsion layout. During conventional flight, the F135 behaves much like the engines of the other F-35 variants, sending its exhaust rearward to produce forward thrust. When the aircraft enters STOVL mode, however, the propulsion system changes configuration.
Doors open around the lift fan and rear nozzle, the drive system engages, and the lift fan begins drawing power mechanically from the engine. At the same time, the three-bearing swivel module rotates the rear exhaust nozzle about 95° downward, as documented by MiGflug. The two sources of lift work together rather than requiring a separate vertical-lift engine. As already examined by Simple Flying, the BAe Harrier, the F-35B predecessor, was a simpler aircraft in comparison: a single Rolls-Royce Pegasus engine vectoring exhaust through four rotating nozzles, generating one concentrated hot jet blast that famously could damage unprepared surfaces and limited how long the aircraft could safely hover.
Why The F-35B’s Single Engine Powers Vertical Flight
The shaft-driven arrangement works because the F-35B does not need its engine to stop being a fighter engine when it reaches hovering. Instead, the propulsion architecture redirects the engine’s available power into the systems required for vertical flight. The lift fan ahead of the engine supplies vertical lift while the rear exhaust system continues to manage the engine’s thrust, allowing the aircraft to transition between flight modes without carrying a dedicated second engine.
The test program included a series of demonstrations that gradually increased in difficulty. Test pilot Graham Tomlinson made the first official vertical landing in the program on March 18, 2010, at Patuxent River Naval Air Station/Trapnell Field Airport(NHK), after hovering the aircraft at 150 feet for a full minute. Three months later, an F-35B exceeded Mach 1, and by October 2011 an F-35B was performing vertical landings at sea aboard a Marine Corps amphibious assault ship.
Those milestones showed that the single-engine architecture was not just theoretical: the same powerplant and integrated lift system could support the radically different operating requirements of the F-35B. The same question of how an engine architecture shapes a fighter program also appears in Simple Flying’s look at Rolls-Royce and future engine programs. But demonstrating that the system could work was only one hurdle. The harder question was whether the aircraft could carry all of that machinery and still meet its weight targets. That problem forced the Joint Strike Fighter team into one of the most consequential redesigns of the F-35B program.
Why A Second Engine Wasn’t Simply Left Out As Unnecessary
The program did not discover a comfortable margin waiting to be spent on a second engine. After the preliminary design review, Lockheed Martin’s engineers found that the F-35B’s actual weight projections did not match their targets. The team halted development for six months and carried out what Lockheed Martin describes as a drastic overhaul of the F-35B’s design. The immediate issue was the aircraft as it existed on paper: weight had become serious enough that the team had to recover margin rather than add another major propulsion system.
As Simple Flying has noted in its comparison of cockpit and flight-control differences between the F-35 and F-22, the STOVL system’s complexity is not limited to the lift fan itself: roll posts embedded in each wing, fed by bleed air from the main engine, provide the lateral stability control that allows the pilot to balance the aircraft during the difficult transition between aerodynamic lift and vertical jet lift.
That redesign matters to the single-engine question because a second engine would require space, structure, ducting, controls, fuel-system changes, maintenance access, and additional mass, while also affecting the surrounding architecture. The F-35B was already managing the lift fan and its mechanical drive within a tightly constrained airframe. In that context, the six-month weight-reduction effort shows how little design freedom it had to absorb a substantially different propulsion concept.
The redesign also demonstrates why the single-engine decision cannot be treated as an F-35B-only compromise. Weight savings achieved during the overhaul benefited the F-35A and F-35C as well, reinforcing the original idea that the three variants were supposed to remain parts of a common program. Once that shared architecture was established, the propulsion decision’s consequences reached far beyond the STOVL version and into how the F-35 can be upgraded today. Another example of how present-day fighter decisions tie closely to future programs is Simple Flying’s look at why Boeing won the F-47 program.
What The Single-Engine Choice Means For The F-35 Today
The modern consequence is architectural. The F-35’s shared systems, internal volume, cooling arrangements, and propulsion architecture were developed around the assumption that one engine would provide the aircraft’s primary power source. That means later changes must fit within an airframe whose space and weight were already carefully allocated, rather than starting with the empty margins a hypothetical twin-engine fighter might have had from the beginning.
For the F-35 program, that becomes increasingly important as mission systems evolve. Additional sensors, more capable mission equipment, and growing electrical or cooling requirements all compete for resources inside the same aircraft architecture. The point is that every new capability has to be integrated without undoing the design choices that allowed the A, B, and C variants to retain their common foundation in the first place.
That brings the original question back into focus. The single engine solved a program-level problem by reinforcing commonality, but every future modification inherits that decision. The next issue is therefore not whether Lockheed Martin could have built a twin-engine F-35 at the start, but whether the architecture chosen then still provides enough margin for the aircraft the program wants to operate years from now.
What The Single-Engine Decision Will Have To Prove
The broader implication is that the F-35’s single-engine architecture is now less a question of what the aircraft was designed to do and more a question of how much additional capability that architecture can absorb. The Joint Strike Fighter was built around a common airframe and common systems, so the value of keeping one propulsion arrangement across the program depends on preserving enough room for that common design to evolve without repeating the weight pressure that once forced the F-35B back to the drawing board. The broader question of how far a mature aircraft architecture can be extended is also explored in Simple Flying’s look at the B-52’s extraordinary service life.
The clearest test will be the modernization work that follows. Each future upgrade will have to fit inside the existing airframe while providing more electrical power, cooling, sensors, or other mission capability without undermining the common architecture shared by the F-35A, F-35B, and F-35C. The six-month F-35B redesign remains the useful benchmark: when weight and volume became critical during development, the solution was not to add room for a fundamentally different propulsion layout, but to redesign the aircraft around the limits it already had.
That leaves one point to watch as the F-35 continues to evolve: whether future upgrade packages can keep adding capability without creating another crisis of weight, volume, or system capacity. If they can, the single-engine decision will look less like a compromise that the program has spent decades defending and more like the architectural choice that allowed three very different aircraft to remain one family in the first place.
