Search NASA⌕ Search

SEARCH · Search NASA

Results for “mission sequencing”

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 271 records · Page 15
All sourcesNASA NTRSDOE OSTI
NASA NTRS2021

Concept of Operations for OSIRIS-REx Optical Navigation Image Planning

Optical navigation (OpNav) is a critical subsystem of the OSIRIS-REx asteroid sample return mission, which operated in the vicinity of near-Earth asteroid (101955) Bennu from August 2018 through April 2021. A substantial amount of mission resources across multiple subsystems and institutions is required to ensure that the OpNav data are successfully acquired. The KinetX OpNav team, part of the Flight Dynamics System (FDS), is responsible for performing required analysis to develop the OpNav operations plans; requesting, reviewing and verifying the plans; and ultimately using the image data for critical navigation operations. The FDS team, responsible for the mission navigation, is operated by KinetX Aerospace with management and operations support from NASA’s Goddard Space Flight Center. The Science Processing and Operations Center (SPOC), located at the University of Arizona’s Lunar and Planetary Laboratory, is responsible for generating the planning products for all science and most OpNav data. These plans are integrated into the spacecraft sequences, tested, and commanded by the Mission Support Area (MSA) at Lockheed Martin Space. To ensure mission-critical navigation image data are successfully acquired, the plan is developed through a waterfall of planning cycles over the course of 3 months prior to onboard plan execution. During the initial strategic planning for a mission phase, detailed analysis is performed by the OpNav team to conceptualize the concept of operations (ConOps) for image data collection. This phase OpNav Narrative is included along with other strategic planning documents for the key ground segment stakeholders to review and provide feedback. The detailed OpNav plans get defined in the tactical planning cycle, which spans 8 to 3 weeks before the week-long integrated sequence is executed on-board the spacecraft. During the tactical cycle, the initial OpNav Request is submitted along with the science requests, kicking off development of the science and OpNav plans. Once the initial plan is drafted, interfaces are exercised so that the plan can be reviewed and iterated, if necessary. A rigorous schedule is followed by the planning teams during the implementation cycle, spanning the last 18 days before uplink, to ensure all the necessary integration, testing, and reviewing can occur on time. The development of the OpNav planning ConOps, including responsibilities, interfaces, timelines, and procedures, took extensive collaboration across mission elements and institutions. The process was robust throughout the 137 weeks of continuous Optical Navigation Operations at Bennu, which concluded on April 9th, 2021.

Coralie D. Adam↗
NASA NTRSDate not supplied

Development of Space Mission Integrated Operations Scenarios

Integrated Operations Scenarios (IOS) describe nominal operations planned for a space mission. Operational scenarios are key to an operations concept, as they help identify issues and drivers on the operations system. This paper covers the tools, processes, and inputs that feed into an IOS product, and how IOS iterations during a mission lifecycle can buy down operational risks. A case used for this paper is nominal operations for an initial crewed Artemis mission that includes cross-program sequence of tasks required to accomplish end to end functions from launch through transit, on-orbit operations, to safely return to Earth. An IOS product serves as a reference for discussions during requirements development, task and risk analyses, concept of operations development, and as foundation to prepare space mission flight plans.

integrated operations scenarios↗
NASA NTRS2018

Radio-hosted Flight / Ground Interface for Operations Standardization

The interface between a spacecraft and its ground operations segment includes the flow of commands, configuration, and sequencing elements to the spacecraft, and the flow of telemetry and data products from the spacecraft. Creating and implementing a complete definition of this interface simplifies and standardizes mission operations, allowing easy sharing of operations personnel across missions. Early spacecraft featured a simple flight / ground interface (FGI) using hardware command decoding in the radio, driven by technological limitations of the time. Modern spacecraft use command and data handling (CDH) avionics on which flight software executes, which in turn controls and configures the mission, executes subsystem and instrument instructions, and implements critical fault protection actions. Deep space missions feature advanced operations software for running sequenced activities over a period of weeks, which allows them to function with only infrequent ground contact. This approach comes at the cost of increased complexity in the FGI, requiring expensive modifications to heritage flight software and ground systems. By hosting the interface in the radio instead of the CDH avionics, modern missions can approximate the FGI design simplicity of early spacecraft, with significant advantages for vendor competition, lowered costs, standardization of operations, and reduction of implementation risk.

Lock, Patricia D.↗
NASA NTRS1996

STS-77 Space Shuttle Mission Report

