WS-201A, informally known as the 1954 interceptor, was a US Air Force project to develop a dedicated interceptor aircraft that would enter service in 1954. Several aircraft were developed as part of the project, leading to the F-102 Delta Dagger, F-106 Delta Dart, XF-103 Thunderwarrior and, indirectly, the F-101B Voodoo and F-104 Starfighter. The electronics and weapons were also destined to become common, including the AIM-4 Falcon missile and a variety of Hughes Aircraft supplied radar and fire control systems. The project also led, eventually, to the upgrading of the SAGE battle control computers to directly control the interceptors for much of their flight. Although greatly delayed, the resulting systems operated for about 20 years, into the 1980s.


  • Background 1
  • WS-201A 2
  • Interim measures 3
  • Continued problems 4
  • Service Entry 5
  • See also 6
  • References 7


The "1954 interceptor" concept first appeared shortly after the creation of the Air Force from the former Tactical Air Command (TAC) and Air Defense Command (ADC), who shared an interest in fighter aircraft. TAC was primarily tasked with offensive duties, but required capable fighters in order to protect their offensive capability. ADC was tasked solely with the defense of the US from enemy attack, in particular long-distance bombers. Soon after their formation, TAC and ADC started moving away from each other in terms of requirements.

In early 1949 ADC started a Request for Proposals (RFP) for an advanced interceptor capable of attacking Soviet bombers that were expected to enter service in the early 1950s. Several jet-powered interceptors were already under development at that point, typically adaptations of existing fighters like the F-86 Sabre (the F-86D Sabre Dog), the F-94 Starfire (adapted from the P-80 Shooting Star), with the exception being the all-new F-89 Scorpion. However these were all subsonic aircraft, and it was felt they would have insufficient performance to effectively intercept high-speed jet bombers known to be under development in the Soviet Union.

To counter these threats, ADC prepared a request for an entirely new aircraft expected to perform "hot war" interceptions at supersonic speeds. For reasons that are not clear, they also demanded that the entire system be flown and operated by a single pilot. Given the complexity of the radar systems and the aircraft themselves, this would require an advanced autopilot system that was integrated with the fire control system to lower pilot workload. Given the perceived threat, the new designs were expected to enter service in 1954.


The Air Force had already realized that the complexity of these newer systems would make integration difficult. In the past, aircraft airframes, engines and weapons were fairly common in size and general layout, allowing existing designs to be modified to change any one component with relative ease. For the 1954 interceptor, new equipment such as missiles and radar systems would be radically different between designs. There was little expectation that one missile could be swapped for another, for instance, due both to different electronic requirements as well as different mechanical layout.

To deal with this problem the Air Force introduced the "Weapons Systems" concept, where an entire aircraft (or other system) would be ordered as a complete working assembly. Although the parts going into it would be ordered under separate contracts, the requirements of the system as a whole would be known to all of the participants in advance, and one of the companies would be considered "prime" on ensuring all the parts would fit when they were delivered. The 1954 interceptor was the first fighter aircraft ordered under the Weapon System concept, and became "WS-201A". Contracts for the various parts making up 201A were sent out as soon as they completed writing them up, starting with the electronics suite, then the missile, and finally airframe and engine.

Studies of the electronics suite had started in February 1949, prior to the 201A specification, and were folded into the project. In January 1950 they sent out the MX-1179 contract tender to eighteen electronics contractors, but only Bendix, General Electric, Hughes Aircraft, North American Aviation, Sperry, and Westinghouse responded. Hughes was announced as the winner in July 1950, with what would become the MA-1. The original contract specified that MX-1179 would "direct some type of air-to-air guided missile." Hughes had already won the MX-904 contract for a missile known as the GAR-1 Falcon, and this was selected for 201A mainly because it seemed to be the only one that could be ready in time to meet the 1954 operational date.

The airframe and engine contract was issued as MX-1554 on 18 June 1950, with a January 1951 deadline for submissions. MX-1554 also stated that the winner of the airframe contract would also be named the lead "integrator" of the overall Weapon System. When the deadline was reached, nine different proposals were submitted; Republic Aircraft entered three designs, North American two, and Chance-Vought, Convair, Douglas, and Lockheed each submitted a single design. On 2 July 1951 the Air Force announced that Convair, Lockheed, and Republic had been selected to continue development through the mockup stage, and a winner would be selected at that point.

A short while later, the Air Force decided that it also needed a day fighter to combat the new MiG-15's that were being encountered over Korea. Existing designs like the P-80 Shooting Star and F-84 Thunderjet were completely outperformed by the MiG, and while the newer F-86 Sabre was more than capable of holding its own, it was not clear that would be the case in a war situation in Europe against "front line" Soviet pilots. A plane of considerably higher performance would be needed to guarantee leadership in this role, so the Lockheed entry was redirected toward a day fighter role, evolving into the F-104 Starfighter. Convair and Republic continued on with the original MX-1554.

