Search NASA⌕ Search

SEARCH · Search NASA

Results for “flight schedules”

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 343 records · Page 19

Scheduling Software

Advanced Scheduling Environment is a software product designed and marketed by AVYX, Inc. to provide scheduling solutions for complex manufacturing environments. It can be adapted to specific scheduling and manufacturing processes and has led to substantial cost savings. The system was originally developed for NASA use in scheduling Space Shuttle flights and satellite activities. AVYX, Inc. is an offshoot of a company formed to provide computer-related services to NASA. TREES-plus, the company's initial product became the programming language for the advanced scheduling environment system.

Source record↗

Simulation Training Versus Real Time Console Training for New Flight Controllers

For new flight controllers, the two main learning tools are simulations and real time console performance training. These benefit the new flight controllers in different ways and could possibly be improved. Simulations: a) Allow for mistakes without serious consequences. b) Lets new flight controllers learn the working style of other new flight controllers. c) Lets new flight controllers eventually begin to feel like they have mastered the sim world, so therefore they must be competent in the real time world too. Real time: a) Shows new flight controllers some of the unique problems that develop and have to be accounted for when dealing with certain payloads or systems. b) Lets new flight controllers experience handovers - gathering information from the previous shift on what the room needs to be aware of and what still needs to be done. c) Gives new flight controllers confidence that they can succeed in the position they are training for when they can solve real anomalies. How Sims could be improved and more like real-time ops for the ISS Operations Controller position: a) Operations Change Requests to review. b) Fewer anomalies (but still more than real time for practice). c) Payload Planning Manager Handover sheet for the E-1 and E-3 reviews. d) Flight note in system with at least one comment to verify for the E-1 and E-3 reviews How the real time console performance training could be improved for the ISS Operations Controller position: a) Schedule the new flight controller to be on console for four days but with a different certified person each day. This will force them to be the source of knowledge about every OCR in progress, everything that has happened in those few days, and every activity on the timeline. Constellation program flight controllers will have to learn entirely from simulations, thereby losing some of the elements that they will need to have experience with for real time ops. It may help them to practice real time console performance training in the International Space Station or Space Shuttle to gather some general anomaly resolution and day-to-day task management skills.

Heaton, Amanda↗

Emergency medicine and the airline passenger

Problems related to immediate medical care in case of in-flight emergencies are discussed with reference to such critical types of medical emergencies as obstructed airway, cardiac dysfunction, trauma, hemorrhage, hypoxia, and pain. It is shown that training flight attendants to deal with in-flight medical emergencies and to use first-aid support equipment and essential and useful drugs may later help with stabilization of a victim and allow continuing the flight to the scheduled destination without the need for a diverted landing. Among the steps suggested in order to upgrade inflight welfare and safety of passengers are the development of an advisory circular by the FAA covering standardized training for flight attendants, regulatory action requiring upgrading of the present rudimentary first-aid kit, and the enactment of Good Samaritan legislation by the U.S. Government.

Mohler, S. R.↗

Schedule Factors Associated with the Use of Controlled Rest in a Long-Haul Airline