The STS-77 Space Shuttle Program Mission Report summarizes the Payload activities as well as the: Orbiter, External Tank (ET), Solid Rocket Booster (SRB), Reusable Solid Rocket Motor (RSRM), and the Space Shuttle Main Engine (SSME) systems performance during the seventy-seventh flight of the Space Shuttle Program, the fifty-second flight since the return-to-flight, and the eleventh flight of the Orbiter Endeavour (OV-105). STS-77 was also the last flight of OV-105 prior to the vehicle being placed in the Orbiter Maintenance Down Period (OMDP). In addition to the Orbiter, the flight vehicle consisted of an ET that was designated ET-78; three SSME's that were designated as serial numbers 2037, 2040, and 2038 in positions 1, 2, and 3, respectively; and two SRB's that were designated BI-080. The RSRM's, designated RSRM-47, were installed in each SRB and the individual RSRM's were designated as 360TO47A for the left SRB, and 360TO47B for the right SRB. The STS-77 Space Shuttle Program Mission Report fulfills the Space Shuttle Program requirement as documented in NSTS 07700, Volume VII, Appendix E. The requirement stated in that document is that each organizational element supporting the Program will report the results of their hardware (and software) evaluation and mission performance plus identify all related in-flight anomalies. The primary objectives of this flight were to successfully perform the operations necessary to fulfill the requirements of Spacehab-4, the SPARTAN 207/inflatable Antenna Experiment (IAE), and the Technology Experiments Advancing Missions in Space (TEAMS) payload. Secondary objectives of this flight were to perform the experiments of the Aquatic Research Facility (ARF), Brilliant Eyes Ten-Kelvin Sorption Cryocooler Experiment (BETSCE), Biological Research in Canisters (BRIC), Get-Away-Special (GAS), and GAS Bridge Assembly (GBA). The STS-77 mission was planned as a 9-day flight plus 1 day, plus 2 contingency days, which were available for weather avoidance or Orbiter contingency operations. The sequence of events for the STS-77 mission is shown in Table 1, and the Space Shuttle Vehicle Management Office Problem Tracking List is shown in Table 11. The Government Fumished Equipment/Flight Crew Equipment (GFE/FCE) Problem Tracking List is shown in Table II. Appendix A lists the sources of data, both formal and informal, that were used to prepare this report. Appendix B provides the definition of acronyms and abbreviations used throughout the report. All times during the flight are given in Greenwich mean time (G.m.t.) and mission elapsed time (MET). The six-person crew for STS-77 consisted of John H. Casper, Col., U. S. Air Force, Commander; Curtis L. Brown, Jr., Lt. Col., U. S. Air Force, Pilot; Andrew S. W. Thomas, Civilian, Ph.D., Mission Specialist 1; Daniel W. Bursch, CDR., U. S. Navy, Mission Specialist 2; Mario Runco, Jr., Civilian, Mission Specialist 3; and Marc Gameau, Civilian, PhD, Mission Specialist 4.

Fricke, Robert W., Jr.↗
NASA NTRS1996

STS-78 Space Shuttle Mission Report

The STS-78 Space Shuttle Program Mission Report summarizes the Payload activities as well as the Orbiter, External Tank (ET), Solid Rocket Booster (SRB), Reusable Solid Rocket Motor (RSRM), and the Space Shuttle main engine (SSME) systems performance during the seventy-eighth flight of the Space Shuttle Program, the fifty-third flight since the return-to-flight, and the twentieth flight of the Orbiter Columbia (OV-102). In addition to the Orbiter, the flight vehicle consisted of an ET that was designated ET-79; three SSME's that were designated as serial numbers 2041, 2039, and 2036 in positions 1, 2, and 3, respectively; and two SRB's that were designated BI-081. The RSRM's, designated RSRM-55, were installed in each SRB and the individual RSRM's were designated as 360L055A for the left SRB, and 360L055B for the right SRB. The STS-78 Space Shuttle Program Mission Report fulfills the Space Shuttle Program requirement as documented in NSTS 07700, Volume 7, Appendix E. The requirement stated in that document is that each organizational element supporting the Program will report the results of their hardware (and software) evaluation and mission performance plus identify all related in-flight anomalies. The primary objective of this flight was to successfully perform the planned operations of the Life and Microgravity Spacelab experiments. The secondary objectives of this flight were to complete the operations of the Orbital Acceleration Research Experiment (OARE), Biological Research in Canister Unit-Block II (BRIC), and the Shuttle Amateur Radio Experiment II-Configuration C (SAREX-II). The STS-78 mission was planned as a 16-day, plus one day flight plus two contingency days, which were available for weather avoidance or Orbiter contingency operations. The sequence of events for the STS-78 mission is shown in Table 1, and the Space Shuttle Vehicle Management Office Problem Tracking List is shown in Table 2. The Government Furnished Equipment/Flight Crew Equipment (GFE/FCE) Problem Tracking List is shown in Table 3. The Marshall Space Flight Center (MSFC) Problem Tracking List is shown in Table 4. Appendix A lists the sources of data, both formal and informal, that were used to prepare this report. Appendix B provides the definition of acronyms and abbreviations used throughout the report. All times during the flight are given in Greenwich mean time (G.m.t.) and mission elapsed time (MET).

