Search NASA⌕ Search

SEARCH · Search NASA

Results for “launch operations”

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 307 records · Page 17

Flight Software Dictionary Development for the Mars2020 Rover

The Mars2020 project, developed and operated by the Jet Propulsion Laboratory (JPL), successfully landed the Perseverance rover and its flying companion Ingenuity on the surface of Mars on February 18th 2021. Perseverance combines heritage and cutting-edge flight software and hardware to accomplish crucial mission requirements related to Martian surface sampling. The design, development, and operation of NASA’s large strategic science missions require the ability to communicate spacecraft capabilities to hundreds of engineers across multiple disciplines. The interaction between flight and ground software development, Verification and Validation (V&V), Assembly, Test, and Launch Operations (ATLO), and management each demand quick understanding of unique slices of information for each discipline. This information includes the current capabilities of the flight system as well as future capabilities and their status as they are developed and tested. Despite the fundamental and critical nature of this information, the flight software dictionaries used to track it are a stumbling block for many projects. These dictionaries provide the cornerstone for the interpretation of data sent from the spacecraft, allowing for quick comprehension by engineers on the ground. During both spacecraft development and operations, flight software dictionary management includes significant challenges due to the large number of interfacing systems and the subtle yet distinct needs of each.The engineering of flight software dictionaries for Mars2020 had numerous challenges, most-notably: parallel dictionary development to support simultaneous separate flight software build campaigns for each mission phase (cruise and surface), managing requests for operations-enabling information without perturbing the heritage interface with the rover, and the introduction of new tools by the dictionary stakeholders that forced the dictionary team to innovate and redesign the heritage tool chain. These challenges generated guiding principles for the dictionary development effort: emphasize coding best practices and unit testing in the dictionary code development tool chain, use institutionally provided COTS (commercial-off-the-shelf) tools whenever possible, and maintain the heritage flight-ground interface all while advancing operations-enabling information via a loosely coupled interface.Throughout development and operations, the Mars2020 dictionary toolchain included IBM DOORS Next Generation, GitHub, Microsoft Excel, Docker, Jenkins, and a significant custom-built Python codebase. Significant interfaces included JPL’s command and control software, heritage flight software team tools and processes, and the many cloud-based ground tools developed for the mission.This paper will discuss the requirements for the Mars2020 dictionary development, the development team’s response to those requirements, lessons learned throughout the process, steps taken towards automated deliveries and continuous integration of stakeholder inputs, potential toolchain improvements for Mars2020, and key takeaways that could be applied to future missions.

Pyrzak, Guy↗

Investigation and Feasibility Assessment of TOPAZ-2 Derivations for Space Power Applications

The ability to provide continuous power at significant levels is of utmost importance for many space missions, from simple satellite operations to manned Mars missions. One of the main problems faced in delivering solar or chemical space power in the tens of kW range, is the increasingly massive nature of the power source and the costs associated with its launch, operation and maintenance. A national program had been initiated to study the feasibility of using certain advanced technologies in developing an efficient lightweight space power source. The starting point for these studies has been the Russian TOPAZ-2 space reactor system, with the ultimate goal to aid in the development of a TOPAZ-2 derivative which will be ready for flight by the year 2000. The main objective of this project has been to perform feasibility assessment and trade studies which would allow the development of an advanced space nuclear power system based on the in-core thermionic fuel element technology currently used in the Russian TOPAZ-2 reactor. Two of the important considerations in developing the concept are: (1) compliance of the current TOPAZ-2 and of any advanced designs with U.S. nuclear safety expectations, and (2) compliance of the design with the seven years lifetime requirement. The project was composed of two major phases. The initial phase of the project has concentrated on understanding the TOPAZ-2 thermionic reactor in sufficient detail to allow several follow-on tasks. The primary interest during this first phase has been given on identifying the potential of the TOPAZ-2 design for further improvements. The second phase of the project has focused on the feasibility of a TOPAZ-2 system capable of delivering 30-50 kWe. Towards the elimination of single-point failures in the load voltage regulation system an active voltage regulator has been designed to be used in conjunction with the available shunt load voltage regulator. The possible use of a dual-loop, model-based adaptive control system for load-following in the TOPAZ-2 has also been investigated. The objective of this fault-tolerant, autonomous control system is to deliver the demanded electric power at the desired voltage level, by appropriately manipulating the neutron power through the control drums. As a result, sufficient thermal power is produced to meet the required demand in the presence of dynamically changing system operating conditions and potential sensor failures. The designed controller is proposed for use in combination with the currently available shunt regulators, or as a back-up controller when other means of power system control, including some of the sensors, fail.

