Search NASA⌕ Search

SEARCH · Search NASA

Results for “Vehicle development”

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.

696 records · Page 3
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

Artemis I Space Launch System Base Heat Shield Thermal Protection System Performance

The Space Launch System (SLS) Core Stage base heat shield experienced the highest external heating environments on the entire launch vehicle during Artemis I ascent flight. This result was consistent with design predictions. The base heat shield experiences P50 cork combustion dynamics at low altitudes, plume-induced recirculation at moderate altitudes and then in-space base flow physics out to Main Engine Cut-Off (MECO). The base heat shield thermal protection system (TPS) is composed of a P50 cork ablator which is bonded to a substrate. The heat shield protects the gimbal actuation system, RS-25 turbomachinery systems and other aft section sensitive components during ascent. This paper estimates the base heat shield TPS performance from Artemis I using flight data from the NASA Langley Research Center’s Scientifically Calibrated In-Flight Imagery (SCIFLI) Airborne Multispectral Imager (SAMI), development flight instrumentation (DFI) and other TPS recession flight measurements. Predictions from computational and ground test-derived engineering ablation models and observations are also applied. Since no base heat shield substrate thermocouple data were obtained for Artemis I, an estimate of the TPS performance data is derived here. This data assesses thermal margin of the SLS Core Stage base heat shield and best informs the Artemis II Crewed mission to the moon.

aerothermodynamics↗
NASA NTRS1996

Minimum Heating Re-Entry Trajectories for Advanced Hypersonic Launch Vehicles

Optimal re-entry trajectories are generated for reusable launch vehicles which minimize: (1) the heat absorbed at the vehicle surface, (2) the lower surface temperature, and (3) the heat absorbed by the internal structure. The approach uses the energy state approximation technique and a finite control volume heat transfer code coupled to a flight path integration code. These trajectories are compared to the optimal re-entry trajectory minimizing the integrated convective heat rate to determine which trajectory produces the minimum internal structural temperatures for a given thermal protection system. Three different thermal protection systems are considered: tile, blanket, and metallic.

Robert Windhorst↗
NASA NTRS2017

Crewed Space Vehicle Battery Safety Requirements Revision D

The Crewed Space Vehicle Battery Safety Requirements document has been prepared for use by designers of battery-powered vehicles, portable equipment, and experiments intended for crewed spaceflight. The purpose of the requirements document is to provide battery designers with information on design provisions to be incorporated in and around the battery and on the verification to be undertaken to demonstrate a safe battery is provided. The term "safe battery" means that the battery is safe for ground personnel and crew members to handle and use; safe to be used in the enclosed environment of a crewed space vehicle; and safe to be mounted or used in unpressurized spaces adjacent to habitable areas. Battery design review, approval, and certification is required before the batteries can be used for ground operations and be certified for flight.

Russell, Samuel↗
NASA NTRS1962

From Peenemuende to Outer Space

Commemorating the Fiftieth Birthday of Wernher von Braun. Launch vehicles and spacecraft for exploration of space and planets

SPACECRAFT↗
NASA NTRS1993

Piloting Vertical Flight Aircraft: A Conference on Flying Qualities and Human Factors

This document contains papers from a specialists' meeting entitled "Piloting Vertical Flight Aircraft. A Conference on Flying Qualities and Human Factors." The conference was co-sponsored by the American Helicopter Society--San Francisco Bay Chapter, and the NASA Ames Research Center. It was held January 20-22, 1993 at the Sheraton Hotel Fisherman's Wharf, San Francisco, California. Vertical flight aircraft, including helicopters and a variety of Vertical Takeoff and Landing (VTOL) concepts, place unique requirements on human perception, control, and performance for the conduct of their design missions. The intent of this conference was to examine, for these vehicles, advances in: (1) design of flight control systems for ADS-33C standards; (2) assessment of human factors influences of cockpit displays and operational procedures; (3) development of VTOL design and operational criteria; and (4) development of theoretical methods or models for predicting pilot-vehicle performance and mission suitability. Recognizing that human capabilities and limitations form an integral aspect of the operations for these classes of vehicles, a secondary goal of the conference was to provide an initial venue for enhanced interaction between human factors and handling qualities specialists.

Helicopter↗
NASA NTRS2014

Crewed Space Vehicle Battery Safety Requirements