Fricke, Robert W., Jr.↗
NASA NTRS1989

Interdependent figure-of-merit software development

This program was undertaken in order to understand the complex nature of interdependent performance in space missions. At the first step in a planned sequence of progress, a spread sheet program was developed to evaluate different fuel/oxidizer combinations for a specific Martian mission. This program is to be linked with output attained using sophisticated software produced by Gordon and McBride. The programming to date makes use of 11 independent parameters. Optimization is essential when faced with the incredible magnitude of costs, risks, and benefits involved with space exploration. A system of weights needs to be devised on which to measure the options. It was the goal to devise a Figure of Merit (FoM) on which different choices can be presented and made. The plan was to model typical missions to Mars, identify the parameters, and vary them until the best one is found. Initially, most of the focus was placed on propellant selection.

Ramohalli, K.↗
NASA NTRS2005

Update on Rover Sequencing and Visualization Program

The Rover Sequencing and Visualization Program (RSVP) has been updated. RSVP was reported in Rover Sequencing and Visualization Program (NPO-30845), NASA Tech Briefs, Vol. 29, No. 4 (April 2005), page 38. To recapitulate: The Rover Sequencing and Visualization Program (RSVP) is the software tool to be used in the Mars Exploration Rover (MER) mission for planning rover operations and generating command sequences for accomplishing those operations. RSVP combines three-dimensional (3D) visualization for immersive exploration of the operations area, stereoscopic image display for high-resolution examination of the downlinked imagery, and a sophisticated command-sequence editing tool for analysis and completion of the sequences. RSVP is linked with actual flight code modules for operations rehearsal to provide feedback on the expected behavior of the rover prior to committing to a particular sequence. Playback tools allow for review of both rehearsed rover behavior and downlinked results of actual rover operations. These can be displayed simultaneously for comparison of rehearsed and actual activities for verification. The primary inputs to RSVP are downlink data products from the Operations Storage Server (OSS) and activity plans generated by the science team. The activity plans are high-level goals for the next day s activities. The downlink data products include imagery, terrain models, and telemetered engineering data on rover activities and state. The Rover Sequence Editor (RoSE) component of RSVP performs activity expansion to command sequences, command creation and editing with setting of command parameters, and viewing and management of rover resources. The HyperDrive component of RSVP performs 2D and 3D visualization of the rover s environment, graphical and animated review of rover predicted and telemetered state, and creation and editing of command sequences related to mobility and Instrument Deployment Device (robotic arm) operations. Additionally, RoSE and HyperDrive together evaluate command sequences for potential violations of flight and safety rules. The products of RSVP include command sequences for uplink that are stored in the Distributed Object Manager (DOM) and predicted rover state histories stored in the OSS for comparison and validation of downlinked telemetry. The majority of components comprising RSVP utilize the MER command and activity dictionaries to automatically customize the system for MER activities.

Cooper, Brian↗
NASA NTRS1993

Main-sequence stars with circumstellar solid material - The Vega phenomenon

The detection of solid grains with temperatures of 50 to 125 K and fractional bolometric luminosities in the range 10 exp -5 to 10 exp -3 early in the IRAS mission around three nearby A main-sequence stars, Alpha Lyrae (Vega), Alpha Piscis Austrinus (Fomalhaut), and Beta Pictoris, is discussed. Spatial resolution of the emission indicates that: the grains are larger than interstellar grains, the material probably lies in disks in the stellar equatorial planes, the disks extend to distances of 100 to 1000 AU from the stars, and zones a few tens of AU in radius around the central stars are relatively empty. Subsequent surveys of IRAS data reveal more than 100 main-sequence stars of all spectral classes having unresolved excesses with similar temperatures and fractional luminosities to the three prototypes. Some stars with excesses have estimated ages of 1 to 5 Gyr. Thus, main-sequence FIR excesses appear to be widespread and are present in systems old enough to be probably past the stage of active planet formation.

Backman, Dana E.↗
NASA NTRS2004

Nanoscale Bio-engineering Solutions for Space Exploration: The Nanopore Sequencer

