SEARCH · Search NASA
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.
Contents include the following: 3 Listing of critical capabilities (knowledge, procedures, training, facilities) and metrics for validating that they are mission ready. Examples of critical capabilities and validation metrics: ground test and simulations. Flight testing to prove capabilities are mission ready. Issues and recommendations.
The NASA Goddard Space Flight Center is working to develop a revolutionary new system architecture concept in support of fully autonomous missions. As part of GSFC's contribution to the New Millenium Program (NMP) Space Technology 7 Autonomy and on-Board Processing (ST7-A) Concept Definition Study, the system incorporates the latest commercial Internet and software development ideas and extends them into NASA ground and space segment architectures. The unique challenges facing the exploration of remote and inaccessible locales and the need to incorporate corresponding autonomy technologies within reasonable cost necessitate the re-thinking of traditional mission architectures. A measure of the resiliency of this architecture in its application to a broad range of future autonomy missions will depend on its effectiveness in leveraging from commercial tools developed for the personal computer and Internet markets. Specialized test stations and supporting software come to past as spacecraft take advantage of the extensive tools and research investments of billion-dollar commercial ventures. The projected improvements of the Internet and supporting infrastructure go hand-in-hand with market pressures that provide continuity in research. By taking advantage of consumer-oriented methods and processes, space-flight missions will continue to leverage on investments tailored to provide better services at reduced cost. The application of ground and space segment architectures each based on Local Area Networks (LAN), the use of personal computer-based operating systems, and the execution of activities and operations through a Wide Area Network (Internet) enable a revolution in spacecraft mission formulation, implementation, and flight operations. Hardware and software design, development, integration, test, and flight operations are all tied-in closely to a common thread that enables the smooth transitioning between program phases. The application of commercial software development techniques lays the foundation for delivery of product-oriented flight software modules and models. Software can then be readily applied to support the on-board autonomy required for mission self-management. An on-board intelligent system, based on advanced scripting languages, facilitates the mission autonomy required to offload ground system resources, and enables the spacecraft to manage itself safely through an efficient and effective process of reactive planning, science data acquisition, synthesis, and transmission to the ground. Autonomous ground systems in turn coordinate and support schedule contact times with the spacecraft. Specific autonomy software modules on-board include mission and science planners, instrument and subsystem control, and fault tolerance response software, all residing within a distributed computing environment supported through the flight LAN. Autonomy also requires the minimization of human intervention between users on the ground and the spacecraft, and hence calls for the elimination of the traditional operations control center as a funnel for data manipulation. Basic goal-oriented commands are sent directly from the user to the spacecraft through a distributed internet-based payload operations "center". The ensuing architecture calls for the use of spacecraft as point extensions on the Internet. This paper will detail the system architecture implementation chosen to enable cost-effective autonomous missions with applicability to a broad range of conditions. It will define the structure needed for implementation of such missions, including software and hardware infrastructures. The overall architecture is then laid out as a common thread in the mission life cycle from formulation through implementation and flight operations.
This paper presents an analysis of the unit testing approach developed and used by the Core Flight Software (CFS) product line team at the NASA GSFC. The goal of the analysis is to understand, review, and reconunend strategies for improving the existing unit testing infrastructure as well as to capture lessons learned and best practices that can be used by other product line teams for their unit testing. The CFS unit testing framework is designed and implemented as a set of variation points, and thus testing support is built into the product line architecture. The analysis found that the CFS unit testing approach has many practical and good solutions that are worth considering when deciding how to design the testing architecture for a product line, which are documented in this paper along with some suggested innprovennents.
NASA Ames Research Center is home to several high-fidelity research flight and air-traffic control simulation facilities which, together with an experienced workforce, produce high-quality research data and findings that have proven to be applicable in the real world. These assets include the Vertical Motion Simulator (VMS), Crew Vehicle Systems Research Facility (CVSRF), Future Flight Central (FFC) air traffic control tower simulator, and several air-traffic control (ATC) simulators. The VMS combines a high-fidelity simulation capability with an adaptable simulation environment, enabling customization for numerous human-in-the-loop research applications. The distinctive feature of the VMS is its unparalleled large amplitude, high-fidelity motion capability. In over 30 years of continuous operation, the VMS has contributed significantly to the body of knowledge in a range of disciplines directly benefiting several aerospace programs and flight safety, including the design and development of flight control systems for the Joint Strike Fighter, Space Shuttle Orbiter, and rotorcraft. It continues to be used for researching new vehicle configurations, vehicle control and safety, transfer-of-training, etc., by NASA, other government agencies, and Industry.The CVSRF includes two motion-based flight simulators: a Boeing 747-400 full flight simulator and the reconfigurable Advanced Concepts Flight Simulator (ACFS). These simulators are primarily used to research air-traffic management concepts and procedures, advanced navigation and avionics concepts, and cockpit human factors. FFC is a full-sized control tower simulator with a 360-degree external field-of-view display system and reconfigurable system architecture. FFC and the ATC simulators are used for testing air-traffic management automation and decision support tools and demonstrate their feasibility in a realistic environment prior to technology transfer for implementation in the National Airspace System (NAS).To support integrated simulations and flight-tests for NASA's Unmanned Aircraft Systems (UAS) in the National Airspace System (NAS) Project, NASA developed a distributed test environment incorporating Live, Virtual, Constructive, (LVC) concepts. Development of the software enabling the LVC is conducted primarily at the Distributed Simulation Research Lab (DSRL) at NASA Ames. The LVC components provide the core infrastructure supporting simulation of UAS operations by integrating live and virtual aircraft in a realistic air traffic environment. This provides the ability to conduct tests more efficiently by promoting the use of existing distributed assets. The LVC infrastructure was used in several human-in-the-loop simulations to evaluate acceptance of Detect and Avoid (DAA) advisories used by UAS pilots to maintain well clear of other virtual traffic and to negotiate maneuvers with air traffic control. It is currently being used to support testing of self-separation algorithms between unmanned and manned aircraft in live flight. Further simulations with more comprehensive air traffic scenarios mixing live and virtual aircraft is planned.In the current fiscal environment, maintaining and upgrading these high-fidelity simulation assets and retaining the skilled workforce necessary to meet future research needs is the primary non-technical challenge.
In anticipation of a projected rise in demand for air transportation, NASA and the FAA are researching new air-traffic-management (ATM) concepts that fall under the paradigm known broadly as ":free flight". This paper documents the software development and engineering efforts in progress by Seagull Technology, to develop a free-flight simulation (FFSIM) that is intended to help NASA researchers test mature-state concepts for free flight, otherwise referred to in this paper as distributed air / ground traffic management (DAG TM). Under development is a distributed, human-in-the-loop simulation tool that is comprehensive in its consideration of current and envisioned communication, navigation and surveillance (CNS) components, and will allow evaluation of critical air and ground traffic management technologies from an overall systems perspective. The FFSIM infrastructure is designed to incorporate all three major components of the ATM triad: aircraft flight decks, air traffic control (ATC), and (eventually) airline operational control (AOC) centers.
The design, development and trials of a satellite telephone system for airline passengers is described. The requirements for ground and space infrastructure are discussed and the aeronautical system is described. Design criteria for the antennas and avionic boxes are given and system operation and technical flight trial requirements are discussed, together with test methodology and development towards fully commercial trials. Finally, an indication of development requirements to achieve the desired aims of airline users is given.
The goal of the Advanced Communications for Air Traffic Management (AC/ATM) Project at the NASA Glenn Research Center at Lewis Field is to enable a communications infrastructure that provides the capacity, efficiency, and flexibility necessary to realize a mature free-flight environment. The technical thrust of the AC/ATM Project is targeted at the design, development, integration, test, and demonstration of enabling technologies for global broadband aeronautical communications. Since Ku-band facilities and equipment are readily available, one of the near-term demonstrations involves a link through a Kuband communications satellite. Two conformally mounted antennas will support the initial AC/ATM communications links. Both of these are steered electronically through monolithic microwave integrated circuit (MMIC) amplifiers and phase shifters. This link will be asymmetrical with the downlink to the aircraft (mobile vehicle) at a throughput rate of greater than 1.5 megabits per second (Mbps), whereas the throughput rate of the uplink from the aircraft will be greater than 100 kilobits per second (kbps). The data on the downlink can be narrow-band, wide-band, or a combination of both, depending on the requirements of the experiment. The AC/ATM project is purchasing a phased-array Ku-band transmitting antenna for the uplink from the test vehicle. Many Ku-band receiving antennas have been built, and one will be borrowed for a short time to perform the initial experiments at the NASA Glenn Research Center at Lewis Field. The Ku-band transmitting antenna is a 254-element MMIC phased-array antenna being built by Boeing Phantom Works. Each element can radiate 100 mW. The antenna is approximately 43-cm high by 24-cm wide by 3.3-cm thick. It can be steered beyond 60 from broadside. The beamwidth varies from 6 at broadside to 12 degrees at 60 degrees, which is typical of phased-array antennas. When the antenna is steered to 60 degrees, the beamwidth will illuminate approximately five satellites on the orbital arc. Spread spectrum techniques will be employed to keep the power impinging on the adjacent satellites below their noise floor so that no interference results. This antenna is power limited. If the antenna elements (currently 254) are increased by a factor of 4 (1024) or 16 (4096), the gain will increase and the beamwidth will decrease in proportion. For the latter two antenna sizes, the power must be "backed off" to prevent interference with the neighboring satellites. The receiving antenna, which is approximately 90-cm high, 60-cm wide, and 3.5-cm thick, is composed of 1500 phased-array elements. The system phased-array controller can control both a 1500-element receiving antenna and a 500-element transmitting antenna. For ground testing, this controller will allow manual beam pointing and polarization alignment. For normal operation, the system can be connected to the receiving antenna and the navigation system for real-time autonomous track operation. This will be accomplished by first pointing both antennas at the satellite using information from the aircraft data bus. Then, the system phased-array controller will electronically adjust the antenna pointing of the receiving antenna to find the peak signal. After the peak signal has been found, the beam of the transmitting antenna will be pointed to the same steering angles as the receiving antenna. For initial ground testing without an aircraft, the ARINC 429 data bus (ARINC Inc., Annapolis, Maryland) will be simulated by a gyro system purchased for the follow-on to the Monolithic Microwave Integrated Circuit (MMIC) Arrays for Satellite Communication on the Move (MASCOM) Project. MASCOM utilized the Advanced Communications Technology Satellite (ACTS) with a pair of Ka-band experimental phased-array antennas.
This presentation provides information on the development, integration, and operational usage of the Enhanced Flight Termination System (EFTS) at NASA Dryden Flight Research Center and Air Force Flight Test Center. The presentation will describe the efforts completed to certify the system and acquire approval for operational usage, the efforts to integrate the system into the NASA Dryden existing flight termination infrastructure, and the operational support of aircraft with EFTS at Edwards AFB.
NASA's Morpheus Project has developed and tested a prototype planetary lander capable of vertical takeoff and landing. Designed to serve as a vertical testbed (VTB) for advanced spacecraft technologies, the vehicle provides a platform for bringing technologies from the laboratory into an integrated flight system at relatively low cost. This allows individual technologies to mature into capabilities that can be incorporated into human exploration missions. The Morpheus vehicle is propelled by a LOX/Methane engine and sized to carry a payload of 1100 lb to the lunar surface. In addition to VTB vehicles, the Project s major elements include ground support systems and an operations facility. Initial testing will demonstrate technologies used to perform autonomous hazard avoidance and precision landing on a lunar or other planetary surface. The Morpheus vehicle successfully performed a set of integrated vehicle test flights including hot-fire and tethered hover tests, leading up to un-tethered free-flights. The initial phase of this development and testing campaign is being conducted on-site at the Johnson Space Center (JSC), with the first fully integrated vehicle firing its engine less than one year after project initiation. Designed, developed, manufactured and operated in-house by engineers at JSC, the Morpheus Project represents an unprecedented departure from recent NASA programs that traditionally require longer, more expensive development lifecycles and testing at remote, dedicated testing facilities. Morpheus testing includes three major types of integrated tests. A hot-fire (HF) is a static vehicle test of the LOX/Methane propulsion system. Tether tests (TT) have the vehicle suspended above the ground using a crane, which allows testing of the propulsion and integrated Guidance, Navigation, and Control (GN&C) in hovering flight without the risk of a vehicle departure or crash. Morpheus free-flights (FF) test the complete Morpheus system without the additional safeguards provided during tether. A variety of free-flight trajectories are planned to incrementally build up to a fully functional Morpheus lander capable of flying planetary landing trajectories. In FY12, these tests will culminate with autonomous flights simulating a 1 km lunar approach trajectory, hazard avoidance maneuvers and precision landing in a prepared hazard field at the Kennedy Space Center (KSC). This paper describes Morpheus integrated testing campaign, infrastructure, and facilities, and the payloads being incorporated on the vehicle. The Project s fast pace, rapid prototyping, frequent testing, and lessons learned depart from traditional engineering development at JSC. The Morpheus team employs lean, agile development with a guiding belief that technologies offer promise, but capabilities offer solutions, achievable without astronomical costs and timelines.
Wind tunnel free-flight tests of a small quadrotor vehicle were completed in the NASA Langley 12-Foot Low Speed Tunnel and 20-Foot Vertical Spin Tunnel. The primary objective of these tests was to acquire flight data in forward and descending flight for the purpose of assessing the fidelity of an all-attitude flight dynamics simulation previously developed from static and dynamic wind tunnel data. A secondary objective was to demonstrate and mature free-flight test methods specific to the emerging class of small unmanned aircraft and urban air mobility vehicles. Experimental flight data correlated well with simulation predictions which included steady trim conditions consistent with straight and level flight and quasi-steady conditions associated with descent velocities prone to vortex ring state development. The test method was shown to be well suited to these classes of vehicles and several unique infrastructure requirements, including tether systems and data acquisition requirements were identified. In addition, unique operational test techniques and safety procedures were developed to accommodate the testing. Results of these tests will be used to support air traffic management studies and research into safety assurance concepts that enable the integration of these classes of vehicles into the National Airspace System.
The Enhanced Flight Termination System (EFTS) program was initiated and propelled due to the inadvertent terminations of Global Hawk and the Strategic Target System and the NASA Inspector General's assessment letter and recommendations regarding the exploration of low-cost, lightweight space COMSEC for FTS. Additionally, the standard analog and high alphabet systems most commonly used in FTS are secure, but not encrypted. A study group was initiated to select and document a robust, affordable, reliable technology that provides encrypted FTS capability. A flight demonstration was conducted to gain experience using EFTS in an operational environment, provide confidence in the use of the EFTS components, integrate EFTS into an existing range infrastructure to demonstrate the scalability of system components, to provide a command controller that generated the EFTS waveform using an existing range infrastructure, and to provide a report documenting the results of the demonstration. The primary goal of the demonstration was to obtain operational experience with EFTS. Areas of operational experience include: mission planning, pre-flight configuration and testing, mission monitoring and recording, vehicle termination, developing mission procedures. and post mission data reduction and other post mission activities. An Advanced Medium-Range Air-to-Air Missile (AMRAAM) was selected to support the EFTS demonstration due to interest in future use of EFTS by the AMRAAM program, familiarity of EFTS by range personnel, and the availability of existing operational environment to support EFTS testing with available program funding. For demonstration purposes, the AMRAAM was successfully terminated using an EFTS receiver and successfully demonstrating EFTS. The EFTS monitoring software with spectrum analyzer and digital graphical display of aircraft, missile, and target were also demonstrated.
This paper addresses the need to predict the flight energy consumption of aerial vehicles in the presence of wind using machine learning techniques. The presented work is critical to achieving sustainable and efficient operations for Advanced Air Mobility (AAM) and to evaluating the readiness of the ground-supporting energy infrastructure, e.g., electric grid and AAM portals. The flight energy consumption is described using the "energy per meter" (EPM) metric. We present a comparison study of influential machine learning techniques in predicting EPM using real-world flight test data. We presented new results of using the Decision Tree, Random Forest, and linear regression techniques, along with our previous results using the Recurrent Neural Network and Feed Forward Neural Network techniques. The comparison results show that the Linear Regression method outperforms other methods on the basis of the Mean Squared Error and error variance.
With the Constellation Program, NASA is entering a new age of space exploration that will take us back to the Moon, to Mars, and beyond, and NASA is developing the new technology and vehicles to take us there. At the forefront are the Orion spacecraft and the Ares I launch vehicle. As NASA's gateway to space, Kennedy Space Center (KSC) will process and launch the new vehicles. This will require new systems and extensive changes to existing infrastructure. KSC is designing a new mobile launcher, a new launch control system, and new ground support equipment; modifying the Vehicle Assembly Building, one of the launch pads, and other facilities; and launching the Ares I-X flight test. It is an exciting and challenging time to be an engineer at KSC.
Exploration beyond Earth will be an enduring legacy for future generations, confirming America's commitment to explore, learn, and progress. NASA's Space Launch System (SLS) Program, managed at the Marshall Space Flight Center, is responsible for designing and developing the first exploration-class rocket since the Apollo Program's Saturn V that sent Americans to the Moon. The SLS offers a flexible design that may be configured for the MultiPurpose Crew Vehicle and associated equipment, or may be outfitted with a payload fairing that will accommodate flagship science instruments and a variety of high-priority experiments. Both options support a national capability that will pay dividends for future generations. Building on legacy systems, facilities, and expertise, the SLS will have an initial lift capability of 70 metric tons (mT) and will be evolvable to 130 mT. While commercial launch vehicle providers service the International Space Station market, this capability will surpass all vehicles, past and present, providing the means to do entirely new missions, such as human exploration of asteroids and Mars. With its superior lift capability, the SLS can expand the interplanetary highway to many possible destinations, conducting revolutionary missions that will change the way we view ourselves, our planet and its place in the cosmos. To perform missions such as these, the SLS will be the largest launch vehicle ever built. It is being designed for safety and affordability - to sustain our journey into the space age. Current plans include launching the first flight, without crew, later this decade, with crewed flights beginning early next decade. Development work now in progress is based on heritage space systems and working knowledge, allowing for a relatively quick start and for maturing the SLS rocket as future technologies become available. Together, NASA and the U.S. aerospace industry are partnering to develop this one-of-a-kind asset. Many of NASA's space centers across the country will provide their unique expertise to the Space Launch System endeavor. Unique infrastructure to be used includes the Michoud Assembly Facility for tank manufacturing, Stennis Space Center for engine testing, and Kennedy Space Center for processing and launch. As this panel will discuss, the SLS team is dedicated to doing things differently-from applying lean oversight/insight models to smartly using legacy hardware and existing facilities. Building on the foundation laid by over 50 years of human and scientific space flight--and on the lessons learned from the Apollo, Space Shuttle, and Constellation Programs-the SLS team has delivered both technical trade studies and business case analyses to ensure that the SLS architecture will be safe, affordable, reliable, and sustainable.
This paper describes how the Orion program is utilizing the Thermal Protection System (TPS) experience from the Apollo and Space Shuttle programs to reduce program risk and improve affordability to meet NASA's future manned exploration missions. The Orion program successfully completed the Exploration Flight Test (EFT-1) mission in 2014 and is currently assembling, integrating, and testing the next spacecraft for the Exploration Mission (EM-1) to meet the flight test objectives of an unmanned orbital mission to the moon and return to earth in 2019. The Orion spacecraft production operations are located in the Neil Armstrong Operations and Checkout (O&C) facility at the Kennedy Space Center (KSC) providing an affordable and seamless delivery approach of vehicles directly to the launch site eliminating spacecraft transportation and additional checkout testing. Innovative vehicle design, manufacturing and test operations approaches are maturing and evolving with each Orion vehicle build to support the challenging NASA exploration mission requirements beyond Low Earth Orbit (LEO) while reducing program cost and schedule impacts. An example of Orion's evolution is the incorporation of an improved heat shield design, assembly and testing approach to meet the higher re-entry velocities for a lunar return for the EM-1 mission. The EFT- 1 heat shield was based on the Apollo heat shield manufacturing processes and was assembled at a supplier location and then transported to KSC for final integration. The EM-1 heat shield is now manufactured, assembled, tested, and installed into the spacecraft at the O&C facility reducing program cost and production schedules. The transition of the Space Shuttle TPS capabilities has enabled Orion to provide a human rated capsule design using proven materials and processes established over years of orbiter re-entry missions. The Orion Crew Module (CM) TPS configuration is derived from the Apollo CM approach utilizing improved materials and processes developed from the Space Shuttle program. The Orion EFT-1 heat shield utilized the Avcoat ablative material from Apollo which was injected into a honeycomb substrate and has been updated for EM-1 incorporating a block configuration bonded to a composite shell structure. This approach utilizes the proven Avcoat material for the heat shield ablator and is utilizing derived bonding and inspection methods and techniques from the Space Shuttle tile experience. The Orion back shell TPS configuration is based on Space Shuttle tile designs using proven tile materials and coatings. The Orion forward bay cover utilizes the high temperature tiles similar to the back shell tiles and low temperature blankets derived from the Space Shuttle program reducing weight impacts. Space Shuttle Multi-Layer Insulation (MLI) is installed in the Orion capsule to control the interior temperature environment providing a light weight design. These TPS design approaches have performed successfully on the Orion first flight test on EFT-1 and are incorporated in the configuration for the next flight test for EM-1. Completion of these two flight tests will certify the TPS for the Orion program for human rated exploration missions and has reduced the development cost to the Orion program. In addition to transitioning the Space Shuttle TPS design configurations to Orion, the supporting manufacturing infrastructure, manufacturing processes, and inspection methods are also incorporated into the Orion assembly operations at KSC. This has avoided significant startup schedule and costs impacts of new capabilities and development of support operations necessary to fabricate, install, inspect, and validate the TPS installations for the Orion spacecraft. The Thermal Protection System Facility (TPSF) which supported the Space Shuttle program provides the heat shield Avcoat blocks and the back shell AETB-8 tiles for Orion program. Extending the existing Space Shuttle TPS operations at KSC provides onsite support to the Orion spacecraft assembly operations. A significant benefit to the Orion program is the transition of the Space Shuttle technician work force at KSC. This highly skilled workforce was able to transition to the Orion program and immediately support the TPS installation operations. They brought with them the human rated manufacturing and assembly operations culture that was critical to the Space Shuttle success avoiding the retraining cost and schedule impacts of a new workforce to Orion. The technician skills certification program from the Space Shuttle was found to be compatible with the Lockheed Martin technician certification programs enabling a seamless training process utilizing process similarity avoiding the cost of retraining the work force to Orion standards. The existing workforce is certificated for multiple processes enabling reassignment of technicians to other tasks in the Orion AI&P operations reducing the overall touch labor manpower requirements. Additional benefits of using the Space Shuttle workforce is the incorporation of the lessons learned from Space Shuttle processes to improve the Orion TPS processes. This has resulted in a continuous evolution of TPS processes to improve the producibility and reduce the program cost for the TPS for the Orion program. Transitioning the Apollo and Space Shuttle TPS designs, processes, and technician workforce has been instrumental in enabling Orion to successfully meet the program challenges for NASA's exploration missions of the future.
This discussion will focus on the development and implementation cycles and their respective challenges of accommodating and integrating with Space Shuttle Operations. There is a difference during the development and implementation cycles while trying to still operate an ongoing program within the same facilities and infrastructure. Due to this unique environment requirements are generated from outside Ares I-X that have significant impacts on design and implementation of those designs. Impacts are technical, schedule, and cost. So in this unique environment besides dealing with changing test flight vehicle changes the system (hardware and team members) must be flexible enough to accommodate operational and manifest changes while still maintaining delivery and performance requirements. The purpose of this session will be to highlight some of these challenges and identify the lessons learned from this experience.
The desire and ability to fly Unmanned Aircraft Systems (UAS) in the National Airspace System (NAS) is of increasing urgency. The application of unmanned aircraft to perform national security, defense, scientific, and emergency management are driving the critical need for less restrictive access by UAS to the NAS. UAS represent a new capability that will provide a variety of services in the government (public) and commercial (civil) aviation sectors. The growth of this potential industry has not yet been realized due to the lack of a common understanding of what is required to safely operate UAS in the NAS. NASA's UAS Integration in the NAS Project is conducting research in the areas of Separation Assurance/Sense and Avoid Interoperability (SSI), Human Systems Integration (HSI), and Communications (Comm), and Certification to support reducing the barriers of UAS access to the NAS. This research is broken into two research themes namely, UAS Integration and Test Infrastructure. UAS Integration focuses on airspace integration procedures and performance standards to enable UAS integration in the air transportation system, covering Detect and Avoid (DAA) performance standards, command and control performance standards, and human systems integration. The focus of Test Infrastructure is to enable development and validation of airspace integration procedures and performance standards, including integrated test and evaluation. In support of the integrated test and evaluation efforts, the Project will develop an adaptable, scalable, and schedulable relevant test environment capable of evaluating concepts and technologies for unmanned aircraft systems to safely operate in the NAS. To accomplish this task, the Project is conducting a series of human-in-the-loop (HITL) and flight test activities that integrate key concepts, technologies and/or procedures in a relevant air traffic environment. Each of the integrated events will build on the technical achievements, fidelity, and complexity of the previous tests and technical simulations, resulting in research findings that support the development of regulations governing the access of UAS into the NAS. The integrated events started with two initial flight test used to develop and test early integrations and components of the test environment. Test subjects and a relevant test environment were brought in for the integrated HITL (or IHITL) conducted in 2014. The IHITL collected data to evaluate the effectiveness of DAA Well Clear (DWC) algorithms and the acceptability of UAS concepts integrated into the NAS. The first integrated flight test (and the subject of this report) followed the IHITL by replacing the simulation components with live aircraft. The project finishes the integrated events with a final flight test to be conducted in 2016 that provides the researchers with an opportunity to collect DWC and Collision Avoidance (CA) interoperability data during flight encounters.
This slide presentation reviews the use of modular infrastructure to assist in the development of flight software. A feature of this program is the use of model based approach for application unique software. A review of two programs that this approach was use on are: the development of software for Hover Test Vehicle (HTV), and Lunar Atmosphere and Dust Environment Experiment (LADEE).