This requirements document is applicable to all batteries on crewed spacecraft, including vehicle, payload, and crew equipment batteries. It defines the specific provisions required to design a battery that is safe for ground personnel and crew members to handle and/or operate during all applicable phases of crewed missions, safe for use in the enclosed environment of a crewed space vehicle, and safe for use in launch vehicles, as well as in unpressurized spaces adjacent to the habitable portion of a space vehicle. The required provisions encompass hazard controls, design evaluation, and verification. The extent of the hazard controls and verification required depends on the applicability and credibility of the hazard to the specific battery design and applicable missions under review. Evaluation of the design and verification program results shall be completed prior to certification for flight and ground operations. This requirements document is geared toward the designers of battery systems to be used in crewed vehicles, crew equipment, crew suits, or batteries to be used in crewed vehicle systems and payloads (or experiments). This requirements document also applies to ground handling and testing of flight batteries. Specific design and verification requirements for a battery are dependent upon the battery chemistry, capacity, complexity, charging, environment, and application. The variety of battery chemistries available, combined with the variety of battery-powered applications, results in each battery application having specific, unique requirements pertinent to the specific battery application. However, there are basic requirements for all battery designs and applications, which are listed in section 4. Section 5 includes a description of hazards and controls and also includes requirements.

Jeevarajan, Judith A.↗
NASA NTRS1999

Battery/Ultracapacitor Evaluation for X-38 Crew Return Vehicle (CRV)

This presentation reported on the evaluation of the battery/ultracapacitor for the crew return vehicle (CRV). The CRV, as part of the international space station (ISS) planning, will be available to return to earth an ill or injured crew person, or if the ISS becomes unsafe, and the shuttle is not available. The requirements of the X-38 CRV are reviewed, and in light of the power requirements, the battery's required performance is reviewed. The ultracapacitor bank, and its test method is described. The test results are reviewed. A picture of the test set up is displayed showing the ultracapacitor bank and the NiMH battery. The presentation continues by reviewing tests of 5 available trade high power cell designs: (1) Hawker lead acid, (2) Bolder lead acid, (3) Energizer NiMH, (4) Sanyo NiCd, and (5) Energizer NiCd. The test methods and results are reviewed. There is also a review of the issues concerning lead acid batteries and conclusions.

Darcy, Eric↗
NASA NTRS2026

Space Suit Material Compatibility with Space Vehicle Coolant PMS-1.5R

During a survey of 82P on February 11, 2023, a shiny substance was detected on the Progress vehicle. The suspected material was PMS-1.5R, a low volatility silicone oil coolant used in the vehicle. Crew exposure to the coolant was a concern as the low volatility would increase residence time, the time a material will stay on a surface after exposure to vacuum. A review of space suit materials revealed several materials with compatibility concerns that could impact Extravehicular Activity (EVA) operations and safety. To understand the risk, space suit materials were exposed to a simulant and tested. This testing provided the basis for rationale generated to continue with EVA operations for US EVA 86 on April 2, 2023. This testing also served as the basis to assess impacts to ISS EMU hardware due to potential contamination brought inside ISS on Russian space suits during RS EVA 61 on October 25, 2023, following an ISS Russian Multipurpose Lab Module (MLM) radiator leak of the same fluid on October 9, 2023. This paper will discuss the testing performed and analyze test results impacts to EVA operations. Additional work was conducted to determine coolant evaporation rates in space vacuum and demonstrate that no significant unreacted coolant from the MLM leak would remain on ISS surfaces long enough to contaminate the EMU or affect the ISS ECLSS water separator.

Space Suit Materials↗
NASA NTRSDate not supplied

Plume Impingement Software Module for Real-Time Proximity Operations

Successfully executing proximity operations in space, such as docking or in-orbit servicing, requires sophisticated spacecraft design that accounts for induced environments. As a chaser vehicle’s attitude control thrusters fire, they create rarefied plumes that can impact the target vehicle, with the potential to overload components, exceed thermal limits, and spin the target vehicle out of control. High-fidelity simulations of the thruster plume impingement environment require the direct simulation Monte Carlo (DSMC) method, but DSMC is too computationally expensive to simulate proximity operations that involve thousands of thruster firings. For this analysis to be tractable, engineering models of the plume flowfield and impingement events are used to simulate these trajectories [1]. Currently, on-orbit plume impingement environments are modeled through an inefficient open-loop analysis cycle where the vehicle’s flight controller and plume impingement teams iterate on the trajectories until they pass the target vehicle’s plume requirements. As complex on-orbit missions evolve and become more frequent, lengthy design cycles will become operational bottlenecks. To address this gap, this work develops an advanced plume impingement module capable of operating at real-time scale that can be integrated with existing mission planning tools and onboard flight systems. The plume module leverages state-of-the-art plume simulation techniques [2] to deliver fast, physics-based impingement predictions in a software architecture that can be tailored to diverse proximity operations scenarios. A prototype of this plume impingement module is built to demonstrate the feasibility of real-time performance. This prototype completes plume impingement calculations in microseconds per target geometry mesh point. The software serves as a foundational capability for plume-aware trajectory design, operational risk assessment, and future autonomous decision-making systems.

