Search NASA⌕ Search

SEARCH · Search NASA

Results for “Trajectory Options Set”

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.

85 records · Page 5

Space Launch System Co-Manifested Payload Options for Habitation

The Space Launch System (SLS) has a co-manifested payload capability that will grow over time as the launch vehicle matures and planned upgrades are implemented. The final configuration is planned to be capable of inserting a payload greater than 10 metric tons (mt) into a trans-lunar injection trajectory along with the crew in the Orion capsule and its service module. The co-manifested payload is located below the Orion and its service module in a 10 m high fairing similar to the way the Saturn launch vehicle carried the lunar lander below the Apollo command and service modules. Various approaches that utilize this comanifested payload capability to build up infrastructure in deep space have been explored in support of future asteroid, lunar, and Mars mission scenarios. This paper reports on the findings of the Advanced Concepts Office study team at NASA Marshall Space Flight Center (MSFC) working with the Advanced Exploration Systems Program on the Exploration Augmentation Module Project. It includes some of the possible options for habitation in the co-manifested payload volume of the SLS. Findings include a set of module designs that can be developed in 10 mt increments to support these co-manifested payload missions along with a comparison of this approach to a large-module payload flight configuration for the SLS.

Smitherman, David↗

Evolution of Orion Mission Design for Exploration Mission 1 and 2

The evolving mission design and concepts of NASA’s next steps have shaped Orion into the spacecraft that it is today. Since the initial inception of Orion, through the Constellation Program, and now in the Exploration Mission frame-work with the Space Launch System (SLS), each mission design concept and pro-gram goal have left Orion with a set of capabilities that can be utilized in many different mission types. Exploration Missions 1 and 2 (EM-1 and EM-2) have now been at the forefront of the mission design focus for the last several years. During that time, different Design Reference Missions (DRMs) were built, analyzed, and modified to solve or mitigate enterprise level design trades to ensure a viable mission from launch to landing. The resulting DRMs for EM-1 and EM-2 were then expanded into multi-year trajectory scans to characterize vehicle performance as affected by variations in Earth-Moon geometry. This provides Orion’s subsystems with stressing reference trajectories to help design their system. Now that Orion has progressed through the Preliminary and Critical Design Reviews (PDR and CDR), there is a general shift in the focus of mission design from aiding the vehicle design to providing mission specific products needed for pre-flight and real time operations. Some of the mission specific products needed include, large quantities of nominal trajectories for multiple monthly launch periods and abort options at any point in the mission for each valid trajectory in the launch window.

Gutkowski, Jeffrey P.↗

Evolution of Orion Mission Design for Exploration Mission 1 and 2

The evolving mission design and concepts of NASA's next steps have shaped Orion into the spacecraft that it is today. Since the initial inception of Orion, through the Constellation Program, and now in the Exploration Mission frame-work with the Space Launch System (SLS), each mission design concept and program goal have left Orion with a set of capabilities that can be utilized in many different mission types. Exploration Missions 1 and 2 (EM-1 and EM-2) have now been at the forefront of the mission design focus for the last several years. During that time, different Design Reference Missions (DRMs) were built, analyzed, and modified to solve or mitigate enterprise level design trades to ensure a viable mission from launch to landing. The resulting DRMs for EM-1 and EM-2 were then expanded into multi-year trajectory scans to characterize vehicle performance and Earth-Moon geometry trends. This provides Orion's subsystems with stressing reference trajectories to help design their system. Now that Orion has progressed through the Preliminary and Critical Design Re-views (PDR and CDR) there is a general shift in the focus of mission design from aiding the vehicle design to providing mission specific products needed for pre-flight and real time operations. Some of the mission specific products need-ed include analysis of steering law performance, inputs into navigational accura-cy assessments, abort options at any point in the mission for each valid trajecto-ry in the launch window, recontact avoidance between the upper stage and Orion post nominal separation, etc.

Gutkowski, Jeffrey P.↗

Enigma Version 12

