Search NASA⌕ Search

SEARCH · Search NASA

Results for “Flight 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 1,549 records · Page 86

Concepts and Challenges for Environmentally Friendly En Route Operations

A flight trajectory optimization algorithm with fuel and contrails models, which develops alternative flight paths, provides policy makers the necessary data to make tradeoffs between persistent contrails mitigation and aircraft fuel consumption. This study develops an algorithm that calculates wind-optimal trajectories for cruising aircraft while avoiding the regions of airspace prone to persistent contrails formation. The optimal trajectory is derived using Singular Perturbation Method. The regions of airspace favorable to persistent contrails formation are modeled as high-risk areas that aircraft should avoid and are adjustable. The tradeoffs between persistent contrails formation and additional travel time are investigated for wind-optimal trajectories and various contrails-avoidance trajectories at 10 different cruising altitudes for flights departing from Chicago and San Diego to New York. The additional travel times required for avoiding 100% persistent contrails formation at various flight altitudes ranged from approximately 0% to 4.3% for flights from Chicago to New York. For flights between San Diego and New York, additional traveling times vary between 1.3% and 5% depending on the cruise altitude and the percentage of contrail avoidance. Talk will present the results of aircraft fuel consumptions that are proportional to the travel time for cruising aircraft.

Sridhar, Banavar↗

A psychophysiological assessment of operator workload during simulated flight missions

The applicability of the dual-task event-related (brain) potential (ERP) paradigm to the assessment of an operator's mental workload and residual capacity in a complex situation of a flight mission was demonstrated using ERP measurements and subjective workload ratings of student pilots flying a fixed-based single-engine simulator. Data were collected during two separate 45-min flights differing in difficulty; flight demands were examined by dividing each flight into four segments: takeoff, straight and level flight, holding patterns, and landings. The P300 ERP component in particular was found to discriminate among the levels of task difficulty in a systematic manner, decreasing in amplitude with an increase in task demands. The P300 amplitude is shown to be negatively correlated with deviations from command headings across the four flight segments.

Kramer, Arthur F.↗

Transportable Payload Operations Control Center reusable software: Building blocks for quality ground data systems

The Mission Operations Division (MOD) at Goddard Space Flight Center builds Mission Operations Centers which are used by Flight Operations Teams to monitor and control satellites. Reducing system life cycle costs through software reuse has always been a priority of the MOD. The MOD's Transportable Payload Operations Control Center development team established an extensive library of 14 subsystems with over 100,000 delivered source instructions of reusable, generic software components. Nine TPOCC-based control centers to date support 11 satellites and achieved an average software reuse level of more than 75 percent. This paper shares experiences of how the TPOCC building blocks were developed and how building block developer's, mission development teams, and users are all part of the process.

Mahmot, Ron↗

Space Operations Center system analysis. Volume 3, book 2: SOC system definition report, revision A

The Space Operations Center (SOC) orbital space station program operations are described. A work breakdown structure for the general purpose support equipment, construction and transportation support, and resupply and logistics support systems is given. The basis for the design of each element is presented, and a mass estimate for each element supplied. The SOC build-up operation, construction, flight support, and satellite servicing operations are described. Detailed programmatics and cost analysis are presented.

Source record↗

Navigation Operations for the Magnetospheric Multiscale Mission

The Magnetospheric Multiscale (MMS) mission employs four identical spinning spacecraft flying in highly elliptical Earth orbits. These spacecraft will fly in a series of tetrahedral formations with separations of less than 10 km. MMS navigation operations use onboard navigation to satisfy the mission definitive orbit and time determination requirements and in addition to minimize operations cost and complexity. The onboard navigation subsystem consists of the Navigator GPS receiver with Goddard Enhanced Onboard Navigation System (GEONS) software, and an Ultra-Stable Oscillator. The four MMS spacecraft are operated from a single Mission Operations Center, which includes a Flight Dynamics Operations Area (FDOA) that supports MMS navigation operations, as well as maneuver planning, conjunction assessment and attitude ground operations. The System Manager component of the FDOA automates routine operations processes. The GEONS Ground Support System component of the FDOA provides the tools needed to support MMS navigation operations. This paper provides an overview of the MMS mission and associated navigation requirements and constraints and discusses MMS navigation operations and the associated MMS ground system components built to support navigation-related operations.