Controlled Rest (CR) refers to a short, voluntary nap opportunity taken by pilots on the flight deck as a countermeasure to unanticipated sleepiness in flight. This study explores the profile of CR use in a long-haul commercial airline. Forty-four pilots wore actiwatches and filled in an application-based sleep/work diary for approximately 2 weeks. After merging sleep diary, actigraphy, and schedule data, complete records were analyzed from 240 flights. Sleep was estimated during CR intervals using the Philips Actiware 6.0.9 (Bend, OR) software with wake threshold set to medium. Timing of sleep periods and flight schedules were analyzed relative to home-base time. A mixed-effects binary logistics regression was used to analyze the impact of schedule factors on CR. Preliminary analyses revealed that CR was taken on 45% (n=107) of flights. Average sleep duration within these rest periods was estimated as 24.8 ± 16.1 minutes. CR was more frequent on return flights (arriving at home-base; 58%, n=69) vs. outbound flights (departing from home-base, 31%, n=38; p<0.001). There was no difference for direction of travel (eastbound: 49%, n= 56; westbound: 40%, n= 44; northbound/southbound: 50%, n=7; p=0.272). CR was more frequent on 2-pilot flights (62%, n=81) compared to augmented crew flights (24%, n=26; p<0.001). Of note, 21% (n=23) of augmented flights contained both CR and Bunk Rest. CR was more frequent on flights <10h duration (<10h: 59%, n=78; >10h: 27%, n=29; p<0.001). Flights departing between 12:00h-19:59h (25%, n=23; p<0.026) had the lowest frequency of CR. Data from this airline show that CR is most commonly used as a countermeasure to sleepiness on return, unaugmented, <10h duration, and nighttime flights. The direction of travel did not influence the use of CR. Future studies are required to determine generalizability of these results to other airlines.

Hilditch, Cassie↗

Space Technology Demonstrations Using Low Cost, Short-Schedule Airborne and Range Facilities at the Dryden Flight Research Center

There is a national effort to expedite advanced space technologies on new space systems for both government and commercial applications. In order to lower risk, these technologies should be demonstrated in a relevant environment before being installed in new space systems. This presentation introduces several low cost, short schedule space technology demonstrations using airborne and range facilities available at the Dryden Flight Research Center.

Carter, John↗

Piloted-simulation evaluation of escape guidance for microburst wind shear encounters

Numerous air carrier accidents and incidents result from encounters with the atmospheric wind shear associated with microburst phenomena, in some cases resulting in heavy loss of life. An important issue in current wind shear research is how to best manage aircraft performance during an inadvertent wind shear encounter. The goals of this study were to: (1) develop techniques and guidance for maximizing an aircraft's ability to recover from microburst encounters following takeoff, (2) develop an understanding of how theoretical predictions of wind shear recovery performance might be achieved in actual use, and (3) gain insight into the piloting factors associated with recovery from microburst encounters. Three recovery strategies were implemented and tested in piloted simulation. Results show that a recovery strategy based on flying a flight path angle schedule produces improved performance over constant pitch attitude or acceleration-based recovery techniques. The best recovery technique was initially counterintuitive to the pilots who participated in the study. Evidence was found to indicate that the techniques required for flight through the turbulent vortex of a microburst may differ from the techniques being developed using classical, nonturbulent microburst models.

Hinton, David A.↗

Simulation-to-Flight 1 (STF-1): Automating the Planning, Scheduling, Assessment and Data Processing/Reduction for a Small Satellite

On December 16, 2019, a 3-U CubeSat named STF-1 launched as West Virginia's first spacecraft. This event marked the culmination of a run-up to launch involving the production of the spacecraft, creation/configuration of command and control infrastructure, and the evolution of its co-creation, the NASA Operational Simulator for Small Satellites (NOS3). This event also marked the beginning of a new phase: operations. While plans, procedures, and infrastructure were already in place or started for operations, many lessons were learned during the operations phase, especially during early operations (first month/commissioning phase). Additional plans, procedures, and infrastructure, especially related to communication planning and automated data processing, were created and developed to fill needs for the operation of the STF-1 mission.This paper and presentation will overview the STF-1 operations team's solutions to addressing the many needs of operating a low-earth orbiting CubeSat mission with a single ground antenna that is shared and scheduled with several other missions. The STF-1 operations team deployed a combination of virtualization technologies, ground station technology solutions, collaboration software, custom planning software solutions, and existing ground antenna scheduling solutions to create an effective and efficient CubeSat operations environment. The end-solution satisfied the operations stakeholders, which include NASA, its industry partner TMC Technologies, and four independent professor-student teams at West Virginia University.

CubeSat↗

Flight-Deck Strategies and Outcomes When Flying Schedule-Matching Descents