Enigma Version 12 software combines model building, animation, and engineering visualization into one concise software package. Enigma employs a versatile user interface to allow average users access to even the most complex pieces of the application. Using Enigma eliminates the need to buy and learn several software packages to create an engineering visualization. Models can be created and/or modified within Enigma down to the polygon level. Textures and materials can be applied for additional realism. Within Enigma, these models can be combined to create systems of models that have a hierarchical relationship to one another, such as a robotic arm. Then these systems can be animated within the program or controlled by an external application programming interface (API). In addition, Enigma provides the ability to use plug-ins. Plugins allow the user to create custom code for a specific application and access the Enigma model and system data, but still use the Enigma drawing functionality. CAD files can be imported into Enigma and combined to create systems of computer graphics models that can be manipulated with constraints. An API is available so that an engineer can write a simulation and drive the computer graphics models with no knowledge of computer graphics. An animation editor allows an engineer to set up sequences of animations generated by simulations or by conceptual trajectories in order to record these to highquality media for presentation. Enigma Version 12 Lyndon B. Johnson Space Center, Houston, Texas 28 NASA Tech Briefs, September 2013 Planetary Protection Bioburden Analysis Program NASA's Jet Propulsion Laboratory, Pasadena, California This program is a Microsoft Access program that performed statistical analysis of the colony counts from assays performed on the Mars Science Laboratory (MSL) spacecraft to determine the bioburden density, 3-sigma biodensity, and the total bioburdens required for the MSL prelaunch reports. It also contains numerous tools that report the data in various ways to simplify the reports required. The program performs all the calculations directly in the MS Access program. Prior to this development, the data was exported to large Excel files that had to be cut and pasted to provide the desired results. The program contains a main menu and a number of submenus. Analyses can be performed by using either all the assays, or only the accountable assays that will be used in the final analysis. There are three options on the first menu: either calculate using (1) the old MER (Mars Exploration Rover) statistics, (2) the MSL statistics for all the assays, or This software implements penetration limit equations for common micrometeoroid and orbital debris (MMOD) shield configurations, windows, and thermal protection systems. Allowable MMOD risk is formulated in terms of the probability of penetration (PNP) of the spacecraft pressure hull. For calculating the risk, spacecraft geometry models, mission profiles, debris environment models, and penetration limit equations for installed shielding configurations are required. Risk assessment software such as NASA's BUMPERII is used to calculate mission PNP; however, they are unsuitable for use in shield design and preliminary analysis studies. The software defines a single equation for the design and performance evaluation of common MMOD shielding configurations, windows, and thermal protection systems, along with a description of their validity range and guidelines for their application. Recommendations are based on preliminary reviews of fundamental assumptions, and accuracy in predicting experimental impact test results. The software is programmed in Visual Basic for Applications for installation as a simple add-in for Microsoft Excel. The user is directed to a graphical user interface (GUI) that requires user inputs and provides solutions directly in Microsoft Excel workbooks. This work was done by Shannon Ryan of the USRA Lunar and Planetary Institute for Johnson Space Center. Further information is contained in a TSP (see page 1). MSC- 24582-1 Micrometeoroid and Orbital Debris (MMOD) Shield Ballistic Limit Analysis Program Lyndon B. Johnson Space Center, Houston, Texas Commercially, because it is so generic, Enigma can be used for almost any project that requires engineering visualization, model building, or animation. Models in Enigma can be exported to many other formats for use in other applications as well. Educationally, Enigma is being used to allow university students to visualize robotic algorithms in a simulation mode before using them with actual hardware.

Shores, David↗

Maven Orbital Trajectory Analysis: Design and Implementation of Lander Relay Support

