Search NASA⌕ Search

SEARCH · Search NASA

Results for “Launch Processing”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 181 records · Page 10

A Geometric Analysis to Protect Manned Assets from Newly Launched Objects - COLA Gap Analysis

A safety risk was identified for the International Space Station (ISS) by The Aerospace Corporation following the launch of GPS IIR-20 (March 24, 2009), when the spent upper stage of the launch vehicle unexpectedly crossed inside the ISS notification box shortly after launch. This event highlighted a 56-hour vulnerability period following the end of the launch Collision Avoidance (COLA) process where the ISS would be unable to react to a conjunction with a newly launched object. Current launch COLA processes screen each launched object across the launch window to determine if an object's nominal trajectory is predicted to pass within 200 km of the ISS (or any other manned/mannable object), resulting in a launch time closure. These launch COLA screens are performed from launch through separation plus I 00 minutes. Once the objects are in orbit, they are cataloged and evaluated as part of routine on-orbit conjunction assessment processes. However, as the GPS IIR-20 scenario illustrated, there is a vulnerability period in the time line between the end of launch COLA coverage and the beginning of standard on-orbit COLA assessment activities. The gap between existing launch and on-orbit COLA processes is driven by the time it takes to track and catalog a launched object, identify a conjunction, and plan and execute a collision avoidance maneuver. For the ISS, the total time required to accomplish an of these steps is 56 hours. To protect human lives, NASA/JSC has requested that an US launches take additional steps to protect the ISS during this "COLA gap" period. The uncertainty in the state of a spent upper stage can be quite large after all bums are complete and all remaining propellants are expelled to safe the stage. Simply extending the launch COLA process an additional 56 hours is not a viable option as the 3-sigma position uncertainty will far exceed the 200 km miss-distance criterion. Additionally, performing a probability of collision (Pc) analysis over this period is also not practical due to the limiting effects of these large orbit state uncertainties. An estimated upper bound for Pc for a typical spent upper stage if nominally aligned for a direct broadside collision with the ISS is only on the order of 10-6. For a smaller manned object such as a Soyuz capsule, the risk level decreases to an order of 10'8 . In comparison, the Air Force Range policy (AFI 91-217) for launch COLAs would only eliminate launch opportunities when conjunctions with objects exceed a Pc of 10'5 This paper demonstrates a conservative geometry-based methodology that may be used to determine if launch opportunities pose a threat to the ISS during the COLA gap period. The NASA Launch Services Program at Kennedy Space Center has developed this COLA gap analysis method and employed it fQr three NASA missions to identify potential ISS conjunctions and corresponding launch window closures during the 56-hour at-risk period. In the analysis, for each launch opportunity, the nominal trajectory of the spent upper stage and the orbit state of the ISS are propagated over the 56 hour period. Each time the upper stage crosses the orbit plane of the ISS, the relative radial and argument of latitude separations are calculated. A window cutout is identified if these separation differences fall within a mission-specific violation box, which is determined from the evaluation of a Monte Carlo dispersions analysis that quantifies the potential variation in the upper stage radial and argument of latitude differences. This paper details the results of these analyses and their impacts to each mission.

Hametz, Mark E.↗

Launch site integration for mixed fleet operations

Launch site impacts and integration planning issues are presented to support launch operations for a mixed vehicle fleet (manned and cargo). Proposed ground systems and launch site configurations are described. Prelaunch processing scenarios and schedules are developed for candidate launch vehicles. Earth-to-orbit (ETO) vehicle architectures are presented to meet future launch requirements, including the Space Exploration Initiative (SEI). Flight vehicle design recommendations to enhance launch processing are discussed. The significance of operational designs for future launch vehicles is shown to be a critical factor in planning for mixed fleet launch site operations.

Scott, L. P.↗

Spacecraft Power Source Installation at Launch Complex

