ALBERT

Description: Exploration Mission 1 (EM-1) will be the first mission to send an uncrewed Orion vehicle to cislunar space in 2018, targeted to a Distant Retrograde Orbit (DRO). Analysis of EM-1 DRO mission opportunities in 2018 help characterize mission parameters that are of interest to other subsystems (e.g., power, thermal, communications, flight operations, etc). Subsystems request mission design trades which include: landing lighting, addition of an Orion main engine checkout burn, and use of auxiliary thruster only cases. This paper examines the evolving trade studies that incorporate subsystem feedback and demonstrate the feasibility of these constrained mission trajectory designs and contingencies.

Description: Exploration Mission 1 (EM-1) will be the first mission to send an uncrewed Orion Multi-Purpose Crew Vehicle (MPCV) to cislunar space in the fall of 2019. EM-1 was originally conceived as a lunar free-return mission, but was later changed to a Distant Retrograde Orbit (DRO) mission as a precursor to the Asteroid Redirect Mission. To understand the required mission performance (i.e., propellant requirement), a series of trajectory optimization runs was conducted using JSC's Copernicus spacecraft trajectory optimization tool. In order for the runs to be done in a timely manner, it was necessary to employ a parallelization approach on a computing cluster using a new trajectory scan tool written in Python. Details of the scan tool are provided and how it is used to perform the scans and post-process the results. Initially, a scan of daily due east launched EM-1 DRO missions in 2018 was made. Valid mission opportunities are ones that do not exceed the useable propellant available to perform the required burns. The initial scan data showed the propellant and delta-V performance patterns for each launch period. As questions were raised from different subsystems (e.g., power, thermal, communications, flight operations, etc.), the mission parameters or data that were of interest to them were added to the scan output data file. The additional data includes: (1) local launch and landing times in relation to sunrise and sunset, (2) length of eclipse periods during the in-space portion of the mission, (3) Earth line of sight from cislunar space, (4) Deep Space Network field of view looking towards cislunar space, and (5) variation of the downrange distance from Earth entry interface to splashdown. Mission design trades can also be performed based on the information that the additional data shows. For example, if the landing is in darkness, but the recovery operations team desires a landing in daylight, then an analysis is performed to determine how to change the mission design to meet this request. Also, subsystems request feasibility of alternate or contingency mission designs, such as adding an Orion main engine checkout burn or Orion completing all of its burns using only its auxiliary thrusters. This paper examines and presents the evolving trade studies that incorporate subsystem feedback and demonstrate the feasibility of these constrained mission trajectory designs and contingencies.

Description: The first crewed mission, Exploration Mission 2 (EM-2), for the MPCV Orion spacecraft is scheduled for August 2021, and its current mission is to orbit the Moon in a highly elliptical lunar orbit for 3 days. A 21-year scan was performed to identify feasible missions that satisfy the propulsive capabilities of the Interim Cryogenic Propulsion Stage (ICPS) and MPCV Service Module (SM). The mission is divided into 4 phases: (1) a lunar free return trajectory, (2) a hybrid maneuver, during the translunar coast, to lower the approach perilune altitude to 100 km, (3) lunar orbit insertion into a 100 x 10,000 km orbit, and (4) lunar orbit loiter and Earth return to a splashdown off the coast of Southern California. Trajectory data was collected for all feasible missions and converted to information that influence different subsystems including propulsion, power, thermal, communications, and mission operations. The complete 21-year scan data shows seasonal effects that are due to the Earth-Moon geometry and the initial Earth parking orbit. The data and information is also useful to identify mission opportunities around the current planned launch date for EM-2.

Description: The evolving mission design and concepts of NASAs 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 Orions 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.

Description: 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.