NASA’s successful Mars Atmosphere and Volatile Evolution Mission (MAVEN), currently engaged in a survey of the Martian atmosphere and its evolution over time, has successfully completed a series of orbit changes, including a two-month aerobraking campaign, to satisfy additional mission roles. Launched on 18 November 2013, it entered Martian orbit on 22 September 2014. Having finished its primary one-year mission, the NASA Mars Program Office (MPO) started discussions with the MAVEN project on feasible options for extending the mission lifetime along with providing support for various Mars lander functions. MAVEN is the latest of the three active NASA Mars orbiters, with no others planned for the foreseeable future. Given that the landers need orbital relay support for years to come, and the MRO and Odyssey orbiters are aging, MAVEN’s role in providing critical orbital relay support has become increasingly important. After several years of studies, MPO directed the MAVEN project in 2018 to reduce its orbit size to provide better telecommunications relay support for Martian surface landers and to support Mars 2020 EDL under the constraint that MAVEN will have enough fuel to operate until 2030. As a part of this effort, the recent aerobraking campaign was one of several steps crucial to accomplishing this goal. This paper discusses the challenges of the entire mission design and its distillation into a concrete set of targeted objectives. With the successful orbit change, MAVEN will be able to provide support for the Mars 2020 relay activities from EDL through surface operations beyond 2030. This effort can serve as an excellent example for future missions having similar needs and requirements.

Jakosky, B. M.↗

Red Dragon: Low-cost Access to the Surface of Mars using Commercial Capabilities

We will discuss the feasibility of using a minimally-modified variant of a SpaceX Dragon capsule as a low-cost, large-capacity, near-term, Mars lander for scientific and human-precursor missions. We have been evaluating such a Red Dragon platform as an option for a Discovery Program mission concept. A Red Dragon lander has the potential to be low cost primarily because it would be derived from a routinely-flying spacecraft. Dragon is being developed to ferry cargo and crew to and from the International Space Station (ISS). The cargo variant is currently undergoing test flights, which will be followed by standard ISS cargo missions and, eventually, crewed flights. The human variant, unlike other Earth-return vehicles, appears to also have most of the capabilities necessary to land on Mars. In particular, it has a set of high-thrust, throttleable, storable bi-propellant Super- Draco engines integrated directly into the capsule which are intended for launch abort and powered landings on Earth. These thrusters suggest the possibility of a parachute-free, fully-propulsive deceleration at Mars from supersonic speeds to the surface. Concepts for large, human-relevant landers (see, e.g., [1]) also often employ supersonic retro-propulsion; Red Dragon's entry, descent, and landing approach would scale to those landers. Further, SpaceX's Falcon Heavy launch vehicle, currently under development and expected to have its first flight in 2013, will be capable of sending Dragon on a trajectory to Mars. We will discuss our motivation for exploring a Red Dragon lander, the primary technical questions which determine its feasibility, and the current results of our analysis. In particular, we will examine entry, descent, and landing (EDL) in detail. We will describe the modifications to Dragon necessary for interplanetary cruise, EDL, and operations on the Martian surface.

Karcz, John↗

Analysis of Launch Vehicle Liftoff Debris: Historical Perspective from Space Shuttle and Application to Artemis I