Parlos, Alexander G.↗

Ascent structural wind loads for the National Space Transportation System (NSTS)

An aerospace vehicle must withstand the design ascent structural load or be within any flight constraint to safely reach orbit. For the NSTS an assessment for flight readiness is made for each mission. This assessment for ascent loads and performance parameters is stated in terms of launch probability derived from samples of Jimsphere wind profiles. For the day of launch operations an allowance is made for the ascent load variability due to the wind profile variability over a 3.5-hour period. This is the current time period required to obtain a Jimsphere measurement and perform a complete load simulation prior to launch time. The load variability is derived from a sample of 3.5-hour Jimsphere wind profile pairs. It is applied as a conditional percentile value given the wind load at 3.5 hours prior to launch time. Probability models are used for these analyses. Application of the univariate, bivariate and conditional forms of the extreme value (Gumbel) probability distribution to the analysis of extreme wind speeds, wind shears and vehicle loads is described.

Smith, O. E.↗

The Distribution of Cloud to Ground Lightning Strike Intensities and Associated Magnetic Inductance Fields Near the Kennedy Space Center

Lightning strike location and peak current are monitored operationally in the Kennedy Space Center (KSC) Cape Canaveral Air Force Station (CCAFS) area by the Cloud to Ground Lightning Surveillance System (CGLSS). The present study compiles ten years worth of CGLSS data into a database of near strikes. Using shuffle launch platform LP39A as a convenient central point, all strikes recorded within a 20-mile radius for the period of record O R ) from January 1, 1993 to December 31,2002 were included in the subset database. Histograms and cumulative probability curves are produced for both strike intensity (peak current, in kA) and the corresponding magnetic inductance fields (in A/m). Results for the full POR have application to launch operations lightning monitoring and post-strike test procedures.

Burns, Lee↗

Automating Range Surveillance Through Radio Interferometry and Field Strength Mapping Techniques

Space vehicle launches are often delayed because of the challenge of verifying that the range is clear, and such delays are likely to become more prevalent as more and more new spaceports are built. Range surveillance is one of the primary focuses of Range Safety for launches and often drives costs and schedules. As NASA's primary launch operation center, Kennedy Space Center is very interested in new technologies that increase the responsiveness of radio frequency (RF) surveillance systems. These systems help Range Safety personnel clear the range by identifying, pinpointing, and resolving any unknown sources of RF emissions prior to each launch.

Source record↗

Development and Testing of Operational Dual-Polarimetric Radar Based Lightning Initiation Forecast Techniques

Lightning is one of Earth s natural dangers, destructive not only to life but also physical property. According to the National Weather Service, there are on average 58 lightning fatalities each year, with over 300 related injuries (NWS 2010). The ability to forecast lightning is critical to a host of activities ranging from space vehicle launch operations to recreational sporting events. For example a single lightning strike to a Space Shuttle could cause billions of dollars of damage and possible loss of life. While forecasting that provides longer lead times could provide sporting officials with more time to respond to possible threatening weather events, thus saving the lives of player and bystanders. Many researchers have developed and tested different methods and tools of first flash forecasting, however few have done so using dual-polarimetric radar variables and products on an operational basis. The purpose of this study is to improve algorithms for the short-term prediction of lightning initiation through development and testing of operational techniques that rely on parameters observed and diagnosed using C-band dual-polarimetric radar.

Woodard, Crystal↗

Satellite Power Systems (SPS) concept definition study, exhibit C. Volume 5: Special emphasis studies

