Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “LANDING SYSTEM”

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 649 records · Page 36

MLS/Airplane system design. RF component design

Results of analysis and design conducted as part of multiyear Microwave Landing System (MLS) study are reported. Design of airborne radio frequency RF MLS components was performed. MLS omnidirectional antennas are developed using microstrip technology. A remote, low-noise, radio frequency (RF) preamplifier is designed for airborne MLS installations.

Walen, D. B.↗

Analysis of DGPS/INS and MLS/INS final approach navigation errors and control performance data

Flight tests were conducted jointly by NASA Langley Research Center and Honeywell, Inc., on a B-737 research aircraft to record a data base for evaluating the performance of a differential DGPS/inertial navigation system (INS) which used GPS Course/Acquisition code receivers. Estimates from the DGPS/INS and a Microwave Landing System (MLS)/INS, and various aircraft parameter data were recorded in real time aboard the aircraft while flying along the final approach path to landing. This paper presents the mean and standard deviation of the DGPS/INS and MLS/INS navigation position errors computed relative to the laser tracker system and of the difference between the DGPS/INS and MLS/INS velocity estimates. RMS errors are presented for DGPS/INS and MLS/INS guidance errors (localizer and glideslope). The mean navigation position errors and standard deviation of the x position coordinate of the DGPS/INS and MLS/INS systems were found to be of similar magnitude while the standard deviation of the y and z position coordinate errors were significantly larger for DGPS/INS compared to MLS/INS.

Hueschen, Richard M.↗

Airplane takeoff and landing performance monitoring system

The invention is a real-time takeoff and landing performance monitoring system which provides the pilot with graphic and metric information to assist in decisions related to achieving rotation speed (V sub R) within the safe zone of the runway or stopping the aircraft on the runway after landing or take off abort. The system processes information in two segments: a pretakeoff segment and a real-time segment. One-time inputs of ambient conditions and airplane configuration information are used in the pretakeoff segment to generate scheduled performance data. The real-time segment uses the scheduled performance data, runway length data and transducer measured parameters to monitor the performance of the airplane throughout the takeoff roll. An important feature of this segment is that it updates the estimated runway rolling friction coefficient. Airplane performance predictions also reflect changes in headwind occurring as the takeoff roll progresses. The system displays the position of the airplane on the runway, indicating runway used and runway available, summarizes the critical information into a situation advisory flag, flags engine failures and off-nominal acceleration performance, and indicates where on the runway particular events such as decision speed (V sub 1), rotation speed (V sub R) and expected stop points will occur based on actual or predicted performance. The display also indicates airspeed, wind vector, engine pressure ratios, second segment climb speed, and balanced field length (BFL). The system detects performance deficiencies by comparing the airplane's present performance with a predicted nominal performance based upon the given conditions.

Middleton, David B.↗

Large Vehicle Lunar Landing Surface Interaction and In-Situ Resource Based Risk Mitigation: Landing & Launch Pads