For certain space missions, an assembly must be integrated onto the spacecraft as late as possible in the launch vehicle processing flow. 12This late integration can be driven for a variety of reasons including thermal or hazardous materials constraints. This paper discusses the process of integrating an assembly onto a spacecraft as late as one week prior to the opening of the launch window. Consideration is given to achieving sufficient access for hardware integration, methods of remotely securing hardware to the spacecraft, maintaining spacecraft cleanliness throughout the integration process, and electrically integrating the component to the spacecraft. Specific examples are taken from the remote mechanical, electrical, and fluid cooling system integration of the power source onto the Mars Science Laboratory (MSL) Rover at the Atlas V Vertical Integration Facility (VIF) at Cape Canaveral Air Force Station, Florida.

Lytal, Paul↗

STS-114: Discovery Post MMT Press Conference

Bruce Buckingham, NASA Public Affairs hosted this conference. Bill Parsons, Space Shuttle Program Manager; John Muratore, Shuttle System and Integration Manager; Mike Wetmore, Shuttle Processing Director were present. The Panel summarizes that thorough effort of analysis and test techniques and great amount of work is being done to fix the sensor problem and will be ready to call the stations for a launch countdown process after the trouble shooting is fully completed. Launch time, grounding problem, sensor failure, trouble shooting, tanking test, pin swap, and heaters were topics covered with the News media. For clarification, Bruce Buckingham provided information that preferred launch time is at 10:39am on July 26, Eastern Time.

Source record↗

The use of airborne and ground-based measurements of launch vehicle HCl puffs in a finite difference parameter estimation procedure

Model 4 of the multilayer diffusion models, version 5 (MDMV5) is discussed. MDMV5 is designed to help factor considerations of the potential environment impact of a given launch operation into the actual launch decision process. The model supports this decision process by providing quantitative estimates of particular air quality indices at a set of spatial positions in the launch area and surrounding communities, for specified meteorological conditions. Modeling concepts, the finite difference estimation algorithm, and data application and results are examined.

Englar, T. S., Jr.↗

Overview od STS ground operations/orbiter turnaround STS-1 through STS-7

A review of STS-1 processing is presented as a reference for Shuttle processing time and the magnitude of the associated modifications, discrepancies, technical requirements, and ground systems activities. STS-1 processing provided the basis from which a plan to perform operational turnaround was established. Turnaround processing for Launch and Landing are treated separately to depict more clearly the progress made to reduce turnaround time and manhours expended. Turnaround time was reduced from 187 days for STS-2 to 60 days for STS-7 and landing turnaround was reduced from 14 days to 5 days. Modifications were reduced from 114 to 51. Requirements changes for launch readiness verification were reduced from 536 to 107. Special tests or inspections were reduced from 292 to 52. Anomalies resolved concurrent with processing were reduced from 13,000 to 4,000. Integration in the Vehicle Assembly Building (VAB) is about 10 percent of the flow, and Launch Pad operations comprise 40 percent of the turnaround. The work force has matured and has demonstrated the capability to perform planned and contingency operations. The turnaround program is fast approaching the goal of becoming operational.

Schwartz, R.↗

NASA Ares 1 Crew Launch Vehicle Upper Stage Configuration Selection Process

The Upper Stage Element of NASA s Ares I Crew Launch Vehicle (CLV) is a "clean-sheet" approach that is being designed and developed in-house, with Element management at MSFC. The USE concept is a self-supporting cylindrical structure, approximately 115 long and 216" in diameter. While the Reusable Solid Rocket Booster (RSRB) design has changed since the CLV inception, the Upper Stage Element design has remained essentially a clean-sheet approach. Although a clean-sheet upper stage design inherently carries more risk than a modified design, it does offer many advantages: a design for increased reliability; built-in extensibility to allow for commonality/growth without major redesign; and incorporation of state-of-the-art materials, hardware, and design, fabrication, and test techniques and processes to facilitate a potentially better, more reliable system.

Cook, Jerry R.↗

Mission Success of U.S. Launch Vehicle Flights from a Propulsion Stage-Based Perspective: 1980-2015

This report documents a study of the historical safety and reliability trends of U.S. space launch vehicles from 1980 to 2015. The launch data history is examined to determine whether propulsion technology choices drove launch system risk and is used to understand how different propulsion system failures manifested into different failure scenarios. The historical data is processed by launch vehicle stage, where a stage is limited by definition to a single propulsion technology, either liquid or solid. Results are aggregated in terms of failure trends and manifestations as a functions of different propulsion stages. Failure manifestations are analyzed in order to understand the types and frequencies of accident environments in which an abort system for a crewed vehicle would be required to operate.

