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 55 records · Page 3

Fe3: An Evaluation Tool for Low-Altitude Air Traffic Operations

The concepts of unmanned aircraft system traffic management (UTM) and urban air mobility (UAM) are introducing high-density operations in low altitude airspace in closer proximity to populated areas than conventional high-altitude air traffic. The Flexible engine for Fast-time Evaluation of Flight Environments (Fe (sup 3)) provides the capability of statistically analyzing the high-density, high-fidelity, and low-altitude traffic system under numerous scenarios, such that stake holders can study impacts of factors in the low-altitude high-density traffic system and define requirements, policies, and protocols needed to support a safe yet efficient traffic system, and even assess operational risks and optimize flight schedules without conducting infeasible and cost-prohibitive flight tests that involve a large volume of aerial vehicles. This work provides an introduction to this simulation tool including its architecture and various models involved. Its performance and sample application in UAM and UTM are also presented.

Trajectory Modeling↗

X-33 Ascent Flight Controller Design by Trajectory Linearization: A Singular Perturbational Approach

The flight control of X-33 poses a challenge to conventional gain-scheduled flight controllers due to its large attitude maneuvers from liftoff to orbit and reentry. In addition, a wide range of uncertainties in vehicle handling qualities and disturbances must be accommodated by the attitude control system. Nonlinear tracking and decoupling control by trajectory linearization can be viewed as the ideal gain-scheduling controller designed at every point on the flight trajectory. Therefore it provides robust stability and performance at all stages of flight without interpolation of controller gains and eliminates costly controller redesigns due to minor airframe alteration or mission reconfiguration. In this paper, a prototype trajectory linearization design for an X-33 ascent flight controller is presented along with 3-DOF and 6-DOF simulation results. It is noted that the 6-DOF results were obtained from the 3-DOF design with only a few hours of tuning, which demonstrates the inherent robustness of the design technique. It is this "plug-and-play" feature that is much needed by NASA for the development, test and routine operations of the RLV'S. Plans for further research are also presented, and refined 6-DOF simulation results will be presented in the final version of the paper.

Zhu, J. Jim↗

X-33 Ascent Flight Controller Design by Trajectory Linearization: A Singular Perturbational Approach

The flight control of X-33 poses a challenge to conventional gain-scheduled flight controllers due to its large attitude maneuvers from liftoff to orbit and reentry. In addition, a wide range of uncertainties in vehicle handling qualities and disturbances must be accommodated by the attitude control system. Nonlinear tracking and decoupling control by trajectory linearization can be viewed as the ideal gain-scheduling controller designed at every point on the flight trajectory. Therefore it provides robust stability and performance at all stages of flight without interpolation of controller gains, and eliminates costly controller redesigns due to minor airframe alteration or mission reconfiguration. A prototype trajectory linearization design for X-33 ascent flight controller was designed and tested with 3-DOF and 6-DOF simulations during the 10 weeks SFFP. It is noted that the 6-DOF results were obtained from the 3-DOF design with only a few hours of tuning, which demonstrates the inherent robustness of the design technique. It is this "plug-and-play" feature that is much needed by NASA for the development, test and routine operations of the RLVs. Plans for further research are also presented.

Zhu, J. Jim↗

Ride quality assessment. III - Questionnaire results of a second flight programme

A questionnaire was completed by 861 passengers on regularly-scheduled flights of four commuter airlines. Four types of aircraft were involved. Questions assessed major demographic variables, attitudes toward flying, frequency of flying, experience of airsickness, and passenger perceptions of detailed aspects of the physical environment. Passengers also rated their overall comfort level and their willingness to fly again. Passengers perceive motion, noise, and seat factors as the primary determinants of their comfort. Rated comfort is strongly related to willingness to fly again. Incidence of airsickness was low. Sex differences in reactions to aspects of the environment were found.

Richards, L. G.↗

DORCA 2 computer program. Volume 1: User's guide