Characterization of biological systems at the molecular level and extraction of essential information for nano-engineering design to guide the nano-fabrication of solid-state sensors and molecular identification devices is a computational challenge. The alpha hemolysin protein ion channel is used as a model system for structural analysis of nucleic acids like DNA. Applied voltage draws a DNA strand and surrounding ionic solution through the biological nanopore. The subunits in the DNA strand block ion flow by differing amounts. Atomistic scale simulations are employed using NASA supercomputers to study DNA translocation, with the aim to enhance single DNA subunit identification. Compared to protein channels, solid-state nanopores offer a better temporal control of the translocation of DNA and the possibility to easily tune its chemistry to increase the signal resolution. Potential applications for NASA missions, besides real-time genome sequencing include astronaut health, life detection and decoding of various genomes.

Stolc, Viktor↗
NASA NTRS2005

Nanoscale Bioengineering Solutions for Space Exploration the Nanopore Sequencer

Characterization of biological systems at the molecular level and extraction of essential information for nano-engineering design to guide the nano-fabrication of solid-state sensors and molecular identification devices is a computational challenge. The alpha hemolysin protein ion channel is used as a model system for structural analysis of nucleic acids like DNA. Applied voltage draws a DNA strand and surrounding ionic solution through the biological nanopore. The subunits in the DNA strand block ion flow by differing amounts. Atomistic scale simulations are employed using NASA supercomputers to study DNA translocation. with the aim to enhance single DNA subunit identification. Compared to protein channels, solid-state nanopores offer a better temporal control of the translocation of DNA and the possibility to easily tune its chemistry to increase the signal resolution. Potential applications for NASA missions, besides real-time genome sequencing include astronaut health, life detection and decoding of various genomes. http://phenomrph.arc.nasa.gov/index.php

Ioana, Cozmuta↗
NASA NTRS1963

Vehicle Design for Mars Landing and Return to Mars Orbit

This paper briefly describes three modes for accomplishing the Mars landing mission and compares them on a gross basis to indicate their probable order of merit and to identify design requirements placed on the Mars-excursion module (MEM) by the choice of mode. The paper shows that a flyby-rendezvous mode requiring low weight in earth orbit requires the MEM to enter the Mars atmosphere at velocities ranging from 20,000 to 30,000 ft/sec. The MEM for the flyby-rendezvous mode is not covered in this paper but merits further study. The MEM for the other modes of mission accomplishment begins its active operational sequence in Mars orbit and need not be greatly influenced by the method of delivery to Mars orbit. Parametric studies of the entry problem for two vehicles typifying a ballistic-type and a lifting-body-type were conducted to identify the problems associated with design of a MEM to accommodate the extremes of Mars atmospheric density presently predicted. This brief study indicates that: (a) the presently predicted density extremes of the Mars atmosphere present no serious design problems for a MEM which can operate across the entire band of predicted densities; (b) details of operational requirements and mission objectives will control the choice of configuration rather than entry requirements; and (c) the ballistic-type MEM is lighter and simpler but has less operational flexibility than a high L/D MEM.

Hammock, D. M.↗
NASA NTRS2007

CEV Trajectory Design Considerations for Lunar Missions

The Crew Exploration Vehicle (CEV) translational maneuver Delta-V budget must support both the successful completion of a nominal lunar mission and an "anytime" emergency crew return with the potential for much more demanding orbital maneuvers. This translational Delta-V budget accounts for Earth-based LEO rendezvous with the lunar surface access module (LSAM)/Earth departure stage (EDS) stack, orbit maintenance during the lunar surface stay, an on-orbit plane change to align the CEV orbit for an in-plane LSAM ascent, and the Moon-to-Earth trans-Earth injection (TEI) maneuver sequence as well as post-TEI TCMs. Additionally, the CEV will have to execute TEI maneuver sequences while observing Earth atmospheric entry interface objectives for lunar high-latitude to equatorial sortie missions as well as near-polar sortie and long duration missions. The combination of these objectives places a premium on appropriately designed trajectories both to and from the Moon to accurately size the translational V and associated propellant mass in the CEV reference configuration and to demonstrate the feasibility of anytime Earth return for all lunar missions. This report examines the design of the primary CEV translational maneuvers (or maneuver sequences) including associated mission design philosophy, associated assumptions, and methodology for lunar sortie missions with up to a 7-day surface stay and with global lunar landing site access as well as for long duration (outpost) missions with up to a 210-day surface stay at or near the polar regions. The analyses presented in this report supports the Constellation Program and CEV project requirement for nominal and anytime abort (early return) by providing for minimum wedge angles, lunar orbit maintenance maneuvers, phasing orbit inclination changes, and lunar departure maneuvers for a CEV supporting an LSAM launch and subsequent CEV TEI to Earth return, anytime during the lunar surface stay.

