Search NASA⌕ Search

SEARCH · Search NASA

Results for “Commercial vehicles”

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 73 records · Page 4

Simulation Development and Analysis of Crew Vehicle Ascent Abort

NASA's Commercial Crew Program is an integral step in its journey to Mars as it would expedite development of space technologies and open up partnership with U.S. commercial companies. NASA reviews and independent assessment of Commercial Crew Program is fundamental to its success, and being able to model a commercial crew vehicle in a simulation rather than conduct a live test would be a safer, faster, and less expensive way to assess and certify the capabilities of the vehicle. To this end, my project was to determine the feasibility of using a simulation tool named SOMBAT version 2.0 to model a multiple parachute system for Commercial Crew Program simulation. The main tasks assigned to me were to debug and test the main parachute system model, (capable of simulating one to four main parachute bodies), and to utilize a graphical program to animate the simulation results. To begin tackling the first task, I learned how to use SOMBAT by familiarizing myself with its mechanics and by understanding the methods used to tweak its various parameters and outputs. I then used this new knowledge to set up, run, and analyze many different situations within SOMBAT in order to explore the limitations of the parachute model. Some examples of parameters that I varied include the initial velocity and orientation of the falling capsule, the number of main parachutes, and the location where the parachutes were attached to the capsule. Each parameter changed would give a different output, and in some cases, would expose a bug or limitation in the model. A major bug that I discovered was the inability of the model to handle any number of parachutes other than three. I spent quite some time trying to debug the code logically, but was unable to figure it out until my mentor taught me that digital simulation limitations can occur when some approximations are mistakenly assumed for certain in a physical system. This led me to the realization that unlike in all of the programming classes I have taken thus far that focus on pure logic, simulation code focuses on mimicking the physical world with some approximation and can have inaccuracies or numerical instabilities. Learning from my mistake, I adopted new methods to analyze these different simulations. One method the student used was to numerically plot various physical parameters using MATLAB to confirm the mechanical behavior of the system in addition to comparing the data to the output from a separate simulation tool called FAST. By having full control over what was being outputted from the simulation, I could choose which parameters to change and to plot as well as how to plot them, allowing for an in depth analysis of the data. Another method of analysis was to convert the output data into a graphical animation. Unlike the numerical plots, where all of the physical components were displayed separately, this graphical display allows for a combined look at the simulation output that makes it much easier for one to see the physical behavior of the model. The process for converting SOMBAT output for EDGE graphical display had to be developed. With some guidance from other EDGE users, I developed a process and created a script that would easily allow one to display simulations graphically. Another limitation with the SOMBAT model was the inability for the capsule to have the main parachutes instantly deployed with a large angle between the air speed vector and the chutes drag vector. To explore this problem, I had to learn about different coordinate frames used in Guidance, Navigation & Control (J2000, ECEF, ENU, etc.) to describe the motion of a vehicle and about Euler angles (e.g. Roll, Pitch, Yaw) to describe the orientation of the vehicle. With a thorough explanation from my mentor about the description of each coordinate frame, as well as how to use a directional cosine matrix to transform one frame to another, I investigated the problem by simulating different capsule orientations. In the end, I was able to show that this limitation could be avoided if the capsule is initially oriented antiparallel to its velocity vector.

Wong, Chi S.↗

Comments on the commercialization of expendable launch vehicles

The President's national space policy encourages private sector investment and involvement in civil space activities. Last November, the President designated the Department of Transportation as lead agency for the commercialization of expendable launch vehicles. This presents a substantial challenge to the United States Government, since the guidelines and requirements that are set now will have great influence on whether American firms can become a viable competitive industry in the world launch market. There is a dual need to protect public safety and free the private sector launch industry from needless regulatory barriers so that it can grow and prosper.

Trilling, D. R.↗

Robotic Vehicle

A commercially available ANDROS Mark V-A robot was used by Jet Propulsion Laboratory (JPL) as the departure point in the development of the HAZBOT III, a prototype teleoperated mobile robot designed for response to emergencies. Teleoperated robots contribute significantly to reducing human injury levels by performing tasks too hazardous for humans. ANDROS' manufacturer, REMOTEC, Inc., in turn, adopted some of the JPL concepts, particularly the control panel. HAZBOT III has exceptional mobility, employs solid state electronics and brushless DC motors for safer operation, and is designed so combustible gases cannot penetrate areas containing electronics and motors. Other features include the six-degree-of-freedom manipulator, the 30-pound squeeze force parallel jaw gripper and two video cameras, one for general viewing and navigation and the other for manipulation/grasping.

