Why the Air Force Picked the F-22 Over a Faster YF-23

The contest that created the F-22 was not decided by a weak airplane losing to a better one. It was decided by two unusually capable stealth fighters, and by which team convinced the Air Force it could turn a prototype into an operational weapon. In the Advanced Tactical Fighter competition, the Lockheed-led YF-22 and Northrop-led YF-23 were both built to answer the same Cold War problem: how to defeat highly agile Soviet-designed fighters such as the Su-27 and MiG-29 while surviving in heavily defended airspace. The requirement was not just raw speed. The Air Force wanted stealth, supercruise, range, and enough agility to dominate close-in air combat. It also expected a fleet large enough to reshape tactical aviation, making the stakes enormous for both industry teams.

Image Credit to Wikimedia Commons | Licence details

The YF-23 built its case around aerodynamic efficiency and low observability. Its long, sleek fuselage, diamond-shaped planform, and dramatic V-tail gave it a look unlike any other fighter of its era. More important, the shape was tied directly to performance. One prototype, the Grey Ghost, reached Mach 1.6 in supercruise, while the overall design was associated with top speed above Mach 2.2. It also offered longer reach, a major advantage for penetrating defended airspace without immediate tanker support.

That was only part of the picture. The YF-22 presented a different answer to the same mission. According to the Air Force, the production F-22’s defining mix became stealth, supercruise, maneuverability, and integrated avionics. Even at the prototype stage, Lockheed’s team leaned hard into the qualities decision-makers could see instantly: violent high-angle maneuvering, strong nose authority, and a demonstration profile that looked like a front-line fighter already in combat trim. The YF-22 also benefited from thrust vectoring, which helped frame it as the more agile and mature dogfighter.

That framing mattered because acquisition decisions are never made on engineering alone. Test pilot Paul Metz, who flew both programs, later described the Northrop jet in unusually strong terms: Never hang your head in shame about what we did. We built a tremendous product that would stand side-by-side with anything else, and in many cases exceed the capabilities of anything else. And we can always be proud of that. He also pointed to a less glamorous reality: Lockheed left stronger impressions on the people making the choice. In his account, Northrop’s team spoke like engineers; Lockheed’s team demonstrated like salesmen as well as aviators.

The YF-23’s loss is often described as a defeat of a stealthier, faster aircraft by a more maneuverable one, but that simplifies the decision too much. The Air Force was choosing not just an airframe, but a development path, an industrial team, and a program it believed could arrive on schedule with manageable risk. Major General Joseph W. Ralston captured that concern when he said, “The thing I like about [the Lockheed proposal] is that the Air Force has confidence that the contractor team . . . can deliver at the cost the Air Force estimated.”

That judgment shaped the next three decades of American air combat. The F-22 entered service and remains a benchmark for air dominance, with 183 aircraft in total force inventory listed by the Air Force fact sheet. The YF-23 never reached squadron service, yet its design ideas did not disappear; the aircraft is widely credited with influencing the B-21 Raider’s shaping. That is why the YF-23 still lingers as one of aviation’s enduring “what if” machines: not a failed fighter, but a prototype that lost a procurement battle even while proving how far stealth design had already advanced.

spot_img

More from this stream

Recomended

Discover more from Modern Engineering Marvels

Subscribe now to keep reading and get access to the full archive.

Continue reading