Plume Impingement↗
NASA NTRSDate not supplied

Spacecraft Fire Safety Predictions using Verified Saffire Model

A model developed using Fire Dynamics Simulator (FDS) that aimed to determine the effect of a fire in a spacecraft was validated by data collected during the Saffire campaign. The model used inlet and outlet temperatures and CO 2 concentrations of the Saffire payload where fire spread was taking place to determine the amount of heat and combustion products that made it into Northrop Grumman’s Cygnus vehicle. The model was then validated using six remote sensors in various places in the vehicle, as well as a far field device (FFD) in the open zenith section that was representative of average vehicle values. The current work focuses on using the model to predict fire safety scenarios. One simulation aimed to determine the fate of HCl, which sticks to surfaces. The model prediction showed that the HCl was removed from the atmosphere rapidly. This compared well against the FFD data in the Saffire VI campaign event where a bottle of 5% HCl was released into the vehicle. An additional simulation where the Environmental Control and Life Support System (ECLSS) was shut off once the FFD reached 5 ppm of HCl showed that HCl stayed in the atmosphere considerably longer. Continuing the simulation with the ECLSS activated and after temperatures returned to their initial conditions, resulted in a rapid removal of HCL similar to that observed in the original HCl release scenario model. Finally, a simulation that used the heat release rate from a lithium-ion battery test to determine the effect it would have on a spacecraft was performed. This simulation used a heat addition rate that is considerably higher than what was determined from the burning of solid fuels in the Saffire campaign and hence produced a non-trivial temperature increase in more locations within the vehicle.

Fire Safety↗
NASA NTRS2026

Space Nuclear Propulsion for Space Applications: Multi-Mission Nuclear Thermal Propulsion Vehicle Design

This NASA Technical Memorandum (TM) is intended to capture design work that the Advanced Concepts Office (ACO) at NASA’s Marshall Space Flight Center (MSFC) performed on behalf of the Space Nuclear Propulsion (SNP) Project during an SNP-driven design and mission analysis initiative in FY2025. Specifically, this TM focuses on several spacecraft design concepts intended to explore the feasibility of nuclear thermal propulsion (NTP) for use in a selection of notional, unmanned space missions. While references to the missions will be made in this TM, the primary focus will be on the spacecraft design concepts themselves, the ground rules and assumptions used for designing the spacecraft, a description of the various subsystems and their performance parameters, and the methodologies used to design them. The TM will also highlight areas of future work and additional considerations that may need to be taken into account when evaluating the feasibility of NTP space systems for other applications. The report will discuss the results from ACO’s analysis as they pertain to the different vehicle concepts that were evaluated. Each discipline section in this report will discuss the discipline-specific ground rules and assumptions, the methodology and design approaches employed, and present the results along with any relevant discussion, and highlight areas of future work where applicable.

Mitchell A Rodriguez↗
NASA NTRS2010

Ares I-X Ground Diagnostic Prototype