Human exploration-class launch vehicles are inherently prone to debris due to the extreme environments generated during pre-launch operations, liftoff, and flight. The use of cryogenic propellants often requires thermal protection system (TPS) coatings, typically foam, to maintain the propellant conditions in the tank and prevent an accumulation ice on the external surface of the vehicle. Some ice growth is to be expected at umbilical interfaces, vents, flanges, or brackets where it is difficult to apply TPS. This ice may come loose at any time due to wind on the launch pad, structural vibration and acoustics after rocket ignition, or aerodynamic forces during flight. This phenomena is especially apparent on vehicles with no TPS, such as the Saturn V rockets used in the Apollo Program, see Figure 1. During propellant tanking, the thermal contraction of the underlying substrate may generate cracks in the TPS (Figure 1). Chunks of TPS can release due to the expansion of ingested gas from cryopumping or from aerodynamic forces if the crack creates an offset surface. Most foams will also have a certain amount of “popcorning” where small pieces of foam will pop off during flight because of the differential between the static surface pressure and the pressure of the gas trapped in the foam cell structure. There are a number of other coating or closeout materials that may be shed from the vehicle and become debris. During pre-launch operations and liftoff, the vehicle may also be exposed to debris originating from the launch pad or ground support equipment. This debris is separate from foreign object debris, or FOD, which is not intended to be present and is strictly controlled through operations and maintenance procedures. In this case, debris is generated from hardware and materials that are necessary for launch and are subject to the intense vibration, acoustics, and direct plume impingement of the launch environment. Examples include ice from umbilicals, tape and tie wraps that protect cables, and rust or corrosion from the launch platform. While NASA has historically been aware of debris as a potential issue that could cause a failure resulting in loss of mission, loss of vehicle, or loss of crew, the likelihood and severity of that risk was not always well understood or given sufficient weight in program and flight decisions. After the Space Shuttle Columbia accident (STS-107), the investigation found that foam TPS debris shed from the external tank was the proximate cause of the damage to the orbiter wing. Six previous observations of debris released from the foam ramp that covered the bipod connecting the forward end of the orbiter to the external tank resulted in minor changes or were determined to be accepted flight risks. Two occurrences of bipod ramp foam loss were not identified until the STS-107 investigation. Despite the damage inflicted by these debris strikes, the Shuttle Program Requirements Control Board deemed the vehicle safe to fly. During the Return to Flight effort following the Columbia disaster, NASA Engineering developed a process for the assessment of debris transport, impact, and damage tolerance to support independent assessments of risk by NASA Safety and Mission Assurance (S&MA). Under this system, each element (vehicle or ground system) defines a catalog of all expected debris based on launch history, component testing, or analysis. Debris transport analysis (DTA) is conducted using the debris catalog characteristics and potential flow transport mechanisms (e.g., vehicle aerodynamics, gravity, wind, plume-driven). The predicted debris impact locations and velocities are provided to the hardware owners, who use available test data and analysis to determine whether each component can withstand the impacts. In cases where the element hardware may be severely damaged or fail, the options are to mitigate the debris source through some change in design or operation, or to work with S&MA to try to characterize the probability of the impact and damage for program risk acceptance. Because of the differences in debris characteristics and transport, the DTA has been divided between the Liftoff and Ascent regimes. The development and application of Liftoff DTA methodology from the Shuttle Program to the current Artemis Program is the subject of this paper. Liftoff DTA covers the time from the start of pre-launch operations at the launch pad, up until the vehicle clears the launch tower and there is no longer any interaction with ground systems. Debris transport during this period is broadly classified as either gravity, wind, and plume-entrained (GWPE) or plume driven (PD). GWPE debris is generally lower speed, travelling in a forward-to-aft direction. PD transport includes flow features from the rocket ignition transient, as well as plume impingement and recirculation that occur as the vehicle lifts off the launch platform. In these cases, the debris typically moves in an aft-to-forward direction at higher speeds. The applicable transport mechanisms must be considered for each piece of debris depending on the material, and release location and time. For example, rust or metallic debris from the tower could fall (GWPE) and impact the vehicle before landing on the launch platform deck where it could be also be transported by plume impingement (PD). However, falling ice (GWPE) from an umbilical is unlikely to survive impact with the vehicle or launch platform and be available for PD transport. Modeling of debris transport is accomplished using a set of DTA tools which simulate debris trajectories subject to a reference frame acceleration (i.e., gravity) and aerodynamic drag. Where the trajectory encounters a solid surface, the debris is allowed to rebound with a specified coefficient of restitution. The drag is calculated by interpolating the fluid state at each point in the debris trajectory from high-fidelity computational fluid dynamics (CFD) simulations of the launch vehicle and pad. The CFD data may either be static (steady state or time averaged), typically for GWPE transport, or dynamic (time-accurate) for PD flow features like the ignition transient. Examples of the CFD flow field solutions for the Space Launch System (SLS) rocket and launch pad are shown in Figure 2. Typical SLS debris trajectory predictions from DTA are illustrated in Figure 3. The final version of this paper will include a more detailed examination of the Liftoff DTA process developed during the Shuttle Program, and how it has been augmented and applied to the SLS rocket under the Artemis Program. Comparisons with debris observations from the Artemis I launch will demonstrate validation of the tools and methodology.

Debris↗