Recent studies at NASA Ames Research Center have investigated the development and use of ground-based (air traffic controller) tools to manage and schedule air traffic in future terminal airspace. An exploratory study was undertaken to investigate the impacts that such tools (and concepts) could have on the flight-deck. Ten Boeing 747-400 crews flew eight optimized profile descents in the Los Angeles terminal airspace, while receiving scripted current day and futuristic speed clearances, to ascertain their ability to fly schedulematching descents without prior training. Although the study was exploratory in nature, four variables were manipulated: route constraints, winds, speed changes, and clearance phraseology. Despite flying the same scenarios with the same events and timing, there were significant differences in the time it took crews to fly the approaches. This variation is the product of a number of factors but highlights potential difficulties for scheduling tools that would have to accommodate this amount of natural variation in descent times. The focus of this paper is the examination of the crews' aircraft management strategies and outcomes. This includes potentially problematic human-automation interaction issues that may negatively impact arrival times, speed and altitude constraint compliance, and energy management efficiency.

Flight Management System↗

X-31 Mishap: Lessons Learned

The experimental X-31 High Angle of Attack Research Aircraft crashed during a 1995 test mission flight conducted by NASA at Edwards Air Force Base, California. The pilot lost control of the airplane and was forced to eject, sustaining a permanent back injury that ended his flying career. Prior to this incident the airplane had a perfect record of several hundred non-eventful flights supported by an experienced team. During the subsequent investigation by a mishap committee it was discovered that a series of cascading events contributed to this accident. Some of the identified contributing factors that resulted in this mishap are common to aircraft design and to flight-test in general. The mistakes and the solutions are presented here so that the flight-test community may consider and learn from them. The primary cause of the crash was icing and, ultimately, a complete blockage of the pitot-static nose probe. The icing was caused by a freak weather phenomenon that was neither expected nor known to exist on the day of the mishap. The normal probe had been replaced with a special Kiel probe to allow total pressure measurements of up to 70 degrees angle of attack for flight-test purposes. The Kiel probe did not include a heater, because it was assumed that the airplane would not be flown in the clouds or in conditions conducive to icing. This assumption was later proven to be incorrect. The iced Kiel probe caused incorrect gain scheduling in the flight control system, resulting in an unstable aircraft. This failure was essentially undetected because of a faulty design in the flight control system architecture. There were, however, also a number of other issues that lead up to this situation that never should have happened. This presentation discusses what the issues were that contributed to the incident. After the incident was investigated, some of these issues were addressed and some changes were made. The second X-31 aircraft flew the remainder of the flight tests, and the program was successfully completed without incident. This presentation also shows a video of the mishap including lessons learned, and the changes that were made to resume the flight-test program are presented.

Larson, Richard R.↗

NASA Ares I Crew Launch Vehicle Upper Stage Overview

By incorporating rigorous engineering practices, innovative manufacturing processes and test techniques, a unique multi-center government/contractor partnership, and a clean-sheet design developed around the primary requirements for the International Space Station (ISS) and Lunar missions, the Upper Stage Element of NASA's Crew Launch Vehicle (CLV), the "Ares I," is a vital part of the Constellation Program's transportation system. Constellation's exploration missions will include Ares I and Ares V launch vehicles required to place crew and cargo in low-Earth orbit (LEO), crew and cargo transportation systems required for human space travel, and transportation systems and scientific equipment required for human exploration of the Moon and Mars. Early Ares I configurations will support ISS re-supply missions. A self-supporting cylindrical structure, the Ares I Upper Stage will be approximately 84' long and 18' in diameter. The Upper Stage Element is being designed for increased supportability and increased reliability to meet human-rating requirements imposed by NASA standards. The design also incorporates state-of-the-art materials, hardware, design, and integrated logistics planning, thus facilitating a supportable, reliable, and operable system. With NASA retiring the Space Shuttle fleet in 2010, the success of the Ares I Project is essential to America's continued leadership in space. The first Ares I test flight, called Ares I-X, is scheduled for 2009. Subsequent test flights will continue thereafter, with the first crewed flight of the Crew Exploration Vehicle (CEV), "Orion," planned for no later than 2015. Crew transportation to the ISS will follow within the same decade, and the first Lunar excursion is scheduled for the 2020 timeframe.