Automating prelaunch diagnostics for launch vehicles offers three potential benefits. First, it potentially improves safety by detecting faults that might otherwise have been missed so that they can be corrected before launch. Second, it potentially reduces launch delays by more quickly diagnosing the cause of anomalies that occur during prelaunch processing. Reducing launch delays will be critical to the success of NASA's planned future missions that require in-orbit rendezvous. Third, it potentially reduces costs by reducing both launch delays and the number of people needed to monitor the prelaunch process. NASA is currently developing the Ares I launch vehicle to bring the Orion capsule and its crew of four astronauts to low-earth orbit on their way to the moon. Ares I-X will be the first unmanned test flight of Ares I. It is scheduled to launch on October 27, 2009. The Ares I-X Ground Diagnostic Prototype is a prototype ground diagnostic system that will provide anomaly detection, fault detection, fault isolation, and diagnostics for the Ares I-X first-stage thrust vector control (TVC) and for the associated ground hydraulics while it is in the Vehicle Assembly Building (VAB) at John F. Kennedy Space Center (KSC) and on the launch pad. It will serve as a prototype for a future operational ground diagnostic system for Ares I. The prototype combines three existing diagnostic tools. The first tool, TEAMS (Testability Engineering and Maintenance System), is a model-based tool that is commercially produced by Qualtech Systems, Inc. It uses a qualitative model of failure propagation to perform fault isolation and diagnostics. We adapted an existing TEAMS model of the TVC to use for diagnostics and developed a TEAMS model of the ground hydraulics. The second tool, Spacecraft Health Inference Engine (SHINE), is a rule-based expert system developed at the NASA Jet Propulsion Laboratory. We developed SHINE rules for fault detection and mode identification. The prototype uses the outputs of SHINE as inputs to TEAMS. The third tool, the Inductive Monitoring System (IMS), is an anomaly detection tool developed at NASA Ames Research Center and is currently used to monitor the International Space Station Control Moment Gyroscopes. IMS automatically "learns" a model of historical nominal data in the form of a set of clusters and signals an alarm when new data fails to match this model. IMS offers the potential to detect faults that have not been modeled. The three tools have been integrated and deployed to Hangar AE at KSC where they interface with live data from the Ares I-X vehicle and from the ground hydraulics. The outputs of the tools are displayed on a console in Hangar AE, one of the locations from which the Ares I-X launch will be monitored. In a previous publication, we discussed how we selected the three tools based primarily on their ability to be certified for human spaceflight and described our plans for the prototype. This abstract is due October 23, 2009, and the Ares I-X launch is currently scheduled for October 27, 2009. If this abstract is accepted, then the full paper will describe how the prototype performed before the launch. It will include an analysis of the prototype's accuracy, including false-positive rates, false-negative rates, and receiver operating characteristics (ROC) curves. It will also include a description of the prototype's computational requirements, including CPU usage, main memory usage, and disk usage. If the prototype detects any faults during the prelaunch period then the paper will include a description of those faults. Similarly, if the prototype has any false alarms then the paper will describe them and will attempt to explain their causes. Also, the paper will describe the three tools and how they are used in the prototype. It will include a description of the TEAMS models of the Ares I-X first-stage TVC and associated ground hydraulics and how we adapted the TVC model for use in real-time diagnostics. It will describe the SHINE rules used for fault detection and mode identification and the software architecture that interfaces the various pieces of existing software that are part of the prototype to one another. It will describe how we selected the sensor values and commands that were used to train the IMS model and how we optimized the number of clusters in the IMS model. It will include screen shots of the graphical display that we developed in Java to display the outputs of the three tools. Because Ares I-X data was not yet available to us while we were developing the prototype, we used historical data from the Space Shuttle's Solid Rocket Booster (SRB) TVCs and the associated ground hydraulics to train IMS and to test the entire prototype. Because most of the failure modes that we modeled have never occurred in the Shuttle we inserted simulated failures into the Shuttle data. The Ares I-X first-stage TVC is very similar to the SRB TVC and we expect the data will be very similar. After the launch, we will determine how similar the data actually is and report how any differences in the data affected the diagnostic accuracy of the prototype. Finally, although we did not get the prototype certified, we designed it in a way that it could be certified and wrote a preliminary certification plan. The paper will include a brief summary of how we considered the need for certification in the design of the prototype, how we tested the prototype before deploying it to Hangar AE, and how we would propose to get it certified if it were deployed as an operational system. The paper will conclude with a description of some of the challenges we faced and some of the lessons learned in developing and deploying the prototype.

International Space Station↗
NASA NTRS2009

General Purpose Data-Driven Monitoring for Space Operations