Applying Advanced and Existing Sensors in Dealing with Potential Natural Disasters

As an integrated observing strategy, the concept of sensorweb for Earth observations is appealing in many aspects. For instance, by increasing the spatial and temporal coverage of observations from space and other vantage points, one can eventually aid in increasing the accuracy of the atmospheric models which are precursor to hurricane track prediction, volcanic eruption forecast, and trajectory path of transcontinental transport of dust, harmful nuclear and chemical plumes. In reality, there is little analysis available in terms of benefits, costs and optimized set of sensors needed to make these necessary observations. This is a complex problem that must be carefully studied and balanced over many boundaries such as science, defense, early warning, security, and surveillance. Simplistically, the sensorweb concept from the technological point of view alone has a great appeal in the defense, early warning and security applications. In fact, it can be relatively less expensive in per unit cost as opposed to building and deploying it for the scientific use. However, overall observing approach should not be singled out and aligned somewhat orthogonally to serve a particular need. On the other hand, the sensorweb should be designed and deployed to serve multiple subject areas and customers simultaneously; and can behave as directed measuring systems for both science and operational entities. Sensorweb can be designed to act as expert systems, and/or also provide a dedicated integrated surveillance network. Today, there is no system in the world that is fully integrated in terms of reporting timely multiple hazards warnings, computing the loss of life and property damage estimates, and is also designed to cater to everyone s needs. It is not an easier problem to undertake and more so is not practically solvable. At this time due to some recent events in the world, the scientific community, social scientists, and operational agencies are more cognizant and getting together to address such colossal problems. Increasing our knowledge of the home planet, via amplified set of observations, is certainly a right step in a right direction. Furthermore, this is a prerequisite in understanding multiple hazard phenomena's. This paper examines various sensorweb options and observing architectures that can be useful specifically in addressing some of these complex issues. The ultimate goal is to serve the society by providing potential natural hazards information to the decision makers in the most expeditious manner so they can prepare themselves to mitigate potential risks to human life, livestock and property.

Habib, Shahid↗

Should We Enhance the Observing Systems or Improve Coordination Among the Operating Agencies: What is Needed the Most for Security--A Philosophical Discussion

As an integrated observing strategy, the concept of sensorweb for Earth observations is appealing in many aspects. For instance, by increasing the spatial and temporal coverage of observations from space and other vantage points, one can eventually aid in increasing the accuracy of the atmospheric models which are precursor to hurricane track prediction, volcanic eruption forecast, and trajectory path of transcontinental transport of dust, harmful nuclear and chemical plumes. In reality, there is little analysis available in terms of benefits, costs and optimized set of sensors needed to make these necessary observations. This is a complex problem that must be carefully studied and balanced over many boundaries such as science, defense, early warning, security, and surveillance. Simplistically, the sensorweb concept from the technological point of view alone has a great appeal in the defense, early warning and security applications. In fact, it can be relatively less expensive in per unit cost as opposed to building and deploying it for the scientific use. However, overall observing approach should not be singled out and aligned somewhat orthogonally to serve a particular need. On the other hand, the sensorweb should be designed and deployed to serve multiple subject areas and customers simultaneously; and can behave as directed measuring systems for both science and operational entities. Sensorweb can be designed to act as expert systems, and/or also provide a dedicated integrated surveillance network. Today, there is no system in the world that is fully integrated in terms of reporting timely multiple hazards warnings, computing the loss of life and property damage estimates, and is also designed to cater to everyone's needs. It is not an easier problem to undertake and more so is not practically solvable. At this time due to some recent events in the world, the scientific community, social scientists, and operational agencies are more cognizant and getting together to address such colossal problems. Increasing our knowledge of the home planet, via amplified set of observations, is certainly a right step in a right direction. Furthermore, this is a pre-requisite in understanding multiple hazard phenomenas. This paper examines various sensorweb options and observing architectures that can be useful specifically in addressing some of these complex issues. The ultimate goal is to serve the society by providing potential natural hazards information to the decision makers in the most expeditious manner so they can prepare themselves to mitigate potential risks to human life, livestock and property.