Specific areas were analyzed and identified as high priority for more in-depth analysis. These areas were: (1) rectenna constructability; (2) satellite constructability; (3) support systems constructability; (4) space environmental analysis, and (5) special end-to-end analyses. Baseline requirements specified coplanar solar blankets and an end mounted antenna, utilizing either GaAlAs solar cells and employing a CR of 2, or Si cells. Several configurations were analyzed. Utilizing the preferred configuration as a baseline, a satellite construction base was defined, precursor operations incident to establishment of orbital support facilities identified, and the satellite construction sequence and procedures developed. Since the baseline specifies sixty instead of one hundred and twenty satellites to be constructed in a thirty year period, mass flow to orbit requirements were revised and new traffic models established. Launch site requirements (exclusive of actual launch operations) in terms of manpower and building space were defined.

Hanley, G.↗

NASA Range Safety Annual Report 2007

As always, Range Safety has been involved in a number of exciting and challenging activities and events. Throughout the year, we have strived to meet our goal of protecting the public, the workforce, and property during range operations. During the past year, Range Safety was involved in the development, implementation, and support of range safety policy. Range Safety training curriculum development was completed this year and several courses were presented. Tailoring exercises concerning the Constellation Program were undertaken with representatives from the Constellation Program, the 45th Space Wing, and the Launch Constellation Range Safety Panel. Range Safety actively supported the Range Commanders Council and it subgroups and remained involved in updating policy related to flight safety systems and flight safety analysis. In addition, Range Safety supported the Space Shuttle Range Safety Panel and addressed policy concerning unmanned aircraft systems. Launch operations at Kennedy Space Center, the Eastern and Western ranges, Dryden Flight Research Center, and Wallops Flight Facility were addressed. Range Safety was also involved in the evaluation of a number of research and development efforts, including the space-based range (formerly STARS), the autonomous flight safety system, the enhanced flight termination system, and the joint advanced range safety system. Flight safety system challenges were evaluated. Range Safety's role in the Space Florida Customer Assistance Service Program for the Eastern Range was covered along with our support for the Space Florida Educational Balloon Release Program. We hope you have found the web-based format both accessible and easy to use. Anyone having questions or wishing to have an article included in the 2008 Range Safety Annual Report should contact Alan Dumont, the NASA Range Safety Program Manager located at the Kennedy Space Center, or Michael Dook at NASA Headquarters.

Dumont, Alan G.↗

Launch Vehicle Production and Operations Cost Metrics

Traditionally, launch vehicle cost has been evaluated based on $/Kg to orbit. This metric is calculated based on assumptions not typically met by a specific mission. These assumptions include the specified orbit whether Low Earth Orbit (LEO), Geostationary Earth Orbit (GEO), or both. The metric also assumes the payload utilizes the full lift mass of the launch vehicle, which is rarely true even with secondary payloads.1,2,3 Other approaches for cost metrics have been evaluated including unit cost of the launch vehicle and an approach to consider the full program production and operations costs.4 Unit cost considers the variable cost of the vehicle and the definition of variable costs are discussed. The full program production and operation costs include both the variable costs and the manufacturing base. This metric also distinguishes operations costs from production costs, including pre-flight operational testing. Operations costs also consider the costs of flight operations, including control center operation and maintenance. Each of these 3 cost metrics show different sensitivities to various aspects of launch vehicle cost drivers. The comparison of these metrics provides the strengths and weaknesses of each yielding an assessment useful for cost metric selection for launch vehicle programs.

Watson, Michael D.↗

Prokaryotic and Fungal Characterization of the Facilities Used to Assemble, Test, and Launch the OSIRIS-REx Spacecraft