As modern space propulsion and exploration systems improve in capability and efficiency, their designs are becoming increasingly sophisticated and complex. Determining the health state of these systems, using traditional parameter limit checking, model-based, or rule-based methods, is becoming more difficult as the number of sensors and component interactions grow. Data-driven monitoring techniques have been developed to address these issues by analyzing system operations data to automatically characterize normal system behavior. System health can be monitored by comparing real-time operating data with these nominal characterizations, providing detection of anomalous data signatures indicative of system faults or failures. Data-driven techniques have a number of advantages over other methods for monitoring complex space vehicles. Unlike model-based systems, the developer does not need to understand or encode the internal operation of the system. The knowledge required to monitor the system is automatically derived from archived data from system operation. Unlike rule-based systems, data-driven systems do not require system analysts to define nominal relationships among sensors. Analysts can and often do determine these relationships for a system with few sensors; it is more difficult to analytically determine the nominal relationship among a large number of sensors. Data-driven techniques are not limited to low-dimensional spaces and work as effectively with dozens of parameters as they do with a few. Knowledge bases formed by data-driven techniques are also easy to update. As the operating envelope of the monitored system is expanded, data-driven techniques can be quickly retrained to incorporate the new behavior into the knowledge base. The expertise and time-consuming process of updating a model or rule base to maintain consistency with the new operation is not required. The Inductive Monitoring System (IMS) is a data-driven system health monitoring software tool that has been successfully applied to several aerospace applications. IMS uses a data mining technique called clustering to analyze archived system data and characterize normal interactions between parameters. This characterization, or model, of nominal operation is stored in a knowledge base that can be used for real-time system monitoring or analysis of archived events. System data is compared with the nominal IMS model to produce a measure of how well current system behavior matches the normal behavior defined by the training data. Significant deviations from the nominal system model can provide alerts to system malfunctions or precursors of significant failures. The scope of IMS based data-driven monitoring applications continues to expand with current development activities. Successful IMS deployment in the International Space Station (ISS) flight control room to monitor ISS attitude control systems has led to applications in other ISS flight control disciplines, such as thermal control. It has also generated interest in data-driven monitoring capability for Constellation, NASA's program to replace the Space Shuttle with new launch vehicles and spacecraft capable of returning astronauts to the moon, and then on to Mars. Several projects are currently underway to evaluate and mature the IMS technology and complementary tools for use in the Constellation program. These include an experiment on board the Air Force TacSat-3 satellite, and ground systems monitoring for NASA's Ares I-X and Ares I launch vehicles. The TacSat-3 Vehicle System Management (TVSM) project is a software experiment to integrate fault and anomaly detection algorithms and diagnosis tools with executive and adaptive planning functions contained in the flight software on-board the Air Force Research Laboratory TacSat-3 satellite. The TVSM software package will be uploaded after launch to monitor spacecraft subsystems such as power and guidance, navigation, and control (GN&C). It will analyze data in real-time to demonstrate detection of faults and unusual conditions, diagnose problems, and react to threats to spacecraft health and mission goals. The experiment will demonstrate the feasibility and effectiveness of integrated system health management (ISHM) technologies with both ground and on-board experiments. Initially, the TVSM software will run open loop, providing system health information and recommendations to ground operators, without automatically performing fault-mitigating corrective actions. After the end of the satellite's mission, closed loop tests combining TVSM monitoring and diagnosis with reactive capabilities by the flight software will be performed. In addition to monitoring for long periods of actual operation, the experiment will include fault injection into TacSat-3 data as well as commanded operations to test and evaluate automatic ISHM monitoring and recovery under controlled conditions.

Satellites↗
NASA NTRSDate not supplied

SERENE: Saturn Enceladus Return Explorer with Nuclear Electric Propulsion

A ‘quick’ Enceladus sample return mission concept was developed based on the scientist recommendations at the recent ‘Accelerating Space Science with Nuclear Technology Workshop’. The Nuclear Electric Propulsion spacecraft assumed a follow-on 40 kWe nuclear reactor using the demonstrated 40 kWe Fission Surface Power system, expected in the early 2030s. The NEP vehicle also utilized a set of NEXT-C ion thrusters as well as planned Artemis commercial launchers. By launching the 40 kW NEP vehicle on a Starship and adding the propellants of 15 tankers, the 27t probe could be sent on a direct trajectory to Saturn (no Earth or Jupiter flybys) where NEP was used for Saturn capture, spiral down, spiral up and return to the Earth. A small lander obtained the surface Enceladus sample. Using the 40 kW NEP provided a round-trip time of only 16.5 years. A second option was more attractive from a science perspective whereby the NEP vehicle would deliver a large, 6t chemical lander to low Enceladus orbit where it would grab and return a sample to Earth (similar to the recent Orbilander design but in reverse). After deploying the lander, the NEP vehicle would stay in Saturn space performing a moon tour by orbiting four more moons and mapping the large moon of Titan. This option took slightly longer (18.5 yrs) due to the chemical return leg limitations. Both options demonstrated the agility, payload capability, and sample return goals the workshop recommended. An all-chemical option with two stages was roughly analyzed but took 21.5 yrs and required a Jupiter gravity assist.