It quickly became clear that the Republic design was far too advanced for the 1954 operational entry deadline, and on 11 September 1951 the Convair design was selected as the MX-1554 airframe and was designated F-102. Republic was to continue development of their much more powerful design at a lower priority, becoming the F-103. With the introduction of these programs, work on the Republic XF-91A, originally slated as an interim interceptor, ended in October 1951 in favor of the new designs.

Although the F-102 had been selected as the "low tech" solution in order to meet the 1954 deadline, practically every part of the 201A system ran into delays. To start with, it was clear that the engine, a Wright-modified version of the Bristol Olympus known as the J67, would almost certainly not be ready in time for a 1954 service entry. Additionally, the MX-1179 fire-control system seemed to be a risky proposition, and was another source of potential delay. In December the Air Force decided to reduce the risk by splitting the program in two, producing a reduced-performance version with interim engines and fire control as an "Interim Interceptor", and continuing with the original design over a longer period of time as the "Ultimate Interceptor". The Interim design would use the Westinghouse J40 engine, already available although of low power, and the Hughes E-9 fire-control system, a slightly updated version of the system being used in the F-86D.

Meanwhile practically every part of the F-103 program was going wrong. Construction of the airframe required extensive use of titanium in order to handle the high heat loads of extended Mach 3+ flight speeds, and this proved much more difficult to work with than originally expected. The engine, a combination of a Wright-modified version of the Bristol Olympus and a "combined cycle" ramjet from Marquardt, also ran into extensive problems and the J67 eventually ended in failure. Nevertheless the expected performance was so high the program was allowed to soldier on.

Interim measures

The delays seriously upset the original timetable, and it was clear by 1952 that even the "low tech" F-102 would not be able to meet the 1954 deadline. Although it was expected that the F-102B would be an excellent long-term solution, something was needed quickly to fill the performance gap between the existing subsonic designs and the continuing delays in the existing F-102 design. ADC argued that having a second design would also guarantee that problems in either program would be less likely to effect the defense as a whole.

The only design with the needed performance at that point in time was the McDonnell F-88. This design had originallyrequire('Module:No globals')

local p = {}

-- articles in which traditional Chinese preceeds simplified Chinese local t1st = { ["228 Incident"] = true, ["Chinese calendar"] = true, ["Lippo Centre, Hong Kong"] = true, ["Republic of China"] = true, ["Republic of China at the 1924 Summer Olympics"] = true, ["Taiwan"] = true, ["Taiwan (island)"] = true, ["Taiwan Province"] = true, ["Wei Boyang"] = true, }

-- the labels for each part local labels = { ["c"] = "Chinese", ["s"] = "simplified Chinese", ["t"] = "traditional Chinese", ["p"] = "pinyin", ["tp"] = "Tongyong Pinyin", ["w"] = "Wade–Giles", ["j"] = "Jyutping", ["cy"] = "Cantonese Yale", ["poj"] = "Pe̍h-ōe-jī", ["zhu"] = "Zhuyin Fuhao", ["l"] = "literally", }

-- article titles for wikilinks for each part local wlinks = { ["c"] = "Chinese language", ["s"] = "simplified Chinese characters", ["t"] = "traditional Chinese characters", ["p"] = "pinyin", ["tp"] = "Tongyong Pinyin", ["w"] = "Wade–Giles", ["j"] = "Jyutping", ["cy"] = "Yale romanization of Cantonese", ["poj"] = "Pe̍h-ōe-jī", ["zhu"] = "Bopomofo", }

-- for those parts which are to be treated as languages their ISO code local ISOlang = { ["c"] = "zh", ["t"] = "zh-Hant", ["s"] = "zh-Hans", ["p"] = "zh-Latn-pinyin", ["tp"] = "zh-Latn", ["w"] = "zh-Latn-wadegile", ["j"] = "yue-jyutping", ["cy"] = "yue", ["poj"] = "hak", ["zhu"] = "zh-Bopo", }

local italic = { ["p"] = true, ["tp"] = true, ["w"] = true, ["j"] = true, ["cy"] = true, ["poj"] = true, } -- Categories for different kinds of Chinese text local cats = { ["c"] = "", ["s"] = "", ["t"] = "", }

function p.Zh(frame) -- load arguments module to simplify handling of args local getArgs = require('Module:Arguments').getArgs local args = getArgs(frame) return p._Zh(args) end function p._Zh(args) local uselinks = not (args["links"] == "no") -- whether to add links local uselabels = not (args["labels"] == "no") -- whether to have labels local capfirst = args["scase"] ~= nil

        local t1 = false -- whether traditional Chinese characters go first
        local j1 = false -- whether Cantonese Romanisations go first
        local testChar
        if (args["first"]) then
                 for testChar in mw.ustring.gmatch(args["first"], "%a+") do
          if (testChar == "t") then
           t1 = true
          if (testChar == "j") then
           j1 = true
        if (t1 == false) then
         local title = mw.title.getCurrentTitle()
         t1 = t1st[title.text] == true