McArthur, J. Craig↗

A Method for Integrating Thrust-Vectoring and Actuated Forebody Strakes with Conventional Aerodynamic Controls on a High-Performance Fighter Airplane

A method, called pseudo controls, of integrating several airplane controls to achieve cooperative operation is presented. The method eliminates conflicting control motions, minimizes the number of feedback control gains, and reduces the complication of feedback gain schedules. The method is applied to the lateral/directional controls of a modified high-performance airplane. The airplane has a conventional set of aerodynamic controls, an experimental set of thrust-vectoring controls, and an experimental set of actuated forebody strakes. The experimental controls give the airplane additional control power for enhanced stability and maneuvering capabilities while flying over an expanded envelope, especially at high angles of attack. The flight controls are scheduled to generate independent body-axis control moments. These control moments are coordinated to produce stability-axis angular accelerations. Inertial coupling moments are compensated. Thrust-vectoring controls are engaged according to their effectiveness relative to that of the aerodynamic controls. Vane-relief logic removes steady and slowly varying commands from the thrust-vectoring controls to alleviate heating of the thrust turning devices. The actuated forebody strakes are engaged at high angles of attack. This report presents the forward-loop elements of a flight control system that positions the flight controls according to the desired stability-axis accelerations. This report does not include the generation of the required angular acceleration commands by means of pilot controls or the feedback of sensed airplane motions.

Lallman, Frederick J.↗

Detailed Skylab ECS consumables analysis for the interim revision flight plan (November, 1972, SL-1 launch)

The consumables analysis was performed for the Skylab 2, 3, and 4 Preliminary Reference Interim Revision Flight Plan. The analysis and the results are based on the mission requirements as specified in the flight plan and on other available data. The results indicate that the consumables requirements for the Skylab missions allow for remaining margins (percent) of oxygen, nitrogen, and water nominal as follows: 83.5, 90.8, and 88.7 for mission SL-2; 57.1, 64.1, and 67.3 for SL-3; and 30.8, 44.3, and 46.5 for SL-4. Performance of experiment M509 as scheduled in the flight plan results in venting overboard the cluster atmosphere. This is due to the addition of nitrogen for propulsion and to the additional oxygen introduced into the cabin when the experiment is performed with the crewman suited.

Wells, C.↗

Testing and Development of NEA Scout Solar Sail Deployer Mechanism

The Near Earth Asteroid (NEA) Scout is a deep space CubeSat designed to use an 86 square meter solar sail to navigate to a near earth asteroid called VG 1991. The solar sail deployment mechanism aboard NEA Scout has gone through numerous design cycles and ground tests since its conception in 2014. An engineering development unit (EDU) was constructed in the spring of 2016 and since then, the NEA Scout team has completed numerous ground deployments aiming to mature the deployment system and the ground test methods used to validate that system. Testing a large, non-rigid gossamer system in 1G environments has presented its difficulties to numerous solar sailing programs before, but NEA Scout’s size, sail configuration, and budget has led the team to develop new deployment techniques and uncover new practices while improving their test methods. NEA Scout’s spooled sail and boom design differs from any solar sail design to date: a single square sail membrane spooled upon a non-circular mandrel and the booms are spooled on two separate coils. This configuration was necessitated by the 6U footprint and is not common among other solar sailing missions. The program has planned and completed 3 separate full scale sail deployments to date, with a flight sail deployment test scheduled for FY18. The sail deployment tests have helped mature flight operations plans and developed preliminary off-nominal deployment mitigation strategies. The paper entitled “Design and Development of NEA Scout Solar Sail Deployer Mechanism” was presented at the 43rd Aerospace Mechanisms Symposium. Since then, the system has matured and completed ascent vent, random vibration, boom deployment and sail deployment tests. This paper will discuss the lessons learned and advancements made while working on solar sail testing and redesign cycles.