propulsion↗

Shuttle Case Study Collection Website Development

As a continuation from summer 2012, the Shuttle Case Study Collection has been developed using lessons learned documented by NASA engineers, analysts, and contractors. Decades of information related to processing and launching the Space Shuttle is gathered into a single database to provide educators with an alternative means to teach real-world engineering processes. The goal is to provide additional engineering materials that enhance critical thinking, decision making, and problem solving skills. During this second phase of the project, the Shuttle Case Study Collection website was developed. Extensive HTML coding to link downloadable documents, videos, and images was required, as was training to learn NASA's Content Management System (CMS) for website design. As the final stage of the collection development, the website is designed to allow for distribution of information to the public as well as for case study report submissions from other educators online.

Ransom, Khadijah S.↗

Anvil Forecast Tool in the Advanced Weather Interactive Processing System (AWIPS)

Launch Weather Officers (LWOs) from the 45th Weather Squadron (45 WS) and forecasters from the National Weather Service (NWS) Spaceflight Meteorology Group (SMG) have identified anvil forecasting as one of their most challenging tasks when predicting the probability of violating the Lightning Launch Commit Criteria (LLCC) (Krider et al. 2006; Space Shuttle Flight Rules (FR), NASA/JSC 2004)). As a result, the Applied Meteorology Unit (AMU) developed a tool that creates an anvil threat corridor graphic that can be overlaid on satellite imagery using the Meteorological Interactive Data Display System (MIDDS, Short and Wheeler, 2002). The tool helps forecasters estimate the locations of thunderstorm anvils at one, two, and three hours into the future. It has been used extensively in launch and landing operations by both the 45 WS and SMG. The Advanced Weather Interactive Processing System (AWIPS) is now used along with MIDDS for weather analysis and display at SMG. In Phase I of this task, SMG tasked the AMU to transition the tool from MIDDS to AWIPS (Barrett et aI., 2007). For Phase II, SMG requested the AMU make the Anvil Forecast Tool in AWIPS more configurable by creating the capability to read model gridded data from user-defined model files instead of hard-coded files. An NWS local AWIPS application called AGRID was used to accomplish this. In addition, SMG needed to be able to define the pressure levels for the model data, instead of hard-coding the bottom level as 300 mb and the top level as 150 mb. This paper describes the initial development of the Anvil Forecast Tool for MIDDS, followed by the migration of the tool to AWIPS in Phase I. It then gives a detailed presentation of the Phase II improvements to the AWIPS tool.

Barrett, Joe H., III↗

Center Planning and Development: Multi-User Spaceport Initiatives

The Vehicle Assembly building at NASAs Kennedy Space Center has been used since 1966 to vertically assemble every launch vehicle, since the Apollo Program, launched from Launch Complex 39 (LC-39). After the cancellation of the Constellation Program in 2010 and the retirement of the Space Shuttle Program in 2011, the VAB faced an uncertain future. As the Space Launch System (SLS) gained a foothold as the future of American spaceflight to deep space, NASA was only using a portion of the VABs initial potential. With three high bays connected to the Crawler Way transportation system, the potential exists for up to three rockets to be simultaneously processed for launch. The Kennedy Space Center (KSC) Master plan, supported by the Center Planning and Development (CPD) Directorate, is guiding Kennedy toward a 21st century multi-user spaceport. This concept will maintain Kennedy as the United States premier gateway to space and provide multi-user operations through partnerships with the commercial aerospace industry. Commercial aerospace companies, now tasked with transporting cargo and, in the future, astronauts to the International Space Station (ISS) via the Commercial Resupply Service (CRS) and Commercial Crew Program (CCP), are a rapidly growing industry with increasing capabilities to make launch operations more economical for both private companies and the government. Commercial operations to Low Earth Orbit allow the government to focus on travel to farther destinations through the SLS Program. With LC-39B designated as a multi-use launch pad, companies seeking to use it will require an integration facility to assemble, integrate, and test their launch vehicle. An Announcement for Proposals (AFP) was released in June, beginning the process of finding a non-NASA user for High Bay 2 (HB2) and the Mobile Launcher Platforms (MLPs). An Industry Day, a business meeting and tour for interested companies and organizations, was also arranged to identify and answer any additional questions posed by potential proposers. After amending the AFP and posting additional material for potential users to consider, proposals are being accepted until July 31, at which point they will be evaluated to determine the proposer which best meets the objectives of the government. By identifying VAB HB2 as available and seeking proposals from the commercial sector for VAB HB2 and MLP use, Center Planning and Development is ensuring Kennedy Space Centers relevance in the evolving launch industry of the 21st century.