Source record↗

Analysis of Advanced Respiratory Support Onboard ISS and CCV

NASA is collaborating with private entities for the development of commercial space vehicles. The Space and Clinical Operations Division was tasked to review the oxygen and respiratory support system and recommend what capabilities, if any, the vehicle should have to support the return of an ill or injured crewmember. The Integrated Medical Model (IMM) was utilized as a data source for the development of these recommendations. The Integrated Medical Model (IMM) was used to simulate a six month, six crew, International Space Station (ISS) mission. Three medical system scenarios were considered based on the availability of (1) oxygen only, (2) oxygen and a ventilator, or (3) neither oxygen nor ventilator. The IMM analysis provided probability estimates of medical events that would require either oxygen or ventilator support. It also provided estimates of crew health, the probability of evacuation, and the probability of loss of crew life secondary to medical events for each of the three medical system scenarios. These IMM outputs were used as objective data to enable evidence‐based decisions regarding oxygen and respiratory support system requirements for commercial crew vehicles. The IMM provides data that may be utilized to support informed decisions regarding the development of medical systems for commercial crew vehicles.

Shah, Ronak V.↗

A Tailored Concept of Operations for NASA LSP Integrated Operations

An integral part of the Systems Engineering process is the creation of a Concept of Operations (ConOps) for a given system, with the ConOps initially established early in the system design process and evolved as the system definition and design matures. As Integration Engineers in NASA's Launch Services Program (LSP) at Kennedy Space Center (KSC), our job is to manage the interface requirements for all the robotic space missions that come to our Program for a Launch Service. LSP procures and manages a launch service from one of our many commercial Launch Vehicle Contractors (LVCs) and these commercial companies are then responsible for developing the Interface Control Document (ICD), the verification of the requirements in that document, and all the services pertaining to integrating the spacecraft and launching it into orbit. However, one of the systems engineering tools that have not been employed within LSP to date is a Concept of Operations. The goal of this project is to research the format and content that goes into these various aerospace industry ConOps and tailor the format and content into template form, so the template may be used as an engineering tool for spacecraft integration with future LSP procured launch services.

Systems↗

Tailoring a ConOps for NASA LSP Integrated Operations

An integral part of the Systems Engineering process is the creation of a Concept of Operations (ConOps) for a given system, with the ConOps initially established early in the system design process and evolved as the system definition and design matures. As Integration Engineers in NASA's Launch Services Program (LSP) at Kennedy Space Center (KSC), our job is to manage the interface requirements for all the robotic space missions that come to our Program for a Launch Service. LSP procures and manages a launch service from one of our many commercial Launch Vehicle Contractors (LVCs) and these commercial companies are then responsible for developing the Interface Control Document (ICD), the verification of the requirements in that document, and all the services pertaining to integrating the spacecraft and launching it into orbit. However, one of the systems engineering tools that have not been employed within LSP to date is a Concept of Operations. The goal of this paper is to research the format and content that goes into these various aerospace industry ConOps and tailor the format and content into template form, so the template may be used as an engineering tool for spacecraft integration with future LSP procured launch services. This tailoring effort was performed as the authors final Masters Project in the Spring of 2016 for the Stevens Institute of Technology and modified for publication with INCOSE (Owens, 2016).

Knowledge↗

Secure and Safe Assured Autonomy (S2A2)

Aviation’s future will likely see the integration of a wide variety of Advanced Air Mobility (AAM) systems including Unmanned Aerial Systems (UAS) for cargo/delivery, personal air vehicles, and commercial Urban Air Mobility (UAM)vehicles. However, substantial challenges exist that could delay (and possibly prevent) these developments and thus research is needed in a variety of areas to leverage technologies in autonomy, Air Traffic Management (ATM), multi-redundant flight systems architectures, and advanced wireless connectivity like 5G to meet these challenges. The goal of this ULI project is to develop new technologies and innovative operational concepts which will ensure safe, secure and robust integration of autonomous vehicles into Advanced Air Mobility-tailored transportation infrastructure. All this must be done while maintaining inter-operability with current civil air transportation systems and associated safety standards. The project is organized into four Technical Challenges (TCs) areas designed to provide unique UAM solutions and a transition roadmap for industry and government to utilize research product output.