A key capability required for the exploration of planetary bodies is the ability to land on the surface. Previous work performed by NASA and other institutions has primarily focused on landing small spacecraft on planetary surfaces and the associated small-to-medium thrusters required for the soft landing. In the case of human exploration—particularly the establishment of long duration exploration and habitation outposts—the ability to land large landers, such as the SpaceX Starship, is necessary. These larger landing systems require the use of more powerful engines, with higher engine exhaust temperatures and higher landing loads. Understanding the excavation of material by the engines, as well as the potential for the landing legs to sink into the subsurface, is key in ensuring reliable and safe landings. A further improvement in landing reliability can be achieved by constructing landing / launch pads, especially with in-situ resources. Some material excavation by the plume is inevitable, leaving at least a portion of the surface scoured and uneven under the lander and ejecting regolith particles and rocks at very high velocities. One possible solution would be to robotically build landing / launch pads (ideally autonomously) at the destination using in-situ materials. In this case, the first one or few landers will need to land on unimproved surfaces at higher risk; however, they would bring the required equipment to build the landing pads with mostly local resources, thus increasing the reliability of safe landing for subsequent larger landers. A number of methods to build in-situ landing and launch pads have already been developed. These methods include no or some addition of required binder additives to the local regolith material, different processing approaches and result in varying landing pad strengths. A sub-scale rocket engine plume, was used to simulate some of the conditions of a landing on the Moon to assess the effectiveness of various materials for an in-situ built landing pad, The GO2/GCH4 rocket engine fired on 1m2 area coupons of representative pad materials. The results will allow continued development towards materials that satisfy the landing pad properties required for the effective risk reduction and increased reliability for landing people and equipment on the lunar surface. This work contained two parts: (1) computer modeling of a large rocket engine plume interacting with regolith on the Moon, using the Granular Gas Flow Solver (GGFS) provided by CFD Research Corporation as well as other computational fluid dynamics codes (CFD) such as Loci/CHEM. (2) Developing landing/launch pad materials that could be used for in-situ construction on the lunar surface in the future, to mitigate the calculated effects of a large vehicle rocket engine landing and launching on the Moon. The resulting computed values of plume impingement surface temperature, stagnation pressure, gas velocity, shear stress and heat flux were then matched as closely as possible in the Earth’s atmosphere in a sub-scale rocket engine GO2/CH4 test which was provided by Masten Space Systems in Mojave, California. The rocket engine was mounted on a test stand with vertical translation capabilities so that the landing operations of a lander could be simulated (Figure 1).The pad materials test coupons were placed at the surface of a large bin containing simulated lunar basalt regolith and subjected to a test firing as shown in Figure 2. The results of this testing will be presented with related findings, analysis and discussion.

Plume Surface Interaction↗

Distributed Sensing and Computer Vision Methods for Advanced Air Mobility Approach and Landing

Advanced Air Mobility (AAM) aircraft require precision approach and landing systems (PALS) in several types of environments such as urban, suburban, and rural. It is difficult to implement current state-of-the-art methods approved for automated approach and landing for AAM operations. However, existing technology and systems that use vision, IR, radar, and GPS methods provide baseline perception and sensing requirements for AAM aircraft approach and landing. This paper focuses on vision-based PAL and computer vision feature correspondence methods to demonstrate a baseline navigation system while adhering to the Federal Aviation Administration requirements and regulations. The coplanar algorithm determines pose estimation, which feeds into an Extended Kalman filter that combines IMU with vision to create a sensor fusion navigation solution for GPS-denied environments. The state estimate leads to glideslope and localizer error computations, which will be pertinent for designing and deriving guidance laws and control laws for AAM PALS. The IMU and vision navigation solution provides promising simulation results for AAM PALS. This paper builds on previous work by incorporating high fidelity simulations with computer graphics rendering to demonstrate a distributed sensor network to track an AAM aircraft during approach and landing to compare with the aircraft's onboard navigation solution.

Evan Kawamura↗

FPGA Sequencer for Radar Altimeter Applications

A sequencer for a radar altimeter provides accurate attitude information for a reliable soft landing of the Mars Science Laboratory (MSL). This is a field-programmable- gate-array (FPGA)-only implementation. A table loaded externally into the FPGA controls timing, processing, and decision structures. Radar is memory-less and does not use previous acquisitions to assist in the current acquisition. All cycles complete in exactly 50 milliseconds, regardless of range or whether a target was found. A RAM (random access memory) within the FPGA holds instructions for up to 15 sets. For each set, timing is run, echoes are processed, and a comparison is made. If a target is seen, more detailed processing is run on that set. If no target is seen, the next set is tried. When all sets have been run, the FPGA terminates and waits for the next 50-millisecond event. This setup simplifies testing and improves reliability. A single vertex chip does the work of an entire assembly. Output products require minor processing to become range and velocity. This technology is the heart of the Terminal Descent Sensor, which is an integral part of the Entry Decent and Landing system for MSL. In addition, it is a strong candidate for manned landings on Mars or the Moon.

Berkun, Andrew C.↗

Adaptive Independent Verification and Validation (IV&V) Reduces Risk of Software Impacting Safety in Artemis Missions

