Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Airline Operations Center”

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
All sourcesNASA NTRSDOE OSTI
NASA NTRS2016

Deploying a Route Optimization EFB Application for Commercial Airline Operational Trials

The Traffic Aware Planner (TAP), developed for NASA Langley Research Center to support the Traffic Aware Strategic Aircrew Requests (TASAR) project, is a flight-efficiency software application developed for an Electronic Flight Bag (EFB). Tested in two flight trials and planned for operational testing by two commercial airlines, TAP is a real-time trajectory optimization application that leverages connectivity with onboard avionics and broadband Internet sources to compute and recommend route modifications to flight crews to improve fuel and time performance. The application utilizes a wide range of data, including Automatic Dependent Surveillance Broadcast (ADS-B) traffic, Flight Management System (FMS) guidance and intent, on-board sensors, published winds and weather, and Special Use Airspace (SUA) schedules. This paper discusses the challenges of developing and deploying TAP to various EFB platforms, our solutions to some of these challenges, and lessons learned, to assist commercial software developers and hardware manufacturers in their efforts to implement and extend TAP functionality in their environments. EFB applications (such as TAP) typically access avionics data via an ARINC 834 Simple Text Avionics Protocol (STAP) server hosted by an Aircraft Interface Device (AID) or other installed hardware. While the protocol is standardized, the data sources, content, and transmission rates can vary from aircraft to aircraft. Additionally, the method of communicating with the AID may vary depending on EFB hardware and/or the availability of onboard networking services, such as Ethernet, WIFI, Bluetooth, or other mechanisms. EFBs with portable and installed components can be implemented using a variety of operating systems, and cockpits are increasingly incorporating tablet-based technologies, further expanding the number of platforms the application may need to support. Supporting multiple EFB platforms, AIDs, avionics datasets, and user interfaces presents a challenge for software developers and the management of their code baselines. Maintaining multiple baselines to support all deployment targets can be extremely cumbersome and expensive. Certification also needs to be considered when developing the application. Regardless of whether the software is itself destined to be certified, data requirements in support of the application and user interface elements may introduce certification requirements for EFB manufacturers and the airlines. The example of TAP, the challenges faced, solutions implemented, and lessons learned will give EFB application and hardware developers insight into future potential requirements in deploying TAP or similar flight-deck EFB applications.

Roscoe, David A.↗
NASA NTRS2003

Rethinking Human-Centered Computing: Finding the Customer and Negotiated Interactions at the Airport

The breakdown in the air transportation system over the past several years raises an interesting question for researchers: How can we help improve the reliability of airline operations? In offering some answers to this question, we make a statement about Huuman-Centered Computing (HCC). First we offer the definition that HCC is a multi-disciplinary research and design methodology focused on supporting humans as they use technology by including cognitive and social systems, computational tools and the physical environment in the analysis of organizational systems. We suggest that a key element in understanding organizational systems is that there are external cognitive and social systems (customers) as well as internal cognitive and social systems (employees) and that they interact dynamically to impact the organization and its work. The design of human-centered intelligent systems must take this outside-inside dynamic into account. In the past, the design of intelligent systems has focused on supporting the work and improvisation requirements of employees but has often assumed that customer requirements are implicitly satisfied by employee requirements. Taking a customer-centric perspective provides a different lens for understanding this outside-inside dynamic, the work of the organization and the requirements of both customers and employees In this article we will: 1) Demonstrate how the use of ethnographic methods revealed the important outside-inside dynamic in an airline, specifically the consequential relationship between external customer requirements and perspectives and internal organizational processes and perspectives as they came together in a changing environment; 2) Describe how taking a customer centric perspective identifies places where the impact of the outside-inside dynamic is most critical and requires technology that can be adaptive; 3) Define and discuss the place of negotiated interactions in airline operations, identifying how these interactions between customers and airline employees provided new insights into design problems in the airline system; 4) Show how taking a customer-centric perspective influences the HCC design of an airline system and make recommendations for new architectures and intelligent devices that will enable airline systems to adapt flexibly to delay situations, supporting both customers and airline employees.

Wales, Roxana↗
NASA NTRS2016

Flight Test Assessments of Pilot Workload, System Usability, and Situation Awareness of TASAR