Habib, Shahid↗

Acquiring Comprehensive Observations using an Integrated Sensorweb for Early Warning

As an integrated observing strategy, the concept of sensorweb for Earth observations is appealing in many aspects. For instance, by increasing the spatial and temporal coverage of observations from space and other vantage points, one can eventually aid in increasing the accuracy of the atmospheric models which are precursor to hurricane track prediction, volcanic eruption forecast, and trajectory path of transcontinental transport of dust, harmful nuclear and chemical plumes. In reality, there is little analysis'available in terms of benefits, costs and optimized set of sensors needed to make these necessary observations. This is a complex problem that must be carefully studied and balanced over many boundaries such as science, defense, early warning security, and surveillance. Simplistically, the sensorweb concept from the technological point of view alone has a great appeal in the defense, early warning and security applications. In fact, it can be relatively less expensive in per unit cost as opposed to building and deploying it for the scientific use. However, overall observing approach should not be singled out and aligned somewhat . orthogonally to serve a particular need. On the other hand, the sensorweb should be designed and deployed to serve multiple subject areas and customers simultaneously; and can behave as directed measuring systems for both science and operational entities. Sensorweb can be designed to act as expert systems, and/or also provide a dedicated integrated surveillance network. Today, there is no system in the world that is fully integrated in terms of reporting timely multiple hazards warnings, computing the lass of life and property damage estimates, and is also designed to cater to everyone's needs. It is not an easier problem to undertake and more so is not practically solvable. At this time due to some recent events in the world, the scientific community, social scientists, and operational agencies are more cognizant and getting together to address such colossal problems. Increasing our knowledge of the home planet, via amplified set of observations, is certainly a right step in a right direction. Furthermore, this is a pre-requisite in understanding multiple hazard phenomena's. This paper examines various sensorweb options and observing architectures that can be useful specifically in addressing some of these complex issues. The ultimate goal is to serve the society by providing potential natural hazards information to the decision makers in the most expeditious manner so they can prepare themselves to mitigate potential risks to human life, livestock and property.

Habib, Shahid↗

Acquiring Comprehensive Observations using an integrated Sensorweb for Early Warning

As an integrated observing strategy, the concept of sensorweb for Earth observations is appealing in many aspects. For instance, by increasing the spatial and temporal coverage of observations from space and other vantage points, one can eventually aid in increasing the accuracy of the atmospheric models which are precursor to hurricane track prediction, volcanic eruption forecast, and trajectory path of transcontinental transport of dust, harmful nuclear and chemical plumes. In reality, there is little analysis'available in terms of benefits, costs and optimized set of sensors needed to make these necessary observations. This is a complex problem that must be carefully studied and balanced over many boundaries such as science, defense, early warning, security, and surveillance. Simplistically, the sensorweb concept from the technological point of view alone has a great appeal in the defense, early warning and security applications. In fact, it can be relatively less expensive in per unit cost as opposed to building and deploying it for the scientific use. However, overall observing approach should not be singled out and aligned somewhat orthogonally to serve a particular need. On the other hand, the sensorweb should be designed and deployed to serve multiple subject areas and customers simultaneously; and can behave as directed measuring systems for both science and operational entities. Sensorweb can be designed to act as expert systems, and/or also provide a dedicated integrated surveillance network. Today, there is no system in the world that is fully integrated in terms of reporting timely multiple hazards warnings, computing the loss of life and property damage estimates, and is also designed to cater to everyone's needs. It is not an easier problem to undertake and more so is not practically solvable. At this time due to some recent events in the world, the scientific community, social scientists, and operational agencies are more cognizant and getting together to address such colossal problems. Increasing our knowledge of the home planet, via amplified set of observations, is certainly a right step in a right direction. Furthermore, this is a pre-requisite in understanding multiple hazard phenomena's. This paper examines various sensorweb options and observing architectures that can be useful specifically in addressing some of these complex issues. The ultimate goal is to serve the society by providing potential natural hazards information to the decision makers in the most expeditious manner so they can prepare themselves to mitigate potential risks to human life, livestock and property.