The National Aeronautics and Space Administration (NASA) is asking more of its human spaceflight programs than ever before through the collective Artemis Missions. The NASA Independent Verification and Validation (IV&V) Program contributes to NASA’s human spaceflight goals by providing IV&V services for NASA’s critical spacecraft and ground software. The IV&V Program is tasked with providing assurance from both individual and integrated mission software perspectives. The Artemis IV&V organization is actively supporting six distinct development efforts: Orion, the Space Launch System (SLS), Exploration Ground Systems (EGS), Mission Control Center (MCC), the Lunar Gateway, and the Human Landing System (HLS), representing a wide diversity of developer organizations, management structures, and development approaches. With much of this extremely complex flight and ground software being essential to human safety both on the ground and in space, Artemis IV&V is likewise challenged to provide more value-added assurance to future Artemis missions within a constrained budget. To meet this challenge, Artemis IV&V employs a variety of novel and evolving “Adaptive IV&V” approaches for planning and executing IV&V analysis to increase both the efficiency and effectiveness of the IV&V Program’s assurance activities, and to address the difficulties imposed by assuring software for a large, highly integrated, multi-mission enterprise managed and executed by physically and organizationally distinct programs. Instilling agile principles like iterative planning cycles, self-organizing teams, and regular retrospectives, into IV&V planning and execution has led to a more rapid turnaround of a minimum viable assurance product and allowed for increased alignment of assurance activities with development progress. Adopting an assurance case methodology has led to greater consistency and clearer communication of assurance design and provided a foundation for long-term maintenance of assurance plans, products, and results across missions. The IV&V-developed Assurance / Safety Case Analytical Network (A-SCAN) framework and tool has enabled the quantification and tracking of system/software risk and confidence. These confidence measures provide a means to repeatedly express the impact of planned and completed assurance work and the remaining residual risk. Applied as part of a “Follow-the-Risk” organizational ethos, this allows consistent rightsizing of analysis rigor and intensity commensurate with the perceived risk of defects, as well as appropriate targeting of the highest risk areas of the software to find safety issues before they can manifest. Finally, the development of the IV&V Advanced Risk Reduction Integrated Software Test and Operations Tri-program Lightweight Environment (ARRISTOTLE), an integrated software-only simulation of Orion, SLS, and EGS systems, has made it possible to independently test integrated pad and flight scenarios and inject faults to observe how the Artemis multi-program, mission software behaves in degraded modes and in response to hazards. These adaptive IV&V investments have enabled Artemis IV&V to become more efficient and effective in IV&V planning and execution and respond more readily to changes in the risk landscape, increasing the breadth and depth of risk reduction possible within the available resources. Residual risk tracking allows IV&V to communicate more effectively with stakeholders, both internal and external at all levels, and inform key decision-making personnel. This evolving assurance design approach provides IV&V surety that work is performed in the highest risk, most value-added areas of the software, to keep our astronauts and ground crews safe and ensure mission success.

Gerek A Whitman↗

Adaptive Independent Verification and Validation (IV&V) Reduces Risk of Software Impacting Safety in Artemis Missions

