DOCSLIB.ORG

Small Payload Accommodations (SPA) for the ATLAS Family Of

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Small Payload Accommodations (SPA) for the ATLAS Family Of I I SMALL PAYLOAD ACCOMMODATIONS (SPA) 1\ for the ATLAS Family of Launch Vehicles I SS·88·60 2nd Annual AIAA!USU Conference on Small Satellites I September 19·21, 1988 I Gerald Broad - David K. Lynn I GOCLS GOSSD Abstract Historical Perspective The history of small, secondary payload ac­ In 1960, GD developed the Scientific Pas­ I commodations on early ATLAS boosters is senger Pod (SPP; Figures 1,2, and 3) for use reviewed. Design and flight operations con­ as low cost space research vehicles to take ad­ cepts for small payloads on current ATLAS vantage of unused payload or fuel capacity on I launch vehicles are presented and discussed. ATLAS flights. The pods were side-mounted ATLAS launch vehicle system capabilities are on the booster, separated, and flew a ballistic presented in terms of launch site integration trajectory for about 35 minutes. This flight I schedules and the excess performance which duration doubled the capability of sounding will be available to launch small payloads. rockets and offered longer, higher flights for I the gathering and telemetering of data. The 'Introduction General Dynamics' Commercial Launch Ser­ I vices, Inc. (GDCLS) is offering launches by the ATLAS Launch System on a commercial basis. The current offering consists of I ATLAS I and ATLAS II, IIA, and lIAS launch vehicles whose performance cover the I range of geo-synchronous transfer orbit (GTO) payload weights to nearly 7000 pounds. With an apparent increase in I demand for the launch of small payloads, CLS is considering reinstituting the 1960s General Dynamics program of launching small, secon­ I dary payloads with the ATLAS. The follow­ ing is a brief recap of the early ATLAS his­ tory of launching these payloads, an overview I of current design and operations concepts and concerns, and a discussion of their future on the ATLAS family of launch vehicles. Figure 1. Tandem SPPs Ready for a 1960s ATLAS I Launch. I SS-88-60 3018'........ ~ I Programmer I ........ - Electrical Subsystem Satellite ---H ExDeriment I Volume 8.1 cu. ft. 102' Payload I Section 8.1 cu. ft. I Adapter --+"'" 60' 151.5 in. I I .......--r- Guidance Subsystem I Figure 2. The Standard SPP Accommodated Canisterized Payloads. I SPPs were designed in two sizes for widely different missions. The standard pod (Figure I 2) was designed for captive flight of small payloads (8.1 ft3 and 450 pounds). The large Ii pod (Figure 3) was designed to house and Attitude'--HI~ deploy a small satellite with a self-contained Control '----..... propulsion system (GD's OV-1 with its 300 lb Subsystem I payload and 800 lb propulsive stage). More than fifty SPPs were flown during the 1960s for the Air Force Office of Aerospace I Research, the Naval Research Laboratory, Figure 3. SPPs Also SUj:Jported,ProRulsive Payloads the Defense Atomic Support Agency, Nation­ (GD's OV:l Depicted). al Aeronautics and Space Administration, and The only SPP interface with the ATLAS was I the Advanced Research Projects Agency. its physical attachment. There were no I I I SS-88-60 I electrical, guidance, nor telemetry interfaces. The small pods remained fixed to ATlAS or were separated pneumatically from the sup­ I port cradle at sustainer engine cut-off (SECO). The large pod remained attached to I the vehicle, the pod's hatch opened, and the propulsive payload jettisoned. The SPP's payloads then performed their mission, either I reentering the atmosphere or, in the case of the propulsive satellites, injecting into low I earth orbit (LEO). The SPPs provided battery power, signal con­ ditioning equipment, commutators, subcarrier I oscillators, an FM/FM transmitter, RF and pod-separation switches, and two antennas. ATLAS Booster I The pod's controller sensed SECO then sup­ plied an output signal to eject the passenger pod from the booster. It also provided step or I pulse outputs to operate payload equipment. SPA eODemts FtgUl'e 4. Dual OV·1s on an early Atlas booster. I Building upon our early experience with small, secondary payloads on the SPP During the 1960s, ATlAS flew multiple small program and utilizing the current excess per­ payloads as shown in Figure 4. Today's I formance available from the ATLAS family ATlAS is available for the launch of multiple of launch vehicles, CLS is studying concepts payloads (with or without the use of our Cen­ for Small Payload Accommodations (SPA) as taur upper stage). I a follow-on to our history of low cost, assured access to space. FtgUl'e 5. A Typical RV Adapted for Lateral Release . ...--. , //- .... "-, ",,' I / /' " \ /,: ATLAS-Mounted 1/ \..(' I: I ' \ I I \ \ Similar to the 1960s SPP, the ATlAS­ I ! , \ ~ i ;!~ .- I mounted SPA pods can be available in two 'I ---- - _ ... ". , . iCi=~= _... : A'TI..AS ( , '1( Ii " .It' sizes, short and long, for payload canister(s) \1' , I '"Ji 11' ,il;~" B, ooster . , I ". l' l.. I I and payloads with integral propulsive stages. \ " ~~J/ !~rue Tank Each pod will offer power, command se­ \\ \• ... ..... + i-~J.. ./ I 1""'\"~'1~. \\ I I' I, " quencing, and telemetry services. All SPA 1 '--:'-1" , ~ ....... I "" l~ pods will follow the fully autonomous " ........ / I regimen of the original SPP. SPA payload customers will be offered the option of I providing their own integrated pods utilizing this same guideline. I I I' SS·88·60 I I Payload Adapte Spacer Adapter Modul SPAPayloa 14ft. PLF I I I I: I Prime Payload l07.0in. Payload Adapter 1-1 SPA Payload I lOO.Oin. Spacer 77.0 in. Equipment I Module I I F'pe 6. Spacer Adapter Concept for Centaur-Mounted SPA Payloads. Another ATlAS-mounted SPA design con· fairing (PLF) will adequately protect these I cept is to provide compatiblity with domestic payloads during the launch and ascent en­ or foreign recoverable vehicles (RVs; Figure vironments. Similar to the ATlAS-mounted 5). Such an RV would be adapted for lateral payloads, all Centaur-mounted payloads will I release and could be encapsulated in an utilize isolated power, command, and aerodynamic fairing. The recovery of the RV telemetry services. I and its payload would be the responsibility of the RV contractor. SPA payloads investigating the LEO regime must be separated from the Centaur during I the park orbit coast. Payloads interested in Centaur-MQunted GTO orbits (with the potential of recovery by In addition to the original 1960s SPP side­ retro-powered RVs) or geosynchronous or­ I mount concept, small, secondary payloads bits (with an integral propulsion stage) will be may be mounted on the ATlAS upper stage constrained to remain attached until after I (Centaur; Figure 6) and offered a variety of prime payload deployment, possibly even high energy orbits to captive, free-flying, and after the Centaur's Collision and Contamina­ propulsive payloads. The ATIAS payload tion Avoidance Maneuver (CCAM). I I I I SS-88-60 Prime Payload Considerations (booster and upper stage) will satisfy the I In the highly competitive world of commer­ prime payload requirements then accom­ cial launch services, CLS has accepted the modate the requirements of the SPA I responsibility for on-schedule mission suc- payloads. Additionally, SPA propulsive cess. Consequently, CLS's prime objective on modules must be inhibited from ignition in every flight is to ensure on-schedule prime the vicinity of the prime payload. I payload delivery. Once a SPA payload has been accepted, CLS CLS will integrate the flight requests of SPA will be responsible for the integration of the I payloads on commercial ATLAS missions on payload with the GD-provided module as well a conservative non-interference (technical as the flight manifesting, interface design, and and schedule) basis. SPA manifesting will be launch operations. The SPA payload cus­ I based on excess mission performance, com­ tomer will be responsible for all payload ac­ patibility of payload requirments with the tivities in support of the integration analysis, I prime payload's ATLAS mission (mission design, and verification and meeting the planning and flight operations) and SPA schedule requirements of the prime payload. resources (optional services), as well as the I) ability of the SPA payload customer's to meet Typical integration activities are expected to the integration and launch schedule of the average nearly two years (Figure 8). This I primary payload. time will be spent ensuring the compatibility of the SPA payload with the prime payload The assessment of non-interference will in- mission and ATLAS launch system to the elude impacts on the launch, ascent, and on­ satisfaction of both CLS and Range Safety. I, . orbit environments of the prime payload. Or­ Figures 9 and 10 outline the SPA payload's bital operations of the launch vehiele system launch site processing time line. I Months Before/After Launch I Milestones 24 123122121120 119118 117116 115114 113112 111 110 I 91 81 71 6 15 14 P 12 11 10Jl 1 Payload Int,o ~ (PIL Data Pkg.) I PIP ~raft 6Final leo 6Draft Ninal Optional Svc Analyse. I I Design I I Safety Reviews 6 6 6 I Match Mate 6 Integ,atlon L::J (detall sched.) I launch 6 Post Fit Anal. c:: I Figure 8. A Typical SPA Integration Schedule. I SS-88-60 I SPAf.light F'li2ht Status SPA Readiness & Iiistallation Verification INSTALLATION I Review Briefing & Acceptance Installation & Checkout Complete LAUNCH I Working Days (before/after SPA Inatallation) 30 20 10 0 0 I Verification of: Verification of: ~Prime Payload interfaces GSE Installation Configurations Procedures I Safety Rqmta Special Support Weighta&cg Schedule for Cleanliness Installation Documentation I NOTE: Payloads should be capable of on-pad holds of up to 60 days without access (electrical umbilical for monitoring and battery charging is permitted).
Load more

Recommended publications
  • ATLAS II | At-Large Summit London 2014
    EN AL-ATLAS-02-DCL-01-01-EN ORIGINAL: English DATE: 26 June 2014 STATUS: Final The 2nd At-Large Summit (ATLAS II) FINAL DECLARATION Introductory Text By the Staff of ICANN Representatives of approximately one hundred and fifty (150) At-Large Structures (“ALSes”) from five Regional At-Large Organizations (“RALOs”) representing ICANN's global At-Large Community met at the 2nd At-Large Summit (ATLAS II) as part of the 50th ICANN meeting in London, United Kingdom between 21-26 June 2014. Amongst the various activities of the Summit were five Thematic Groups on issues of concern to the At-Large Community. The subjects for the Thematic Groups were selected by the representatives of ALSes. Each Summit participant was allocated to the Thematic Group according to his/her preference. The five Thematic Groups were: Thematic Group 1 (TG1): Future of Multi-Stakeholder Models Thematic Group 2 (TG2): The Globalization of ICANN Thematic Group 3 (TG3): Global Internet: The User Perspective Thematic Group 4 (TG4): ICANN Transparency and Accountability Thematic Group 5 (TG5): At-Large Community Engagement in ICANN All Thematic Groups commenced their work on Saturday 21 June 2014, the opening day of the Summit, and then each met in four individual breakout sessions during the Summit to finalize their statements. The text that follows, including the appendix which is an integral part of the Final Declaration, was endorsed by approximately 150 ALSes on the morning of Thursday, 26 June 2014 and then endorsed by the At-Large Advisory Committee (ALAC) by acclamation on the same day. The Final Declaration is to be presented to the Board of ICANN at its public session in London, United Kingdom on Thursday, 26 June 2014.
    [Show full text]
  • L AUNCH SYSTEMS Databk7 Collected.Book Page 18 Monday, September 14, 2009 2:53 PM Databk7 Collected.Book Page 19 Monday, September 14, 2009 2:53 PM
    databk7_collected.book Page 17 Monday, September 14, 2009 2:53 PM CHAPTER TWO L AUNCH SYSTEMS databk7_collected.book Page 18 Monday, September 14, 2009 2:53 PM databk7_collected.book Page 19 Monday, September 14, 2009 2:53 PM CHAPTER TWO L AUNCH SYSTEMS Introduction Launch systems provide access to space, necessary for the majority of NASA’s activities. During the decade from 1989–1998, NASA used two types of launch systems, one consisting of several families of expendable launch vehicles (ELV) and the second consisting of the world’s only partially reusable launch system—the Space Shuttle. A significant challenge NASA faced during the decade was the development of technologies needed to design and implement a new reusable launch system that would prove less expensive than the Shuttle. Although some attempts seemed promising, none succeeded. This chapter addresses most subjects relating to access to space and space transportation. It discusses and describes ELVs, the Space Shuttle in its launch vehicle function, and NASA’s attempts to develop new launch systems. Tables relating to each launch vehicle’s characteristics are included. The other functions of the Space Shuttle—as a scientific laboratory, staging area for repair missions, and a prime element of the Space Station program—are discussed in the next chapter, Human Spaceflight. This chapter also provides a brief review of launch systems in the past decade, an overview of policy relating to launch systems, a summary of the management of NASA’s launch systems programs, and tables of funding data. The Last Decade Reviewed (1979–1988) From 1979 through 1988, NASA used families of ELVs that had seen service during the previous decade.
    [Show full text]
  • Atlas Launch System Mission Planner's Guide, Atlas V Addendum
    ATLAS Atlas Launch System Mission Planner’s Guide, Atlas V Addendum FOREWORD This Atlas V Addendum supplements the current version of the Atlas Launch System Mission Plan- ner’s Guide (AMPG) and presents the initial vehicle capabilities for the newly available Atlas V launch system. Atlas V’s multiple vehicle configurations and performance levels can provide the optimum match for a range of customer requirements at the lowest cost. The performance data are presented in sufficient detail for preliminary assessment of the Atlas V vehicle family for your missions. This guide, in combination with the AMPG, includes essential technical and programmatic data for preliminary mission planning and spacecraft design. Interface data are in sufficient detail to assess a first-order compatibility. This guide contains current information on Lockheed Martin’s plans for Atlas V launch services. It is subject to change as Atlas V development progresses, and will be revised peri- odically. Potential users of Atlas V launch service are encouraged to contact the offices listed below to obtain the latest technical and program status information for the Atlas V development. For technical and business development inquiries, contact: COMMERCIAL BUSINESS U.S. GOVERNMENT INQUIRIES BUSINESS INQUIRIES Telephone: (691) 645-6400 Telephone: (303) 977-5250 Fax: (619) 645-6500 Fax: (303) 971-2472 Postal Address: Postal Address: International Launch Services, Inc. Commercial Launch Services, Inc. P.O. Box 124670 P.O. Box 179 San Diego, CA 92112-4670 Denver, CO 80201 Street Address: Street Address: International Launch Services, Inc. Commercial Launch Services, Inc. 101 West Broadway P.O. Box 179 Suite 2000 MS DC1400 San Diego, CA 92101 12999 Deer Creek Canyon Road Littleton, CO 80127-5146 A current version of this document can be found, in electronic form, on the Internet at: http://www.ilslaunch.com ii ATLAS LAUNCH SYSTEM MISSION PLANNER’S GUIDE ATLAS V ADDENDUM (AVMPG) REVISIONS Revision Date Rev No.
    [Show full text]
  • Atlas As a Human Rated LV
    AtlasAtlas As As A A Human Human RatedRated LV LV STAIF Conference 2006 Lockheed Martin Space Systems Company Atlas for Human Spaceflight 15 Feb 2006 1 © 2006 Lockheed Martin Corporation. All Rights Reserved Reliable and Versatile Launch Vehicle Family Atlas I Atlas II Atlas IIA Atlas IIAS Atlas IIIA Atlas IIIB Atlas V-400 Atlas V-500 AC-69 AC-102 AC-105 AC-108 AC-201 AC-204 AV-001 AV-003 Jul 1990 Dec 1991 Jun 1992 Dec 1993 May 2000 Feb 2002 Aug 2002 Jul 2003 8/11 10/10 23/23 30/30 2/2 4/4 4/4 3/3 Legend: First Flight X/Y X successes in Y flights •8 of 8 First Flight Successes •78 Consecutive Successful Atlas Centaur Flights •100% Mission Success Atlas II, IIA, IIAS, III & V Families •487 Total Launch Successes Since Atlas Program Inception Mission Success—One Launch at a Time Atlas for Human Spaceflight 15 Feb 2006 2 AV-010 Launch • January 19, 2006 • NASA Pluto New Horizons Spacecraft • First 551 configuration • First Block 2 Fault Tolerant Avionics • First Block B SRB • Nuclear certified • Nominal flight profile • Injection conditions well within 1 sigma – C3, RLA, DLA Fastest Spacecraft Ever Launched Atlas for Human Spaceflight 15 Feb 2006 3 Atlas Evolution History Atlas I/II Family Atlas III Family Atlas V Family 5-m PLF ) 30 GSO Kit T m ( y 26 t i l Avionics i Single Common Upgrade b Engine a 22 Centaur Centaur p a C 3.8-m . Common c 18 r LO2 Core i Tank Booster C Stretch ) 14 m n 0 2 10 Liquid 2 SRBs ( Strap-ons m RD-180 SRBs k 6 Engine 7 0 Atlas I Atlas IIAS Atlas IIIA Atlas IIIB Atlas V Atlas V Atlas V 4 2 Atlas II (SEC) (DEC)
    [Show full text]
  • Historian's Corner
    Historian’s Corner Ray Ziehm (POC) ([email protected] ) We are making some minor changes to the Historian’s writings for each addition of the STAR. Ray Ziehm has volunteered to take the lead in coordinating our quarterly write ups. He will be the only one listed under the officers for Historians. The individual contributors are well appreciated and are needed every year. We have in the past missed some Historian write ups, so having a lead coordinator should eliminate that. The individual writers will continue to be identified with their writings. Those of you that would like to write an article in the STAR for an item of historical interest should contact Ray at 303-784- 1413. Thanks, Bob Snodgress Ed Bock ([email protected] ) Atlas/Centaur Sale and Transition to Martin Marietta This Atlas Program history was originally presented at the Centaur 50th Anniversary celebration in San Diego by Ed Bock. It has been expanded with input from Tony Christensen to include the Centaur for Titan Program Transition. To appreciate this sale and transition, it’s necessary to understand the environment at General Dynamics Space Systems (GDSS) Division in the early 1990’s. The Commercial Atlas Program was inaugurated with the launch of AC-69, the first Atlas I, in July 1990. Atlas II was in development, and its first launch occurred in December 1991. GDSS was in the process of evaluating a Russian rocket engine (the RD-180) for its evolved Atlas. From mid 1990 to late 1993 there were 14 Atlas/Centaur launches, including three Atlas I failures.
    [Show full text]
  • SPACE NUCLEAR THER4. PROPULSION Progrth Conpilation of New Releases, News Clippings, and Journal Articles
    ,SPACE NUCLEAR THER4. PROPULSION PROGRth Conpilation of new releases, news clippings, and journal articles DEPARTMENT OF THE AIR FORCE AIR FORCE CENTER FOR ENVIRONMENTAL EXCELLENCE (AFCEE) BROOKS AIR FORCE BASE, TEXAS 78235-5000 INEL Technical Library (PRR) Attn: Gail Willmore 1776 Science Center Drive Idaho Falls, ID 83415 Dear Ms Willmore Per our telephone conversation on 23 March, 1992, I am enclosing a compilation of news releases, news clippings, and journal articles on the Space Nuclear Thermal Propulsion program. Request you make these available to the general public through your reference desk (along with this letter), and suggest-a-3=74 31- hour--tinte---1-inti-t—on-ch-eekeut so all interested parties have the- opportunity to view-it7 All of this material is in the public domain and may be reproduced. Our intent in making this available is to provide an understanding of the technology and why it is being studied. However, since much of this consists of media articles, we cannot guarantee its accuracy. Decisions yet to be made about this program include whether to proceed with the technology development and if so, where to conduct ground testing. These decisions will be based in part on an Environmental Impact Statement (EIS) that we are preparing. Since two sites at the Idaho National Engineering Laboratory are under consideration, we will be conducting a scoping meeting in Idaho Falls on Thursday, 9 April, 1992. It will be held at the Bonneville High School Auditorium at 7:00 PM. This meeting is open to the general public, and will assist us in determining the scope of environmental issues to be analyzed in the EIS.
    [Show full text]
  • ATLAS I/O Overview Peter Van Gemmeren (ANL) [email protected] for Many in ATLAS
    ATLAS I/O Overview Peter van Gemmeren (ANL) [email protected] for many in ATLAS 8/23/2018 Peter van Gemmeren (ANL): ATLAS I/O Overview 1 High level overview of ATLAS Input/Output framework and data persistence. Athena: The ATLAS event processing framework The ATLAS event data model Persistence: Writing Event Data: OutputStream and OutputStreamTool Overview Reading Event Data: EventSelector and AddressProvider ConversionSvc and Converter Timeline Run 2: AthenaMP, xAOD Run 3: AthenaMT Run 4: Serialization, Streaming, MPI, ESP 8/23/2018 Peter van Gemmeren (ANL): ATLAS I/O Overview 2 Simulation, reconstruction, and analysis/derivation are run as part of the Athena framework: Using the most current (transient) version of the Event Data Model Athena software architecture belongs to the blackboard family: Athena: The StoreGate is the Athena implementation of the blackboard: A proxy defines and hides the cache-fault ATLAS event mechanism: Upon request, a missing data object processing instance can be created and added to the transient data store, retrieving it from framework persistent storage on demand. Support for object identification via data type and key string: Base-class and derived-class retrieval, key aliases, versioning, and inter-object references. 8/23/2018 Peter van Gemmeren (ANL): ATLAS I/O Overview 3 Athena is used for different workflows in Reconstruction, Simulation and Analysis (mainly Derivation). Total CPU Total Read (incl. Total Write (w/o evt-loop Step ROOT compression ROOT and P->T) compression) time
    [Show full text]
  • N AS a Facts
    National Aeronautics and Space Administration NASA’s Launch Services Program he Launch Services Program (LSP) manufacturing, launch operations and rockets for launching Earth-orbit and Twas established at Kennedy Space countdown management, and providing interplanetary missions. Center for NASA’s acquisition and added quality and mission assurance in In September 2010, NASA’s Launch program management of expendable lieu of the requirement for the launch Services (NLS) contract was extended launch vehicle (ELV) missions. A skillful service provider to obtain a commercial by the agency for 10 years, through NASA/contractor team is in place to launch license. 2020, with the award of four indefinite meet the mission of the Launch Ser- Primary launch sites are Cape Canav- delivery/indefinite quantity contracts. The vices Program, which exists to provide eral Air Force Station (CCAFS) in Florida, expendable launch vehicles that NASA leadership, expertise and cost-effective and Vandenberg Air Force Base (VAFB) has available for its science, Earth-orbit services in the commercial arena to in California. and interplanetary missions are United satisfy agencywide space transporta- Other launch locations are NASA’s Launch Alliance’s (ULA) Atlas V and tion requirements and maximize the Wallops Flight Facility in Virginia, the Delta II, Space X’s Falcon 1 and 9, opportunity for mission success. Kwajalein Atoll in the South Pacific’s Orbital Sciences Corp.’s Pegasus and facts The principal objectives of the LSP Republic of the Marshall Islands, and Taurus XL, and Lockheed Martin Space are to provide safe, reliable, cost-effec- Kodiak Island in Alaska. Systems Co.’s Athena I and II.
    [Show full text]
  • Making the Invisible Visible: a History of the Spitzer Infrared Telescope Facility (1971–2003)/ by Renee M
    MAKING THE INVISIBLE A History of the Spitzer Infrared Telescope Facility (1971–2003) MONOGRAPHS IN AEROSPACE HISTORY, NO. 47 Renee M. Rottner MAKING THE INVISIBLE VISIBLE A History of the Spitzer Infrared Telescope Facility (1971–2003) MONOGRAPHS IN AEROSPACE HISTORY, NO. 47 Renee M. Rottner National Aeronautics and Space Administration Office of Communications NASA History Division Washington, DC 20546 NASA SP-2017-4547 Library of Congress Cataloging-in-Publication Data Names: Rottner, Renee M., 1967– Title: Making the invisible visible: a history of the Spitzer Infrared Telescope Facility (1971–2003)/ by Renee M. Rottner. Other titles: History of the Spitzer Infrared Telescope Facility (1971–2003) Description: | Series: Monographs in aerospace history; #47 | Series: NASA SP; 2017-4547 | Includes bibliographical references. Identifiers: LCCN 2012013847 Subjects: LCSH: Spitzer Space Telescope (Spacecraft) | Infrared astronomy. | Orbiting astronomical observatories. | Space telescopes. Classification: LCC QB470 .R68 2012 | DDC 522/.2919—dc23 LC record available at https://lccn.loc.gov/2012013847 ON THE COVER Front: Giant star Zeta Ophiuchi and its effects on the surrounding dust clouds Back (top left to bottom right): Orion, the Whirlpool Galaxy, galaxy NGC 1292, RCW 49 nebula, the center of the Milky Way Galaxy, “yellow balls” in the W33 Star forming region, Helix Nebula, spiral galaxy NGC 2841 This publication is available as a free download at http://www.nasa.gov/ebooks. ISBN 9781626830363 90000 > 9 781626 830363 Contents v Acknowledgments
    [Show full text]
  • Space Transportation Atlas V / Auxiliary Payload Overview Space
    SpaceSpace TransportationTransportation AtlasAtlas VV // AuxiliaryAuxiliary PayloadPayload OverviewOverview LockheedLockheed MartinMartin SpaceSpace SystemsSystems CompanyCompany JimJim EnglandEngland (303)(303) 977-0861977-0861 ProgramProgram Manager,Manager, AtlasAtlas GovernmentGovernment ProgramsPrograms BusinessBusiness DevelDevelopmentopment andand AdvancedAdvanced ProgramsPrograms 33 AugustAugust 20062006 1 Video – Take a Ride 2 ReliableReliable && VersatileVersatile LaunchLaunch VehicleVehicle FamilyFamily RReettiirreedd RReettiirreedd Atlas I AC-69 RReettiirreedd Jul 1990 Atlas II AC-102 RReettiirreedd 8/11 Dec 1991 Atlas IIA 10/10 AC-105 RReettiirreedd Jun 1992 • Consecutive Successful Atlas CentaurAtlas Flights: IIAS 79 Retired • First Flight Successes: 823/23 of 8 AC-108 Retired • Mission Success: 100% Atlas II, IIA, IIAS,Dec 1993 IIIA, IIIB, and V Families Atlas IIIA First Flight • Retired Variants: A, B, C, D, E, F, G, H,30/30 I, II, IIA, IIAS,AC-201 IIIA, IIIB May 2000 Atlas IIIB X/Y AC-204 2/2 X Successes / Y FlightsFeb 2002 Atlas V-400 AV-001 4/4 Mission Success: One Launch at a Time 4/4 Aug 2002 Atlas V-500 AV-003 4/4 Jul 2003 3/3 3 RecentRecent AtlasAtlas // CentaurCentaur EvolutionEvolution Atlas I / II Family Atlas III Family Atlas V Family dd dd iirree iirree eett eett RR RR 5-m PLF 30 GSO Kit 26 Single Avionics Engine Common Upgrade 22 Centaur Centaur 3.8-m 18 Common LO2 Core Tank Booster Stretch 14 10 Liquid SRBs Strap-ons RD-180 SRBs 6 Engine Atlas I Atlas IIAS Atlas IIIA Atlas IIIB Atlas V Atlas V Atlas V 407
    [Show full text]
  • Information Summary Assurance in Lieu of the Requirement for the Launch Service Provider Apollo Spacecraft to the Moon
    National Aeronautics and Space Administration NASA’s Launch Services Program he Launch Services Program was established for mission success. at Kennedy Space Center for NASA’s acquisi- The principal objectives are to provide safe, reli- tion and program management of Expendable able, cost-effective and on-schedule processing, mission TLaunch Vehicle (ELV) missions. A skillful NASA/ analysis, and spacecraft integration and launch services contractor team is in place to meet the mission of the for NASA and NASA-sponsored payloads needing a Launch Services Program, which exists to provide mission on ELVs. leadership, expertise and cost-effective services in the The Launch Services Program is responsible for commercial arena to satisfy Agencywide space trans- NASA oversight of launch operations and countdown portation requirements and maximize the opportunity management, providing added quality and mission information summary assurance in lieu of the requirement for the launch service provider Apollo spacecraft to the Moon. to obtain a commercial launch license. The powerful Titan/Centaur combination carried large and Primary launch sites are Cape Canaveral Air Force Station complex robotic scientific explorers, such as the Vikings and Voyag- (CCAFS) in Florida, and Vandenberg Air Force Base (VAFB) in ers, to examine other planets in the 1970s. Among other missions, California. the Atlas/Agena vehicle sent several spacecraft to photograph and Other launch locations are NASA’s Wallops Island flight facil- then impact the Moon. Atlas/Centaur vehicles launched many of ity in Virginia, the North Pacific’s Kwajalein Atoll in the Republic of the larger spacecraft into Earth orbit and beyond. the Marshall Islands, and Kodiak Island in Alaska.
    [Show full text]
  • A Probabilistic Patch-Based Label Fusion Model for Multi-Atlas Segmentation with Registration Refinement: Application to Cardiac
    1 A Probabilistic Patch-Based Label Fusion Model for Multi-Atlas Segmentation with Registration Refinement: Application to Cardiac MR Images Wenjia Bai, Wenzhe Shi, Declan P. O’Regan, Tong Tong, Haiyan Wang, Shahnaz Jamil-Copley, Nicholas S. Peters∗ and Daniel Rueckert Abstract—The evaluation of ventricular function is important Multi-atlas segmentation has been demonstrated to signif- for the diagnosis of cardiovascular diseases. It typically involves icantly improve segmentation accuracy compared to segmen- measurement of the left ventricular (LV) mass and LV cavity tation based on a single atlas [13]–[16]. It utilises a set of volume. Manual delineation of the myocardial contours is time- consuming and dependent on the subjective experience of the atlases that represent the inter-subject variability of the cardiac expert observer. In this paper, a multi-atlas method is proposed anatomy. The target image to be segmented is registered to for cardiac MR image segmentation. The proposed method is each atlas and the propagated labels from multiple atlases are novel in two aspects. First, it formulates a patch-based label combined to form a consensus segmentation. This method has fusion model in a Bayesian framework. Second, it improves image two advantages compared to single atlas propagation. First, it registration accuracy by utilising label information, which leads to improvement of segmentation accuracy. The proposed method accounts for the anatomical shape variability by using multi- was evaluated on a cardiac MR image set of 28 subjects. The ple atlases. Second, it is robust because segmentation errors average Dice overlap metric of our segmentation is 0.92 for the associated with single atlas propagation can be averaged out LV cavity, 0.89 for the RV cavity and 0.82 for the myocardium.
    [Show full text]