Traffic Aware Strategic Aircrew Requests (TASAR) is an onboard automation concept intended to identify trajectory optimizations, in terms of fuel and time saving objectives, clear of known traffic, weather, and airspace restrictions prior to the aircrew initiating a route-change request to Air Traffic Control (ATC). The software implementation of the TASAR concept is the Traffic Aware Planner (TAP). TASAR analysis and development is being executed by the NASA Langley Research Center's Crew Systems and Aviation Operations Branch (CSAOB) under the sponsorship of the Airspace Technology Demonstration (ATD) Project of the NASA Airspace Operations and Safety Program (AOSP). The TASAR Flight Trial-2 (FT-2) was conducted in June, 2015 out of the Newport News/Williamsburg International Airport. This flight trial was conducted using a Piaggio Avanti flight test aircraft and consisted of 12 Evaluation Flights with airline commercial pilots participating as the Evaluation Pilots, three destination airports in Atlanta and Jacksonville Air Route Traffic Control Centers, and one pair of flight plans associated with each destination airport. The primary goal of FT-2 was to reduce risk for upcoming operational trials with NASA partner airlines, Alaska Airlines and Virgin America. To accomplish this primary goal, six independent objectives were conducted during FT-2, however, this paper will report only the findings of Objective 5; the assessment of system usability, pilot perceived workload, and the degree of pilot acceptability of the TAP Human Machine Interface (HMI) during flight operations, via the administration of several subjective measures.

TASAR↗
NASA NTRS2005

Joint NASA Ames/Langley Experimental Evaluation of Integrated Air/Ground Operations for En Route Free Maneuvering

In order to meet the anticipated future demand for air travel, the National Aeronautics and Space Administration (NASA) is investigating a new concept of operations known as Distributed Air-Ground Traffic Management (DAG-TM). Under the En Route Free Maneuvering component of DAG-TM, appropriately equipped autonomous aircraft self separate from other autonomous aircraft and from managed aircraft that continue to fly under today s Instrument Flight Rules (IFR). Controllers provide separation services between IFR aircraft and assign traffic flow management constraints to all aircraft. To address concept feasibility issues pertaining to integrated air/ground operations at various traffic levels, NASA Ames and Langley Research Centers conducted a joint human-in-the-loop experiment. Professional airline pilots and air traffic controllers flew a total of 16 scenarios under four conditions: mixed autonomous/managed operations at three traffic levels and a baseline all-managed condition at the lowest traffic level. These scenarios included en route flights and descents to a terminal area meter fix in airspace modeled after the Dallas Ft. Worth area. Pilots of autonomous aircraft met controller assigned meter fix constraints with high success. Separation violations by subject pilots did not appear to vary with traffic level and were mainly attributable to software errors and procedural lapses. Controller workload was lower for mixed flight conditions, even at higher traffic levels. Pilot workload was deemed acceptable under all conditions. Controllers raised several safety concerns, most of which pertained to the occurrence of near-term conflicts between autonomous and managed aircraft. These issues are being addressed through better compatibility between air and ground systems and refinements to air and ground procedures.

Barhydt, Richard↗
NASA NTRS1989

Airline Crew Training

The discovery that human error has caused many more airline crashes than mechanical malfunctions led to an increased emphasis on teamwork and coordination in airline flight training programs. Human factors research at Ames Research Center has produced two crew training programs directed toward more effective operations. Cockpit Resource Management (CRM) defines areas like decision making, workload distribution, communication skills, etc. as essential in addressing human error problems. In 1979, a workshop led to the implementation of the CRM program by United Airlines, and later other airlines. In Line Oriented Flight Training (LOFT), crews fly missions in realistic simulators while instructors induce emergency situations requiring crew coordination. This is followed by a self critique. Ames Research Center continues its involvement with these programs.

Source record↗
NASA NTRS2013

Operational Evaluatioin of Dynamic Weather Routes at American Airlines

