Category THE DEVELOPMENT. OF PROPULSION. TECHNOLOGY. FOR U. S.. SPACE-LAUNCH. VEHICLES,. 1926-1991

The Atlas, Thor, and Jupiter Missiles

Following Redstone and Vanguard, the Atlas, Thor, and Jupiter mis­siles brought further innovations in rocket technology and became the first stages of launch vehicles themselves, with Atlas and Thor having more significance in this role than Jupiter. All three pro­grams illustrated the roles of interservice and interagency rivalry and cooperation that were both key features of rocket development in the United States. They also showed the continued use of both theory and empiricism in the complex engineering of rocket sys­tems. “It was not one important ‘breakthrough’ that enabled this advance; rather, it was a thousand different refinements, a hundred thousand tests and design modifications, all aimed at the develop­ment of equipment of extraordinary power and reliability," accord­ing to Milton Rosen, writing in 1962.61

Atlas was a much larger effort than Vanguard, and it began to create the infrastructure in talent, knowledge, data, and capability necessary for the maturation of launch-vehicle technology in the decade of the 1960s. However, until the air force became serious about Atlas, that service had lagged behind the army and the navy in the development of purely ballistic missiles.62

The process began in a significant way on January 23, 1951, when 32 the air force awarded the Consolidated Vultee Aircraft Corporation Chapter 1 (Convair) a contract for MX-1593, the project that soon became Atlas. (MX-1593 had been preceded by MX-774B and a number of other air force missile contracts in the late 1940s, with a total of $34 million devoted to missile research in fiscal year 1946, much re-

duced in subsequent years.) But the specifications for the MX-1593 missile changed drastically as technology for nuclear warheads evolved to fit more explosive power into smaller packages. This new technology plus the increased threat from the Soviets provided one condition for greater air force support of Atlas and other bal­listic missiles.

But it also took two heterogeneous engineers to nudge the new­est armed service and the Department of Defense (DoD) in a new direction. One of them was Trevor Gardner, assistant for research and development to Secretary of the Air Force Harold Talbott in the Eisenhower administration. The other key promoter of ballistic missiles was the “brilliant and affable" polymath, John von Neu­mann, who was research professor of mathematics at Princeton’s Institute for Advanced Study and also director of its electronic com­puter project. In 1953, he headed a Nuclear Weapons Panel of the Air Force Scientific Advisory Board, which confirmed beliefs that in the next six to eight years, the United States would have the capability to field a thermonuclear warhead weighing about 1,500 pounds and yielding 1 megaton of explosive force. This was 50 times the yield of the atomic warhead originally planned for the Atlas missile, fit in a much lighter package. This and a report (dated February 1, 1954) for von Neumann’s Teapot Committee set the stage for extraordi­nary air force support for Atlas.63

Подпись: 33 German and U.S. Missiles and Rockets, 1926-66 In May 1954 the air force directed that the Atlas program be­gin an accelerated development schedule, using the service’s high­est priority. The Air Research and Development Command within the air arm created a new organization in Inglewood, California, named the Western Development Division (WDD), and placed Brig. Gen. Bernard A. Schriever in charge. Schriever, who was born in Germany but moved to Texas when his father became a prisoner of war there during World War I, graduated from the Agricultural and Mechanical College of Texas (since 1964, Texas A&M Univer­sity) in 1931 with a degree in architectural engineering. Tall, slen­der, and handsome, the determined young man accepted a reserve commission in the army and completed pilot training, eventu­ally marrying the daughter of Brig. Gen. George Brett of the army air corps in 1938. Placed in charge of the WDD, Schriever in es­sence took over from Gardner and von Neumann the role of het­erogeneous engineer, promoting and developing the Atlas and later missiles.64

Gardner had been intense and abrasive in pushing the develop­ment of missiles. Schriever was generally calm and persuasive. He selected highly competent people for his staff, many of them be-

coming general officers. An extremely hard worker, like von Braun he demanded much of his staff; but unlike von Braun he seemed somewhat aloof to most of them and inconsiderate of their time— frequently late for meetings without even realizing it. Good at plan­ning and organizing, gifted with vision, he was poor at management, often overlooking matters that needed his attention—not surprising because he spent much time flying back and forth to Washington, D. C. His secretary and program managers had to watch carefully over key documents to ensure that he saw and responded to them. One of his early staff members (later a lieutenant general), Otto J. Glasser, said Schriever was “probably the keenest planner of any­body I ever met" but he was “one of the lousiest managers."

Later Lt. Gen. Charles H. Terhune Jr., who became Schriever’s deputy director for technical operations, called his boss a “superb front man" for the organization, “very convincing. . . . He had a lot of people working for him [who] were very good and did their jobs, but Schriever was the one who pulled it all together and represented them in Congress and other places." Glasser added, “He was just superb at. . . laying out the wisdom of his approach so that the Congress wanted to ladle out money to him." Glasser also said he was good at building camaraderie among his staff.65

To facilitate missile development, Schriever received from the air force unusual prerogatives, such as the Gillette Procedures. Designed by Hyde Gillette, a budgetary expert in the office of the secretary of the air force, these served to simplify procedures for managing intercontinental ballistic missiles (ICBMs). Schriever had complained that there were 40 different offices and agencies he had to deal with to get his job done. Approval of his annual develop­ment plans took months to sail through all of these bodies. With the new procedures (granted November 8, 1955), Schriever had to deal with only two ballistic missile committees, one at the secretary – of-defense and the other at the air-force level. Coupled with other arrangements, this gave Schriever unprecedented authority to de­velop missiles.66

Another key element in the management of the ballistic mis­sile effort was the Ramo-Wooldridge Corporation. Simon Ramo and Dean Wooldridge, classmates at Caltech, each had earned a Ph. D. there at age 23. After World War II, they had presided over an 34 electronics team that built fire-control systems for the air force at Chapter 1 Hughes Aircraft. In 1953, they set up their own corporation, with the Thompson Products firm buying 49 percent of the stock. For a variety of reasons, including recommendations of the Teapot Com­mittee, Schriever made Ramo-Wooldridge into a systems engineer-

ing-technical direction contractor to advise his staff on the man­agement of the Atlas program. The air force issued a contract to the firm for this task on January 29, 1955, although it had begun working in May 1954 under letter contract on a study of how to redirect the Atlas program. This unique arrangement with Ramo- Wooldridge caused considerable concern in the industry (especially on the part of Convair) that Ramo-Wooldridge employees would be in an unfair position to use the knowledge they gained to bid on other contracts, although the firm was not supposed to produce hardware for missiles. To ward off such criticism, the firm created a Guided Missile Research Division (GMRD) and kept it separate from other divisions of the firm. Louis Dunn, who had served on the Teapot Committee, became the GMRD director, bringing sev­eral people with him from JPL. This arrangement did not put an end to controversy about Ramo-Wooldridge’s role, so in 1957, GMRD became Space Technology Laboratories (STL), an autonomous divi­sion of the firm, with Ramo as president and Dunn as executive vice president and general manager.67

Some air force officers on Schriever’s staff objected to the con­tract with Ramo-Wooldridge, notably Col. Edward Hall, a propul­sion expert. Hall had nothing good to say about Ramo-Wooldridge (or Schriever), but several engineers at Convair concluded that the firm made a positive contribution to Atlas development.68

The Ramo-Wooldridge staff outnumbered the air force staff at WDD, but the two groups worked together in selecting contrac­tors for components of Atlas and later missiles, overseeing their performance, testing, and analyzing results. For such a large under­taking as Atlas, soon joined by other programs, there needed to be some system to inform managers and allow them to make decisions on problem areas. The WDD, which became the Air Force Ballistic Missile Division on June 1, 1957, developed a management control system to collect information for planning and scheduling.

Подпись: 35 German and U.S. Missiles and Rockets, 1926-66 Schriever and his program directors gathered all of this data in a program control room, located in a concrete vault and kept under guard at all times. At first, hundreds of charts and graphs covered the walls, but WDD soon added digital computers for tracking infor­mation. Although some staff members claimed Schriever used the control room only to impress important visitors, program managers benefited from preparing weekly and monthly reports of status, be­cause they had to verify their accuracy and thereby keep abreast of events. Separate reports from a procurement office the Air Force Air Materiel Command assigned to the WDD on August 15, 1954, pro­vided Schriever an independent check on information from his own

managers. The thousands of milestones—Schriever called them inchstones—in the master schedule kept him and his key manag­ers advised of how development matched planning. All of the infor­mation came together on “Black Saturday" meetings once a month starting in 1955. Here program managers and department heads presented problem areas to Schriever, Ramo, and Brig. Gen. Ben I. Funk, commander of the procurement office. As problems arose, discussion sometimes could resolve them in the course of the meet­ing. If not, a specific person or organization would be assigned to come up with a solution, while the staff of the program control room tracked progress. Sometimes, Ramo brought in outside experts from industry or academia to deal with particularly difficult problems.69

Because the process of developing new missile systems entailed considerable urgency when the Soviet threat was perceived as great and the technology was still far from mature, Schriever and his team used a practice called concurrency that was not new but not routinely practiced in the federal government. Used on the B-29 bomber, the Manhattan Project, and development of nuclear vessels for the U. S. Navy, it involved developing all subsystems and the facilities to test and manufacture them on overlapping schedules; likewise, the systems for operational control and the training sys­tem for the Strategic Air Command, which took over the missiles when they became operational.

Schriever claimed that implementing concurrency was equiva­lent to requiring a car manufacturer to build the automobile and also to construct highways, bridges, and filling stations as well as teach drivers’ education. He argued that concurrency saved money, but this seems doubtful. Each model of the Atlas missile from A to F involved expensive improvements, and the F models were housed in silos. Each time the F-model design changed, the Army Corps of Engineers had to reconfigure the silo. There were 199 engineering change orders for the silos near Lincoln, Nebraska, and these raised the costs from $23 million to more than $50 million dollars—to give one example of costs added by concurrency. What concurrency did achieve was speed of overall development and the assurance that all systems would be available on schedule.70

A further tool in WDD’s management portfolio was parallel de­velopment. To avoid being dependent on a single supplier for a sys – 36 tem, Schriever insisted on parallel contractors for many of them.

Chapter 1 Eventually, when Thor and Titan I came along, the testing program became overwhelming, and Glasser argued that Ramo-Wooldridge just ignored the problem. He went to Schriever, who directed him to come up with a solution. He decided which systems would go on

Atlas, which on Titan and Thor, in the process becoming the deputy for systems management and the Atlas project manager.71

A final component of the management structure for Schriever’s west-coast operation consisted of the nonprofit Aerospace Corpora­tion. It had come into existence on June 4, 1960, as a solution to the problems many people saw in Space Technology Laboratories’ serv­ing as a systems-engineering and technical-direction contractor to the air force while part of Thompson Ramo Wooldridge (later, just TRW), as the company had become following an eventual merger of Ramo-Wooldridge with Thompson Products. STL continued its operations for programs then in existence, but many of its person­nel transferred to the Aerospace Corporation for systems engineer­ing and technical direction of new programs. Further complicat­ing the picture, a reorganization occurred within the air force on April 1, 1961, in which Air Force Systems Command (AFSC) re­placed the Air Research and Development Command. On the same date, within AFSC, the Ballistic Missile Division split into a Ballis­tic Systems Division (BSD), which would retain responsibility for ballistic missiles (and would soon move to Norton Air Force Base [AFB] east of Los Angeles near San Bernardino); and a Space Systems Division (SSD), which moved to El Segundo, much closer to Los Angeles, and obtained responsibility for military space systems and boosters. There would be further reorganizations of the two offices, but whether combined or separated, they oversaw the development of a variety of missiles and launch vehicles, ranging from the Atlas and Thor to Titans I through IV.72

To return specifically to the Atlas program, under the earlier (1946-48) MX-774B project, Convair had developed swiveling of en­gines (a precursor of gimballing); monocoque propellant tanks that were integral to the structure of the rockets and pressurized with nitrogen to provide structural strength with very little weight pen­alty (later evolving into what Convair called a steel balloon); and separable nose cones so that the missile itself did not have to travel with a warhead to the target and thus have to survive the aerody­namic heating from reentering the atmosphere.73

Подпись: 37 German and U.S. Missiles and Rockets, 1926-66 Other innovations followed under the genial leadership of Karel (Charlie) Bossart. Finally, on January 6, 1955, the air force awarded a contract to Convair for the development and production of the Atlas airframe, the integration of other subsystems with the airframe and one another, their assembly and testing. The contractor for the At­las engines was North American Aviation, which built upon earlier research done on the Navaho missile. NAA’s Rocketdyne Division, formed in 1955 to handle the requirements of Navaho, Atlas, and

Redstone, developed one sustainer and two outside booster engines for the Atlas under a so-called stage-and-a-half arrangement, with the boosters discarded after they had done their work. Produced in

1957 and 1958, the early engines ran into failures of systems and components in flight testing that also plagued the Thor and Jupiter engines, which were under simultaneous development and shared many component designs with the Atlas.74

But innovation continued, partly through engineers making “the right guess or assumption" or simply learning from problems. De­spite repeated failures and (trial-and-error) modifications to elimi­nate their causes, development proceeded from Atlas A through At­las F with a total of 158 successful launches for all models against 69 failures—a success rate of only 69.6 percent. The Atlas D became the first operational version in September 1959, with the first E and F models following in 1961. All three remained operational until 1965, when they were phased out of the missile inventory, with many of them later becoming launch-vehicle stages.75