Nuclear Electric Propulsion↗
NASA NTRS1997

Future Aerospace Technology in the Service of the Alliance: Sustained Hypersonic Flight - Volume 3

Sustained Hypersonic Flight capability is envisioned for several future military and civilian applications, such as long range immediate reaction reconnaissance, high speed interception of air targets, long range precision strike against hardened or time critical targets, and access to space. The inherent reduction in time-to-target and low vulnerability will permit new operational tactics. The symposium outlined mission needs and operational scenarios for hypersonic vehicles. Addressed were: Technological issues and challenges in external hypersonic aerodynamics and design, propulsion and engine/airframe integration, military ramjet applications, overall system design including structures and materials development needs, and test facilities. Ground based test facilities cannot provide full simulation at Mach numbers above 5. Therefore, the use of Computational Fluid Dynamics design tools is essential. For routine use of the computational tools in analysis, design and optimization, it is necessary to reduce the time for the entire computational process by two orders of magnitude. Hypersonic boundary layer transition remains a critical design issue because of the important impact on engine drag and on heating, which can affect the choice of materials and thermal protection systems. In addition, reliable prediction of scramjet net thrust is an absolute must in resolving hypersonic air breathing vehicle design issues. Due to current facility and computational shortfalls, the development of future hypersonic flight systems requires research flight tests in the technology areas of boundary layer transition and air-breathing propulsion engine performance. For sustained hypersonic flight beyond Mach 6, the supersonic combustion ramjet (scramjet) engine is the only choice for the near future. Only this air-breathing concept offers a significant promise of large reductions in required propellant fractions, increased payload fractions, and reduced size vehicles, together with a foreseeable technological feasibility. Airframe/engine integration, combustor design and thermal management are the predominant engineering tasks. Fuels, hydrogen or hydrocarbon, must be matched to the operational needs of military or civil use. Experience in existing ramjet propelled missiles capable of speeds up to Mach 4 can support the development effort. The potential mission and cost benefits of sustained hypersonic flight to both military and civil applications are tremendous. From the budget point of view, the possibility of sharing development costs between military and civil programs offers a specific advantage.

Combustion chambers↗
NASA NTRS1988

Integrated Inverter And Battery Charger

Circuit combines functions of dc-to-ac inversion (for driving ac motor in battery-powered vehicle) and ac-to-dc conversion (for charging battery from ac line when vehicle not in use). Automatically adapts to either mode. Design of integrated inverter/charger eliminates need for duplicate components, saves space, reduces weight and cost of vehicle. Advantages in other applications : load-leveling systems, standby ac power systems, and uninterruptible power supplies.

Rippel, Wally E.↗
NASA NTRS2026

Helicopter and Urban Air Mobility (UAM) Laboratory Comparison (HULC) Psychoacoustic Test

The Helicopter and Urban Air Mobility (UAM) Laboratory Comparison (HULC) psychoacoustic test was conducted in July 2025 to compare human annoyance responses to noise from UAM vehicles and helicopters. This document provides a literature review, describes the HULC test methodology including stimuli selection and test administration procedures, and presents results from an initial analysis using multilevel statistical modeling. The test utilized 123 sound stimuli from four helicopters and six UAM vehicles across three flight phases (departure, cruise, and approach), presented to 40 subjects in the Exterior Effects Room (EER) at NASA's Langley Research Center. Subjects rated their annoyance on a 0 to 10 scale while imagining hearing these sounds multiple times daily near their homes. Key findings revealed that, at the same A-weighted sound exposure levels, UAM vehicles and helicopters produced similar annoyance responses across all flight phases, with mean differences of only approximately 1 dB and overlapping confidence intervals. However, at equivalent observer distances, UAM vehicles had inherently quieter operations and lower mean annoyance ratings. These results suggest that UAM vehicles and helicopters may be assessed in a similar manner for community noise impact. The quieter noise characteristics of UAM vehicles may provide advantages for operating in communities and integrating into urban environments.

psychoacoustics↗