The National Aeronautics and Space Administration (NASA) is asking more of its human spaceflight programs than ever before through the collective Artemis Missions. The NASA Independent Verification and Validation (IV&V) Program contributes to NASA’s human spaceflight goals by providing IV&V services for NASA’s critical spacecraft and ground software. The IV&V Program is tasked with providing assurance from both individual and integrated mission software perspectives. The Artemis IV&V organization is actively supporting six distinct development efforts: Orion, the Space Launch System (SLS), Exploration Ground Systems (EGS), Mission Control Center (MCC), the Lunar Gateway, and the Human Landing System (HLS), representing a wide diversity of developer organizations, management structures, and development approaches. With much of this extremely complex flight and ground software being essential to human safety both on the ground and in space, Artemis IV&V is likewise challenged to provide more value-added assurance to future Artemis missions within a constrained budget. To meet this challenge, Artemis IV&V employs a variety of novel and evolving “Adaptive IV&V” approaches for planning and executing IV&V analysis to increase both the efficiency and effectiveness of the IV&V Program’s assurance activities, and to address the difficulties imposed by assuring software for a large, highly integrated, multi-mission enterprise managed and executed by physically and organizationally distinct programs. Instilling agile principles like iterative planning cycles, self-organizing teams, and regular retrospectives, into IV&V planning and execution has led to a more rapid turnaround of a minimum viable assurance product and allowed for increased alignment of assurance activities with development progress. Adopting an assurance case methodology has led to greater consistency and clearer communication of assurance design and provided a foundation for long-term maintenance of assurance plans, products, and results across missions. The IV&V-developed Assurance / Safety Case Analytical Network (A-SCAN) framework and tool has enabled the quantification and tracking of system/software risk and confidence. These confidence measures provide a means to repeatedly express the impact of planned and completed assurance work and the remaining residual risk. Applied as part of a “Follow-the-Risk” organizational ethos, this allows consistent rightsizing of analysis rigor and intensity commensurate with the perceived risk of defects, as well as appropriate targeting of the highest risk areas of the software to find safety issues before they can manifest. Finally, the development of the IV&V Advanced Risk Reduction Integrated Software Test and Operations Tri-program Lightweight Environment (ARRISTOTLE), an integrated software-only simulation of Orion, SLS, and EGS systems, has made it possible to independently test integrated pad and flight scenarios and inject faults to observe how the Artemis multi-program, mission software behaves in degraded modes and in response to hazards. These adaptive IV&V investments have enabled Artemis IV&V to become more efficient and effective in IV&V planning and execution and respond more readily to changes in the risk landscape, increasing the breadth and depth of risk reduction possible within the available resources. Residual risk tracking allows IV&V to communicate more effectively with stakeholders, both internal and external at all levels, and inform key decision-making personnel. This evolving assurance design approach provides IV&V surety that work is performed in the highest risk, most value-added areas of the software, to keep our astronauts and ground crews safe and ensure mission success.

Gerek Whitman↗

A flight-test and simulation evaluation of the longitudinal final approach and landing performance of an automatic system for a light wing loading STOL aircraft

As part of a comprehensive flight-test program of STOL operating systems for the terminal area, an automatic landing system was developed and evaluated for a light wing loading turboprop aircraft. The aircraft utilized an onboard advanced digital avionics system. Flight tests were conducted at a facility that included a STOL runway site with a microwave landing system. Longitudinal flight-test results were presented and compared with available (basically CTOL) criteria. These comparisons were augmented by results from a comprehensive simulation of the controlled aircraft which included representations of navigation errors that were encountered in flight and atmospheric disturbances. Acceptable performance on final approach and at touchdown was achieved by the autoland (automatic landing) system for the moderate winds and turbulence conditions encountered in flight. However, some touchdown performance goals were marginally achieved, and simulation results suggested that difficulties could be encountered in the presence of more extreme atmospheric conditions. Suggestions were made for improving performance under those more extreme conditions.

Brown, S. C.↗

Airplane takeoff and landing performance monitoring system

The invention is a real-time takeoff and landing performance monitoring system for an aircraft which provides a pilot with graphic and metric information to assist in decisions related to achieving rotation speed (VR) within the safe zone of a runway, or stopping the aircraft on the runway after landing or take-off abort. The system processes information in two segments: a pretakeoff segment and a real-time segment. One-time inputs of ambient conditions and airplane configuration information are used in the pretakeoff segment to generate scheduled performance data. The real-time segment uses the scheduled performance data, runway length data and transducer measured parameters to monitor the performance of the airplane throughout the takeoff roll. Airplane acceleration and engine-performance anomalies are detected and annunciated. A novel and important feature of this segment is that it updates the estimated runway rolling friction coefficient. Airplane performance predictions also reflect changes in head wind occurring as the takeoff roll progresses. The system provides a head-down display and a head-up display. The head-up display is projected onto a partially reflective transparent surface through which the pilot views the runway. By comparing the present performance of the airplane with a continually predicted nominal performance based upon given conditions, performance deficiencies are detected by the system and conveyed to pilot in form of both elemental information and integrated information.

Middleton, David B.↗

Airplane takeoff and landing performance monitoring system