Meanwhile, fearing (unnecessarily) that an ICBM like the Atlas could not be deployed before 1962, a Technology Capabilities Panel headed by James R. Killian Jr., president of MIT, issued a report in mid-February 1955 recommending the development of both sea – and land-based intermediate-range ballistic missiles (IRBMs). In Novem­ber 1955, the Joint Chiefs of Staff recommended, in turn, that the air force develop the land-based version while the army and navy collaborate on an IRBM that could be both land and sea based. Thus were born the air force’s Thor and the army’s Jupiter, with the navy eventually developing the solid-propellant Polaris after initially try­ing to adapt the liquid-propellant Jupiter to shipboard use.76

Arising out of this decision was the “Thor-Jupiter Controversy," which the House of Representatives Committee on Government Operations called a “case study in interservice rivalry." The Thor did not use the extremely light, steel-balloon structure of Atlas but a more conventional aluminum airframe. Its main engine consisted essentially of half of the booster system for Atlas. In 1957 and 1958, it experienced 12 failures or partial successes out of the first 18 launches. Before the air force nevertheless decided in September

1958 that Thor was ready for operational deployment, problems with the turbopumps (common to the Atlas, Thor, and Jupiter) and

38 differences of approach to these problems had led to disagreement Chapter 1 between the Thor and Jupiter teams.77

Von Braun’s engineers, working on the Jupiter for the army, di­agnosed the problem first and had Rocketdyne design a bearing re­tainer for the turbopump that solved the problem, which the Thor

program would not admit at first, suspecting another cause. Once the Jupiters resumed test flights, they had no further turbopump problems. Meanwhile, failures of an Atlas and a Thor missile in April 1958, plus subsequent analysis, led the air force belatedly to accept the army’s diagnosis and a turbopump redesign. The first Thor squadron went on operational alert in Great Britain in June 1959, with three others following by April 1960. When the Atlas and Titan ICBMs achieved operational readiness in 1960, the last Thors could be removed from operational status in 1963, making them available for space-launch activities.78

While the Western Development Division and the successor Air Force Ballistic Missile Division were developing the Thor in con­junction with contractors, von Braun’s group at what had become the Army Ballistic Missile Agency (ABMA) in Alabama and its con­tractors were busily at work on Jupiter without a clear indication whether the army or the air force would eventually deploy the mis­sile. At ABMA, the forceful and dynamic Maj. Gen. John B. Medaris enjoyed powers of initiative roughly analogous to those of Schriever for the air force. On December 8, 1956, the navy left the Jupiter program to develop Polaris, but not before the sea service’s require­ments had altered the shape of the army missile to a much shorter and somewhat thicker contour than the army had planned. With Chrysler the prime contractor (as on the Redstone), Medaris reluc­tantly accepted the same basic engine North American Rocketdyne was developing for the Thor except that the Jupiter engine evolved from an earlier version of the powerplant and ended as somewhat less powerful than the air force counterparts.79

Подпись: 39 German and U.S. Missiles and Rockets, 1926-66 With a quite different vernier engine and guidance/control sys­tem, the Jupiter was a decidedly distinct missile from the Thor. The first actual Jupiter (as distinguished from the Jupiter A and Jupiter C, which were actually Redstones) launched on March 1, 1957, at Cape Canaveral. Facing the usual developmental problems, including at least one that Medaris blamed on the thicker shape resulting from the navy’s requirements, the Jupiter nevertheless achieved 22 sat­isfactory research-and-development flight tests out of 29 attempts. The air force, instead of the army, deployed the missile, with initial operational capability coming on October 20, 1960. Two squadrons of the missile became fully operational in Italy as of June 20, 1961. A third squadron in Turkey was not operational until 1962, with all of the missiles taken out of service in April of the following year. Three feet shorter, slightly thicker and heavier, the Jupiter was more accurate but less powerful than the Thor, with a comparable range. The greater average thrust of the Thor may have contributed

to its becoming a standard first-stage launch vehicle, whereas Jupi­ter served in that capacity to only a limited degree. Another factor may have been that there were 160 production Thors to only 60 Ju­piter missiles.80

Although much has rightly been made of the intense interservice rivalry between the army and the air force over Thor and Jupiter, even those two programs cooperated to a considerable extent and exchanged much data. Medaris complained about the lack of infor­mation he received from the air force, but Schriever claimed that his Ballistic Missile Division had transmitted to ABMA a total of 4,476 documents between 1954 and February 1959. By his count, BMD withheld only 28 documents for a variety of reasons, including con­tractors’ proprietary information.81 This was one of many examples showing that—although interservice and interagency rivalry helped encourage competing engineers to excel—without sharing of infor­mation and technology, rocketry might have advanced much less quickly than in fact it did.

Atlas Propulsion

Even though the Viking rocket used alcohol and the Vanguard first stage adopted kerosene as its fuel, the next major advance in alcohol and kerosene propulsion technology came with the Atlas missile. As with the Redstone, North American Aviation designed and built the Atlas engines, which also owed a great deal to NAA’s work for the Navaho. Unlike the Redstone, the Atlas engines burned kero­sene rather than alcohol. (Both used liquid oxygen as the oxidizer.) Kerosene that would work in rocket engines was another legacy of the protean Navaho program. In January 1953, Lt. Col. Edward Hall and others from Wright-Patterson AFB insisted to Sam Hoffman that he convert from alcohol to a hydrocarbon fuel for a 120,000-pound – 122 thrust Navaho engine. Hoffman protested because the standard Chapter 3 kerosene the air force used was JP-4, whose specifications allowed a range of densities. JP-4 clogged a rocket engine’s slim cooling lines with residues. The compounds in the fuel that caused these prob­lems did not affect jet engines but would not work easily in rocket powerplants. To resolve these problems, Hoffman initiated the Rocket Engine Advancement Program, resulting in development of the RP-1 kerosene rocket fuel, without JP-4’s contaminants and variations in density. This fuel went on to power the Atlas, Thor, and Jupiter engines. The specifications for RP-1 were available in January 1957, before the delivery date of the Atlas engines.38

On October 28, 1954, the Western Development Division and Special Aircraft Projects (procurement) Office that Air Force Ma­teriel Command had located next to it issued a letter contract to NAA to continue research and development of liquid-oxygen and

kerosene (RP-1) engines for Atlas. The cooperating air force organi­zations followed this with a contract to NAA for 12 pairs of rocket engines for the series-A flights of Atlas, which tested only two outside booster engines and not the centrally located sustainer en­gine for the Atlas. The Rocketdyne Division, formed to handle the requirements of Navaho, Atlas, and Redstone, also developed the sustainer engine, which differed from the two boosters in having a nozzle with a higher expansion ratio for optimum performance at higher altitudes once the boosters were discarded.39

Using knowledge gained from the Navaho and Redstone engines, the NAA engineers began developing the MA-1 Atlas engine system for Atlases A, B, and C in 1954. (Atlas B added the sustainer engine to the two boosters; Atlas C had the same engines but included improvements to the guidance system and thinner skin on the pro­pellant tanks. Both were test vehicles only.) The MA-1, like its suc­cessors the MA-2 and MA-3, was gimballed and used the brazed "spaghetti" tubes forming the inner and outer walls of the regen­eratively cooled combustion chamber. NAA had developed the ar­rangement used in the MA-1 in 1951, perhaps in ignorance of the originator of the concept, Edward Neu at Reaction Motors. NAA/ Rocketdyne began static "hot-fire" tests of the booster engines in 1955 and of all three MA-1 engines in 1956 at Santa Susana. The two booster engines, designated XLR43-NA-3, had a specific im­pulse of 245 lbf-sec/lbm and a total thrust of 300,000 pounds, much more than the Redstone engine. The sustainer engine, designated XLR43-NA-5, had a lower specific impulse (210 lbf-sec/lbm) and a total thrust of 54,000 pounds.40

Подпись: 123 Propulsion with Alcohol and Kerosene Fuels, 1932-72 Produced in 1957 and 1958, these engines ran into failures of systems and components in flight testing that also plagued the Thor and Jupiter engines, which were under simultaneous develop­ment and shared many component designs with the Atlas. They used high-pressure turbopumps that transmitted power from the turbines to the propellant pumps via a high-speed gear train. Both Atlas and Thor used the MK-3 turbopump, which failed at high al­titude on several flights of both missiles, causing the propulsion system to cease functioning. Investigations showed that lubrication was marginal. Rocketdyne engineers redesigned the lubrication sys­tem and a roller bearing, strengthening the gear case and related parts. Turbine blades experienced cracking, attributed to fatigue from vibration and flutter. To solve this problem, the engineers ta­pered each blade’s profile to change the natural frequency and added shroud tips to the blades. These devices extended from one blade to the next, restricting the amount of flutter. There was also an explo-

Atlas Propulsion

FIG. 3.4 Technical drawing of a baffled injector similar to the one used on the Atlas MA-1 engine to prevent combustion instability by containing lateral oscillations in the combustion chamber. (Taken from Dieter K. Huzel and David H. Huang, Design of Liquid Propellant Rocket Engines [Washington, D. C.: NASA SP-125, 1967], p. 122)

sion of a sustainer engine caused by rubbing in the oxygen side of the turbopump, solved by increasing clearances in the pump and installing a liner.

Another problem encountered on the MA-1 entailed a high – frequency acoustic form of combustion instability resulting in vi­bration and increased transfer of heat that could destroy the engine 124 in less than a hundredth of a second. The solution proved to be rect – Chapter 3 angular pieces of metal called baffles, attached to a circular ring near the center of the injector face and extending from the ring to the chamber walls. Fuel flowed through the baffles and ring for cooling. The baffles and ring served to contain the transverse oscillations in much the way that the 18 pots on the V-2 had done but without the cumbersome plumbing. Together with changing the injection pat­tern, this innovation made the instability manageable. These im­provements came between the flight testing of the MA-1 system and the completion of the MA-3 engine system (1958—63).41 They showed the need to modify initial designs to resolve problems that appeared in the process of testing and the number of innovations that resulted, although we do not always know who conceived them or precisely how they came about. (But see the account below of Rocketdyne’s Experimental Engines Group for some of the explanations.)

FIG. 3.5

Technical drawing showing components of an MA-5 sustainer engine, used on the Atlas space-launch vehicle, 1983. (Photo courtesy of NASA)

 

С 1983-781

 

GIMBAL BEARING

 

OX D ZER INLET ELBOW

 

OXIDIZER DOME

 

FUEL MANIFOLD

 

SUSTAINER THRUST CHAMBER ASSEMBLY

 

Atlas Propulsion

Atlas Propulsion

National Aeronautics and Space Administration Lewis Research Center

Подпись: 125 Propulsion with Alcohol and Kerosene Fuels, 1932-72 The MA-2 “was an uprated and simplified version of the MA-1," used on the Atlas D, which was the first operational Atlas ICBM and later became a launch vehicle under Project Mercury. Both MA-1 and MA-2 systems used a common turbopump feed system in which the turbopumps for fuel and oxidizer operated from a single gas gen­erator and provided propellants to booster and sustainer engines. For the MA-2, the boosters provided a slightly higher specific im­pulse, with that of the sustainer also increasing slightly. The overall thrust of the boosters rose to 309,000 pounds; that of the sustainer climbed to 57,000 pounds. An MA-5 engine was initially identical to the MA-2 but used on space-launch vehicles rather than missiles. In development during 1961-73, the booster engines went through several upratings, leading to an ultimate total thrust of 378,000 pounds (compared to 363,000 for the MA-2).

The overall MA-3 engine system contained separate subsystems for each of the booster and sustainer engines. Each engine had its own turbopump and gas generator, with the booster engines being identical to one another. The MA-3 exhibited a number of other changes from the MA-2, including greater simplification and bet­ter starting reliability resulting from hypergolic thrust-chamber ig­nition. A single electrical signal caused solid-propellant initiators and gas-generator igniters to begin the start sequence. Fuel flow

FIG. 3.6

Подпись: C-1983-780Подпись: INLETSПодпись:Подпись: PASSAGESПодпись: OXIDIZERПодпись:Подпись: IGNITIONПодпись: FUELПодпись:Подпись: BOOSTED ENGINE THRUST CHAMBER INJECTORAtlas PropulsionTechnical drawing of an injector for an MA-5 booster engine, used on the Atlas space-launch vehicle, 1983. (Photo courtesy of NASA)

National Aeronautics and Space Administration Lewis Research Center

through an igniter fuel valve burst a diaphragm holding a hypergolic cartridge and pushed it into the thrust chambers. Oxygen flow oc­curred slightly ahead of the fuel, and the cartridge with its triethyl aluminum and triethyl boron reacted with the oxygen in the thrust chamber and began combustion. Hot gases from combustion oper­ated the turbopump, a much more efficient arrangement than previ­ous turbopumps operated by hydrogen peroxide in rockets like the 126 V-2 and Redstone.