-- based on setting/preference specify order local orderlist = {"c", "s", "t", "p", "tp", "w", "j", "cy", "poj", "zhu", "l"} if (t1) then orderlist[2] = "t" orderlist[3] = "s" end if (j1) then orderlist[4] = "j" orderlist[5] = "cy" orderlist[6] = "p" orderlist[7] = "tp" orderlist[8] = "w" end -- rename rules. Rules to change parameters and labels based on other parameters if args["hp"] then -- hp an alias for p ([hanyu] pinyin) args["p"] = args["hp"] end if args["tp"] then -- if also Tongyu pinyin use full name for Hanyu pinyin labels["p"] = "Hanyu Pinyin" end if (args["s"] and args["s"] == args["t"]) then -- Treat simplified + traditional as Chinese if they're the same args["c"] = args["s"] args["s"] = nil args["t"] = nil elseif (not (args["s"] and args["t"])) then -- use short label if only one of simplified and traditional labels["s"] = labels["c"] labels["t"] = labels["c"] end local body = "" -- the output string local params -- for creating HTML spans local label -- the label, i.e. the bit preceeding the supplied text local val -- the supplied text -- go through all possible fields in loop, adding them to the output for i, part in ipairs(orderlist) do if (args[part]) then -- build label label = "" if (uselabels) then label = labels[part] if (capfirst) then label = mw.language.getContentLanguage():ucfirst( been ordered by Strategic Air Command (SAC) as a long-range "penetration fighter" to escort their heavy bombers. When newer bomber designs offered performance so great that the F-88 could not hope to keep up with them, TAC then took over the work and started modifying it as a low-level nuclear-armed fighter-bomber, renaming it as the F-101 Voodoo in 26 November 1951.

ADC also became interested in the Voodoo in October 1952, but funding from higher headquarters was difficult to find. They rejected modifying the F-101, mainly due to its high cost, and suggested attempting solving the problem by increasing the numbers of F-86Ds and speeding up work on the F-102. In April ADC once again asked for the F-101, this time justifying it as a longer-range counterpart for use in areas not widely covered by radar. It appears this suggestion was also rejected.

However, in August 1953 the Soviets detonated their first hydrogen bomb, and ADC's concerns became considerably more urgent. The Air Force Council issued proposals to industry for a new design to work alongside the F-102 that would help fill the gap between the F-89 and F-106. After short consideration of alternatives — an updated F-89 and an interceptor version of F-100 — the two-seat modification of F-101 was finally selected for development. Known as F-101B, it would be equipped with the MG-3/Falcon suite from the F-102, but operated by a weapons officer instead of the pilot. It would greatly simplify the complexity of the system as a whole.

Continued problems

Work on the airframes continued through 1952 and into 1953. NACA wind tunnel tests in early 1953 showed that the maximum altitude of 57,000 feet and combat radius of 350 miles predicted by Convair were too optimistic. Drag turned out to be higher than expected, but NACA was able to suggest the application of the recently developed area rule to combat this problem. Convair did not immediately put these recommendations into effect, and the initial two flying prototypes, of an order of 42 aircraft, continued with the original design. When these flew starting in October 1953, NACA's estimates were proven correct, and the F-102 had only a marginal performance improvement over the F-86D it was supposed to replace.

Service Entry

See also


  • Titanium Titan: the story of the XF-103, Airpower, January 2004
  • A Genesis Workshop: Five Generations of Engineering Enterprise from the Birthplace of Aviation, Chapter 7, "A New Paradigm"
This article was sourced from Creative Commons Attribution-ShareAlike License; additional terms may apply. World Heritage Encyclopedia content is assembled from numerous content providers, Open Access Publishing, and in compliance with The Fair Access to Science and Technology Research Act (FASTR), Wikimedia Foundation, Inc., Public Library of Science, The Encyclopedia of Life, Open Book Publishers (OBP), PubMed, U.S. National Library of Medicine, National Center for Biotechnology Information, U.S. National Library of Medicine, National Institutes of Health (NIH), U.S. Department of Health & Human Services, and, which sources content from all federal, state, local, tribal, and territorial government publication portals (.gov, .mil, .edu). Funding for and content contributors is made possible from the U.S. Congress, E-Government Act of 2002.
Crowd sourced content that is contributed to World Heritage Encyclopedia is peer reviewed and edited by our editorial staff to ensure quality scholarly research articles.
By using this site, you agree to the Terms of Use and Privacy Policy. World Heritage Encyclopedia™ is a registered trademark of the World Public Library Association, a non-profit organization.