The Dynamic Operational Requirements and Cost Analysis Program (DORCA 2) is described. The computer program provides a top level analysis tool for NASA and relies on a man machine interaction to optimize results based on external criteria. The computer program relies heavily on outside sources to provide cost information and vehicle parameters. Given data describing mission, vehicles, payloads, containers, space facilities, schedules, cost values, and costing procedures, the program computes flight schedules, cargo manifests, vehicle fleet requirements, acquisition schedules, and cost summaries. The program is designed to consider earth orbit, lunar, interplanetary, and automated satellite missions.

Wray, S. T., Jr.↗

DORCA computer program. Volume 1: User's guide

The Dynamic Operational Requirements and Cost Analysis Program (DORCA) was written to provide a top level analysis tool for NASA. DORCA relies on a man-machine interaction to optimize results based on external criteria. DORCA relies heavily on outside sources to provide cost information and vehicle performance parameters as the program does not determine these quantities but rather uses them. Given data describing missions, vehicles, payloads, containers, space facilities, schedules, cost values and costing procedures, the program computes flight schedules, cargo manifests, vehicle fleet requirements, acquisition schedules and cost summaries. The program is designed to consider the Earth Orbit, Lunar, Interplanetary and Automated Satellite Programs. A general outline of the capabilities of the program are provided.

Wray, S. T., Jr.↗

Analysis of Factors for Incorporating User Preferences in Air Traffic Management: A system Perspective

This paper presents an analysis of factors that impact user flight schedules during air traffic congestion. In pre-departure flight planning, users file one route per flight, which often leads to increased delays, inefficient airspace utilization, and exclusion of user flight preferences. In this paper, first the idea of filing alternate routes and providing priorities on each of those routes is introduced. Then, the impact of varying planning interval and system imposed departure delay increment is discussed. The metrics of total delay and equity are used for analyzing the impact of these factors on increased traffic and on different users. The results are shown for four cases, with and without the optional routes and priority assignments. Results demonstrate that adding priorities to optional routes further improves system performance compared to filing one route per flight and using first-come first-served scheme. It was also observed that a two-hour planning interval with a five-minute system imposed departure delay increment results in highest delay reduction. The trend holds for a scenario with increased traffic.

Sheth, Kapil S.↗

Optimal Time Advance In Terminal Area Arrivals: Throughput vs. Fuel Savings

The current operational practice in scheduling air traffic arriving at an airport is to adjust flight schedules by delay, i.e. a postponement of an aircrafts arrival at a scheduled location, to manage safely the FAA-mandated separation constraints between aircraft. To meet the observed and forecast growth in traffic demand, however, the practice of time advance (speeding up an aircraft toward a scheduled location) is envisioned for future operations as a practice additional to delay. Time advance has two potential advantages. The first is the capability to minimize, or at least reduce, the excess separation (the distances between pairs of aircraft immediately in-trail) and thereby to increase the throughput of the arriving traffic. The second is to reduce the total traffic delay when the traffic sample is below saturation density. A cost associated with time advance is the fuel expenditure required by an aircraft to speed up. We present an optimal control model of air traffic arriving in a terminal area and solve it using the Pontryagin Maximum Principle. The admissible controls allow time advance, as well as delay, some of the way. The cost function reflects the trade-off between minimizing two competing objectives: excess separation (negatively correlated with throughput) and fuel burn. A number of instances are solved using three different methods, to demonstrate consistency of solutions.

Sadovsky, Alexander V .↗

Near Earth Asteroid Scout Solar Sail Engineering Development Unit Test Suite