Chapter 3 The MA-3 sustainer engine had a slightly higher specific impulse of almost 215 lbf-sec/lbm but the same thrust (57,000 pounds) as the MA-2 sustainer. The total thrust of the boosters, however, went up to 330,000 pounds with a climb in specific impulse to about 250 lbf-sec/lbm. Both specific impulses were at sea level. At altitude the specific impulse of the sustainer rose to almost 310 and that of the boosters to nearly 290 lbf-sec/lbm. The higher value for the sustainer engine at altitude resulted from the nozzles that were de­signed for the lower pressure outside Earth’s atmosphere. The MA-3 appeared on the Atlas E and F missiles, with production running from 1961 to 1964.42

Most of the changes from the MA-1 to the MA-3 resulted from a decision in 1957 by Rocketdyne management to create an Experi­mental Engines Group under the leadership of Paul Castenholz, a

design and development engineer who had worked on combustion devices, injectors, and thrust chambers. He “enjoyed a reputation at Rocketdyne as a very innovative thinker, a guy who had a lot of en­ergy, a good leader." The group consisted of about 25 mostly young people, including Dick Schwarz, fresh out of college and later presi­dent of Rocketdyne. Bill Ezell, who was the development supervi­sor, had come to NAA in 1953 and was by 1957 considered an “old- timer" in the company at age 27. Castenholz was about 30. Before starting the experimental program, Ezell had just come back from Cape Canaveral, where there had been constant electrical problems on attempted Thor launches. The Atlas and Thor contracts with the air force each had a clause calling for product improvement, which was undefined, but one such improvement the group sought was to reduce the number of valves, electrical wires, and connections that all had to function in a precise sequence for the missile to operate.

Подпись: 127 Propulsion with Alcohol and Kerosene Fuels, 1932-72 The experimental engineers wanted a system with one wire to start the engine and one to stop it. Buildup of pressure from the turbopump would cause all of the valves to “open automatically by using the. . . propellant as the actuating fluid." This one-wire start arrangement became the solid-propellant mechanism for the MA-3, but the engineers under Castenholz first used it on an X-1 ex­perimental engine on which Cliff Hauenstein, Jim Bates, and Dick Schwarz took out a patent. They used the Thor engine as the start­ing point and redesigned it to become the X-1. Their approach was mostly empirical, which was different from the way rocket devel­opment had evolved by the 1980s, when the emphasis had shifted to more analysis on paper and with a computer, having simulation precede actual hardware development. In the period 1957 to the early 1960s, Castenholz’s group started with ideas, built the hard­ware, and tried it out, learning from their mistakes.

Stan Bell, another engineer in Castenholz’s group, noted a further difference from the 1980s: “We were allowed to take risks and to fail and to stumble and to recover from it and go on. Now, everything has got to be constantly successful." Jim Bates added that there were not any “mathematical models of rocket engine combustion processes" in the late 1950s and early 1960s. “There weren’t even any computers that could handle them," but, he said, “we had our experience and hindsight."

The reason the engineers in the group moved to a hypergolic ig­niter was that existing pyrotechnic devices required a delicate bal­ance. It proved difficult to get a system that had sufficient power for a good, assured ignition without going to the point of a hard start that could damage hardware. This led them to the hypergolic cartridge

(or slug) used on the MA-3. In the process of developing it, however, the group discovered that a little water in the propellant line ahead of the slug produced combustion in the line but not in the chamber; there the propellants built up and caused a detonation, “blow[ing] hell out of an engine," as Bill Ezell put it. They learned from that experience to be more careful, but Ezell said, “there’s probably no degree of analysis that could have prevented that from happening." There were simply a lot of instances in rocket-engine development where the experimenters had to “make the right guess or assump­tion"; otherwise, there was “no way to analyze it. So you’ve got to get out and get the hard experience." Ezell also opined that “with­out the Experimental Engine program going, in my opinion there never would have been a Saturn I," suggesting a line of evolution from their work to later engines.43

The experiences and comments of the members of Castenholz’s group illuminate the often dimly viewed nature of early rocket en­gineering. Without the product-improvement clauses in the Atlas and Thor contracts, a common practice of the Non-Rotating Engine Branch of the Power Plant Laboratory at Wright-Patterson AFB, the innovations made by this group probably would not have occurred. They thus would not have benefited Thor and Atlas as well as later projects like Saturn I. Even with the clauses, not every company would have put some 25 bright, young engineers to work on pure experiment or continued their efforts after the first engine explo­sion. That Rocketdyne did both probably goes a long way toward explaining why it became the preeminent rocket-engine producer in the country.

The changes in the Atlas engines to the MA-3 configuration as 128 a result of the experimental group’s work did not resolve all of the Chapter 3 problems with the Atlas E and F configurations. The Atlas lifted off with all three engines plus its two verniers (supplementary en­gines) firing. Once the missile (or later, launch vehicle) reached a predetermined velocity and altitude, it jettisoned the booster en­gines and structure, with the sustainer engine and verniers then continuing to propel the remaining part of the rocket to its destina­tion. The separation of the booster sections occurred at disconnect valves that closed to prevent the loss of propellant from the feed lines. This system worked through the Atlas D but became a major problem on the E and F models, with their independent pumps for each engine (rather than the previous common turbopump for all of them). Also, the E and F had discarded the use of water in the regen­erative cooling tubes because it reacted with the hypergolic slug. The water had ensured a gentle start with previous igniters. With

the hypergolic device, testing of the engines by General Dynamics had produced some structural damage in the rear of the missile. Design fixes included no thought of a large pressure pulse when the new models ignited.

On June 7, 1961, the first Atlas E launched from Vandenberg AFB on the California coast at an operational launch site that used a dry flame bucket rather than water to absorb the missile’s thrust. The missile lifted off and flew for about 40 seconds before a failure of the propulsion system resulted in destruction of the missile, with its parts landing on the ground and recovered. Rocketdyne specialists analyzed the hardware and data, concluding that a pressure pulse had caused the problem. The pulse had resulted in a sudden up­ward pressure from the dry flame bucket back onto fire-resistant blankets called boots that stretched from the engines’ throat to the missile’s firewall to form a protective seal around the gimballing engines. The pressure caused one boot to catch on a drain valve at the bottom of a pressurized oil tank that provided lubrication for the turbopump gearbox. The tank drained, and the gearbox ceased to operate without lubrication. To solve this problem, engineers re­sorted to a new liquid in the cooling tubes ahead of the propellants to soften ignition and preclude pressure pulses.

Подпись: 129 Propulsion with Alcohol and Kerosene Fuels, 1932-72 Repeated failures of different kinds also occurred during the flight-test program of the E and F models at Cape Canaveral. Control instrumentation showed a small and short-lived pitch upward of the vehicle during launch. Edward J. Hujsak, assistant chief engineer for mechanical and propulsion systems for the Atlas airframe and as­sembly contractor, General Dynamics, reflected about the evidence and spoke with the firm’s director of engineering. Hujsak believed that the problem lay with a change in the geometry of the propellant lines for the E and F models that allowed RP-1 and liquid oxygen (ex­pelled from the booster engines when they were discarded) to mix. Engineers “did not really know what could happen behind the mis­sile’s traveling shock front" as it ascended, but possibly the mixed propellants were contained in such a way as to produce an explosion. That could have caused the various failures that were occurring.

The solution entailed additional shutoff valves in the feed lines on the booster side of the feed system, preventing expulsion of the propellants. Engineers and technicians had to retrofit these valves in the operational missiles. However, the air force decided that since there could be no explosion if only one of the propellants were cut off, the shutoff valves would be installed only in the oxygen lines. A subsequent failure on a test flight convinced the service to approve installation in the fuel lines as well, solving the problem.44 Here

130

Подпись:Atlas PropulsionChapter 3

was a further example of engineers not always fully understanding how changes in a design could affect the operation of a rocket. Only failures in flight testing and subsequent analysis pinpointed prob­lem areas and provided solutions.

Double-Base Propellants during and Soon after World War II

At the beginning of recent solid-propellant development during World War II, the vast majority of rockets produced for use in com­bat employed extruded double-base propellants. These were limited in size by the nature of the extrusion process used at that time to produce them. In extrusion using a solvent, nitrocellulose was sus­pended in the solvent, which caused the nitrocellulose to swell. It was formed into a doughlike composition and then extruded (forced) through dies to form it into grains. This process of production lim­ited the size of the grains to thin sections so the solvent could evap­orate, and the elasticity of the grain was too low for bonding large charges to the motor case. With a solventless (or dry) process, there 232 were also limitations on the size of the grain and greater hazards of Chapter 6 explosion than with extrusion using a solvent.

These factors created the need for castable double-base propel­lants. But before a truly viable process for producing large castable propellants could be developed, the United States, because it was at war, needed a variety of rockets to attack such targets as ships (including submarines), enemy fortifications, gun emplacements, aircraft, tanks, and logistical systems. The development of these weapons did not lead directly to any launch-vehicle technology, but the organizations that developed them later played a role in furthering that technology. Two individuals provided the leader­ship in producing the comparatively small wartime rockets with extruded grains. One was Clarence Hickman, who had worked with Goddard on rockets intended for military applications during World War I. He then earned a Ph. D. at Clark University and went to work at Bell Telephone Laboratories. After consulting with God­dard, in June 1940 Hickman submitted a series of rocket proposals to Frank B. Jewett, president of Bell Labs and chairman of a divi­sion in the recently created National Defense Research Committee (NDRC). The upshot was the creation of Section H (for Hickman) of the NDRC’s Division of Armor and Ordnance. Hickman’s section had responsibility for researching and developing rocket ordnance. Although Section H was initially located at the Naval Proving Ground at Dahlgren, Virginia, it worked largely for the army.

Hickman chose to use wet-extruded, double-base propellants (em­ploying a solvent) because he favored the shorter burning times they afforded compared with dry-extruded ones. He and his associates worked with this propellant at Dahlgren, moved to the Navy Pow­der Factory at Indian Head, Maryland, and finally to Allegany Ord­nance Plant, Pinto Branch, on the West Virginia side of the Potomac

River west of Cumberland, Maryland. There at the end of 1943 they set up Allegany Ballistics Laboratory, a rocket-development facility operated for Section H by George Washington University. By using traps, cages, and other devices to hold the solvent-extruded, double­base propellant, they helped develop the bazooka antitank weapon, a 4.5-inch aircraft rocket, JATO devices with less smoke than those produced by Aerojet using Parson’s asphalt-based propellant, and a recoilless gun.22 Under different management, ABL later became an important producer of upper stages for missiles and rockets.

Подпись:Hickman’s counterpart on the West Coast was physics professor Charles Lauritsen of Caltech. Lauritsen was vice chairman of the Division of Armor and Ordnance (Division A), and in that capacity he had made an extended trip to England to observe rocket devel­opments there. The English had developed a way to make solvent­less, double-base propellant by dry extrusion. This yielded a thicker grain that would burn longer than the wet-extruded propellant but required extremely heavy presses for the extrusion. However, the benefits were higher propellant loading and the longer burning time that Lauritsen preferred.

Convinced of the superiority of this kind of extrusion and be­lieving that the United States needed a larger rocket program than Section H could provide with its limited facilities, Lauritsen argued successfully for a West Coast program. Caltech then set up opera­tions in Eaton Canyon in the foothills of the San Gabriel Moun­tains northeast of the campus in Pasadena. It operated from 1942 to 1945 and expanded to a 3,000-person effort involving research, development, and pilot production of rocket motors; development of fuses and warheads; and static and flight testing. The group pro­duced an antisubmarine rocket 7.2 inches in diameter, a 4.5-inch barrage rocket, several retro-rockets (fired from the rear of airplanes at submarines), 3.5- and 5-inch forward-firing aircraft rockets, and the 11.75-inch “Tiny Tim" rocket that produced 30,000 pounds of thrust and weighed 1,385 pounds. (This last item later served as a booster for the WAC Corporal.)

By contrast with Section H, Section L (for Lauritsen) served mainly the navy’s requirements. In need of a place to test and eval­uate the rockets being developed at Eaton Canyon, in November 1943 the navy established the Naval Ordnance Test Station (NOTS) in the sparsely populated desert region around Inyokern well north of the San Gabriel Mountains. Like the Allegany Ballistics Labora­tory, NOTS was destined to play a significant role in the history of U. S. rocketry, mostly with tactical rockets but also with contribu­tions to ballistic missiles and launch vehicles.

One early contribution was the “White Whizzer" 5.0-inch rocket developed by members of the Caltech team who had already moved to NOTS but were still under direction of the university rather than the navy. By about January1944, combustion instability had become a problem with the 2.25-inch motors for some of the tactical rock­ets. These rockets used tubular, partially internal-burning charges of double-base propellant. Radial holes in the grain helped solve se­vere pressure excursions—it was thought, by allowing the gas from the burning propellant to escape from the internal cavity. Edward W. Price, who had not yet received his bachelor’s degree but would later become one of the nation’s leading experts in combustion in­stability, suggested creating a star-shaped perforation in the grain for internal burning. He thought this might do a better job than the 234 radial holes in preventing oscillatory gas flow that was causing the Chapter 6 charges of propellant to split. He tested the star perforation, and it did produce stable burning.