AFP↗

The Wallops Flight Facility Rapid Response Range Operations Initiative

While the dominant focus on short response missions has appropriately centered on the launch vehicle and spacecraft, often overlooked or afterthought phases of these missions have been launch site operations and the activities of launch range organizations. Throughout the history of organized spaceflight, launch ranges have been the bane of flight programs as the source of expense, schedule delays, and seemingly endless requirements. Launch Ranges provide three basic functions: (1) provide an appropriate geographical location to meet orbital other mission trajectory requirements, (2) provide project services such as processing facilities, launch complexes, tracking and data services, and expendable products, and (3) assure safety and property protection to participating personnel and third-parties. The challenge with which launch site authorities continuously struggle, is the inherent conflict arising from projects whose singular concern is execution of their mission, and the range s need to support numerous simultaneous customers. So, while tasks carried out by a launch range committed to a single mission pale in comparison to efforts of a launch vehicle or spacecraft provider and could normally be carried out in a matter of weeks, major launch sites have dozens of active projects separate sponsoring organizations. Accommodating the numerous tasks associated with each mission, when hardware failures, weather, maintenance requirements, and other factors constantly conspire against the range resource schedulers, make the launch range as significant an impediment to responsive missions as launch vehicles and their cargo. The obvious solution to the launch site challenge was implemented years ago when the Department of Defense simply established dedicated infrastructure and personnel to dedicated missions, namely an Inter Continental Ballistic Missile. This however proves to be prohibitively expensive for all but the most urgent of applications. So the challenge becomes how can a launch site provide acceptably responsive mission services to a particular customer without dedicating extensive resources and while continuing to serve other projects? NASA's Wallops Flight Facility (WFF) is pursuing solutions to exactly this challenge. NASA, in partnership with the Virginia Commercial Space Flight Authority, has initiated the Rapid Response Range Operations Initiative (R3Ops). R3Ops is a multi-phased effort to incrementally establish and demonstrate increasingly responsive launch operations, with an ultimate goal of providing ELV-class services in a maximum of 7-10 days from initial notification routinely, and shorter schedules possible with committed resources. This target will be pursued within the reality of simultaneous concurrent programs, and ideally, largely independent of specialized flight system configurations. WFF has recently completed Phase 1 of R3Ops, an in-depth collection (through extensive expert interviews) and software modeling of individual steps by various range disciplines. This modeling is now being used to identify existing inefficiencies in current procedures, to identify bottlenecks, and show interdependencies. Existing practices are being tracked to provide a baseline to benchmark against as new procedures are implemented. This paper will describe in detail the philosophies behind WFF's R3Ops, the data collected and modeled in Phase 1, and strategies for meeting responsive launch requirements in a multi-user range environment planned for subsequent phases of this initiative.

Underwood, Bruce E.↗

Shuttle Transportation System Case-Study Development

A case-study collection was developed for NASA's Space Shuttle Program. Using lessons learned and documented by NASA KSC engineers, analysts, and contractors, decades of information related to processing and launching the Space Shuttle was gathered into a single database. The goal was to provide educators with an alternative means to teach real-world engineering processes and to enhance critical thinking, decision making, and problem solving skills. Suggested formats were created to assist both external educators and internal NASA employees to develop and contribute their own case-study reports to share with other educators and students. Via group project, class discussion, or open-ended research format, students will be introduced to the unique decision making process related to Shuttle missions and development. Teaching notes, images, and related documents will be made accessible to the public for presentation of Space Shuttle reports. Lessons investigated included the engine cutoff (ECO) sensor anomaly which occurred during mission STS-114. Students will be presented with general mission infom1ation as well as an explanation of ECO sensors. The project will conclude with the design of a website that allows for distribution of information to the public as well as case-study report submissions from other educators online.