Habib, Shahid↗

Delay Banking for Managing Air Traffic

Delay banking has been invented to enhance air-traffic management in a way that would increase the degree of fairness in assigning arrival, departure, and en-route delays and trajectory deviations to aircraft impacted by congestion in the national airspace system. In delay banking, an aircraft operator (airline, military, general aviation, etc.) would be assigned a numerical credit when any of their flights are delayed because of an air-traffic flow restriction. The operator could subsequently bid against other operators competing for access to congested airspace to utilize part or all of its accumulated credit. Operators utilize credits to obtain higher priority for the same flight, or other flights operating at the same time, or later, in the same airspace, or elsewhere. Operators could also trade delay credits, according to market rules that would be determined by stakeholders in the national airspace system. Delay banking would be administered by an independent third party who would use delay banking automation to continually monitor flights, allocate delay credits, maintain accounts of delay credits for participating airlines, mediate bidding and the consumption of credits of winning bidders, analyze potential transfers of credits within and between operators, implement accepted transfers, and ensure fair treatment of all participating operators. A flow restriction can manifest itself in the form of a delay in assigned takeoff time, a reduction in assigned airspeed, a change in the position for the aircraft in a queue of all aircraft in a common stream of traffic (e.g., similar route), a change in the planned altitude profile for an aircraft, or change in the planned route for the aircraft. Flow restrictions are typically imposed to mitigate traffic congestion at an airport or in a region of airspace, particularly congestion due to inclement weather, or the unavailability of a runway or region of airspace. A delay credit would be allocated to an operator of a flight that has accepted, or upon which was imposed, a flow restriction. The amount of the credit would increase with the amount of delay caused by the flow restriction, the exact amount depending on which of several candidate formulas is eventually chosen. For example, according to one formula, there would be no credit for a delay smaller than some threshold value (e.g., 30 seconds) and the amount of the credit for a longer delay would be set at the amount of the delay minus the threshold value. Optionally, the value of a delay credit could be made to decay with time according to a suitable formula (e.g., an exponential decay). Also, optionally, a transaction charge could be assessed against the value of a delay credit that an operator used on a flight different from the one for which the delay originated or that was traded with a different operator. The delay credits accumulated by a given airline could be utilized in various ways. For example, an operator could enter a bid for priority handling in a new flow restriction that impacts one or more of the operator s flights; if the bid were unsuccessful, all or a portion of the credit would be returned to the bidder. If the bid pertained to a single aircraft that was in a queue, delay credits could be consumed in moving the aircraft to an earlier position within the queue. In the case of a flow restriction involving a choice of alternate routes, planned altitude profile, aircraft spacing, or other non-queue flow restrictions, delay credits could be used to bid for an alternative assignment.

Green, Steve↗

A Multi-Disciplinary Analysis Framework for the Design of Small Launch Vehicles