To characterize the ATLO (Assembly, Test, and Launch Operations) environment of the OSIRIS-REx spacecraft, we analyzed 17 aluminum witness foils and two blanks for bacterial, archaeal, fungal, and arthropod DNA. Under NASA’s Planetary Protection guidelines, OSIRIS-REx is a Category II outbound, Category V unrestricted sample return mission. As a result, it has no bioburden restrictions. However, the mission does have strict organic contamination requirements to achieve its primary objective of returning pristine carbonaceous asteroid regolith to Earth. Its target, near-Earth asteroid (101955) Bennu, is likely to contain organic compounds that are biologically available. Therefore, it is useful to understand what organisms were present during ATLO as part of the larger contamination knowledge effort—even though it is unlikely that any of the organisms will survive the multi-year deep space journey. Even though these samples of opportunity were not collected or preserved for DNA analysis, we successfully amplified bacterial and archaeal DNA (16S rRNA gene) from 16 of the 17 witness foils containing as few as 7 ± 3 cells per sample. Fungal DNA (ITS1) was detected in 12 of the 17 witness foils. Despite observing arthropods in some of the ATLO facilities, arthropod DNA (COI gene) was not detected. We observed 1,009 bacterial and archaeal sOTUs (sub-operational taxonomic units, 100% unique) and 167 fungal sOTUs across all of our samples (25–84 sOTUs per sample). The most abundant bacterial sOTU belonged to the genus Bacillus. This sOTU was present in blanks and may represent contamination during sample handling or storage. The sample collected from inside the fairing just prior to launch contained several unique bacterial and fungal sOTUs that describe previously uncharacterized potential for contamination during the final phase of ATLO. Additionally, fungal richness (number of sOTUs) negatively correlates with the number of carbon-bearing particles detected on samples. The total number of fungal sequences positively correlates with total amino acid concentration. These results demonstrate that it is possible to use samples of opportunity to characterize the microbiology of low-biomass environments while also revealing the limitations imposed by sample collection and preservation methods not specifically designed with biology in mind.

Aaron B. Regberg↗

TNT equivalency study for space shuttle (EOS). Volume 1: Management summary report

The existing TNT equivalency criterion for LO2/LH2 propellant is reevaluated. It addresses the static, on-pad phase of the space shuttle launch operations and was performed to determine whether the use of a TNT equivalency criterion lower than that presently used (60%) could be substantiated. The large quantity of propellant on-board the space shuttle, 4 million pounds, was considered of prime importance to the study. A qualitative failure analysis of the space shuttle (EOS) on the launch pad was made because it was concluded that available test data on the explosive yield of LO2/LH2 propellant was insufficient to support a reduction in the present TNT equivalency value, considering the large quantity of propellant used in the space shuttle. The failure analysis had two objectives. The first was to determine whether a failure resulting in the total release of propellant could occur. The second was to determine whether, if such a failure did occur, ignition could be delayed long enough to allow the degree of propellant mixing required to produce an explosion of 60% TNT equivalency since the explosive yield of this propellant is directly related to the quantities of LH2 and LO2 mixed at the time of the explosion.

Wolfe, R. R.↗

50 Years of Electronic Check Out and Launch Systems at Kennedy Space Center

When NASA was created in 1958 one of the elements incorporated into this new agency was the Army Ballistic Missile Agency (ABMA) in Huntsville, AL and its subordinate Missile Firing Laboratory (MFL) in Cape Canaveral. Under NASA, the MFL became the Launch Operations Directorate of the George C. Marshall Space Flight Center in Huntsville, but expanding operations in the build up to Apollo dictated that it be given the status of a full fledged Center in July, 1 962[ 1]. The next year it was renamed the John F. Kennedy Space Center (KS C) after the president whose vision transformed its first decade of operation. The ABMA was under the technical leadership of Dr. Werner Von Braun. The MEL was run by his deputy Dr. Kurt Debus, an electrical engineer whose experience in the field began in the early days of V-2 testing in war time Germany. In 1952 a group led by Debus arrived in Cape Canaveral to begin test launches of the new Redstone missile [2]. During the 50's, The MFL built several launch complexes and tested the Redstone, Jupiter and Jupiter C missiles. This small experienced team of engineers and technicians formed the seed from which has grown the KSC team of today. This article briefly reviews the evolution of the KSC electronic technologies for integration, check-out and launch of space vehicles and payloads during NASA's first 50 years.

Starr, Stanley O.↗