Dynamic Weather Routes (DWR) is a search engine that continuously and automatically analyzes inflight aircraft in en route airspace and proposes simple route amendments for more efficient routes around convective weather while considering sector congestion, traffic conflicts, and active Special Use Airspace. NASA and American Airlines (AA) are conducting an operational trial of DWR at the AA System Operations Center in Fort Worth, TX. The trial includes only AA flights in Fort Worth Center airspace. Over the period from July 31, 2012 through August 31, 2012, 45% of routes proposed by DWR and evaluated by AA users - air traffic control coordinators and flight dispatchers - were rated as acceptable as proposed or with some modifications. The wind-corrected potential flying time savings for these acceptable routes totals 470 flying min, and results suggest another 1,500 min of potential savings for flights not evaluated due to staffing limitations. A sector congestion analysis shows that in only two out of 83 DWR routes rated acceptable by AA staff were the flights predicted to fly through a congested sector inside of 30 min downstream of present position. This shows that users considered sector congestion data provided by DWR automation and in nearly all cases did not accept routes through over-capacity sectors. It is estimated that 12 AA flights were given reroute clearances as a direct result of DWR for a total savings of 67 flying min.

air traffic trajectory automation↗
NASA NTRS2021

NASA Ames Fatigue Countermeasures Laboratory and AA FRMS - A Working Relationship

American Airlines and NASA Ames Research Center have a long-standing partnership to conduct human factors fatigue research in airline operations. Since 2016, using a mechanism known as a Space Act Agreement, NASA Ames’ Fatigue Countermeasures Laboratory has worked with the American’s Fatigue Risk Management team to gather sleep and alertness data from volunteer flight crew members. Operations studied include long-range transpacific flights, timing of inflight rest breaks during augmented flights, and rates of acclimation related to flights making theater changes. This mutually beneficial collaborative working arrangement allows American to conduct operations of specific interest under the FAA’s Alternative Means of Compliance process and provides NASA with a means to gather and analyze data that can be used to inform operational safety-related decisions. Earlier this year, results from the study of inflight rest breaks was published in the journal Aerospace Medicine and Human Performance. A total of 500 American pilots responded to a survey with landing crew reporting more and better-quality sleep during break 2 than break 3. Subsequent ratings of sleepiness and alertness at TOD were significantly better for crew who used break 2. Findings from this study were reported to the FAA leading to an inflight fatigue mitigation capability for many pilots in the industry. An upcoming study is to evaluate workload and alertness levels during Caribbean Turn (DFW-SJO-DFW) operations. For this study, the FRMS team and NASA will ask volunteers to collect data on sleep, workload, performance, and alertness using scientifically valid methods The information gained in this study will help inform how workload and fatigue interact with duty duration during short-haul, daytime operations.

in-flight rest↗
NASA NTRS2021

Metroplex Planner User Manual

This document serves as a user manual for the ATD-2 Metroplex Planner (version 6.1.2) for use by the Air Route Traffic Control Center (ARTCC), Terminal Radar Approach Control (TRACON), airport Air Traffic Control Tower, and airline Flight Operators. It describes the elements of the Metroplex Planner interface and provides step-by-step instructions for using the tool. In addition to live flight information, traffic management information, and demand/delay predictions, the Metroplex Planner supports Trajectory Option Set (TOS) rerouting. The Metroplex Planner is a component of the NASA Airspace Technology Demonstration 2 (ATD-2) sub-project.

Deborah L Bakowski↗
NASA NTRS1980

Toward new small transports for commuter airlines

The article discusses the results of a survey of commuter airline operators and large and small airframe manufacturers conducted by the Small Transport Aircraft Technology Office of the NASA Ames Research Center. Attention is given to economic concerns of the operator and manufacturer, as well as social concerns of the passenger, community, and system. Discussion also covers research and technology opportunities for improving commuter aircraft, and provides a background of information on the commuter and short-haul local-service air carriers, regulations pertaining to their aircraft, and operations, overall airline interfaces, and facility requirements.

Giulianetti, D. J.↗
NASA NTRS2015

Assessment of a National Airspace System Airborne Rerouting Tool