Navigation↗

Verification and Implementation of Operations Safety Controls for Flight Missions

Approximately eleven years ago, the International Space Station launched the first module from Russia, the Functional Cargo Block (FGB). Safety and Mission Assurance (S&MA) Operations (Ops) Engineers played an integral part in that endeavor by executing strict flight product verification as well as continued staffing of S&MA's console in the Mission Evaluation Room (MER) for that flight mission. How were these engineers able to conduct such a complicated task? They conducted it based on product verification that consisted of ensuring that safety requirements were adequately contained in all flight products that affected crew safety. S&MA Ops engineers apply both systems engineering and project management principles in order to gain a appropriate level of technical knowledge necessary to perform thorough reviews which cover the subsystem(s) affected. They also ensured that mission priorities were carried out with a great detail and success.

Jones, Cheryl L.↗

Control center operations at the Goddard Space Flight Center

Information is given in viewgraph form on control center operations at the Goddard Space Flight Center. Information is given on multi-mission, dedicated and attached payload support; the mission operations environment; technical challenges; Hubble Space Telescope (HST) science planning interface; operations engineering life cycle; Special Analysis of Maneuverable Satellites (SAMS) operations; and user interface applications.

Connerton, Robert M.↗

Pyrotechnically Operated Valves for Testing and Flight

Pyrovalves still warrant careful description of their operating characteristics, which is consistent with the NASA mission - to assure that both testing and flight hardware perform with the utmost reliability. So, until the development and qualification of the next generation of remotely controlled valves, in all likelihood based on shape memory alloy technology, pyrovalves will remain ubiquitous in controlling flow systems aloft and will possibly see growing use in ground-based testing facilities. In order to assist NASA in accomplishing this task, we propose a three-phase, three-year testing program. Phase I would set up an experimental facility, a 'test rig' in close cooperation with the staff located at the White Sands Test Facility in Southern New Mexico.

Conley, Edgar G.↗

Mars Pathfinder mission operations concepts

The Mars Pathfinder Project plans a December 1996 launch of a single spacecraft. After jettisoning a cruise stage, an entry body containing a lander and microrover will directly enter the Mars atmosphere and parachute to a hard landing near the sub-solar latitude of 15 degrees North in July 1997. Primary surface operations last for 30 days. Cost estimates for Pathfinder ground systems development and operations are not only lower in absolute dollars, but also are a lower percentage of total project costs than in past planetary missions. Operations teams will be smaller and fewer than typical flight projects. Operations scenarios have been developed early in the project and are being used to guide operations implementation and flight system design. Recovery of key engineering data from entry, descent, and landing is a top mission priority. These data will be recorded for playback after landing. Real-time tracking of a modified carrier signal through this phase can provide important insight into the spacecraft performance during entry, descent, and landing in the event recorded data is never recovered. Surface scenarios are dominated by microrover activity and lander imaging during 7 hours of the Mars day from 0700 to 1400 local solar time. Efficient uplink and downlink processes have been designed to command the lander and microrover each Mars day.

Sturms, Francis M., Jr.↗

Rapid development of the X-31 simulation to support flight-testing

The X-31 Enhanced Fighter Maneuverability Program has been recognized to form the International Test Organization, with the NASA Dryden Flight Research Facility (NASA-Dryden) as the responsible test organization. The two X-31 research aircraft and engineering support personnel were colocated at NASA-Dryden, with flight test operations beginning in Apr. 1992. Therefore, rapid development of a hardware-in-the-loop simulation was needed to support the flight test operations at NASA-Dryden, and to perform verification and validation of flight control software. The X-31 simulation system requirements, distributed simulation system architecture, simulation components math models to the visual system, and the advanced capabilities the X-31 simulation provides. In addition, unique software tools and the methods used to rapidly develop this simulation system will be highlighted.