In 1946, Price applied this technique to the White Whizzer, which featured a star-perforated, internal-burning grain with the outside of the charge wrapped in plastic to inhibit burning there. This ge­ometry allowed higher loading of propellant (the previous design having channels for gas flow both inside and outside the grain). And since the grain itself protected the case from the heat in the internal cavity, the case could be made of lightweight aluminum, providing better performance than heavier cases that were slower to accelerate because of the additional weight. Ground-launched about May 1946, the White Whizzer yielded a speed of 3,200 feet per second, then a record for solid rockets. The internal-burning, aluminum-cased design features later appeared in the 5.0-inch Zuni and Sidewinder tactical missiles. The internal-burning feature of the design also came to be applied to a great many other solid rock­ets, including ballistic missiles and stages for launch vehicles. This apparently was the first flight of a rocket using such a grain design in the United States, preceding JPL’s use of a similar design, known as the Deacon, and also flight testing of the first member of the Vicar family to be flown.23

Polaris and Minuteman

Jupiter, Thor, and Atlas marked a huge step forward in the matura­tion of U. S. rocketry, but before the technology from those missiles came to significant use in launch vehicles, the navy’s development of the Polaris inaugurated a solid-propellant breakthrough in mis­sile technology that also profoundly affected launch vehicles.82 Un­til Polaris A1 became operational in 1960, all intermediate-range and intercontinental missiles in the U. S. arsenal had employed liq­uid propellants. These had important advantages in terms of perfor­mance but required extensive plumbing and large propellant tanks that made protecting them in silos difficult and expensive. Such factors also virtually precluded their efficient use onboard ships, especially submarines. Once Minuteman I became operational in 1962, the U. S. military began to phase out liquid-propellant stra­tegic missiles. To this day, Minuteman III and the solid-propellant fleet ballistic missiles continue to play a major role in the nation’s strategic defenses because they are simpler and cheaper to operate than liquid-propellant missiles.

Because of the higher performance of some liquid propellants and 40 their ability to be throttled as well as turned off and on by the use of Chapter 1 valves, they remained the primary propellants for space-launch ve­hicles. However, since solid-propellant boosters could be strapped on the sides of liquid-propellant stages for an instant addition of high thrust (because their thrust-to-weight ratio is higher, allowing

faster liftoff), solid-propellant boosters became important parts of launch-vehicle technology. The technologies used on Polaris and Minuteman transferred to such boosters and also to upper stages of rockets used to launch satellites. Thus, the solid-propellant break­through in missiles had important implications for launch-vehicle technology. By the time that Polaris got under way in 1956 and Minuteman in 1958, solid-propellant rocketry had already made tremendous strides from the use of extruded double-base propel­lants in World War II tactical missiles. But there were still enor­mous technical hurdles to overcome before solid-propellant missiles could hope to launch strategic nuclear warheads far and accurately enough to serve effectively as a deterrent or as a retaliatory weapon in case of enemy aggression.83

With a much smaller organization than the army or air force, a navy special projects office under the leadership of Capt. (soon-to-be Rear Adm.) William F. Raborn pushed ahead to find the right tech­nologies for a submarine-launched, solid-propellant missile, a daunt­ing task since a solid propellant with the necessary performance did not yet exist. Capt. Levering Smith—who, at the Naval Ord­nance Test Station (NOTS), had led the effort to develop a 50-foot solid-propellant missile named “Big Stoop" that flew 20 miles in 1951—joined Raborn’s special projects office in April 1956. Smith contributed importantly to Polaris, but one key technical discovery came from the Atlantic Research Corporation (ARC), a chemical firm founded in 1949 with which the Navy Bureau of Ordnance had contracted to improve the specific impulse of solid propellants (the ratio of thrust a rocket engine or motor produced to the amount of propellant needed to produce that thrust).84

ARC’s discovery that the addition of comparatively large quan­tities of aluminum to solid propellants significantly raised perfor­mance, together with the work of Aerojet chemists, led to successful propellants for both stages of Polaris A1. The addition of aluminum to Aerojet’s binder essentially solved the problem of performance for both Polaris (and, as it turned out, with a different binder, for Minuteman). Other key technical solutions relating to guidance and an appropriate warhead led to the directive on December 8, 1956, that formally began the Polaris program.85

Подпись: 41 German and U.S. Missiles and Rockets, 1926-66 Flight testing of Polaris at the air force’s Cape Canaveral (be­ginning in 1958 in a series designated AX) revealed a number of problems. Solutions required considerable interservice cooperation. On July 20, 1960, the USS George Washington launched the first functional Polaris missile. The fleet then deployed the missile on November 15, 1960.86

The navy quickly moved forward to Polaris A2. It increased the range of the fleet ballistic missile from 1,200 to 1,500 miles. Flight testing of the A2 missiles started in November 1960, with the first successful launch from a submerged submarine occurring on Octo­ber 23, 1961. The missile became operational less than a year later in June 1962. Polaris A3 was still more capable, with a range of 2,500 miles. It incorporated many other new technologies in both propulsion and guidance/control, becoming operational on Septem­ber 28, 1964. All three versions of Polaris made significant contri­butions to launch-vehicle technology, such as the Altair II motor, produced by the Hercules Powder Company under sponsorship of the Bureau of Naval Weapons and NASA and used as a fourth stage for the Scout launch vehicle.87

While Polaris was still in development, the air force had officially begun work on Minuteman I. Its principal architect was Edward N. Hall, a heterogeneous engineer who helped begin the air force’s involvement with solid propellants as a major at Wright-Patterson AFB in the early 1950s. As Karl Klager, who worked on both Polaris and Minuteman, has stated, Hall “deserves most of the credit for maintaining interest in large solid rocket technology [during the mid-1950s] because of the greater simplicity of solid systems over liquid systems." Hall’s efforts “contributed substantially to the Polaris program," Klager added, further illustrating the extent to which (unintended) interservice cooperation and shared informa­tion contributed to the solid-propellant breakthrough. Hall moved to the WDD as the chief for propulsion development in the liq­uid-propellant Atlas, Titan, and Thor programs, but he continued his work on solids, aided by his former colleagues back at Wright – Patterson AFB.88

Despite this sort of preparatory work for Minuteman, the mis­sile could not begin its formal development until the air force se­cured final DoD approval in February 1958, more than a year later than Polaris. Hall and others at WDD had a difficult job convincing Schriever in particular to convert to solids. Without their heteroge­neous engineering, the shift to solids might never have happened. They were aided, however, by development of Polaris because it provided what Harvey Sapolsky has dubbed “competitive pressure" for the air force to develop its own solid-propellant missile.89

Soon after program approval, Hall left the Ballistic Missile Divi­sion. From August 1959 to 1963, the program director was Col. (soon promoted to Brig. Gen.) Samuel C. Phillips. Hall and his coworkers deserve much credit for the design of Minuteman and its support by the air force, whereas Phillips brought the missile to completion.

Facing many technical hurdles, Phillips succeeded as brilliantly as had Levering Smith with Polaris in providing technical manage­ment of a complex and innovative missile. Often using trial-and – error engineering, his team working on the three-stage Minuteman I overcame problems with materials for nozzle throats in the lower stages, with firing the missile from a silo, and with a new binder for the first stage called polybutadiene-acrylic acid-acrylonitrile (PBAN), developed by the contractor, Thiokol Chemical Corpora­tion. Incorporating substantial new technology as well as some bor­rowed from Polaris, the first Minuteman I wing became operational in October 1962.90

Minuteman II included a new propellant in stage two, known as carboxy-terminated polybutadiene and an improved guidance/con – trol system. The new propellant yielded a higher specific impulse, and other changes (including increased length and diameter) made Minuteman II a more capable and accurate missile than Minute – man I. The newer version gradually replaced its predecessor in mis­sile silos after December 1966.91

In Minuteman III, stages one and two did not change from Min – uteman II, but stage three became larger. Aerojet replaced Hercules as the contractor for the new third stage. With the larger size and a different propellant, the third stage more than doubled its total impulse. These and other modifications allowed Minuteman IIIs to achieve their initial operational capability in June 1970. As a result of the improvements, the range of the missile increased from about 6,000 miles for Minuteman I to 7,021 for Minuteman II, and 8,083 for Minuteman III.92

Подпись: 43 German and U.S. Missiles and Rockets, 1926-66 The deployment of Minuteman I in 1961 marked the completion of the solid-propellant breakthrough in terms of its basic technol­ogy, though innovations and improvements continued to occur. But the gradual phaseout of liquid-propellant missiles followed almost inexorably from the appearance on the scene of the first Minuteman. The breakthrough in solid-rocket technology required the extensive cooperation of a great many firms, government laboratories, and uni­versities, only some of which could be mentioned here. It occurred on many fronts, ranging from materials science and metallurgy through chemistry to the physics of internal ballistics and the mathematics and physics of guidance and control, among many other disciplines. It was partially spurred by interservice rivalries for roles and mis­sions. Less well known, however, was the contribution of interser­vice cooperation. Necessary funding for advances in and the sharing of technology came from all three services, the Advanced Research Projects Agency, and NASA. Technologies such as aluminum fuel,

methods of thrust vector control, and improved guidance and con­trol transferred from one service’s missiles to another. Also crucial were the roles of heterogeneous engineers like Raborn, Schriever, and Hall. But a great many people with more purely technical skills, such as Levering Smith and Sam Phillips, ARC, Thiokol, and Aerojet engineers made vital contributions.

The solid-propellant breakthrough that these people and many others achieved had important implications for launch vehicles as well as missiles. The propellants for the large solid-rocket boosters on the Titan III, Titan IVA, and the Space Shuttles were derived from the one used on Minuteman, stage one. Without ARC’s dis­covery of aluminum as a fuel and Thiokol’s development of PBAN as a binder, it is not clear that the huge Titan and shuttle boosters would have been possible. Many other solid-propellant formula­tions also used aluminum and other ingredients of the Polaris and Minuteman motors. Although some or all of them might have been developed even if there had been no urgent national need for solid – propellant missiles, it seems highly unlikely that their development would have occurred as quickly as it did without the impetus of the cold-war missile programs and their generous funding.

Propulsion for the Saturn Launch Vehicles

There were other developments relating to kerosene-based engines for Thor and Delta, among other vehicles, but the huge Saturn en­gines marked the most important step forward in the use of RP-1 for launch-vehicle propulsion. The H-1 engine for the Saturn I’s first stage resulted from the work of the Rocketdyne Experimental Engines Group on the X-1. Under a contract to the Army Ballistic

Propulsion for the Saturn Launch VehiclesПодпись: 131 Propulsion with Alcohol and Kerosene Fuels, 1932-72 Подпись: Missile Agency (ABMA), let on September 1, 1958, Rocketdyne suc-ceeded in building on its X-1 development to deliver the first production version of the H-1 in a little over half a year. This version had only 165,000 pounds of thrust, however, less than the Thor MB-3, Block II, but the H-1 went through versions of 188,000, 200,000, and 205,000 pounds as the Saturn project evolved, with Saturn I using the first two, and Saturn IB, the final pair.45 One problem with the 165,000-pound-thrust H-1 was that it still used a 20-gallon pressurized oil tank to lubricate the turbopump gearbox, as had the Thor-Jupiter engine. Later, 188,000-pound versions of the engine eliminated this problem by using RP-1 with an additive to lubricate the gearbox. This modification required a blender that mixed fuel from the turbopump with the additive and supplied it to the gearbox. The H-1 also featured a simplified starting sequence. Instead of auxiliary start tanks under pressure to supply oxygen and RP-1 to begin operation of the turbopump, a solid- propellant device started the turbines spinning. The engine kept the hypergolic ignition procedure used in the Atlas MA-3 and the later Thor-Jupiter engines.46 Rocketdyne delivered the first 165,000-pound H-1 engine to ABMA on April 28, 1959. Von Braun and his engineers conducted the first static test on this engine 28 days later, with an 8-second, eight-engine test following on April 29, 1960. On May 17, 1960, a second static test of eight clustered engines lasted 24 seconds and generated a thrust of 1.3 million pounds. That fall, the engine
H-1 engines, which were used in a cluster of eight to power the first stage of both the Saturn I and the Saturn IB. (Photo courtesy of NASA)

passed its preliminary flight-rating tests, leading to the first flight test on October 27, 1961.47

Meanwhile, Rocketdyne had begun uprating the H-1 to 188,000 pounds of thrust, apparently by adjusting the injectors and increas­ing the fuel and oxidizer flow rates. Although the uprated engine was ready for its preliminary flight-rating tests on September 28, 1962, its uprating created problems with combustion instability that en­gineers had not solved by that time but did fix without detriment to the schedule. The first launch of a Saturn I with the 188,000-pound engine took place successfully on January 29, 1964.48

Development had not been unproblematic. Testing for combus­tion instability (induced by setting off small bombs in the combus­tion chamber beginning in 1963) showed that the injectors inher­ited from the Thor and Atlas could not recover and restore stable combustion once an instability occurred. So Rocketdyne engineers rearranged the injector orifices and added baffles to the injector face. These modifications solved the problem. Cracks in liquid-oxygen domes and splits in regenerative-cooling tubes also required rede­sign. Embrittlement by sulfur from the RP-1 in the hotter environ­ment of the 188,000-pound engine required a change of materials in the tubular walls of the combustion chamber from nickel alloy to stainless steel. There were other problems, but the Saturn person­nel resolved them in the course of the launches of Saturn I and IB from late 1961 to early 1968.49