This paper presents the assessment of a National Airspace System airborne rerouting tool. The tool implements NASA’s Dynamic Weather Routes concept for wind-corrected flying-time savings during convective weather activity. A description of the system, as applicable to the entire United States airspace is provided, and results are presented demonstrating benefits of such a system from various Centers and airlines’ perspectives. Three cases for selection of reroute-return capture fix, which prevent unrealistically large controller clearances are presented. Results are shown for potential time- and fuel-savings (over 134,000 minutes and 4.2 million lbs. of fuel for over 35,000 proposed reroutes) and sector congestion reduction (over 121 hours in congested sectors) for all 20 Centers. The data used were for 30 days with highest delays attributable to convective weather from April to October of 2014. Other results show the evaluation of the maneuver or reroute start point (a parameter representing the amount of coordination time needed), which highlight the need for a controller-pilot data link. A data link would help achieve higher savings. The results for persistence time, beyond which the time-savings dwindle quickly, help determine the maximum coordination time required for each Center. Finally, an assessment from a current National Operations Manager at the Air Traffic Control System Command Center of the FAA is documented. Those suggestions could improve the efficiency of the air transportation system, especially with the expected improvements in the traffic flow management infrastructure. Currently, one industry partner and one airline are assessing this technology for commercial operational use.

Benefits Assessment↗
NASA NTRS2004

Pilot in Command: An Illustration of Autonomous Flight Management

Several years of NASA research have produced the concept for air traffic management called "Distributed Air/Ground Traffic Management," a major operational advancement that should significantly increase the capacity of the National Airspace System. A key component, "Autonomous Flight Management," introduces a new class of aircraft operations in which pilots are authorized to freely maneuver and execute optimal trajectories independent from air traffic controllers. These aircraft operators would benefit from significant increases in flexibility to optimize all flight operations and from avoiding most of the delays associated with ground-controlled operations. Responsibilities for aircraft separation and arrival flow conformance are transferred to the flight deck, and the pilots use computerized decision-support tools to accomplish these tasks. A research prototype of these tools called the "Autonomous Operations Planner" is being developed at the NASA Langley Research Center. This 14-minute video illustrates Autonomous Flight Management from the airline pilot's perspective.

Wing, David J.↗
NASA NTRSDate not supplied

Automatic Dependent Surveillance-Broadcast (ADS-B) In-Trail Procedures (ITP)

Aircraft in oceanic and remote non-radar airspace frequently fly for extended periods of time in the same direction, at the same time, along similar flight paths as other aircraft. Since there is no radar surveillance, controllers use procedural separation to ensure that aircraft remain separated. Procedural separation distances are typically larger than radar separation distances and as a result aircraft operating in oceanic airspace are sometimes held at non-optimal flight levels due to conflicting traffic at intervening flight levels. Automatic Dependent Surveillance-Broadcast (ADS-B) In-Trail Procedures (ITP) were developed to enable flight level change maneuvers that would otherwise not be possible with current procedural separation standards. Aircraft operators choosing to equip with an ADS-B transceiver and an appropriate onboard decision support system would be able to take advantage of these procedures when operating in proximity to aircraft equipped with a suitable ADS-B transmitter (“ADS-B Out”). The ability to perform in-trail maneuvers to achieve more time at optimum altitudes could result in more efficient and predictable flight profiles thereby saving fuel and in some cases allowing operators to make beneficial operational decisions. NASA first began developing ADS-B ITP in 2003 as a result of a desire to develop methodologies, concepts, and procedures to reduce separation requirements for future air transportation systems using airborne ADS-B. The objectives were to provide insight into the details necessary to reduce separation requirements for the future and to develop applications that could provide incentives for operators to voluntarily equip with transformational technologies. From 2003 to 2008, NASA conducted research that supported the development of ITP including batch simulations, human-in-the-loop experiments and avionics and separation standards development. This research showed enough maturity and benefit that in 2008, the FAA Surveillance and Broadcast Services (SBS) program adopted ADS-B ITP as one of their three key, near-term applications to make use of ADS-B-In. The FAA developed an agreement with NASA to transition the technology and established an FAA project for the purpose of performing an operational trial of ADS-B ITP in revenue service in the summer of 2011. The objectives of the project are to a) validate the operational performance and economic benefits of ITP; and b) develop and validate ADS-B ITP Minimum Operational Performance Specifications (MOPS) material. As a part of this project, the FAA established agreements with United Airlines and Honeywell. The agreements include the work necessary for the development, certification and installation of onboard systems for twelve United Airlines 747-400s. ITP system development is nearly complete and certification activities are underway. The FAA project has also been working with Oakland Oceanic Control Center (ZOA) and the FAA’s Oceanic and Offshore Operations Office to develop controller procedures and safety analyses that are required to support the flight trial. The FAA has also been working on the development of an ITP Operational Specification that should be approved this April. The presentation will cover some of the key aspects of the development, challenges, and integration required to successfully transition ADS-B ITP from a concept in 2003 to flight trials in revenue service in 2011.