Mackall, Dale↗

Rapid development of the X-31 simulation to support flight-testing

The X-31 Enhanced Fighter Maneuverability Program has been recognized to form the International Test Organization, with the NASA Dryden Flight Research Facility (NASA-Dryden) as the responsible test organization. The two X-31 research aircraft and engineering support personnel were colocated at NASA-Dryden, with flight test operations beginning in Apr. 1992. Therefore, rapid development of a hardware-in-the-loop simulation was needed to support the flight test operations at NASA-Dryden, and to perform verification and validation of flight control software. The X-31 simulation system requirements, distributed simulation system architecture, simulation components math models to the visual system, and the advanced capabilities the X-31 simulation provides. In addition, unique software tools and the methods used to rapidly develop this simulation system will be highlighted.

Mackall, Dale↗

"Built-In" Action/Issues Tracking and Post-Ops Analysis Tool for Realtime Console Operations

Marshall Space Flight Center's (MSFC) Payload Operations Integration Center (POIC) for the International Space Station (ISS) uses a number of formal databases to manage and track flight plan changes, onboard and ground equipment anomalies, and other events. However, individual console positions encounter many action items and/or occurrences that don't fit neatly into the databases, and while console logs are comprehensive, manual or automated searches do not always yield consistent results. The Payload Communications Manager (PAYCOM) team, whose members speak directly with the ISS onboard crew with respect to NASA payload operations, has found a creative way to reformat a mandatory Daily Report to organize action items, standing reminders, significant events, and other comments. While the report keeps others appraised of PAYCOMs activities and issues of the moment, the format makes it easy to capture very brief summaries of the items in a "Roll Off Matrix", including start and stop dates, resolution, and possible applicability to future ops. The matrix provides accountability for all action items, gives direct insight into the issues surrounding various payloads and methods of dealing with them, yields indirect information on PAYCOM priorities and processes, and provides a roadmap that makes it easier to get back to extensive details if needed. This paper describes how the ISS PAYCOM Daily Report and Roll Off Matrix are organized, used, and inter-related to each other and the PAYCOM operations log. While the application is for a manned vehicle, the concepts could apply in a wide spectrum of operational settings.

Scott, David W.↗

Cassini's Test Methodology for Flight Software Verification and Operations

The Cassini spacecraft was launched on 15 October 1997 on a Titan IV-B launch vehicle. The spacecraft is comprised of various subsystems, including the Attitude and Articulation Control Subsystem (AACS). The AACS Flight Software (FSW) and its development has been an ongoing effort, from the design, development and finally operations. As planned, major modifications to certain FSW functions were designed, tested, verified and uploaded during the cruise phase of the mission. Each flight software upload involved extensive verification testing. A standardized FSW testing methodology was used to verify the integrity of the flight software. This paper summarizes the flight software testing methodology used for verifying FSW from pre-launch through the prime mission, with an emphasis on flight experience testing during the first 2.5 years of the prime mission (July 2004 through January 2007).

Cassini Mission↗

A Flight Deck Decision Support Tool for Autonomous Airborne Operations

NASA is developing a flight deck decision support tool to support research into autonomous operations in a future distributed air/ground traffic management environment. This interactive real-time decision aid, referred to as the Autonomous Operations Planner (AOP), will enable the flight crew to plan autonomously in the presence of dense traffic and complex flight management constraints. In assisting the flight crew, the AOP accounts for traffic flow management and airspace constraints, schedule requirements, weather hazards, aircraft operational limits, and crew or airline flight-planning goals. This paper describes the AOP and presents an overview of functional and implementation design considerations required for its development. Required AOP functionality is described, its application in autonomous operations research is discussed, and a prototype software architecture for the AOP is presented.

Ballin, Mark G.↗