Future Interagency Range and Spaceport Technologies (FIRST) Formulation Products: 1. Transformational Spaceport and Range Concept of Operations. 2. F.I.R.S.T. Business Case Analysis

The Baseline Report captures range and spaceport capabilities at five sites: KSC, CCAFS, VAFB, Wallops, and Kodiak. The Baseline depicts a future state that relies on existing technology, planned upgrades, and straight-line recapitalization at these sites projected through 2030. The report presents an inventory of current spaceport and range capabilities at these five sites. The baseline is the first part of analyzing a business case for a set of capabilities designed to transform U.S. ground and space launch operations toward a single, integrated national "system" of space transportation systems. The second part of the business case compares current capabilities with technologies needed to support the integrated national "system". The final part, a return on investment analysis, identifies the technologies that best lead to the integrated national system and reduce recurring costs..Numerous data sources were used to define and describe the baseline spaceport and range by identifying major systems and elements and describing capabilities, limitations, and capabilities

Source record↗

Objective Lightning Probability Forecasts for East-Central Florida Airports

The forecasters at the National Weather Service in Melbourne, FL, (NWS MLB) identified a need to make more accurate lightning forecasts to help alleviate delays due to thunderstorms in the vicinity of several commercial airports in central Florida at which they are responsible for issuing terminal aerodrome forecasts. Such forecasts would also provide safer ground operations around terminals, and would be of value to Center Weather Service Units serving air traffic controllers in Florida. To improve the forecast, the AMU was tasked to develop an objective lightning probability forecast tool for the airports using data from the National Lightning Detection Network (NLDN). The resulting forecast tool is similar to that developed by the AMU to support space launch operations at Kennedy Space Center (KSC) and Cape Canaveral Air Force Station (CCAFS) for use by the 45th Weather Squadron (45 WS) in previous tasks (Lambert and Wheeler 2005, Lambert 2007). The lightning probability forecasts are valid for the time periods and areas needed by the NWS MLB forecasters in the warm season months, defined in this task as May-September.

Crawford, Winfred C.↗

Earth Satellite Population Instability: Underscoring the Need for Debris Mitigation

A recent study by NASA indicates that the implementation of international orbital debris mitigation measures alone will not prevent a significant increase in the artificial Earth satellite population, beginning in the second half of this century. Whereas the focus of the aerospace community for the past 25 years has been on the curtailment of the generation of long-lived orbital debris, active remediation of the current orbital debris population should now be reconsidered to help preserve near-Earth space for future generations. In particular, we show in this paper that even if launch operations were to cease today, the population of space debris would continue to grow. Further, proposed remediation techniques do not appear to offer a viable solution. We therefore recommend that, while the aerospace community maintains the current debris-limiting mission regulations and postmission disposal procedures, future emphasis should be placed on finding new remediation technologies for solving this growing problem. Since the launch of Sputnik 1, space activities have created an orbital debris environment that poses increasing impact risks to existing space systems, including human space flight and robotic missions (1, 2). Currently, more than 9,000 Earth orbiting man-made objects (including many breakup fragments), with a combined mass exceeding 5 million kilograms, are tracked by the US Space Surveillance Network and maintained in the US satellite catalog (3-5). Three accidental collisions between cataloged satellites during the period from late 1991 to early 2005 have already been documented (6), although fortunately none resulted in the creation of large, trackable debris clouds. Several studies conducted during 1991-2001 demonstrated, with assumed future launch rates, the unintended growth potential of the Earth satellite population, resulting from random, accidental collisions among resident space objects (7-13). In some low Earth orbit (LEO) altitude regimes where the number density of satellites is above a critical spatial density, the production rate of new satellites (i.e., debris) due to collisions exceeds the loss of objects due to orbital decay. NASA s evolutionary satellite population model LEGEND (LEO-to-GEO Environment Debris model), developed by the Orbital Debris Program Office at the NASA Lyndon B. Johnson Space Center, is a high fidelity three-dimensional physical model that is capable of simulating the historical satellite environment, as well as the evolution of future debris populations (14, 15). The subject study assumed no rocket bodies and spacecraft were launched after December 2004, and no future disposal maneuvers were allowed for existing spacecraft, few of which currently have such a capability. The rate of satellite explosions would naturally decrease to zero within a few decades as the current satellite population ages. The LEGEND future projection adopts a Monte Carlo approach to simulate future on-orbit explosions and collisions. Within a given projection time step, once the explosion probability is estimated for an intact object, a random number is drawn and compared with the probability to determine if an explosion would occur. A similar procedure is applied to collisions for each pair of target and projectile involved within the same time step. Due to the nature of the Monte Carlo process, multiple projection runs must be performed and analyzed before one can draw reliable and meaningful conclusions from the outcome. A total of fifty, 200-year future projection Monte Carlo simulations were executed and evaluated (16).