The Near Earth Asteroid (NEA) Scout project is a 6U reconnaissance mission to investigate a near Earth asteroid utilizing an 86m(sub 2) solar sail as the primary propulsion system. This will be the largest solar sail NASA has launched to date. NEA Scout is currently manifested on the maiden voyage of the Space Launch System in 2018. In development of the solar sail subsystem, design challenges were identified and investigated for packaging within a 6U form factor and deployment in cis-lunar space. Analysis was able to capture understanding of thermal, stress, and dynamics of the stowed system as well as mature an integrated sail membrane model for deployed flight dynamics. Full scale system testing on the ground is the optimal way to demonstrate system robustness, repeatability, and overall performance on a compressed flight schedule. To physically test the system, the team developed a flight sized engineering development unit with design features as close to flight as possible. The test suite included ascent vent, random vibration, functional deployments, thermal vacuum, and full sail deployments. All of these tests contributed towards development of the final flight unit. This paper will address several of the design challenges and lessons learned from the NEA Scout solar sail subsystem engineering development unit. Testing on the component level all the way to the integrated subsystem level. From optical properties of the sail material to fold and spooling the single sail, the team has developed a robust deployment system for the solar sail. The team completed several deployments of the sail system in preparation for flight at half scale (4m) and full scale (6.8m): boom only, half scale sail deployment, and full scale sail deployment. This paper will also address expected and received test results from ascent vent, random vibration, and deployment tests.

Lockett, Tiffany Russell↗

Sliding Mode Control of the X-33 with an Engine Failure

Ascent flight control of the X-3 is performed using two XRS-2200 linear aerospike engines. in addition to aerosurfaces. The baseline control algorithms are PID with gain scheduling. Flight control using an innovative method. Sliding Mode Control. is presented for nominal and engine failed modes of flight. An easy to implement, robust controller. requiring no reconfiguration or gain scheduling is demonstrated through high fidelity flight simulations. The proposed sliding mode controller utilizes a two-loop structure and provides robust. de-coupled tracking of both orientation angle command profiles and angular rate command profiles in the presence of engine failure, bounded external disturbances (wind gusts) and uncertain matrix of inertia. Sliding mode control causes the angular rate and orientation angle tracking error dynamics to be constrained to linear, de-coupled, homogeneous, and vector valued differential equations with desired eigenvalues. Conditions that restrict engine failures to robustness domain of the sliding mode controller are derived. Overall stability of a two-loop flight control system is assessed. Simulation results show that the designed controller provides robust, accurate, de-coupled tracking of the orientation angle command profiles in the presence of external disturbances and vehicle inertia uncertainties, as well as the single engine failed case. The designed robust controller will significantly reduce the time and cost associated with flying new trajectory profiles or orbits, with new payloads, and with modified vehicles

Shtessel, Yuri B.↗

A Method for Forecasting the Commercial Air Traffic Schedule in the Future

This report presents an integrated set of models that forecasts air carriers' future operations when delays due to limited terminal-area capacity are considered. This report models the industry as a whole, avoiding unnecessary details of competition among the carriers. To develop the schedule outputs, we first present a model to forecast the unconstrained flight schedules in the future, based on the assumption of rational behavior of the carriers. Then we develop a method to modify the unconstrained schedules, accounting for effects of congestion due to limited NAS capacities. Our underlying assumption is that carriers will modify their operations to keep mean delays within certain limits. We estimate values for those limits from changes in planned block times reflected in the OAG. Our method for modifying schedules takes many means of reducing the delays into considerations, albeit some of them indirectly. The direct actions include depeaking, operating in off-hours, and reducing hub airports'operations. Indirect actions include using secondary airports, using larger aircraft, and selecting new hub airports, which, we assume, have already been modeled in the FAA's TAF. Users of our suite of models can substitute an alternative forecast for the TAF.

Long, Dou↗

Shuttle spacelab simulation using a Lear jet aircraft: Mission no. 3 (ASSESS program)

The third ASSESS mission using a Lear Jet aircraft conducted to continue the study of scientific experiment operations in a simulated Spacelab environment. Prior to the mission, research planning and equipment preparation were observed and documented. A flight readiness review for the experiment was conducted. Nine of the ten scheduled flights were completed during simulation mission and all major science objectives were accomplished. The equipment was well qualified for flight and gave little trouble; telescope malfunctions occurred early in the mission and were corrected. Both real-time and post-observation data evaluation were used to assess research progress and to plan subsequent flight observations for maximum effectiveness.

Reller, J. O., Jr.↗

An aircraft noise study in Norway