Few, Alex↗

Management by Trajectory: Improving Predictability for Airspace Operations

In the present-day National Airspace System, the air traffic management system attempts to predict the trajectory for each flight based on the flight plan and scheduled or controlled departure time. However, gaps in trajectory data and models, coupled with tactical control actions that are not communicated to automation systems or other stakeholders, lead to trajectory predictions that are less accurate than they could be. This affects traffic flow management performance. Management by Trajectory (MBT) is a NASA concept for air traffic management in which every flight operates in accordance with a 4D trajectory that is negotiated between the airspace user and the FAA to account for the airspace user’s goals while complying with NAS constraints. The primary benefit of MBT is an improvement in system performance due to increased trajectory predictability and stability, which result from managing traffic in all four dimensions (2D route, vertical, and time), ensuring that changes to the flight’s trajectory are incorporated into the assigned trajectory, and utilizing improved time or arrival control standards. Importantly, the performance improvements support increasing efficiency without increasing collision risk. This paper provides an overview of MBT and describes fast-time simulation results evaluating the safety, performance, and efficiency effects of MBT.

Fernandes, Alicia B.↗

Concept of Operations for Management by Trajectory

This document describes Management by Trajectory (MBT), a concept for future air traffic management (ATM) in which every flight operates in accordance with a four-dimensional trajectory (4DT) that is negotiated between the airspace user and the Federal Aviation Administration (FAA) to respect the airspace user's goals while complying with National Airspace System (NAS) constraints. In the present-day NAS, the ATM system attempts to predict the trajectory for each flight based on the approved flight plan and scheduled or controlled departure time. However, once the aircraft starts to move, controllers tactically manage the aircraft to implement traffic management restrictions, separate otherwise conflicting aircraft, and address arising NAS constraints. Tactical controller actions are not directly communicated to the automation systems or other stakeholders. Furthermore, the initial trajectory prediction does not anticipate these disruptions or how they will impact the flight. Consequently, and compounded by gaps in required data and models, trajectory predictions are less accurate than possible, which affects Traffic Flow Management (TFM) performance. A cornerstone of the MBT concept is that all air vehicles have, at all times, an assigned 4DT from their current state to their destination. These assigned trajectories consist of trajectory constraints and descriptions. Pilots and air traffic controllers, with the aid of automation, operate the aircraft to comply with the assigned trajectory, unless first negotiating a revision. Equipped aircraft have substantial responsibility for complying with the assigned trajectory without controller intervention. To maximize the operational flexibility available to the airspace user, the assigned trajectory only imposes trajectory constraints as required to achieve the ATM goals of NAS constraint compliance and aircraft separation. Trajectory descriptions are added to the assigned trajectory to ensure sufficient predictability. To further improve trajectory prediction accuracy, airspace users supplement the assigned trajectory by broadcasting intent information and updating it as necessary. Air vehicle intent is a more detailed description of the airspace user's plan for how the flight will fly the assigned trajectory. Air vehicle intent can change freely, without negotiation, as long as it remains in compliance with the assigned trajectory. Aircraft assigned trajectories, air vehicle intent, and predicted trajectories are shared, creating a common view among stakeholders. A NAS Constraint Service gathers and publishes information about all known NAS constraints, enabling airspace users to be informed participants in trajectory negotiation. Trajectory constraints in the assigned trajectory are mapped to NAS constraints to facilitate identifying which aircraft are affected when NAS constraints change. To support efficient trajectory negotiation, all aircraft provide current information about air vehicle capabilities. Assigned trajectories are constructed to satisfy all known NAS constraints, improving trajectory stability and predictability. Uncertainty and disruptions are handled by modifying the assigned trajectory as far in advance as possible. By proactively negotiating changes to the assigned trajectory, rather than relying on controller-selected tactical actions such as vectors to resolve traffic conflicts or implement miles-in-trail restrictions, MBT keeps aircraft on closed trajectories that are fully known to all stakeholders. Since reactive air traffic control actions cannot be predicted in advance, the downstream trajectory cannot be accurately predicted until they happen. Reliable trajectory predictions allow the system to identify needed modifications to trajectories further in advance, where they can be negotiated and communicated as amendments (i.e., additional or altered trajectory constraints) to the assigned trajectory. Decision Support Tools (DSTs) aid controllers in rapidly defining and communicating closed trajectories to the aircraft and support all stakeholders in trajectory negotiation. Anticipated MBT benefit mechanisms include more accurate trajectory predictions, improved ATM performance and robustness to off-nominal conditions, increased flexibility and operational efficiency, reduced impediments to emerging classes of airspace users accessing NAS resources, reduced environmental impacts, and enhanced safety.