Koushik Datta↗

Visions of tomorrow: A focus on national space transportation issues; Proceedings of the Twenty-fifth Goddard Memorial Symposium, Greenbelt, MD, Mar. 18-20, 1987

The present conference on U.S. space transportation systems development discusses opportunities for aerospace students in prospective military, civil, industrial, and scientific programs, current strategic conceptualization and program planning for future U.S. space transportation, the DOD space transportation plan, NASA space transportation plans, medium launch vehicle and commercial space launch services, the capabilities and availability of foreign launch vehicles, and the role of commercial space launch systems. Also discussed are available upper stage systems, future space transportation needs for space science and applications, the trajectory analysis of a low lift/drag-aeroassisted orbit transfer vehicle, possible replacements for the Space Shuttle, LEO to GEO with combined electric/beamed-microwave power from earth, the National Aerospace Plane, laser propulsion to earth orbit, and a performance analysis for a laser-powered SSTO vehicle.

Soffen, Gerald A.↗

Analysis of the Tropospheric Doppler Radar Wind Profiler Measurement Accuracy

- The Tropospheric Doppler Radar Wind Profiler (TDRWP) is a wind measurement instrument at NASA’s Kennedy Space Center, co-located on the United States Space Force’s (USSF) Eastern Range (ER) at the Cape Canaveral Space Force Station (CCAFS), that generates atmospheric wind profiles which are utilized in the design, certification and operations of various launch vehicles - NASA’s Space Launch System (SLS) - Commercial launch vehicles - NASA Crew-4 in April 2022 was first NASA crewed mission to use TDRWP - Composed of twenty antenna sectors and transmitter unit pairs which operate at 48 MHz - TDRWP data is required for day-of-launch structural margin and performance assessments

Meghan E. Carrico↗

Automated Software for Manned Spacecraft - Bridging the Gap from Sci Fi to Reality

With a voice command or a few taps on the console, the spacecraft pivots on a dime at high velocity and gently docks to an orbiting space platform. This is the image most people have of the complex software computations and integrated hardware performance necessary for a spacecraft to successfully perform an automated launch, rendezvous, and docking. Today’s reality is that while computer operations are advancing rapidly, science fiction over-simplifies and over-sells current capabilities. This paper discusses the integration of spacecraft computer automation into the operation of one of the United States’ new Commercial Crew vehicles - the Boeing CST-100 Starliner. Lessons learned by the Boeing Mission Operations team, a private-public partnership with NASA, from conceptual design through real-time operation of the first test flight will be discussed. Focus will center on how operations has learned to use the automated software to their advantage while also knowing how to adjust the automation in response to spacecraft or mission anomalies. One goal of advanced spacecraft automation is the ability to reduce both the crew workload and the ground control footprint while at the same time increasing spacecraft and mission flexibility. Historically, crewed spacecraft required a large number of operators on the ground to use a plethora of tools to compute nominal and contingency mission trajectories. Moving those sophisticated software tools to being onboard the vehicle can reduce the need for such complex ground support. Given that today’s spacecraft software is not yet as capable or as flexible in all circumstances as the computers depicted in movies, there is usually a trade-off between software automation cost and the flexibility of that software resulting in a trade-off between what is performed on the spacecraft and what is left to onboard crew or ground control. For missions that go beyond the Moon, software that autonomously controls nearly every aspect of a crewed mission will become a necessity given the long time delays between the spacecraft and Earth’s ground control teams. The lessons learned by Boeing and its Mission Operations team, through the design and implementation of Starliner’s hardware and software automation, will be able to inform future public and private spacecraft design. As the technologies and capabilities evolve, incorporating lessons learned in successful low Earth orbit commercial crew vehicle missions, spacecraft designs will continue to improve and be able to better enable safe execution of human missions to the Moon and beyond.

Robert C Dempsey↗