An extensive study of aircraft noise is currently being conducted in Oslo, Norway. The traffic at Oslo Airport Fornebu that includes both national and international flights, totals approximately 350 movements per day: 250 of these are regular scheduled flights with intermediate and large size aircraft, the bulk being DC9 and Boeing 737. The total traffic during the summer of 1989 was expected to resemble the maximum level to which the regular traffic will increase before the new airport can be put into operation. The situation therefore represented a possibility to study the noise impact on the communities around Fornebu. A comprehensive social survey was designed, including questions on both aircraft and road traffic noise. A random sample of 1650 respondents in 15 study areas were contacted for an interview. These areas represent different noise levels and different locations relative to the flight paths. The interviews were conducted in a 2 week period just prior to the transfer of charter traffic from Gardemoen to Fornebu. In the same period the aircraft noise was monitored in all 15 areas. In addition the airport is equipped with a permanent flight track and noise monitoring system. The noise situation both in the study period and on an average basis can therefore be accurately described. In August a group of 1800 new respondents were subjected to identical interviews in the same 15 areas, and the noise measurement program was repeated. Results of the study are discussed.

Gjestland, Truls T.↗

Mitigating fatigue on the flight deck: how is controlled rest used in practice?

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 resulting in complete records from 239 flights. Timing of sleep periods and flight schedules were analyzed relative to home-base time. Pearson correlations were used to assess the influence of pilot demographics on CR use. A mixed-effects logistic regression was used to analyze the impact of schedule factors on CR. CR was taken on 46% (n=110) of flights, with 80% (n=106/133) of all CR attempts estimated by actigraphy to have successfully achieved sleep. Average sleep duration during successful rest periods was estimated as 31.7 ± 12.2 minutes. CR was more frequent on return (60%, n=71) vs. outbound flights (33%, n=39); 2-pilot (69%, n=83) vs. >2-pilot flights (23%, n=27); <10h (63%, n=80) vs. >10h duration flights (27%, n=30); and night (55%, n=76) vs. day flights (34%, n=34) (all p≤0.001). There was no significant difference for direction of travel (eastbound: 51%, n= 57; westbound: 40%, n= 44; p=0.059). Of note, 22% (n=26) of augmented flights contained both CR and bunk rest. Data from this airline show that CR is most commonly used as a countermeasure to sleepiness on flights <10h duration (2-pilot crews) and home-base nighttime flights. Future studies are required to determine the generalizability of these results to other airlines.

sleepiness↗

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↗

Future ATM Concepts Evaluation Tool (FACET) Interface Control Document

This Interface Control Document (ICD) documents the airspace adaptation and air traffic inputs of NASA's Future ATM Concepts and Evaluation Tool (FACET). Its intended audience is the project manager, project team, development team, and stakeholders interested in interfacing with the system. FACET equips Air Traffic Management (ATM) researchers and service providers with a way to explore, develop and evaluate advanced air transportation concepts before they are field-tested and eventually deployed. FACET is a flexible software tool that is capable of quickly generating and analyzing thousands of aircraft trajectories. It provides researchers with a simulation environment for preliminary testing of advanced ATM concepts. Using aircraft performance profiles, airspace models, weather data, and flight schedules, the tool models trajectories for the climb, cruise, and descent phases of flight for each type of aircraft. An advanced graphical interface displays traffic patterns in two and three dimensions, under various current and projected conditions for specific airspace regions or over the entire continental United States. The system is able to simulate a full day's dynamic national airspace system (NAS) operations, model system uncertainty, measure the impact of different decision-makers in the NAS, and provide analysis of the results in graphical form, including sector, airport, fix, and airway usage statistics. NASA researchers test and analyze the system-wide impact of new traffic flow management algorithms under anticipated air traffic growth projections on the nation's air traffic system. In addition to modeling the airspace system for NASA research, FACET has also successfully transitioned into a valuable tool for operational use. Federal Aviation Administration (FAA) traffic flow managers and commercial airline dispatchers have used FACET technology for real-time operations planning. FACET integrates live air traffic data from FAA radar systems and weather data from the National Weather Service to summarize NAS performance. This information allows system operators to reroute flights around congested airspace and severe weather to maintain safety and minimize delay. FACET also supports the planning and post-operational evaluation of reroute strategies at the national level to maximize system efficiency. For the commercial airline passenger, strategic planning with FACET can result in fewer flight delays and cancellations. The performance capabilities of FACET are largely due to its architecture, which strikes a balance between flexibility and fidelity. FACET is capable of modeling the airspace operations for the continental United States, processing thousands of aircraft on a single computer. FACET was written in Java and C, enabling the portability of its software to a variety of operating systems. In addition, FACET was designed with a modular software architecture to facilitate rapid prototyping of diverse ATM concepts. Several advanced ATM concepts have already been implemented in FACET, including aircraft self-separation, prediction of aircraft demand and sector congestion, system-wide impact assessment of traffic flow management constraints, and wind-optimal routing.