The invention is a real-time takeoff and landing performance monitoring system for an aircraft which provides a pilot with graphic and metric information to assist in decisions related to achieving rotation speed (V.sub.R) within the safe zone of a runway, or stopping the aircraft on the runway after landing or take-off abort. The system processes information in two segments: a pretakeoff segment and a real-time segment. One-time inputs of ambient conditions and airplane configuration information are used in the pretakeoff segment to generate scheduled performance data. The real-time segment uses the scheduled performance data, runway length data and transducer measured parameters to monitor the performance of the airplane throughout the takeoff roll. Airplane acceleration and engine-performance anomalies are detected and annunciated. A novel and important feature of this segment is that it updates the estimated runway rolling friction coefficient. Airplane performance predictions also reflect changes in head wind occurring as the takeoff roll progresses. The system provides a head-down display and a head-up display. The head-up display is projected onto a partially reflective transparent surface through which the pilot views the runway. By comparing the present performance of the airplane with a continually predicted nominal performance based upon given conditions, performance deficiencies are detected by the system and conveyed to pilot in form of both elemental information and integrated information.

Middleton, David B.↗

Airplane takeoff and landing performance monitoring system

The invention is a real-time takeoff and landing performance monitoring system for an aircraft which provides a pilot with graphic and metric information to assist in decisions related to achieving rotation speed (V.sub.R) within the safe zone of a runway, or stopping the aircraft on the runway after landing or take-off abort. The system processes information in two segments: a pretakeoff segment and a real-time segment. One-time inputs of ambient conditions and airplane configuration information are used in the pretakeoff segment to generate scheduled performance data. The real-time segment uses the scheduled performance data, runway length data and transducer measured parameters to monitor the performance of the airplane throughout the takeoff roll. Airplane and engine performance deficiencies are detected and annunciated. A novel and important feature of this segment is that it updates the estimated runway rolling friction coefficient. Airplane performance predictions also reflect changes in head wind occurring as the takeoff roll progresses. The system provides a head-down display and a head-up display. The head-up display is projected onto a partially reflective transparent surface through which the pilot views the runway. By comparing the present performance of the airplane with a predicted nominal performance based upon given conditions, performance deficiencies are detected by the system.

Middleton, David B.↗

Facilities and capabilities catalog for landing and escape systems

This catalog serves as a single source reference for designers of landing and escape systems for spacecraft, aircraft, weapons, and airdrop system. It includes those facilities which may be required by a system designer in planning a development test program for many applications. The primary objective of this catalog is to provide a means for identifying critical facilities with the U.S. which can be used for the development of landing and escape systems. A secondary objective is to provide a useful tool to the system designer for picking and choosing facilities and capabilities. The six chapters in this volume include wind tunnels, drop zones, test aircraft, fabrication facilities, design tools, and other miscellaneous facilities. A different data sheet format is used for each of the chapters which provides information on performance, location, special capabilities, and a local point of contact. All inputs were solicited from the individual facilities and have not been independently verified for accuracy.

Meyerson, Robert E.↗

An evaluation of the MSBLS/nose boom interference for the approach and landing test

An analysis was performed to investigate whether or not the obstruction caused by boom-mounted probes forward of the Orbiter nose could cause Microwave Scan Beam Landing System (MSBLS) data dropout during the autoland flight phase of the Approach and Landing Test (ALT). The results indicate that there will be no interference from the nose boom to cause MSBLS data dropout for the flight conditions under which the ALT is to be performed. Additional analysis considering approach trajectories in more extreme wind conditions than anticipated for the ALT also indicates that the nose boom creates no interference.

Tate, J. M.↗

Saving Space and Time: The Tractor That Einstein Built