Automated Software for Manned Spacecraft - Bridging the Gap from Sci Fi to Reality

With a voice command or a few taps on the console, the spacecraft pivots on a dime at high velocity and gently docks to an orbiting space platform. This is the image most people have of the complex software computations and integrated hardware performance necessary for a spacecraft to successfully perform an automated launch, rendezvous, and docking. Today’s reality is that while computer operations are advancing rapidly, science fiction over-simplifies and over-sells current capabilities. This paper discusses the integration of spacecraft computer automation into the operation of one of the United States’ new Commercial Crew vehicles - the Boeing CST-100 Starliner. Lessons learned by the Boeing Mission Operations team, a private-public partnership with NASA, from conceptual design through real-time operation of the first test flight will be discussed. Focus will center on how operations has learned to use the automated software to their advantage while also knowing how to adjust the automation in response to spacecraft or mission anomalies. One goal of advanced spacecraft automation is the ability to reduce both the crew workload and the ground control footprint while at the same time increasing spacecraft and mission flexibility. Historically, crewed spacecraft required a large number of operators on the ground to use a plethora of tools to compute nominal and contingency mission trajectories. Moving those sophisticated software tools to being onboard the vehicle can reduce the need for such complex ground support. Given that today’s spacecraft software is not yet as capable or as flexible in all circumstances as the computers depicted in movies, there is usually a trade-off between software automation cost and the flexibility of that software resulting in a trade-off between what is performed on the spacecraft and what is left to onboard crew or ground control. For missions that go beyond the Moon, software that autonomously controls nearly every aspect of a crewed mission will become a necessity given the long time delays between the spacecraft and Earth’s ground control teams. The lessons learned by Boeing and its Mission Operations team, through the design and implementation of Starliner’s hardware and software automation, will be able to inform future public and private spacecraft design. As the technologies and capabilities evolve, incorporating lessons learned in successful low Earth orbit commercial crew vehicle missions, spacecraft designs will continue to improve and be able to better enable safe execution of human missions to the Moon and beyond.

Robert C. Dempsey↗

Automated Software for Crewed Spacecraft - Bridging the Gap from Sci Fi to Reality

With a voice command or a few taps on the console, the spacecraft pivots on a dime at high velocity and gently docks to an orbiting space platform. This is the image most people have of the complex software computations and integrated hardware performance necessary for a spacecraft to successfully perform an automated launch, rendezvous, and docking. Today’s reality is that while computer operations are advancing rapidly, science fiction over-simplifies and over-sells current capabilities. This paper discusses the integration of spacecraft computer automation into the operation of one of the United States’ new Commercial Crew vehicles - the Boeing CST-100 Starliner. Lessons learned by the Boeing Mission Operations team, a private-public partnership with NASA, from conceptual design through real-time operation of the first test flight will be discussed. Focus will center on how operations has learned to use the automated software to their advantage while also knowing how to adjust the automation in response to spacecraft or mission anomalies. One goal of advanced spacecraft automation is the ability to reduce both the crew workload and the ground control footprint while at the same time increasing spacecraft and mission flexibility. Historically, crewed spacecraft required a large number of operators on the ground to use a plethora of tools to compute nominal and contingency mission trajectories. Moving those sophisticated software tools to being onboard the vehicle can reduce the need for such complex ground support. Given that today’s spacecraft software is not yet as capable or as flexible in all circumstances as the computers depicted in movies, there is usually a trade-off between software automation cost and the flexibility of that software resulting in a trade-off between what is performed on the spacecraft and what is left to onboard crew or ground control. For missions that go beyond the Moon, software that autonomously controls nearly every aspect of a crewed mission will become a necessity given the long time delays between the spacecraft and Earth’s ground control teams. The lessons learned by Boeing and its Mission Operations team, through the design and implementation of Starliner’s hardware and software automation, will be able to inform future public and private spacecraft design. As the technologies and capabilities evolve, incorporating lessons learned in successful low Earth orbit commercial crew vehicle missions, spacecraft designs will continue to improve and be able to better enable safe execution of human missions to the Moon and beyond.

Robert C Dempsey↗

Analysis of Alternative Architectures for a 2024 Lunar Sortie