Because the H-1s would be clustered in two groups of four each for the Saturn I first stage, there were two types of engines. H-1Cs used for the four inboard engines were incapable of gimballing to steer the first stage. The four outboard H-1D engines did the gim – 132 balling. Both versions used bell-shaped nozzles, but the outboard Chapter 3 H-1Ds used a collector or aspirator to channel the turbopump exhaust gases, which were rich in unburned RP-1 fuel, and deposit them in the exhaust plume from the engines to prevent the still-combustible materials from collecting in the first stage’s boat tail.50

The first successful launch of Saturn I did not mean that devel­opers had solved all problems with the H-1 powerplant. On May 28, 1964, Saturn I flight SA-6 unexpectedly confirmed that the first stage of the launch vehicle could perform its function with an en­gine out, a capability already demonstrated intentionally on flight SA-4 exactly 14 months earlier. An H-1 engine on SA-6 ceased to function 117.3 seconds into the 149-second stage-one burn. Telem­etry showed that the turbopump had ceased to supply propellants. Analysis of the data suggested that the problem was stripped gears in the turbopump gearbox. Previous ground testing had revealed to

Подпись: FIG. 3.9 Launch of a Saturn IB vehicle on the Skylab 4 mission from Launch Complex 39B at Kennedy Space Center on November 16, 1973. (Photo courtesy of NASA)
Propulsion for the Saturn Launch Vehicles

Rocketdyne and Marshall technicians that there was need for rede­sign of the gear’s teeth to increase their width. Already programmed to fly on SA-7, the redesigned gearbox did not delay flight testing, and there were no further problems with H-1 engines in flight.51

Подпись: 133 Propulsion with Alcohol and Kerosene Fuels, 1932-72 None of the sources for this history explain exactly how Rock­etdyne increased the thrust of each of the eight H-1 engines from 188,000 to 200,000 pounds for the first five Saturn IBs (SA-201 through SA-205) and then to 205,000 pounds for the remaining ve­hicles. It would appear, as with the uprated Saturn I engines, that the key lay in the flow rates of the propellants into the combustion chambers, resulting in increased chamber pressure. After increasing with the shift from the 165,000- to the 188,000-pound H-1s, these flow rates increased again for the 200,000-pound and once more for the 205,000-pound H-1s.52

LAUNCH VEHICLE ENGINES

H-l ON SATURN IB FIRST STAGE

F-l ON SATURN V FIRST STAGE

J-2 ON SATURN IB

SECOND STAGE

J-2 ON SATURN V SECOND STAGE

Подпись: MSEC-69-IND 14900* ALSO SATURN V THIRD STAGE

FIG. 3.10 Diagram of the engines used on the Saturn IB and Saturn V. The Saturn IB used eight H-1s on its first stage and a single J-2 on its second stage; the Saturn V relied on five F-1 engines for thrust in its first stage, with five J-2s in the second and one J-2 in the third stage. (Photo courtesy of NASA)

For the Saturn V that launched the astronauts and their spacecraft into their trajectory toward the Moon for the six Apollo Moon land­ings, the first-stage engines had to provide much more thrust than the eight clustered H-1s could supply. Development of the larger F-1 engine by Rocketdyne originated with an air force request in 1955. NASA inherited the reports and other data from the early de – 134 velopment, and when Rocketdyne won the NASA contract to build Chapter 3 the engine in 1959, it was, “in effect, a follow-on" effort. Since this agreement preceded a clear conception of the vehicle into which the F-1 would fit and the precise mission it would perform, designers had to operate in a bit of a cognitive vacuum. They had to make early assumptions, followed by reengineering to fit the engines into the actual first stage of the Saturn V, which itself still lacked a firm configuration in December 1961 when NASA selected Boeing to build the S-IC (the Saturn V first stage). Another factor in the design of the F-1 resulted from a decision “made early in the program. . . [to make] the fullest possible use of components and techniques proven in the Saturn I program."

Propulsion for the Saturn Launch VehiclesIn 1955, the goal had been an engine with a million pounds of thrust, and by 1957 Rocketdyne was well along in developing it. That year and the next, the division of NAA had even test-fired

Propulsion for the Saturn Launch Vehicles

SATURN IB LAUNCH VEHICLE

 

PROPOSED MISSIONS

 

CHARACTERISTICS

 

Propulsion for the Saturn Launch Vehicles

• APOLLO SPACECRAFT DEVELOP­MENT AND ORBITAL MANEUVERS

• APOLLO CREW TRAINING IN LM RENDEZVOUS AND DOCKING

•ADVANCE LARGE BOOSTER TECHNOLOGY

•ORBIT LARGE SCIENTIFIC PAYLOADS

 

Propulsion for the Saturn Launch Vehicles

Propulsion for the Saturn Launch Vehicles

MS’C-M-INO HAM

such an engine, with much of the testing done at Edwards AFB’s rocket site, where full-scale testing continued while Rocketdyne did the basic research, development, and production at its plant in Canoga Park. It conducted tests of components at nearby Santa Su – sana Field Laboratory. At Edwards the future air force Rocket Pro­pulsion Laboratory (so named in 1963) had three test stands (1-A, 1-B, and 2-A) set aside for the huge engine. The 1959 contract with NASA called for 1.5 million pounds of thrust, and by April 6, 1961, Rocketdyne was able to static-fire a prototype engine at Edwards whose thrust peaked at 1.64 million pounds.53

Подпись: 135 Propulsion with Alcohol and Kerosene Fuels, 1932-72 Burning RP-1 as its fuel with liquid oxygen as the oxidizer, the F-1 did not break new ground in its basic technology. But its huge thrust level required so much scaling up that, as an MSFC publica­tion said, “An enlargement of this magnitude is in itself an inno­vation." For instance, the very size of the combustion chamber— 40 inches in diameter (20.56 inches for the H-1) with a chamber area almost 4 times that of the H-1 (1,257 to 332 square inches)—required new techniques to braze together the regenerative cooling tubes. Also because of the engine’s size, Rocketdyne adopted a gas-cooled, removable nozzle extension to make the F-1 easier to transport.54

The engine was bell shaped and had an expansion ratio of 16:1 with the nozzle extension attached. Its turbopump consisted of a single, axial-flow turbine mounted directly on the thrust chamber with separate centrifugal pumps for the oxidizer and fuel that were driven at the same speed by the turbine shaft. This eliminated the

The huge first stage of the Saturn V launch vehicle being hoisted by crane from a barge onto the B-2 test stand at the Mississippi Test Facility (later the Stennis Space Center) on January 1, 1967. Nozzles for the F-1 engines show at the bottom of the stage. (Photo courtesy of NASA)

Propulsion for the Saturn Launch Vehicles136

Chapter 3

need for a gearbox, which had been a problematic feature of many earlier engines. A fuel-rich gas generator burning the engine pro­pellants powered the turbine. The initial F-1 had the prescribed 1.5 million pounds of thrust, but starting with vehicle 504, Rock – etdyne uprated the engine to 1.522 million pounds. It did so by in­creasing the chamber pressure through greater output from the tur­bine, which in turn required strengthening components (at some expense in engine weight). There were five F-1s clustered in the S-IC stage, four outboard and one in the center. All but the center engine gimballed to provide steering. As with the H-1, there was a hypergolic ignition system.55

Perhaps the most intricate design feature of the F-1 was the in­jection system. As two Rocketdyne engineers wrote in 1989, the

injector “might well be considered the heart of a rocket engine, since virtually no other single component has such a major impact on overall engine performance." The injector not only inserted the propellants into the combustion chamber but mixed them in a pro­portion designed to produce optimal thrust and performance. “As is the case with the design of nearly all complex, high technology hardware," the two engineers added, “the design of a liquid rocket injector is not an exact science, although it is becoming more so as analytical tools are continuously improved. This is because the basic physics associated with all of the complex, combustion pro­cesses that are affected by the design of the injector are only partly known." A portion of the problem lay with the atomization of the propellants and the distribution of the fine droplets to ensure proper mixing. Even as late as 1989, “the atomization process [wa]s one of the most complex and least understood phenomena, and reli­able information [wa]s difficult to obtain." One result of less-than – optimal injector design was combustion instability, whose causes and mechanisms still in 1989 were “at best, only poorly known and understood." Even in 2006, “a clear set of generalized validated design rules for preventing combustion instabilities in new TCs [thrust chambers] ha[d] not yet been identified. Also a good uni­versal mathematical three-dimensional simulation of the complex nonlinear combustion process ha[d] not yet been developed."56

Подпись: 137 Propulsion with Alcohol and Kerosene Fuels, 1932-72 This was still more the case in the early 1960s, and it caused huge problems for development of the F-1 injector. Designers at Rocket – dyne knew from experience with the H-1 and earlier engines that injector design and combustion instability would be problems. They began with three injector designs, all based essentially on that for the H-1. Water-flow tests provided information on the spacing and shape of orifices in the injector, followed by hot-fire tests in 1960 and early 1961. But as Leonard Bostwick, the F-1 engine manager at Marshall, reported, “None of the F-1 injectors exhibited dynamic stability." Designers tried a variety of flat-faced and baffled injec­tors without success, leading to the conclusion that it would not be possible simply to scale up the H-1 injector to the size needed for the F-1. Engineers working on the program did borrow from the H-1 effort the use of bombs to initiate combustion instability, saving a lot of testing to await its spontaneous appearance. But on June 28, 1962, during an F-1 hot-engine test in one of the test stands built for the purpose at the rocket site on Edwards AFB, combustion instabil­ity caused the engine to melt.57

Marshall appointed Jerry Thomson, chief of the MSFC Liquid Fuel Engines Systems Branch, to chair an ad hoc committee to ana-

lyze the problem. Thomson had earned a degree in mechanical en­gineering at Auburn University following service in World War II. Turning over the running of his branch to his deputy, he moved to Canoga Park where respected propulsion engineer Paul Castenholz and a mechanical engineer named Dan Klute, who also “had a spe­cial talent for the half-science, half-art of combustion chamber de­sign," joined him on the committee from positions as Rocketdyne managers. Although Marshall’s committee was not that large, at Rocketdyne there were some 50 engineers and technicians assigned to a combustion devices team, supplemented by people from uni­versities, NASA, and the air force. Using essentially cut-and-try methods, they initially had little success. The instability showed no consistency and set in “for reasons we never quite understood," as Thomson confessed.58

Подпись: 138 Chapter 3 Using high-speed instrumentation and trying perhaps 40-50 de­sign modifications, eventually the engineers found a combination of baffles, enlarged fuel-injection orifices, and changed impinge­ment angles that worked. By late 1964, even following explosions of the bombs, the combustion chamber regained its stability. The en­gineers (always wondering if the problem would recur) rated the F-1 injector as flight-ready in January 1965. However, there were other problems with the injector. Testing revealed difficulties with fuel and oxidizer rings containing multiple orifices for the propellants. Steel rings called lands held copper rings through which the propel­lants flowed. Brazed joints held the copper rings in the lands, and these joints were failing. Engineers gold-plated the lands to create a better bonding surface. Developed and tested only in mid-1965, the new injector rings required retrofitting in engines Rocketdyne had already delivered.59

Overall, from October 1962 to September 1966, there were 1,332 full-scale tests with 108 injectors during the preliminary, the flight­rating, and flight-qualification testing of the F-1 to qualify the en­gine for use. According to one expert, this was “probably the most intensive (and expensive) program ever devoted primarily to solving a problem of combustion instabilities."60

The resultant injector contained 6,300 holes—3,700 for RP-1 and 2,600 for liquid oxygen. Radial and circumferential baffles divided the flat-faced portion of the injector face into 13 compartments, with the holes or orifices arranged so that most of them were in groups of five. Two of the five injected the RP-1 so that the two streams impinged to produce atomization, while the other three in­serted liquid oxygen, which formed a fan-shaped spray that mixed with the RP-1 to combust evenly and smoothly. Driven by the

FIG. 3.13

Fuel tank assembly for the Saturn V S-IC (first) stage being prepared for transportation. (Photo courtesy of NASA)

 

Propulsion for the Saturn Launch Vehicles

52,900-horsepower turbine, the propellant pumps delivered 15,471 gallons of RP-1 and 24,811 gallons of liquid oxygen per minute to the combustion chamber via the injector.61

Подпись: 139 Propulsion with Alcohol and Kerosene Fuels, 1932-72 Despite all the effort that went into the injector design, the turbo­pump required even more design effort and time. Engineers experi­enced 11 failures of the system during development. Two of these involved the liquid-oxygen pump’s impeller, which required use of stronger components. The other 9 failures involved explosions. Causes varied. The high acceleration of the shaft on the turbopump constituted one problem. Others included friction between mov­ing parts and metal fatigue. All 11 failures necessitated redesign or change in procedures. For instance, Rocketdyne made the turbine manifold out of a nickel-based alloy manufactured by GE, Rene 41, which had only recently joined the materials used for rocket en­gines. Unfamiliarity with its welding techniques led to cracking near the welds. It required time-consuming research and training to teach welders proper procedures for using the alloy, which could withstand not only high temperatures but the large temperature dif­ferential resulting from burning the cryogenic liquid oxygen. The final version of this turbopump provided the speed and high vol­umes needed for a 1.5-million-pound-thrust engine and did so with minimal parts and high ultimate reliability.62