Condon, Gerald L.↗
NASA NTRS2009

Global Performance Characterization of the Three Burn Trans-Earth Injection Maneuver Sequence over the Lunar Nodal Cycle

The Orion spacecraft will be required to perform a three-burn trans-Earth injection (TEI) maneuver sequence to return to Earth from low lunar orbit. The origin of this approach lies in the Constellation Program requirements for access to any lunar landing site location combined with anytime lunar departure. This paper documents the development of optimized databases used to rapidly model the performance requirements of the TEI three-burn sequence for an extremely large number of mission cases. It also discusses performance results for lunar departures covering a complete 18.6 year lunar nodal cycle as well as general characteristics of the optimized three-burn TEI sequence.

Williams, Jacob↗
NASA NTRS2009

Presentation Extensions of the SOAP

A set of extensions of the Satellite Orbit Analysis Program (SOAP) enables simultaneous and/or sequential presentation of information from multiple sources. SOAP is used in the aerospace community as a means of collaborative visualization and analysis of data on planned spacecraft missions. The following definitions of terms also describe the display modalities of SOAP as now extended: In SOAP terminology, View signifies an animated three-dimensional (3D) scene, two-dimensional still image, plot of numerical data, or any other visible display derived from a computational simulation or other data source; a) "Viewport" signifies a rectangular portion of a computer-display window containing a view; b) "Palette" signifies a collection of one or more viewports configured for simultaneous (split-screen) display in the same window; c) "Slide" signifies a palette with a beginning and ending time and an animation time step; and d) "Presentation" signifies a prescribed sequence of slides. For example, multiple 3D views from different locations can be crafted for simultaneous display and combined with numerical plots and other representations of data for both qualitative and quantitative analysis. The resulting sets of views can be temporally sequenced to convey visual impressions of a sequence of events for a planned mission.

Carnright, Robert↗
NASA NTRS2011

Flight Dynamics Operations: Methods and Lessons Learned from Space Shuttle Orbit Operations

The Flight Dynamics Officer is responsible for trajectory maintenance of the Space Shuttle. This paper will cover high level operational considerations, methodology, procedures, and lessons learned involved in performing the functions of orbit and rendezvous Flight Dynamics Officer and leading the team of flight dynamics specialists during different phases of flight. The primary functions that will be address are: onboard state vector maintenance, ground ephemeris maintenance, calculation of ground and spacecraft acquisitions, collision avoidance, burn targeting for the primary mission, rendezvous, deorbit and contingencies, separation sequences, emergency deorbit preparation, mass properties coordination, payload deployment planning, coordination with the International Space Station, and coordination with worldwide trajectory customers. Each of these tasks require the Flight Dynamics Officer to have cognizance of the current trajectory state as well as the impact of future events on the trajectory plan in order to properly analyze and react to real-time changes. Additionally, considerations are made to prepare flexible alternative trajectory plans in the case timeline changes or a systems failure impact the primary plan. The evolution of the methodology, procedures, and techniques used by the Flight Dynamics Officer to perform these tasks will be discussed. Particular attention will be given to how specific Space Shuttle mission and training simulation experiences, particularly off-nominal or unexpected events such as shortened mission durations, tank failures, contingency deorbit, navigation errors, conjunctions, and unexpected payload deployments, have influenced the operational procedures and training for performing Space Shuttle flight dynamics operations over the history of the program. These lessons learned can then be extended to future vehicle trajectory operations.

Cutri-Kohart, Rebecca M.↗
NASA NTRS1991

[STS-48 Mission Highlights Resource Tape. Part 1 of 2]

In this first part of a two part video mission-highlights set, the flight of the STS-48 Space Shuttle Orbiter Discovery is reviewed. The flight crew consisted of: J. O. Creighton (Commander); Ken Reightler (Pilot); Charles 'Sam' Gemar (Mission Specialist); James 'Jim' Buchli (MS); and Mark Brown (MS). Step-by-step pre-launch and sunset launch sequences are shown with accompanying shots inside the Mission Control Center. The primary goal of this mission was the deployment of Upper Atmosphere Research Satellite (UARS). Other (secondary) payloads included: the MidDeck Zero Gravity Experiment (MODE); the Sam/Cream device; the Shuttle Activation Monitor/Cosmic Ray Effects and Activation Monitor Experiment; and the Physiology and Anatomical Rodent Experiment (PARE). Crew activities were shown, along with Earth views (Aurora Borealis (B/W), light from the Kuwait oil fires, lightning over Italy and other areas, polar regions and ice caps, and the United States at night (B/W)). This was the thirteenth flight of the Space Shuttle Discovery. A night landing is shown.

Source record↗