This study focused on performing a broad analysis of lunar architectures to identify key alternatives capable of performing a 2024 human lunar landing mission. The goal of the study was to identify architecture alternatives which exhibit robustness, as measured by launch vehicle payload margin, to absorb the natural growth that occurs during design maturation. The study consisted of up to three element architectures which perform the mission from cis-lunar aggregation, through the surface sortie, and return to cis-lunar space. More than 600,000 data points were evaluated utilizing a novel architecture synthesis framework currently being developed by NASA/MSFC. Key findings from the study indicate that architecture complexity can be reduced by minimizing the number of discrete, unique architecture elements, which in turn translates into reduced design, development, test, and evaluation (DDT&E) complexity. It was identified that heavy lift launch vehicles enable such architectures while also providing significant increases to launch vehicle margin over existing and near-term commercial launch vehicle (CLV) performance expected in the 2024 time frame. Additionally, the study identified storable propellant based lander architectures as leading alternatives in achieving a 2024 human lunar landing by providing reduced technology needs and development schedules.

Architecture Analysis↗

Overview of the Lunar Transit Trajectory Performed by the Power and Propulsion Element of NASA’s Gateway

NASA has committed to returning to the moon, landing the first woman and the next man on its surface. To support a sustained lunar presence, NASA is designing an orbital platform to be assembled in an orbit near the moon called the Near Rectilinear Halo Orbit (NRHO). This platform is known as the Gateway and its purpose it to support missions primarily to the lunar south pole. As NASA continues to study ways to reduce the cost of lunar exploration, a simplification implemented in 2020combinedthe first two elements of the Gateway, the Power and Propulsion Element (PPE) and NASA’s Habitation and Logistics Outpost (HALO), onto a single commercial launch vehicle (CLV). When launched together, the PPE and HALO make up the first two elements of NASA’s Gateway and exceed the performance capacity of commercially available launch vehicles to deliver directly to the moon. The delivery of the Gateway is enabled by and takes advantage of the high efficiency of the PPEs high-power Solar Electric Propulsion (SEP) system to transfer a significant starting mass from an initial Earth orbit to final insertion into the NRHO. The PPE is a 50-kW class high power solar electric propulsion stage comprised of two different types of electric thruster strings. The SEP system is operated in two different modes, a high thrust and high Isp (specific impulse), to both maximize the final delivered mass and attempt to minimize the time spent in the Van Allen Belts early in the transit trajectory. Additionally, this SEP system brings the capability to the assembled Gateway for transfer between orbits in cislunar space. This paper captures the preliminary low thrust lunar transfer reference trajectory to be flown by the PPE it delivers itself and HALO via a spiral trajectory from launch vehicle insertion to insertion into the NRHO as well as a preliminary reference round trip transfer of the Gateway from the NRHO to a Distant Retrograde Orbit (DRO) using the PPE. Once in its final NRHO, the Gateway is being designed to enable long duration human and robotic exploration of the lunar south pole as a precursor to Mars. The Gateway’s low thrust lunar transit trajectory is envisioned to prove out the application of and flight of a high-power SEP system as a demonstration of technologies applicable to the enabling of future human space exploration.

human exploration↗

CFD - Mature Technology?

Over the past 30 years, numerical methods and simulation tools for fluid dynamic problems have advanced as a new discipline, namely, computational fluid dynamics (CFD). Although a wide spectrum of flow regimes are encountered in many areas of science and engineering, simulation of compressible flow has been the major driver for developing computational algorithms and tools. This is probably due to a large demand for predicting the aerodynamic performance characteristics of flight vehicles, such as commercial, military, and space vehicles. As flow analysis is required to be more accurate and computationally efficient for both commercial and mission-oriented applications (such as those encountered in meteorology, aerospace vehicle development, general fluid engineering and biofluid analysis) CFD tools for engineering become increasingly important for predicting safety, performance and cost. This paper presents the author's perspective on the maturity of CFD, especially from an aerospace engineering point of view.

Kwak, Dochan↗

The Federal electric and hybrid vehicle program

The commercial development and use of electric and hybrid vehicles is discussed with respect to its application as a possible alternative transportation system. A market demonstration is described that seeks to place 10,000 electric hybrid vehicles into public and private sector demonstrations.

Schwartz, H. J.↗