Once designed and delivered, the F-1 engines required further testing at Marshall and NASA’s Mississippi Test Facility. At the lat­ter, contractors had built an S-IC stand after 1961 on the mud of a swamp along the Pearl River near the Louisiana border and the Gulf of Mexico. Mosquito ridden and snake infested, this area served as home to wild pigs, alligators, and panthers. Construction workers faced 110 bites a minute from salt marsh mosquitoes, against which nets, gloves, repellent, and long-sleeved shirts afforded little protec­tion. Spraying special chemicals from two C-123 aircraft did reduce the number of bites to 10 per minute, but working conditions re­mained challenging. Nevertheless, the stand was ready for use in March 1967, more than a year after the first static test at Marshall. But thereafter, the 410-foot S-IC stand, the tallest structure in Mis­sissippi, became the focus of testing for the first-stage engines.63

Despite static testing, the real proof of successful design came only in actual flight. For AS-501, the first Saturn V vehicle, the flight on November 9, 1967, largely succeeded. The giant launch vehicle lifted the instrument unit, command and service modules, and a boilerplate lunar module to a peak altitude of 11,240 miles. The third stage then separated and the service module’s propulsion sys­tem accelerated the command module to a speed of 36,537 feet per second (about 24,628 miles per hour), comparable to lunar reentry speed. It landed in the Pacific Ocean 9 miles from its aiming point, where the USS Bennington recovered it. The first-stage engines did experience longitudinal oscillations (known as the pogo effect), but these were comparatively minor.64

Euphoria from this success dissipated, however, on April 4, 1968, when AS-502 (Apollo 6) launched. As with AS-501, this vehicle did 140 not carry astronauts onboard, but it was considered “an all-important Chapter 3 dress rehearsal for the first manned flight" planned for AS-503. The initial launch went well, but toward the end of the first-stage burn the pogo effect became much more severe than on AS-501, reaching five cycles per second, which exceeded the spacecraft’s design speci­fications. Despite the oscillations, the vehicle continued its upward course. Stage-two separation occurred, and all five of the engines ignited. Two of them subsequently shut down, but the instrument unit compensated with longer-than-planned burns for the remain­ing three engines and the third-stage propulsion unit, only to have the latter fail to restart in orbit, constituting a technical failure of the mission, although some sources count it a success.65

As Apollo Program Director Samuel Phillips told the Senate Aero­nautical and Space Sciences Committee on April 22, 1968, 18 days

after the flight, pogo was not a new phenomenon, having occurred in the Titan II and come “into general attention in the early days of the Gemini program." Aware of pogo, von Braun’s engineers had tested and analyzed the Saturn V before the AS-501 flight and found “an acceptable margin of stability to indicate" it would not de­velop. The AS-501 flight “tended to confirm these analyses." Each of the five F-1 engines had “small pulsations," but each engine ex­perienced them “at slightly different points in time." Thus, they did not create a problem. But on AS-502, the five 1.5-million-pound engines “came into a phase relationship" so that “the engine pulsa­tion was additive."66

All engines developed a simultaneous vibration of 5.5 hertz (cy­cles per second). The entire vehicle itself developed a bending fre­quency that increased (as it consumed propellants) to 5.25 hertz about 125 seconds into the flight. The engine vibrations traveled longitudinally up the vehicle structure with their peak occurring at the top where the spacecraft was (and the astronauts would be on a flight carrying them). Alone, the vibrations would not have been a problem, but they coupled with the vehicle’s bending frequency, which moved in a lateral direction. When they intersected (with both at about the same frequency), their effects combined and mul­tiplied. In the draft of an article he wrote for the New York Times, Phillips characterized the “complicated coupling" as “analogous to the annoying feedback squeal you encounter when the microphone and loud speaker of a public address system. . . coupled." This cou­pling was significant enough that it might interfere with astronauts’ performance of their duties.67

Подпись: 141 Propulsion with Alcohol and Kerosene Fuels, 1932-72 NASA formed a pogo task force including people from Marshall, other NASA organizations, contractors, and universities. The task force recommended detuning the five engines, changing the fre­quencies of at least two so that they would no longer produce vi­brations at the same time. Engineers did this by inserting liquid helium into a cavity formed in a liquid-oxygen prevalve with a cast­ing that bulged out and encased an oxidizer feed pipe. The bulging portion was only half filled with the liquid oxygen during engine operation. The helium absorbed pressure surges in oxidizer flow and reduced the frequency of the oscillations to 2 hertz, lower than the frequency of the structural oscillations. Engineers eventually applied the solution to all four outboard engines. Technical people contributing to this solution came from Marshall, Boeing, Martin, TRW, Aerospace Corporation, and North American’s Rocketdyne Division.68 This incidence of pogo showed how difficult it was for

FIG. 3.14

Propulsion for the Saturn Launch VehiclesLaunch of the giant Saturn V on the Apollo 11 mission (July 16, 1969) that carried Neil Armstrong, Edwin Aldrin, and Michael Collins on a trajectory to lunar orbit from which Armstrong and Aldrin descended to walk on the Moon’s surface. (Photo courtesy of NASA)

142

Chapter 3

rocket designers to predict when and how such a phenomenon might occur, even while aware of and actively testing for it. The episode also illustrated the cooperation of large numbers of people from a variety of organizations needed to solve such problems.

The redesign worked. On the next Saturn V mission, Apollo 8 (AS-503, December 21, 1968), the five F-1s performed their mission without pogo (or other) problems. On Christmas Eve the three astro­nauts aboard the spacecraft went into lunar orbit. They completed 10 circuits around the Moon, followed by a burn on Christmas Day to return to Earth, splashing into the Pacific on December 27. For the first time, humans had escaped the confines of Earth’s imme­diate environs and returned from orbiting the Moon. There were no further significant problems with the F-1s on Apollo missions.69

The development of the huge engines had been difficult and unpre­dictable but ultimately successful.

CASTABLE DOUBLE-BASE PROPELLANT

The next major development in double-base propellants was a method for casting (rather than extruding) the grain. The company that produced the first known rocket motor using this procedure was the Hercules Powder Company, which had operated the govern­ment-owned Allegany Ballistics Laboratory since the end of World War II. The firm came into existence in 1912 when an antitrust suit

against its parent company, E. I. du Pont de Nemours & Company, forced du Pont to divest some of its holdings. Hercules began as an explosives firm that produced more than 50,000 tons of smokeless powder during World War I. It then began to diversify into other uses of nitrocellulose. During World War II, the firm supplied large quantities of extruded double-base propellants for tactical rockets. After the war, it began casting double-based propellants by beginning with a casting powder consisting of nitrocellulose, nitroglycerin, and a stabilizer. Chemists poured this into a mold and added a cast­ing solvent of nitroglycerin plus a diluent and the stabilizer. With heat and the passage of time, this yielded a much larger grain than could be produced by extrusion alone.

Подпись:Wartime research by John F. Kincaid and Henry M. Shuey at the National Defense Research Committee’s Explosives Research Laboratory at Bruceton, Pennsylvania (operated by the Bureau of Mines and the Carnegie Institute of Technology), had yielded this process. Kincaid and Shuey, as well as other propellant chemists, had developed it further after transferring to ABL, and under Hercu­les management, ABL continued work on cast double-base propel­lants. This led to the flight testing of a JATO using this propellant in 1947. The process allowed Hercules to produce a propellant grain that was as large as the castable, composite propellants that Aero­jet, Thiokol, and Grand Central were developing in this period but with a slightly higher specific impulse (also with a greater danger of exploding rather than burning and releasing the exhaust gases at a controlled rate).24

The navy had contracted with Hercules for a motor to be used as an alternative third stage on Vanguard (designated JATO X241 A1). The propellant that Hercules’ ABL initially used for the motor was a cast double-base formulation with insulation material between it and the case. This yielded a specific impulse of about 250 lbf-sec/ lbm, higher both than Grand Central’s propellant for its Vanguard third-stage motor and the specification of 245 lbf-sec/lbm for both motors. A key feature of the motor was its case and nozzle, made of laminated fiberglass. ABL had subcontracted work on the case and nozzle to Young Development Laboratories, which developed a method during 1956 of wrapping threads of fiberglass soaked in epoxy resin around a liner made of phenolic asbestos. (A phenol is a compound used in making resins to provide laminated coatings or form adhesives.) Following curing, this process yielded a strong, rigid Spiralloy (fiberglass) shell with a strength-to-weight ratio 20 percent higher than the stainless steel Aerojet was using for its propellant tanks on stage two of Vanguard.25

In 1958, while its third-stage motor was still under development, Hercules acquired this fiberglass-winding firm. Richard E. Young, a test pilot who had worked for the M. W. Kellogg Company on the Manhattan Project, had founded it. In 1947, Kellogg had designed a winding machine under navy contract, leading to a laboratory in New Jersey that built a fiberglass nozzle. It moved to Rocky Hill, New Jersey, in 1948. There, Young set up the development labora­tories under his own name and sought to develop lighter materials for rocket motors. He and the firm evolved from nozzles to cases, seeking to improve a rocket’s mass fraction (the mass of the propel­lant divided by the total mass of a stage or rocket), which was as important as specific impulse in achieving high velocities. In the mid-1950s, ABL succeeded in testing small rockets and missiles us – 236 ing cases made with Young’s Spiralloy material.26

Chapter 6 This combination of a cast double-base propellant and the fiber­glass case and nozzle created a lot of problems for Hercules engi­neers. By February 1957, ABL had performed static tests on about 20 motors, 15 of which resulted in failures of insulation or joints. Combustion instability became a problem on about a third of the tests. Attempting to reduce the instability, Hercules installed a plastic paddle in the combustion zone to interrupt the acoustic pat­terns (resonance) that caused the problem. This did not work as well as hoped, so the engineers developed a suppressor of thicker plastic. They also improved the bond between insulator and case, then cast the propellant in the case instead of just sliding it in as a single piece. Nine cases still failed during hydrostatic tests or static firings. The culprits were high stress at joints and “severe combus­tion instability."27

In February 1958, ABL began developing a follow-on third-stage motor designated X248 A2 in addition to X241. Perhaps it did so in part to reduce combustion instability, because 3 percent of the propellant in the new motor consisted of aluminum, which burned in the motor and produced particles in the combustion gases that suppressed (damped) high-frequency instabilities. But another moti­vation was increased thrust. The new motor was the one that actu­ally flew on the final Vanguard mission, September 18, 1959. As of August 1958, ABL had developed a modification of this motor, X248 A3, for use as the upper stage in a Thor-Able lunar probe. By this time, ABL was testing the motors in an altitude chamber at the air force’s Arnold Engineering Development Center and was experienc­ing problems with ignition and with burnthroughs of the case the last few seconds of the static tests.28

The X248 solid-rocket motor consisted of an epoxy-fiberglass case filled with the case-bonded propellant. The nozzle was still made of epoxy fiberglass, but with a coating of "ceramo-asbestos." By November 11, 1958, wind-tunnel static tests had shown that the X248 A2 filament-wound exit cone was adequate. By this time also, the motor had a sea-level theoretical specific impulse of about 235, which extrapolated to an impulse at altitude of some 255 lbf-sec/ lbm, and designers had overcome the other problems with the mo­tor. The X248 offered a "considerable improvement in reliability and performance over the X241 contracted for originally," according to Kurt Stehling. He also said the ABL version of the third stage suc­cessfully launched the Vanguard III satellite weighing 50 pounds, whereas Grand Central Rocket’s third stage could orbit only about 30 pounds.29

Titan I and Titan II

Simultaneously with the development of Polaris and then Minute – man, the air force continued work on two liquid-propellant missiles, the Titans I and II. The Titan II introduced storable propellants into the missile inventory and laid the groundwork for the core portion of the Titans III and IV space-launch vehicles. Titan I began as es­sentially insurance for Atlas in case the earlier missile’s technology proved unworkable. The major new feature of the first of the Titans was demonstration of the ability to start a large second-stage engine at a high altitude.93 The WAC Corporal had proved the viability of the basic process involved, and Vanguard would develop it further (after Titan I was started). But in 1955, using a full second stage on a ballistic missile and igniting it only after the first-stage engines had exhausted their propellants seemed risky.

The air force approved development of Titan I on May 2, 1955. Meanwhile, the Western Development Division had awarded a 44 contract on January 14, 1955, to Aerojet for engines burning liq – Chapter 1 uid oxygen and a hydrocarbon fuel for possible use on Atlas. These soon evolved into engines for the two-stage missile. Even though the Aerojet engines burned the same propellants as Atlas, there were problems with development, showing that rocket engineers

still did not have the process of design “down to a science." Despite the change in propellants, the Titan II used a highly similar design for its engines, making Aerojet’s development for that missile less problematic than it might otherwise have been (although still not without difficulties), with technology then carrying over into the Titans III and IV core launch vehicles. Meanwhile, the air force de­ployed the Titan Is in 1962. They quickly deactivated in 1965 with the deployment of Minuteman I and Titan II, but Titan I did provide an interim deterrent force.94