FACET↗

Space Flight Handbooks. Volume 3- Planetary Flight Handbook: Supplementary Trajectory Data: Venus to Earth and Mars to Earth - Part 2

Parts 2 and 3 present tabulations of trajectory data for scheduling flights to and from Venus and Mars during the period 1960-2000. Part 2 contains information for outbound flights to these planets; Part 3 contains information for trajectories returning from the planets to Earth. Each Part contains data for single-plane transfers, as well as for broken-plane transfers which employ a midcourse plane-change to eliminate the high speed "ridges." The mathematical analyses employed for all calculations are described in Part 1 of this handbook. To facilitate the construction of round-trip trajectories, the date at the target planet is held fixed while the trip duration is varied in 10-day increments from zero days to the length of that planet's synodic period with Earth. Dates of arrival at the target planet are presented in the extreme right-hand column of Part 2, and dates of departure from the target planet are presented in the extreme left-hand column of Part 3. Thus, by holding Part 2 directly to the left of Part 3, the analyst may easily and rapidly scan all trip possibilities which involve any desired stopover time at the target planet. Within approximately 200 days of each conjunction or opposition, data are presented in 10-day increments at the target planet. Only those trips are listed for which the hyperbolic excess speeds at either or both ends of the trajectory do not exceed 0.6 EMOS (Earth Mean Orbital Speed). For the remaining mission regions, the requirements are so smoothly varying that a 50-day interval in dates at the target planet may be employed; the 10-day interval in trip times is, however, preserved here. In these regions, only those trips are listed for which either or both speeds do not exceed 0.3 EMOS.

INTERPLANETARY FLIGHT↗

Space Flight Handbooks. Volume 3- Planetary Flight Handbook: Supplementary Trajectory Data: Venus to Earth and Mars to Earth - Part 3

Parts 2 and 3 present tabulations of trajectory data for scheduling flights to and from Venus and Mars during the period 1960-2000. Part 2 contains information for outbound flights to these planets; Part 3 contains information for trajectories returning from the planets to Earth. Each Part contains data for single-plane transfers, as well as for broken-plane transfers which employ a midcourse plane-change to eliminate the high speed "ridges." The mathematical analyses employed for all calculations are described in Part 1 of this handbook. To facilitate the construction of round-trip trajectories, the date at the target planet is held fixed while the trip duration is varied in 10-day increments from zero days to the length of that planet's synodic period with Earth. Dates of arrival at the target planet are presented in the extreme right-hand column of Part 2, and dates of departure from the target planet are presented in the extreme left-hand column of Part 3. Thus, by holding Part 2 directly to the left of Part 3, the analyst may easily and rapidly scan all trip possibilities which involve any desired stopover time at the target planet. Within approximately 200 days of each conjunction or opposition, data are presented in 10-day increments at the target planet. Only those trips are listed for which the hyperbolic excess speeds at either or both ends of the trajectory do not exceed 0.6 EMOS (Earth Mean Orbital Speed). For the remaining mission regions, the requirements are so smoothly varying that a 50-day interval in dates at the target planet may be employed; the 10-day interval in trip times is, however, preserved here. In these regions, only those trips are listed for which either or both speeds do not exceed 0.3 EMOS.

Source record↗