Ransom, Khadijah↗

Data Acquisition System for Multi-Frequency Radar Flight Operations Preparation

A three-channel data acquisition system was developed for the NASA Multi-Frequency Radar (MFR) system. The system is based on a commercial-off-the-shelf (COTS) industrial PC (personal computer) and two dual-channel 14-bit digital receiver cards. The decimated complex envelope representations of the three radar signals are passed to the host PC via the PCI bus, and then processed in parallel by multiple cores of the PC CPU (central processing unit). The innovation is this parallelization of the radar data processing using multiple cores of a standard COTS multi-core CPU. The data processing portion of the data acquisition software was built using autonomous program modules or threads, which can run simultaneously on different cores. A master program module calculates the optimal number of processing threads, launches them, and continually supplies each with data. The benefit of this new parallel software architecture is that COTS PCs can be used to implement increasingly complex processing algorithms on an increasing number of radar range gates and data rates. As new PCs become available with higher numbers of CPU cores, the software will automatically utilize the additional computational capacity.

Leachman, Jonathan↗

NASA's Space Launch System Progress Report

Exploration beyond Earth will be an enduring legacy for future generations, confirming America's commitment to explore, learn, and progress. NASA's Space Launch System (SLS) Program, managed at the Marshall Space Flight Center, is responsible for designing and developing the first exploration-class rocket since the Apollo Program's Saturn V that sent Americans to the Moon. The SLS offers a flexible design that may be configured for the MultiPurpose Crew Vehicle and associated equipment, or may be outfitted with a payload fairing that will accommodate flagship science instruments and a variety of high-priority experiments. Both options support a national capability that will pay dividends for future generations. Building on legacy systems, facilities, and expertise, the SLS will have an initial lift capability of 70 metric tons (mT) and will be evolvable to 130 mT. While commercial launch vehicle providers service the International Space Station market, this capability will surpass all vehicles, past and present, providing the means to do entirely new missions, such as human exploration of asteroids and Mars. With its superior lift capability, the SLS can expand the interplanetary highway to many possible destinations, conducting revolutionary missions that will change the way we view ourselves, our planet and its place in the cosmos. To perform missions such as these, the SLS will be the largest launch vehicle ever built. It is being designed for safety and affordability - to sustain our journey into the space age. Current plans include launching the first flight, without crew, later this decade, with crewed flights beginning early next decade. Development work now in progress is based on heritage space systems and working knowledge, allowing for a relatively quick start and for maturing the SLS rocket as future technologies become available. Together, NASA and the U.S. aerospace industry are partnering to develop this one-of-a-kind asset. Many of NASA's space centers across the country will provide their unique expertise to the Space Launch System endeavor. Unique infrastructure to be used includes the Michoud Assembly Facility for tank manufacturing, Stennis Space Center for engine testing, and Kennedy Space Center for processing and launch. As this panel will discuss, the SLS team is dedicated to doing things differently-from applying lean oversight/insight models to smartly using legacy hardware and existing facilities. Building on the foundation laid by over 50 years of human and scientific space flight--and on the lessons learned from the Apollo, Space Shuttle, and Constellation Programs-the SLS team has delivered both technical trade studies and business case analyses to ensure that the SLS architecture will be safe, affordable, reliable, and sustainable.

Singer, Joan A.↗

An Analysis of Peak Wind Speed Data from Collocated Mechanical and Ultrasonic Anemometers