Kenneth M Jones↗
NASA NTRS1983

Advanced symbology for general aviation approach to landing displays

A set of flight tests designed to evaluate the relative utility of candidate displays with advanced symbology for general aviation terminal area instrument flight rules operations are discussed. The symbology was previously evaluated as part of the NASA Langley Research Center's Terminal Configured Vehicle Program for use in commercial airlines. The advanced symbology included vehicle track angle, flight path angle and a perspective representation of the runway. These symbols were selectively drawn on a cathode ray tube (CRT) display along with the roll attitude, pitch attitude, localizer deviation and glideslope deviation. In addition to the CRT display, the instrument panel contained standard turn and bank, altimeter, rate of climb, airspeed, heading, and engine instruments. The symbology was evaluated using tracking performance and pilot subjective ratings for an instrument landing system capture and tracking task.

Bryant, W. H.↗
NASA NTRS2007

System for Secure Integration of Aviation Data

The Aviation Data Integration System (ADIS) of Ames Research Center has been established to promote analysis of aviation data by airlines and other interested users for purposes of enhancing the quality (especially safety) of flight operations. The ADIS is a system of computer hardware and software for collecting, integrating, and disseminating aviation data pertaining to flights and specified flight events that involve one or more airline(s). The ADIS is secure in the sense that care is taken to ensure the integrity of sources of collected data and to verify the authorizations of requesters to receive data. Most importantly, the ADIS removes a disincentive to collection and exchange of useful data by providing for automatic removal of information that could be used to identify specific flights and crewmembers. Such information, denoted sensitive information, includes flight data (here signifying data collected by sensors aboard an aircraft during flight), weather data for a specified route on a specified date, date and time, and any other information traceable to a specific flight. The removal of information that could be used to perform such tracing is called "deidentification." Airlines are often reluctant to keep flight data in identifiable form because of concerns about loss of anonymity. Hence, one of the things needed to promote retention and analysis of aviation data is an automated means of de-identification of archived flight data to enable integration of flight data with non-flight aviation data while preserving anonymity. Preferably, such an automated means would enable end users of the data to continue to use pre-existing data-analysis software to identify anomalies in flight data without identifying a specific anomalous flight. It would then also be possible to perform statistical analyses of integrated data. These needs are satisfied by the ADIS, which enables an end user to request aviation data associated with de-identified flight data. The ADIS includes client software integrated with other software running on flight-operations quality-assurance (FOQA) computers for purposes of analyzing data to study specified types of events or exceedences (departures of flight parameters from normal ranges). In addition to ADIS client software, ADIS includes server hardware and software that provide services to the ADIS clients via the Internet (see figure). The ADIS server receives and integrates flight and non-flight data pertaining to flights from multiple sources. The server accepts data updates from authorized sources only and responds to requests from authorized users only. In order to satisfy security requirements established by the airlines, (1) an ADIS client must not be accessible from the Internet by an unauthorized user and (2) non-flight data as airport terminal information system (ATIS) and weather data must be displayed without any identifying flight information. ADIS hardware and software architecture as well as encryption and data display scheme are designed to meet these requirements. When a user requests one or more selected aviation data characteristics associated with an event (e.g., a collision, near miss, equipment malfunction, or exceedence), the ADIS client augments the request with date and time information from encrypted files and submits the augmented request to the server. Once the user s authorization has been verified, the server returns the requested information in de-identified form.

Kulkarni, Deepak↗
NASA NTRS2012

Advisory Systems Save Time, Fuel for Airlines