Between the years of 1995 and 2014 the number of small satellites (1-500 kg) went up from 20 to 180. [1] Out of the 180 launched in 2014 66% were Nano satellites (1-10 kg). [1] With this trend of smaller satellites, one would expect a rise in number of small launch vehicles (SLVs are defined by capability to carry 1-100 kg to orbit), but this has not happened: [3] only 8% of all small satellites are launched on SLVs and the others become secondary payloads on regular launch vehicles. [1] This results in small satellites being placed into either suboptimal orbits or waiting for launch schedules to align with bigger launches, resulting in long waiting times. Dedicated SLVs could improve the responsiveness of small satellite launches, but SLV design is complicated by the large architecture space needed to be explored in order to find efficient and affordable designs. The SLV architecture trade space contains many discrete options, e.g. solid vs. liquid fuels, air launch vs. ground launch, number of stages, etc. [2][3] Performing detailed analysis for all the options at once would be prohibitive. Thus, a sizing environment/framework that is capable of providing necessary information for conceptual-level trade studies and can rapidly explore the vast SLV architecture space is necessary. The framework, illustrated in Figure 1, consists of four disciplines central to the sizing and synthesis of launch vehicles: propulsion, aerodynamics, structures, and trajectory. For the aerodynamics and trajectory disciplines, Missile DATCOM and POST2 are used, respectively. The propulsion and structures disciplines are represented in the framework with tools developed at ASDL Georgia Tech. For propulsion, the Solid Motor Analysis Code (SMAC) is a physics-based conceptual design tool for solid rocket motors. SMAC is capable of geometric burn simulation, ballistic analysis, and prediction of thrust performance. [4] For structures, Launch Vehicle Structural Analysis (LVSA) tool is a physics-based tool that focuses on structural dynamic analysis with sizing capability. These tools are integrated into the framework illustrated in Figure 1 with the corresponding connections described in Table 1. The process flow is as follows: first, SMAC sizes insulation and calculates maximum operating pressures for each vehicle stage. The MEOP and insulation thickness values from SMAC are fed to LVSA which then utilizes this information to size the motor casing. This creates a feedback loop between LVSA and SMAC that converges on the radius available for fuel, casing, and insulation thickness. Once the stage sizing is converged on SMAC creates an engine deck that is passed to POST2. Next, the data from SMAC and LVSA goes into Missile DATCOM which generates an aerodynamics database for POST2. Finally, POST2 performs a targeting optimization while maximizing the payload mass to orbit. Within the framework, POST2 is automated in order to be robust to a wide variety of possible designs by performing a Monte Carlo simulation over the initialization vector of the POST2 optimization variables. To demonstrate the capability of this framework, a sample problem of exploring the design space of an SLV capable of placing satellites into a low Earth orbit (inclination=47 deg, 196.5 by 211.3 nm) is used. This sample problem is a ground-launched SLV consisting of four in-line SRM stages. The multidisciplinary design analysis (MDA) environment is utilized to explore a design space consisting of 22 continuous and 12 discrete variables, shown by Table 1 by blocks 1,2,3. Running a full factorial design of experiments (DOE) would have been prohibitively expensive even with this reduced design space, thus a space filling design with 3,502 and then additional expansion of 2,602 cases was used. The first DOE consisted of 3,502 cases, and all of the variables were varied. These input variables are listed in blocks 1, 2, and 3 in Table 1. Most of the variables are propulsion related with stage lengths determining the delta-V split of the SLV. The expansion consisted of 2,602 cases, and the continuous variables were set to be equal to the most promising designs from the sizing of first DOE. For each set of continuous variables, the discrete variables (grain type, star points, and propellant) were to varied. The results of the DOE can be seen in Figure 2; each of the points in this plot represents a closed launch vehicle that reaches the targeted orbit. For each of the cases, there is information on flown trajectory, structural, and propulsion properties of the SLV. For example, Figure 3 shows changes in altitude and velocity with time for a particular case. The right side of Figure 3 clearly shows the coasting (slow decrease) and burning phases (sharp increase) of the SLV mission. LV mass is positively correlated with the optimized payload mass to orbit because heavier LVs carry more fuel and thus have more stored chemical energy. Furthermore, for any given payload mass to orbit, the most efficient design would result in the smallest LV. The results as visualized in Figure 2 shows this tradeoff, and the Pareto frontier of the efficient designs can be seen along the dotted line. Figure 2 can be divided into regions with the lowest mass vehicles corresponding to the minimum bound on radius, and the highest mass vehicles corresponding to the maximum bound on radius. Within a mass region, the discrete variables, such as propellant type and propellant grain arrangement, have the most effect on payload mass. This paper presents an MDA framework that can perform an automated physics-based sizing of SLV designs and a corresponding methodology to utilize the MDA to explore the design space of SLVs. The proposed methodology was applied to a perform a design space exploration for a four stage SLV. The outputs show the expected pareto frontier forming and provide detailed information about the SLV performance and staging. Using the produced data, it will be possible to select a set of pareto optimal designs that can then be further explored in subsequent design cycles. This demonstration shows that automated design space exploration should be used in the early phase design of future SLV concepts.

Nikita S Birbasov↗