ConOps↗

Solar Dynamics Observatory On-Orbit Jitter Testing, Analysis, and Mitigation Plans

The Solar Dynamics Observatory (SDO) was designed to understand the Sun and the Sun s influence on Earth. SDO was launched on February 11, 2010 carrying three scientific instruments: the Atmospheric Imaging Assembly (AIA), the Helioseismic and Magnetic Imager (HMI), and the Extreme Ultraviolet Variability Experiment (EVE). Both AIA and HMI are sensitive to high frequency pointing perturbations and have sub-arcsecond level line-of-sight (LOS) jitter requirements. Extensive modeling and analysis efforts were directed in estimating the amount of jitter disturbing the science instruments. To verify the disturbance models and to validate the jitter performance prior to launch, many jitter-critical components and subassemblies were tested either by the mechanism vendors or at the NASA Goddard Space Flight Center (GSFC). Although detailed analysis and assembly level tests were performed to obtain good jitter predictions, there were still several sources of uncertainties in the system. The structural finite element model did not have all the modes correlated to test data at high frequencies (greater than 50 Hz). The performance of the instrument stabilization system was not known exactly but was expected to be close to the analytical model. A true disturbance-to-LOS observatory level test was not available due to the tight schedule of the flight spacecraft, the cost in time and manpower, difficulties in creating gravity negation systems, and risks of damaging flight hardware. To protect the observatory jitter performance against model uncertainties, the SDO jitter team devised several on-orbit jitter reduction plans in addition to reserve margins on analysis results. Since some of these plans severely restricted the capabilities of several spacecraft components (e.g. wheels and High Gain Antennas), the SDO team performed on-orbit jitter tests to determine which jitter reduction plans, if any, were necessary to satisfy science LOS jitter requirements. The SDO on-orbit jitter tests were designed to satisfy the following four objectives: 1. Determine the acceptable reaction wheel operational speed range during Science Mode. 2. Determine HGA algorithm jitter parameters (number of stagger steps and enable/disable no-steprequests). 3. Determine acceptable EVE instrument filter wheels spin rates. 4. Determine if AIA instrument filter wheels excite the first AIA telescope structural mode. This paper provides detailed information on the SDO wheel jitter test plan, shows on-orbit jitter measurements and how ground predictions compare to those measurements, and describes the final jitter mitigation plan executed on SDO.

Liu, Kuo-Chia (Alice)↗

The Solar Array Module Plasma Interactions Experiment (SAMPIE): A shuttle-based plasma interaction experiment

The SAMPIE flight experiment, tentatively scheduled to fly on a shuttle mission in mid 1992, will investigate plasma interactions of high voltage space power systems. Solar cells representing a number of technologies will be biased to high voltage to study both negative potential arching and positive potential current collection characteristics. Additionally, several idealized metal/insulator mockups will be flown to study the basic nature of these interactions. Described here is the basic rationale for a space experiment as well as the measurements to be made and the significance of the expected results. The current design status of the flight hardware is presented.

Hillard, G. Barry↗