The history of the transition from Titan I to Titan II is compli­cated. One major factor stimulating the change was the 15 minutes or so it took to raise Titan I from its silo, load the propellants, and launch it. Another was the difficulty of handling Titan I’s extremely cold liquid oxygen used in Titan I inside a missile silo. One solution to the twin problems would have been conversion to solid propel­lants like those used in Polaris and Minuteman, but another was storable propellants. Under a navy contract in 1951, Aerojet had begun studying hydrazine as a rocket propellant. It had good perfor­mance but could detonate. Aerojet came up with a compromise so­lution, an equal mixture of hydrazine and unsymmetrical dimethyl hydrazine, which it called Aerozine 50. With nitrogen tetroxide as an oxidizer, this fuel mixture ignited hypergolically (upon contact with the oxidizer, without the need for an ignition device), offering a much quicker response time than for Titan I.95 As a result of this and other issues and developments, in November 1959 the Depart­ment of Defense authorized the air force to develop the Titan II. The new missile would use storable propellants, in-silo launch, and an all-inertial guidance system.96

Подпись: 45 German and U.S. Missiles and Rockets, 1926-66 On April 30, 1960, the Air Force Ballistic Missile Division’s de­velopment plan for Titan II called for it to be 103 feet long (compared to 97.4 feet for Titan I), have a uniform diameter of 10 feet (whereas Titan I’s second stage was only 8 feet across), and have increased thrust over its predecessor. This higher performance would increase the range with the Mark 4 reentry vehicle from about 5,500 nauti­cal miles for Titan I to 8,400. With the new Mark 6 reentry vehicle, which had about twice the weight and more than twice the yield of the Mark 4, the range would remain about 5,500 nautical miles. Because of the larger nuclear warhead it could carry, the Titan II served a different and complementary function to Minuteman I’s in the strategy of the air force, convincing Congress to fund them both. It was a credible counterforce weapon, whereas Minuteman I served primarily as a countercity missile, offering deterrence rather than the ability to destroy enemy weapons in silos.97

In May 1960, the air force signed a letter contract with the Mar­tin Company to develop, produce, and test the Titan II. It followed this with a contract to General Electric to design the Mark 6 reentry vehicle. In April 1959, AC Spark Plug had contracted to build an in­ertial guidance system for a Titan missile, although it was not clear at the time that this would be the Titan II.98

Although the Titan II engines were based on those for Titan I, the new propellants and the requirements in the April 30 plan necessi­tated considerable redesign. Because the new designs did not always work as anticipated, the engineers had to resort to empirical solu­tions until they found the combinations that provided the necessary performance. Even with other changes to the Titan I engine designs, the Titan II propulsion system had significantly fewer parts than its Titan I predecessor, reducing chances for failure during operation. Despite the greater simplicity, the engines had higher thrust and higher performance, as planned.99

Flight testing of the Titan II had its problems, complicated by plans to use the missile as a launch vehicle for NASA’s Project Gem­ini, leading to the Project Apollo Moon flights. However, the last 13 flights in the research-and-development series were successful, giving the air force the confidence to declare the missile fully opera­tional on the final day of 1963. Between October and December 1963, the Strategic Air Command deployed six squadrons of nine Titan IIs apiece. They remained a part of the strategic defense of the United States until deactivated between 1984 and 1987. By that time, fleet ballistic missiles and smaller land-based, solid-propellant ballistic missiles could deliver (admittedly smaller) warheads much more accurately than could the Titan IIs. Deactivation left the former operational Titan II missiles available for refurbishment as space – launch vehicles.100

Development of Titan I and Titan II did not require a lot of new technology. Instead, it adapted technologies developed either ear­lier or simultaneously for other missile or launch-vehicle programs. Nevertheless, the process of adaptation for the designs of the two Titan missiles generated problems requiring engineers to use their fund of knowledge to find solutions. These did work, and Titan II became the nation’s longest-lasting liquid-propellant missile with the greatest throw weight of any vehicle in the U. S. inventory.

Early Storable Liquid-Propulsion Efforts

It would appear that the Caltech group had not made great progress on liquid propulsion as of July 1940 when it was joined by Malina’s roommate, Martin Summerfield, who completed work on his Ph. D. during 1941 in the physics department at Caltech. After joining Malina’s group, he went to the Caltech library, consulted the litera­ture on combustion-chamber physics, and found a text with infor­mation on the speed of combustion. Using it, he calculated—much in the fashion of Thiel at Kummersdorf—that the combustion chamber being used by the GALCIT team was far too large, result­ing in heat transfer that degraded performance. So he constructed a smaller chamber of cylindrical shape that yielded a 20 percent increase in performance. Von Karman believed that roughly 25 to 30 percent of the heat in the combustion chamber would be lost, based on information about reciprocating engines. The eminent aerodynamicist had therefore concluded that it would be impossi­ble for rocket engines to be self-cooling, restricting both their light­ness and length of operation. Summerfield’s calculations showed 146 these assumptions about heat transfer to be far too high, indicating Chapter 4 that it was possible for a self-cooling engine to operate for a sus­tained period. Subsequent tests confirmed Summerfield’s calcula­tions, and Malina learned about the technique of regenerative cool­ing from James H. Wyld of Reaction Motors during one of his trips back East.2

For the moment, the group worked with uncooled engines burn­ing RFNA and gasoline. Successive engines of 200, 500, and 1,000 pounds of thrust with various numbers of injectors provided some successes but presented problems with throbbing or incomplete ini­tial ignition, which led to explosions. After four months of efforts to improve combustion and ignition, Malina paid a visit to the Na­val Engineering Experiment Station in Annapolis in February 1942. There he learned that chemical engineer Ray C. Stiff had discovered in the literature of chemistry that aniline ignited hypergolically with nitric acid. Malina telegrammed Summerfield to replace the gasoline with aniline. He did so, but it took three different injector designs to make the 1,000-pound engine work. The third involved eight sets of injectors each for the two propellants, with the stream of pro­pellants washing against the chamber walls. Summerfield recalled

that after 25 seconds of operation, the heavy JATO units glowed cherry red. But they worked on a Douglas A-20A bomber for 44 suc­cessive firings in April 1942, the first successful operation of a liq­uid JATO in the United States. This led to orders by the army air forces (AAF) with the newly formed Aerojet Engineering Corpora­tion, which Malina and von Karman had helped to found.3

Aerojet did considerable business with the AAF and navy for JATO units during the war and had become by 1950 the largest rocket – engine manufacturer in the world, as well as a leader in research and development of rocket technology. Until Aerojet’s acquisition by General Tire in 1944-45, the rocket firm and the GALCIT rocket project maintained close technical relations. Although GALCIT/JPL was involved essentially with JATO work from 1939 to 1944, in the summer of 1942 the project began designing pumps to deliver liquid propellants to a combustion chamber instead of feeding the propel­lants by gas under pressure. By the fall of that year, project engineers were working on using the propellants to cool the combustion cham­ber of a 200-pound-thrust engine.4

Подпись:Meanwhile, as a result of Stiff’s discovery, Truax’s group at Annapolis began using 1,500-pound JATOs burning nitric acid and aniline on navy PBY aircraft in 1943. Both Truax and Stiff subse­quently got orders to work at Aerojet, where Stiff devoted his efforts to a droppable JATO using storable, hypergolic propellants. Aerojet produced about 100 of these units, and some came to be used by the U. S. Coast Guard. In these ways, Aerojet became familiar with use of storable propellants, and Stiff joined the firm after completing his obligatory service with the navy.5

The next important development involving engines with stor­able propellants was the WAC Corporal sounding rocket (the term WAC standing for Women’s Auxiliary Corps or Without Attitude Control, depending upon the source consulted). The Army Ord­nance Corps had requested that Malina’s project investigate the fea­sibility of developing a rocket carrying meteorological equipment that could reach a minimum altitude of 100,000 feet. The JPL team redesigned an Aerojet motor that used monoethylene as a fuel and nitric acid mixed with oleum as an oxidizer. The original motor was regeneratively cooled by the monoethylene. JPL adapted the motor to use RFNA containing 6.5 percent nitrogen dioxide as oxidizer and aniline containing 20 percent furfuryl alcohol as a fuel, thereby increasing the exhaust velocity from 5,600 to 6,200 feet per second but leaving the thrust at 1,500 pounds for 45 seconds. According to one source, the specific impulse was 200 lbf-sec/lbm (slightly lower than the V-2).6

Besides exceeding the requirements of the army, the small, liquid-propellant rocket also functioned as a smaller test version of the Corporal E research vehicle, providing valuable experience in the development of that larger unit. During the testing, the pro­gram decided to modify the WAC Corporal to attain higher alti­tudes. A substantial modification of the engine reduced its weight from 50 to 12 pounds. The WAC A initial version of the rocket had a comparatively thin, cylindrical inner shell of steel for the combus­tion chamber, with an outer shell that fit tightly around it but was equipped with a joint to permit expansion. Helical coils (ones that spiraled around the outside of the combustion chamber like a screw thread) provided regenerative cooling, with a shower-type injector in which eight fuel streams impinged on eight oxidizer streams. For the modified WAC B engine, designers reduced the combustion chamber in length from 73 to 61 inches and made minor modifica­tions to the injector. It had an inner shell spot-welded to the outer shell, still with helical cooling passages. The injector remained a showerhead with eight pairs of impinging jets.7

In a series of flight tests at White Sands Proving Ground, New Mexico, in December 1946, none of the WAC Corporal B vehicles rose more than 175,000 feet in altitude. Apparently the test team suspected cavitation (gas bubbles) in the injector system as the cause of the less-than-optimal performance, since team members 148 constructed three more B-model vehicles with orifice inserts that Chapter 4 were screwed in, rather than drilled as before, to achieve cavitation – free injection of the propellants into the combustion chamber. In three February-March 1947 tests, one WAC Corporal B reached an altitude of 240,000 feet. Overall, the WAC Corporal demonstrated that the propulsion system was sound and the nitric acid-aniline – furfuryl alcohol propellant combination was viable.8

The WAC Corporal led directly to the successful Aerobee sound­ing rocket built by Aerojet, which was used by the Applied Physics Laboratory of Johns Hopkins University for research in the upper atmosphere. Then, in the Bumper-WAC project, the WAC Corporal B flew as a second stage on V-2 missiles. The reported altitude of 244 miles and maximum speed of 7,553 feet per second (reached on February 24, 1949) were records. This highly successful launch demonstrated that a rocket’s velocity could be increased with a sec­ond stage and that ignition of a rocket engine could occur at high altitudes.9

In addition, the engine for the WAC Corporal contributed to the Corporal missile’s propulsion system. As first conceived, Corporal E was a research vehicle for the study of guidance, aerodynamic, and

propulsion problems of long-range rockets. In 1944, von Karman estimated that a rocket with a range of 30 to 40 miles would be necessary to serve as a prototype for a later missile. He thought such a vehicle would need an engine with 20,000 pounds of thrust and 60 seconds of burning time. Experience at JPL to that point had indicated that the only already-developed rocket type meeting von Karman’s specifications would be a liquid-propellant vehicle burn­ing red fuming nitric acid and aniline. Early plans called for use of centrifugal, turbine-driven pumps to feed the propellants. Since Aerojet had a turborocket under development, JPL thought it could draw on the nearby rocket firm’s experience to provide a pump for the Corporal. This design became the never-completed Corporal F. Corporal E used air pressurization, as had the WAC Corporal.10

Подпись:Scaling the WAC Corporal engine up to a larger size proved chal­lenging. The first major design for a Corporal E engine involved a 650-pound, mild-steel version with helical cooling passages. Such a heavy propulsion device resulted from four unsuccessful attempts to scale up the WAC Corporal B engine to 200 pounds. None of them passed their proof testing. In the 650-pound engine, the cool­ing passages were machined to a heavy outer shell that formed a sort of hourglass shape around the throat of the nozzle. The injector consisted of 80 pairs of impinging jets that dispersed the oxidizer (fuming nitric acid) onto the fuel. The direction, velocity, and di­ameter of the streams were similar to those employed in the WAC Corporal A. The injector face was a showerhead type with orifices more or less uniformly distributed over it. It mixed the propellants in a ratio of 2.65 parts of oxidizer to 1 of fuel. The outer shell of the combustion chamber was attached to an inner shell by silver solder. When several of these heavyweight engines underwent proof test­ing, they cracked and nozzle throats eroded as the burning propel­lant exhausted out the rear of the engine. But three engines with the inner and outer shells welded together proved suitable for flight testing.11

On May 22, 1947, the first Corporal E with this heavyweight engine launched from the army’s White Sands Proving Ground. Its intended range was 60 miles, and it actually achieved a range of 62.5 (in one account, 64.25) miles. The second launch occurred on July 17, 1947, but the rocket failed to achieve enough thrust to rise significantly until 90 seconds of burning reduced the weight to the point that it flew a very short distance. On November 4, 1947, the third launch was more successful, but its propellants burned for only 43 (instead of 60) seconds before the engine quit. This reduced its range to just over 14 miles. Both it and the “rabbit killer" (the

second vehicle, so-called because it flew along the ground) expe­rienced burnthroughs in the throat area, the helical cooling coils proving inadequate for their purpose.12

Deciding that in addition to these flaws, the engine was too heavy, the Corporal team determined to design a much lighter-weight en­gine. Several engines combining features of the WAC Corporal B and 650-pound Corporal E combustion chambers all suffered burnouts of the throat area during static tests. Finally, a redesigned engine weighing about 125 pounds stemmed in part from an examination of the V-2, revealing that its cooling passages were axial (with no helix angle, i. e., they took the shortest distance around the combustion chamber’s circumference). Analysis showed the advantage of that ar­rangement, so JPL adopted it. The inner shell of the new engine was corrugated, and the outer shell, smooth. The shape of the combus­tion chamber changed from semispherical to essentially cylindrical, with the inside diameter reduced from 23 to 11 inches and the length shortened slightly, contributing to the much lighter weight.