In 1984, NASA initiated the Gravity Probe B (GP-B) program to test two unverified predictions of Albert Einstein s theory of general relativity, hypotheses about the ways space, time, light, and gravity relate to each other. To test these predictions, the Space Agency and researchers at Stanford University developed an experiment that would check, with extreme precision, tiny changes in the spin direction of four gyroscopes contained in an Earth satellite orbiting at a 400-mile altitude directly over the Earth s poles. When the program first began, the researchers assessed using Global Positioning System (GPS) technology to control the attitude of the GP-B spacecraft accurately. At that time, the best GPS receivers could only provide accuracy to nearly 1 meter, but the GP-B spacecraft required a system 100 times more accurate. To address this concern, researchers at Stanford designed high-performance, attitude-determining hardware that used GPS signals, perfecting a high-precision form of GPS called Carrier-Phase Differential GPS that could provide continuous real-time position, velocity, time, and attitude sensor information for all axes of a vehicle. The researchers came to the realization that controlling the GP-B spacecraft with this new system was essentially no different than controlling an airplane. Their thinking took a new direction: If this technology proved successful, the airlines and the Federal Aviation Administration (FAA) were ready commercial markets. They set out to test the new technology, the "Integrity Beacon Landing System," using it to automatically land a commercial Boeing 737 over 100 times successfully through Real-Time Kinematic (RTK) GPS technology. The thinking of the researchers shifted again, from automatically landing aircraft, to automating precision farming and construction equipment.

Source record↗

Moon to Mars (M2M) Cross Program Utilization Payload Safety Process

It is the goal of Moon to Mars (M2M) to establish a single consolidated set of safety requirements and a safety review process for utilization payloads that will cross program vehicle hatches or operate externally on multiple program vehicles during transport or operation that satisfies Exploration Ground Systems (EGS), Orion, EVA, and Human Surface Mobility Program (EHP), Gateway (GW), and Human Landing System (HLS) programs. This document defines the Cross Program Utilization Payload (xPUP) safety review process for mission effectivity of Artemis III and beyond. This review process will help ensure protection of the overall Moon to Mars integrated system from potential hazards created by cross program payloads that either cross a program vehicle hatch or can interface with more than one M2M lunar exploration program vehicle. The process will identify payload hazards and controls that will protect ground personnel, flight crew, the integrated vehicle, ground equipment, or facilities. This process is also applicable to samples that cross hatches between vehicles including for return to Earth. The xPUP safety review process will be led by one of the M2M programs' integration safety panels, chosen on a per-payload basis. After the lead integration safety panel is determined, the common safety process is established, based on pre-determined criteria, which includes ad-hoc members from other stakeholder programs. Stakeholder programs are those that interface with the utilization payload in any way (e.g., operating on a lunar exploration vehicle or crossing program vehicle hatches). The xPUP will execute this safety review process for flight and ground utilization payload hardware design, its ground support equipment, and landing and recovery in accordance with the applicable safety requirements as specified in M2M-30043: Moon to Mars Cross Program Utilization Payload Safety Requirements. The xPUP safety process will follow the lead integration safety panel’s safety process requirements. Formal agreements will be communicated with the payload developer using the payload integration processes documented in M2M-30037, Artemis Payload Integration Implementation Plan.

payloads↗

Output Data: gcam_usa_v5p3_im3

Output databases and tables supporting the publication: Khan, Z., Zhao, M., Ahsan, H., Wolfram, P., Vernon, C., Rice, J., Iyer, G., Binsted, M., Snyder, A., Graham, N., Kyle, P., 2023. Coevolution of future water, energy and land systems across the United States in response to national and global socioeconomic, climate, and energy policy drivers. (In progress) Earths Future, DOI: XXX with further details available at the meta-repository: https://immm-sfa.github.io/khan-etal_2023_im3gcamusa Folder: gcam_usa_im3_outputs (GCAM USA v 5.3 used for IM3 experiment Output Databases): database_rcp45cooler_ssp3.tar.gz database_rcp45cooler_ssp5.tar.gz database_rcp45hotter_ssp5.tar.gz database_rcp45hotter_ssp5.tar.gz database_rcp85cooler_ssp3.tar.gz database_rcp85cooler_ssp5.tar.gz database_rcp85hotter_ssp5.tar.gz database_rcp85hotter_ssp5.tar.gz Folder: gcam_usa_im3_gcamextractor_outputs (gcamextractor post-processing of the GCAM databases for specific downstream models ): dataGCAM_cerf.tar.gz (For CERF Model) dataGCAM_demeter.tar.gz (For Demeter model) dataGCAM_go.tar.gz (For GO model) gcamDataTable.tar.gz (All IM3 scenarios)

Climate Change↗