Heinz Erzberger never thought the sky was falling, but he knew it could benefit from enhanced traffic control. Throughout the 1990s, Erzberger led a team at Ames Research Center to develop a suite of automated tools to reduce restrictions and improve the efficiency of air traffic control operations. Called CTAS, or Center-TRACON (Terminal Radar Approach Control) Automation System, the software won NASA s Software of the Year award in 1998, and one of the tools in the suite - the traffic management advisor - was adopted by the Federal Aviation Administration and implemented at traffic control centers across the United States. Another one of the tools, Direct-To, has followed a different path. The idea behind Direct-To, explains Erzberger, a senior scientist at Ames, was that airlines could save fuel and money by shortening the routes they flew between take-off and landing. Aircraft are often limited to following established airways comprised of inefficient route segments. The routes are not easily adjusted because neither the pilot nor the aircraft controller can anticipate the constantly changing air traffic situation. To make the routes more direct while in flight, Erzberger came up with an idea for a software algorithm that could automatically examine air traffic in real-time, check to see if a shortcut was available, and then check for conflicts. If there were no conflicts and the shortcut saved more than 1 minute of flight time, the controller could be notified. "I was trying to figure out what goes on in the pilot and controller s minds when they decide to guide the aircraft in a certain way. That resulted in a different kind analysis," Erzberger says. As the engineer s idea went from theory to practice, in 2001, NASA demonstrated Direct-To in the airspace of Dallas-Ft. Worth. Estimations based on the demonstration found the technology was capable of saving 900 flying minutes per day for the aircraft in the test area.

Source record↗
NASA NTRS1981

Flight test evaluation of advanced symbology for general aviation approach to landing displays

This paper describes a set of flight test experiments which were designed to evaluate the relative utility of candidate displays with advanced symbology for General Aviation IFR operations in the terminal area. This symbology was previously evaluated as part of the NASA Langley Research Center's Terminal Configured Vehicle Program for use in commercial airlines. The advanced symbology included vehicle track-angle, flight path angle and a perspective representation of the runway. These symbols were selectively drawn on a CRT display along with the roll attitude, pitch attitude, localizer-deviation and glideslope deviation. In addition to the CRT display, the instrument panel contained standard turn and bank, altimeter, rate of climb, airspeed, heading and engine instruments. The symbology was evaluated using tracking performance and pilot subjective ratings for an ILS capture and tracking task.

Downing, D. R.↗
NASA NTRSDate not supplied

Demonstrating Early-Adopter Benefits of Submitting Multiple Trajectory Options for Airlines

A workshop at NASA Ames Research Center was held with airline industry stakeholders to demonstrate the impact of using Trajectory Options Sets (TOSs) during a Collaborative Trajectory Options Program (CTOP) for severe weather operations. The demonstration was conducted using apart-task Human-in-the-Loop (HITL) simulation of the Integrated Demand Management (IDM) concept, which is an air traffic management method that uses CTOP to deliver preconditioned traffic to the Time-Based Flow Management (TBFM) region. The demonstration addressed the following research objectives: first, determine who receives a greater benefit, TOS-participating or TOS-excluded airlines? Second, determine which method of trajectory selection yields a better solution, human/manual selection or automation? Finally, obtain feedback from stakeholders on their impression of the concept and recommendations for future work. The results showed that TOS-participating airlines received greater benefit in terms of total ground delay, ground delay savings, number of reroute options, and additional flight time, compared to TOS-excluded airlines. However, this result was dependent on the situational context, such as the number and location of flights. We found that all airlines benefitted when just a subset of airlines submitted TOS, but the greatest benefit went to the TOS-participating airlines. These benefits to the TOS-participating airlines were diminished as the number of TOS-participants in the system increased. Therefore, there was an “early-adopter” effect that suggested airlines could benefit by becoming the first to equip TOS without causing unfair disadvantages to those who do not equip TOS. In addition, we found that manual selection of trajectory options performed similarly to CTOP, but the CTOP solution was more efficient in terms of number of reroutes, additional flight time, and average ground delay for rerouted flights. Feedback from the stakeholders was solicited, and their overall impressions of the demonstrations were positive. They remarked that CTOP could do a better job than current day solutions, and they thought airlines could benefit from continuing to develop TOS capabilities.

Integrated Demand Management↗
NASA NTRS1991

Flight Planning

Seagull Technology, Inc., Sunnyvale, CA, produced a computer program under a Langley Research Center Small Business Innovation Research (SBIR) grant called STAFPLAN (Seagull Technology Advanced Flight Plan) that plans optimal trajectory routes for small to medium sized airlines to minimize direct operating costs while complying with various airline operating constraints. STAFPLAN incorporates four input databases, weather, route data, aircraft performance, and flight-specific information (times, payload, crew, fuel cost) to provide the correct amount of fuel optimal cruise altitude, climb and descent points, optimal cruise speed, and flight path.

Source record↗