It took two designs to achieve a satisfactory injector, the first having burned through on its initial static test. The second injector had 52 pairs of impinging jets angled about 2.5 degrees in the direc­tion of (but located well away from) the chamber wall. Initially, the Corporal team retained the mixture ratio of 2.65:1. But static tests of the axially cooled engine in November 1948 at the Ordnance – 150 California Institute of Technology (ORDCIT) Test Station in Muroc, Chapter 4 California (in the Mojave Desert above the San Gabriel Mountains and well north of JPL), showed that lower mixture ratios yielded higher characteristic velocities and specific impulses, as well as smoother operation. Thus, the mixture ratio was first reduced to 2.45 and then 2.2. Later still, the propellant was changed to stabi­lized fuming nitric acid (including a very small amount of hydrogen fluoride) as the oxidizer and aniline-furfuryl alcohol-hydrazine (in the percentages of 46.5, 46.5, and 7.0, respectively) as the fuel. With this propellant, the mixture ratio shifted further downward to 2.13 because of changes in the densities of the propellants. The resul­tant engine, made of mild steel, provided high reliability. Its suc­cess rested primarily upon its “unique configuration, wherein the cool, uncorrugated outer shell carrie[d] the chamber pressure loads, and the thin inner shell, corrugated to form forty-four axial cooling passages, [wa]s copper-brazed to the outer shell." Finally, the inside of the inner shell (the combustion chamber inside face) was plated with chrome to resist corrosion from the propellants.13

The sixth Corporal E launch took place on November 2, 1950. The missile experienced multiple failures. It landed 35.9 miles

downrange, about 35 miles short of projections. Later static tests revealed problems with a propellant regulator that had caused over­rich mixture ratios on both the fifth and sixth launches. Failure of a coupling had resulted in loss of air pressure. The radar beacon to provide overriding guidance in azimuth operated satisfactorily until failure of a flight-beacon transmitter some 36 seconds into the flight. The Doppler beacon never went into operation to cut off propellant flow at the proper moment because the missile failed to achieve the velocity prescribed, but also because the Doppler bea­con itself failed at 24 seconds after liftoff. As a final blow, all elec­tronic equipment failed, apparently from extreme vibration.14

Подпись:On launch seven of the Corporal E in January 1951, the vehicle landed downrange at 63.85 miles, 5 miles short of the targeted im­pact point. This was the first flight to demonstrate propellant shut­off and also the first to use a new multicell air tank and a new air – disconnect coupling. These two design changes to fix some of the problems on launch six increased the reliability of the propulsion system significantly. However, although the Corporal performed even better on launch eight (March 22, 1951), hitting about 4 miles short of the target, on launch nine (July 12, 1951) the missile landed 20 miles beyond the target because of failure of the Doppler tran­sponder and the propellant cutoff system. The final “round" of Cor­poral E never flew. But the Corporal team had learned from the first nine rounds how little it understood about the flight environment of the vehicle, especially vibrations that occurred when it was op­erating. The team began to use vibration test tables to make the design better able to function and to test individual components before installation. This testing resulted in changes of suppliers and individual parts as well as to repairs before launch (or redesigns in the case of multiple failures of a given component.)15

The next 20 Corporals, with the airframes built by Douglas Air­craft (like the Corporal Es), received the designation Corporal I. Its first flight occurred on October 10, 1951. But the frequency regulator for the central power supply failed on takeoff, causing the missile to follow nearly a vertical trajectory. Range safety cut its flight short so that it would impact between White Sands and the city of Las Cruces, New Mexico. Flight 11 (referred to as round 12, counting the last Corporal E, which never launched) occurred on December 6, 1951. Before the launch, the army invited several companies to bid on production contracts as prime contractors. Ryan Aeronautical Company of San Diego manufactured the engines for both the air­frames built by Douglas and those from the new prime contractor, Firestone Tire and Rubber Company of Los Angeles. JPL received

the Firestone missiles and disassembled them for inspection. It then rebuilt them and performed preflight testing before sending them to White Sands for the actual flight tests. Then it sent comments to the manufacturer to help improve factory production. According to Clayton Koppes, however, the two major contractors and JPL failed to work together effectively. Meanwhile, between January and De­cember 1952, JPL launched 26 Corporals, including the first 10 of the Firestone lot as well as 16 produced by Douglas.16

Because of problems with the missile’s guidance system and engi­neering changes to correct them, a second production order to Fire­stone for Corporal missiles in late 1954 resulted in a redesignation of the missile as Corporal II. JPL retained technical control of the Corporal program throughout 1955, relinquishing it in 1956 while continuing to provide technical assistance to the army’s contrac­tors, including Firestone. Corporal II continued to have problems with its guidance/control system but also with propellant shutoff during firings of the missile by army field forces. Fact-finding in­vestigations and informal discussions on the parts of contractors, the field forces, Army Ordnance Corps, and JPL led to greater care by field forces personnel in following operational procedures. These eliminated shutoff problems when not violated. The army declared the Corporal to be operational in 1954, and in January 1955 the Corporal I deployed to Europe. Eight Corporal II battalions replaced 152 it during 1956 and the first half of 1957.17

Chapter 4 Although the Corporal was less powerful and had a shorter range than the V-2, the U. S. missile’s propulsion system had a higher spe­cific impulse (about 220 lbf-sec/lbm as compared with 210 for the V-2). In some respects, such as the axial nature of the cooling sys­tem and the use of Doppler radar for propellant cutoff, the Corporal had borrowed from the V-2. In most respects, however, the Ameri­can missile was an independent development, in some cases one that separately adopted features developed at Peenemunde after it was too late to incorporate them into the V-2. These included a showerhead injector and the use of hypergolic propellants. Both had been developed for the Wasserfall antiaircraft rocket, and a single injector plate later became a standard element in the construction of the rockets designed in Huntsville.18

Among the achievements of the Corporal was testing the effects of vibration on electronic equipment. The vibration tables used for this purpose may have been the first effective simulators of the flight environment in that area. Subsequently, both testing for the effects of vibrations and analysis of components and systems for reliability became standard practice in missile development.19

The engine itself was also a notable achievement. Although the idea for the axial direction of cooling flow came from the V-2, the overall engine was certainly original. It was both light and efficient, and even though there seems to be no evidence that its design influ­enced subsequent engines, it seems likely that propulsion engineers learned something of their art from it. Moreover, the early work of JPL in hypergolics transferred to Aerojet, later the contractor for the Titan II, which used storable liquid propellants that ignited on contact. This technology was also used in the Titan III and Titan IV liquid rockets, which employed direct descendants of the early hy – pergolic propellants Malina learned about in part from the navy in Annapolis. This was a significant contribution from both indige­nous U. S. research efforts during World War II. It illustrates one of the ways that technology transferred from one program to another in American rocketry. The borrowings from the V-2 exemplify a dif­ferent pattern of information flow.

The Sergeant Missile Powerplant

Meanwhile, the first major application of the technologies devel­oped for the RV-A-10 was the Sergeant missile, for which JPL began planning in 1953 under its ORDCIT contract with Army Ordnance. JPL submitted a proposal for a Sergeant missile in April 1954, and on June 11, 1954, the army’s chief of ordnance programmed $100,000 for it. At the same time, he transferred control of the effort to the com­manding general of Redstone Arsenal. Using lessons learned from the liquid-propellant Corporal missile, JPL proposed a co-contractor for the development and ultimate manufacture of the missile. In February 1956, a Sergeant Contractor Selection Committee unani­mously chose Sperry Gyroscope Company for this role, based on JPL’s recommendation and Sperry’s capabilities and experience with other missiles, including the Sparrow I air-to-air missile system for the navy. In April 1954, the Redstone Arsenal had reached an agreement with the Redstone Division of Thiokol to work on the solid-propellant motor for the Sergeant, with the overall program to develop Sergeant beginning in 1955.30

There is no need to provide a detailed history of the Sergeant missile here. It took longer to develop than originally planned and was not operational until 1962. By then the navy had completed the far more significant Polaris A1, and the air force was close to field­ing the much more important Minuteman I. The Sergeant did meet a slipped ordnance support readiness date of June 1962 and became a limited-production weapons system until June 1968. It did equal its predecessor, Corporal, in range and firepower in a package only

FIG. 6.3

The Sergeant Missile PowerplantTechnical drawing of the Jupiter C (actually,

Juno I, including scaled-down Sergeant upper stages) with America’s first satellite, Explorer I, showing the latter’s characteristics. (Photo courtesy of NASA)

The Sergeant Missile Powerplant

half as large and requiring less than a third as much ground-support equipment. Its solid-propellant motor could also be readied for fir­ing much more quickly than the liquid-propellant Corporal.31

The Sergeant motor was a modification or direct descendant of the RV-A-10’s motor. The latter (using the TRX-110A propulsion formulation) employed 63 percent ammonium perchlorate as an oxidizer, whereas the TP-E8057 propellant for the Sergeant motor (designated JPL 500) had 63.3 percent of that oxidizer and 33.2 per­cent LP-33 liquid polymer in addition to small percentages of a curing agent, two reinforcing agents, and a curing accelerator. At a nozzle expansion ratio of 5.39, its specific impulse was about 185 lbf-sec/lbm, considerably lower than the performance of Polaris A1. It employed a five-point-star grain configuration, used a case of 4130 steel at a nominal thickness of 0.109 inch (almost half that of the RV-A-10 case), and a nozzle (like that of the RV-A-10) using 1020 steel with a graphite nozzle-throat insert.32 Ironically, perhaps, the main contributions the Sergeant made to launch-vehicle tech­nology were through a scaled-down version of the missile used for testing. These smaller versions became the basis for upper stages in reentry test vehicles for the Jupiter missile and in the launch vehicles for Explorer and Pioneer satellites.33

Analysis and Conclusions

The development of missiles and rockets for DoD needs arguably contributed to national defense and, through deterrence, kept the

cold war from becoming hotter than it actually got in Korea, Viet­nam, and Afghanistan, among other places. For the purposes of this book, however, the importance of the missiles and rockets discussed in this chapter lay in the technology that could transfer to launch – vehicle uses. In many cases, actual missiles, with some adaptations, became either launch vehicles or stages in larger combinations of rockets used to place satellites or spacecraft on their trajectories. Without the perceived urgency created by cold-war concerns and without the heterogeneous engineering of missile proponents, it conceivably would have taken much longer for launch vehicles to develop, although many satellites themselves were high on the DoD’s priority lists.

Подпись: 47 German and U.S. Missiles and Rockets, 1926-66

Quite apart from their contributions to launch-vehicle technol­ogy, the missiles and rockets discussed in this chapter also illustrate many of the themes that will be further explored in subsequent chapters. Missiles such as the Titan II and Minuteman showed the ways in which technology for earlier missiles contributed to their successors. Although this chapter provides only an overview of mis­sile development, it shows several examples of trial-and-error engi­neering that was necessary to overcome often unforeseen problems. Clearly, the missiles discussed here required a wide range of talents and a huge number of different organizations to design and develop them. Also important was a considerable sharing of information, even between competing organizations and firms. Finally, manage­ment systems such as the one Schriever adopted at WDD (and a similar system called Program Evaluation and Review Technique [PERT] adopted by Raborn for the Polaris program) enabled very complicated missiles and launch vehicles to be developed reason­ably on time and in such a way that all component systems (such as propulsion, structures, guidance and control) worked together effectively.

Подпись: U.S. Space- Launch Vehicles, 1958-91 LAUNCH VEHICLES FREQUENTLY USED MIS­siles as first stages, but these required many modi­fications, particularly when they had to boost hu­mans into space. Even for satellite and spacecraft launches, technology for the booster stages fre­quently represented modification of technologies missiles needed for their ballistic paths from one part of Earth to another. Thus, the history of the Thor-Delta, Atlas, Scout, Saturn, Titan, and Space Shuttle launch vehicles differed from, but remained

dependent on, the earlier development of the missiles discussed in chapter 1. Missiles and launch vehicles represented a continuum, with many of the same people contributing to both. But they re­mained different enough from one another to require separate treat­ment in this chapter.

Despite the differences, launch-vehicle development exhibited many of the same themes that characterized missiles. It featured the same engineering culture that relied heavily on extensive test­ing on the ground. But this did not always succeed in revealing all problems that occurred in flight. When unexpected problems oc­curred, it was not always possible for engineers to understand the exact causes. But they were able to arrive at fixes that worked. There continued to be a wide range of organizations and disciplines that contributed to launch-vehicle development, including the solution of unanticipated problems. Also characteristic of launch vehicles was a competitive environment that nevertheless featured sharing of information among organizations involved in development. In part, this sharing occurred through the movement of knowledge­able engineers from one organization to another. More often, the information sharing (plus its recording and validation) occurred through professional societies, papers delivered at their meetings, and publication of reports in professional journals.1 Finally, mis­siles and launch vehicles shared the use of management systems that tracked development of components to ensure that all of them occurred on schedule and that they all worked together effectively.