Liou, Jer-chyi↗

Comparison of the KSC-ER Cloud-to-Ground Lightning Surveillance System (CGLSS) and the U.S. National Lightning Detection Network(TradeMark)(NLDN)

The NASA Kennedy Space Center (KSC) and Air Force Eastern Range (ER) use data from two cloud-to-ground lightning detection networks, CGLSS and NLDN, during ground and launch operations at the KSC-ER. For these applications, it is very important to understand the location accuracy and detection efficiency of each network near the KSC-ER. If a cloud-to-ground (CG) lightning strike is missed or mis-located by even a small amount, the result could have significant safety implications, require expensive retests, or create unnecessary delays or scrubs in launches. Therefore, it is important to understand the performance of each lightning detection system in considerable detail. To evaluate recent upgrades in the CGLSS sensors in 2000 and the entire NLDN in 2002- 2003, we have compared. measurements provided by these independent networks in the summers of 2005 and 2006. Our analyses have focused on the fraction of first strokes reported individually and in-common by each network (flash detection efficiency), the spatial separation between the strike points reported by both networks (relative location accuracy), and the values of the estimated peak current, Ip, reported by each network. The results within 100 km of the KSC-ER show that the networks produce very similar values of Ip (except for a small scaling difference) and that the relative location accuracy is consistent with model estimates that give median values of 200-300m for the CGLSS and 600-700m for the NLDN in the region of the KSC-ER. Because of differences in the network geometries and sensor gains, the NLDN does not report 10-20% of the flashes that have a low Ip (2 kA < |Ip| < 16 kA), both networks report 99 % of the flashes that have intermediate values of Ip (16< |Ip| < 50 kA), and the CGLSS fails to report 20-30% of the high-current events (|Ip| >=0 kA).

Ward, Jennifer G.↗

Vehicle management and mission planning systems with shuttle applications

A preliminary definition of a concept for an automated system is presented that will support the effective management and planning of space shuttle operations. It is called the Vehicle Management and Mission Planning System (VMMPS). In addition to defining the system and its functions, some of the software requirements of the system are identified and a phased and evolutionary method is recommended for software design, development, and implementation. The concept is composed of eight software subsystems supervised by an executive system. These subsystems are mission design and analysis, flight scheduler, launch operations, vehicle operations, payload support operations, crew support, information management, and flight operations support. In addition to presenting the proposed system, a discussion of the evolutionary software development philosophy that the Mission Planning and Analysis Division (MPAD) would propose to use in developing the required supporting software is included. A preliminary software development schedule is also included.

Source record↗

Trade study: Liquid hydrogen transportation - Kennedy Space Center

Cryogenic transportation methods for providing liquid hydrogen requirements are examined in support of shuttle transportation system launch operations at Kennedy Space Center, Florida, during the time frames 1982-1991 in terms of cost and operational effectiveness. Transportation methods considered included sixteen different options employing mobile semi-trailer tankers, railcars, barges and combinations of each method. The study concludes that the most effective method of delivering liquid hydrogen from the vendor production facility in New Orleans to Kennedy Space Center includes maximum utilization of existing mobile tankers and railcars supplemented by maximum capacity mobile tankers procured incrementally in accordance with shuttle launch rates actually achieved.

Gray, D. J.↗