This study compared peak wind speeds reported by mechanical and ultrasonic anemometers at Cape Canaveral Air Force Station and Kennedy Space Center (CCAFS/KSC) on the east central coast of Florida and Vandenberg Air Force Base (VAFB) on the central coast of California. Launch Weather Officers, forecasters, and Range Safety analysts need to understand the performance of wind sensors at CCAFS/KSC and VAFB for weather warnings, watches, advisories, special ground processing operations, launch pad exposure forecasts, user Launch Commit Criteria (LCC) forecasts and evaluations, and toxic dispersion support. The legacy CCAFS/KSC and VAFB weather tower wind instruments are being changed from propeller-and-vane (CCAFS/KSC) and cup-and-vane (VAFB) sensors to ultrasonic sensors under the Range Standardization and Automation (RSA) program. Mechanical and ultrasonic wind measuring techniques are known to cause differences in the statistics of peak wind speed as shown in previous studies. The 45th Weather Squadron (45 WS) and the 30th Weather Squadron (30 WS) requested the Applied Meteorology Unit (AMU) to compare data between the RSA ultrasonic and legacy mechanical sensors to determine if there are significant differences. Note that the instruments were sited outdoors under naturally varying conditions and that this comparison was not designed to verify either technology. Approximately 3 weeks of mechanical and ultrasonic wind data from each range from May and June 2005 were used in this study. The CCAFS/KSC data spanned the full diurnal cycle, while the VAFB data were confined to 1000-1600 local time. The sample of 1-minute data from numerous levels on five different towers on each range totaled more than 500,000 minutes of data (482,979 minutes of data after quality control). The ten towers were instrumented at several levels, ranging from 12 ft to 492 ft above ground level. The ultrasonic sensors were collocated at the same vertical levels as the mechanical sensors and typically within 15 ft horizontally of each another. Data from a total of 53 RSA ultrasonic sensors, collocated with mechanical sensors were compared. The 1- minute average wind speed/direction and the 1-second peak wind speed/direction were compared.

Short, David A.↗

Space Station operations

An evaluation of the success of the Space Station will be based on the service provided to the customers by the Station crew, the productivity of the crew, and the costs of operation. Attention is given to details regarding Space Station operations, a summary of operational philosophies and requirements, logistics and resupply operations, prelaunch processing and launch operations, on-orbit operations, aspects of maintainability and maintenance, habitability, and questions of medical care. A logistics module concept is considered along with a logistics module processing timeline, a habitability module concept, and a Space Station rescue mission.

Gray, R. H.↗

A Comparison of Wind Speed Data from Mechanical and Ultrasonic Anemometers

This study compared the performance of mechanical and ultrasonic anemometers at the Eastern Range (ER; Kennedy Space Center and Cape Canaveral Air Force Station on Florida's Atlantic coast) and the Western Range (WR; Vandenberg Air Force Base on California's Pacific coast). Launch Weather Officers, forecasters, and Range Safety analysts need to understand the performance of wind sensors at the ER and WR for weather warnings, watches, advisories, special ground processing operations, launch pad exposure forecasts, user Launch Commit Criteria (LCC) forecasts and evaluations, and toxic dispersion support. The current ER and WR weather tower wind instruments are being changed from the current propeller-and-vane (ER) and cup-and-vane (WR) sensors to ultrasonic sensors through the Range Standardization and Automation (RSA) program. The differences between mechanical and ultrasonic techniques have been found to cause differences in the statistics of peak wind speed in previous studies. The 45th Weather Squadron (45 WS) and the 30th Weather Squadron (30 WS) requested the Applied Meteorology Unit (AMU) to compare data between RSA and current sensors to determine if there are significant differences. Approximately 3 weeks of Legacy and RSA wind data from each range were used in the study, archived during May and June 2005. The ER data spanned the full diurnal cycle, while the WR data was confined to 1000-1600 local time. The sample of 1-minute data from numerous levels on 5 different towers on each range totaled more than 500,000 minutes of data (482,979 minutes of data after quality control). The 10 towers were instrumented at several levels, ranging from 12 ft to 492 ft above ground level. The RSA sensors were collocated at the same vertical levels as the present sensors and typically within 15 ft horizontally of each another. Data from a total of 53 RSA ultrasonic sensors, collocated with present sensors were compared. The 1-minute average wind speed/direction and the 1-second peak wind speed/direction were compared.

Short, D.↗