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.
We have studied the ATN (Aeronautical telecommunications Network) in term of its architecture, its current applications, and its suitability in meeting the needs of Low-Visibility Landing and Surface Operations (LVLASO) system being developed by NASA. This report summarizes our findings.
The current air traffic environment in airport terminal areas experiences substantial delays when weather conditions deteriorate to Instrument Meteorological Conditions (IMC). Expected future increases in air traffic will put additional pressures on the National Airspace System (NAS) and will further compound the high costs associated with airport delays. To address this problem, NASA has embarked on a program to address Terminal Area Productivity (TAP). The goals of the TAP program are to provide increased efficiencies in air traffic during the approach, landing, and surface operations in low-visibility conditions. The ultimate goal is to achieve efficiencies of terminal area flight operations commensurate with Visual Meteorological Conditions (VMC) at current or improved levels of safety.
Recently the Low Visibility Landing and Surface Operations (LVLASO) project team of the Systems Integration Branch at the NASA Langley Research Center completed a flight demonstration of TAP/ASTA concepts at the Atlantic City airport. This paper is concerned with the analysis of the aircraft data that was recorded by the test vehicle during the duration of the flight demonstrations.
This paper describes the software written for the VO Concentrator Unit in support of the Low Visibility Landing and Surface Operations (LVLASO) experiment flown on-board NASA's Boeing 757 aircraft.
As part of this research, we have modeled the Mode-S system when used to enhance communications among several ground vehicles to facilitate low-visibility landing and surface operations. The model has then been simulated using Bones Designer software. The effectiveness of the model has been evaluated under several conditions: (i) different number of vehicles (100, 200, and 300), (ii) different distributions of interarrival times for squitters: uniform, exponential, and constrained exponential, and (iii) Different safe distances (for collision purpose): squitter length, 1.5*squitter length, and 2* squitter length. The model has been developed in a modular fashion to facilitate any future modifications. The results from the simulations suggest that the Mode S system is indeed capable of functioning satisfactorily even when covering up to 300 vehicles. Certainly, about 10 percent of the squitters undergo collisions and hence the interarrival times for these is much larger than the expected time of 500 msec. In fact, the delay could be as much as 2 seconds. The model could be further enhanced to incorporate more realistic scenarios.
Low-visibility Landing and Surface Operations System (LVLASO) is currently being prototyped and tested at NASA Langley Research Center. Since the main objective of the system is to maintain the aircraft landings and take-offs even during low-visibility conditions, timely exchange of positional and other information between the aircraft and the ground control is critical. For safety and reliability reasons, there are several redundant sources on the ground (e.g., ASDE, AMASS) that collect and disseminate information about the environment to the aircrafts. The data link subsystem of LVLASO is responsible for supporting the timely transfer of information between the aircrafts and the ground controllers. In fact, if not properly designed, the data link subsystem could become a bottleneck in the proper functioning of LVLASO. Currently, the other components of the system are being designed assuming that the data link has adequate capacity and is capable of delivering the information in a timely manner. During August 1-28, 1997, several flight experiments were conducted to test the prototypes of subsystems developed under LVLASO project, The back-round and details of the tests are described in the next section. The test results have been collected in two CDs by FAA and Rockwell-Collins. Under the current grant, we have analyzed the data and evaluated the performance of the Mode S datalink. In this report, we summarize the results of our analysis. Much of the results are shown in terms of graphs or histograms. The test date (or experiment number) was often taken as the X-axis and the Y-axis denotes whatever metric of focus in that chart. In interpreting these charts, one need to take into account the vehicular traffic during a particular experiment. In general, the performance of the data link was found to be quite satisfactory in terms of delivering long and short Mode S squitters from the vehicles to the ground receiver, Similarly, its performance in delivering control messages from the ground control to the vehicles (aircrafts) was also satisfactory. The report is organized as follows. In Section 2, we describe the background information for the LVLASO and the system flight experiments. Section 3 contains formats of the performance data that was analyzed during our research. Section 4 describes different experiments flight experiments and their setup. Section 5 analyzes each of the graphs produced in this report. Finally, Section 6 has a summary of observations that we make based on our research.
The paper addresses the issue of the vertical distribution of aerosol in the troposphere and the relation to causative mechanisms. The focus is on visible wavelength, aerosol extinction cross sections. A background on the state of knowledge will be presented, but the emphasis is on experimental results from several field programs, The GLOBE project (GLobal aerosol Backscatter Experiment) involved a series of flights by the NASA DC-8 throughout the Pacific basin region with comprehensive in situ and multi-spectral lidar aerosol distribution measurements. The data has been extensively analyzed. The results show the existence of a background mode for aerosol loading in the troposphere and a pattern of distribution for transport and boundary layer aerosol for the Pacific region. The ARM (Atmospheric Radiation Measurement) program, operates surface based monitoring sites. For several years at sites in the central great plains and northern coast of Alaska of North America and a site in the tropical western Pacific have been acquiring comprehensive radiation measurements including multispectral aerosol optical thickness and near continuous lidar profiling. Data have been analyzed for typical and special case aerosol events including smoke aerosol from biomass burning for the tropical West Pacific site. Measurements with continuous lidar and multispectral were similarly acquired from a site at Tenerife, Canary Islands during the Aerosol Characterization Experiment and include analysis of the Saharan dust layer. Various measurements will be compared and summarized.
The primary objective of the Mars 2003/2005 Sample Return Project is to return Martian surface materials to Earth from two different sites by the year 2008. The baseline mission plan relies heavily on the use of a Mars orbit rendezvous strategy similar to the lunar orbit rendezvous scheme used for the Apollo missions. The 2003 mission consists of a single spacecraft comprised of a Lander, Rover, and Mars ascent vehicle (MAV). The 2003 mission will be launched on a Delta-III-class launch vehicle in May/June 2003 and arrive at Mars in December 2003/January 2004. The Lander deploys the Rover to collect surface samples from several sites and return them to the Lander where they are transferred to a sample canister onboard the MAV. The MAV is launched into a low Mars orbit (targeted for 600 km circular, 45 deg inclination) and releases the sample canister to await retrieval by an Orbiter launched in 2005. (The sample canister is a passive vehicle with no maneuvering capability.) The duration of Mars surface operations is at most about 90 days. The 2005 mission consists of two separate spacecraft: a Lander/Rover/MAV spacecraft identical to that used for the 2003 mission and an Orbiter carrying an Earth Entry Vehicle (EEV). Both spacecraft will be launched on a single Ariane-5 in August 2005 and arrive at Mars in July/August 2006. A second sample canister is delivered to Mars orbit using the same scenario as was used for the 2003 mission. The Orbiter uses aerocapture for insertion into Mars orbit (targeted for 250 x 1400 km, 45 deg inclination). During its approximately one-year stay at Mars, the Orbiter will search for and attempt to rendezvous first with the 2003 sample canister and then with the 2005 sample canister. After retrieval, each sample canister is transferred to the EEV. The Orbiter departs Mars in July 2007 and returns to Earth in October 2008 on a trajectory targeted for landing at the Utah Test and Training Range (UTTR). After deploying the EEV, the Orbiter performs a deflection maneuver to avoid reentry into Earth's atmosphere.
The architecture of NASA's program of robotic Mars exploration missions received an intense scrutiny during the summer months of 1998. We present here the results of that scrutiny, and describe a list of Mars exploration missions which are now being proposed by the nation's space agency. The heart of the new program architecture consists of missions which will return samples of Martian rocks and soil back to Earth for analysis. A primary scientific goal for these missions is to understand Mars as a possible abode of past or present life. The current level of sophistication for detecting markers of biological processes and fossil or extant life forms is much higher in Earth-based laboratories than possible with remotely deployed instrumentation, and will remain so for at least the next decade. Hence, bringing Martian samples back to Earth is considered the best way to search for the desired evidence. A Mars sample return mission takes approximately three years to complete. Transit from Earth to Mars requires almost a single year. After a lapse of time of almost a year at Mars, during which orbital and surface operations can take place, and the correct return launch energy constraints are met, a Mars-to-Earth return flight can be initiated. This return leg also takes approximately one year. Opportunities to launch these 3-year sample return missions occur about every 2 years. The figure depicts schedules for flights to and from Mars for Earth launches in 2003, 2005, 2007 and 2009. Transits for less than 180 deg flight angle, measured from the sun, and more than 180 deg are both shown.
Miniature rovers with articulated mobility mechanisms are being developed for planetary surface exploration on Mars and small solar system bodies. These vehicles are designed to be capable of autonomous recovery from overturning during surface operations. This paper describes a computational means of developing motion behaviors that achieve the autonomous recovery function. It proposes a control software design approach aimed at reducing the effort involved in developing self-righting behaviors. The approach is based on the integration of evolutionary computing with a dynamics simulation environment for evolving and evaluating motion behaviors. The automated behavior design approach is outlined and its underlying genetic programming infrastructure is described.
Our objective is to propose a landing site that the Mars Surveyor 2001 Lander and Curie Rover could go to on Mars that should meet the safety requirements of the spacecraft landing system and optimize surface operations (chiefly driven by power and communications requirements). This site lies between 1.5-3.5 deg S latitude, 195-198 deg W longitude, along a sharp albedo contact between the low-viscosity flow units of southern Elysium Planitia and the eroded highlands margin east of Aeolis Mensae. A relatively-bright "peninsula-like" protrusion of the eroded highlands into the south Elysium plains in this area reminds us of the head of an Ibis, and so we nickname this site "Ibishead Peninsula". This site is designed to be situated as close to a diversity of geologic units within view of the lander instruments. Based on our experience with the visibility of horizon details from the Mars Pathfinder and Viking landing sites, we stipulate that for horizon features to be resolved suitably for detailed study from the lander, they must be no more than several kilometers distant. This is so that diversity can be placed in a geologic context in a region that we feel has some exciting science potential. This objective is different from the Mars Pathfinder requirement to land at a site with a maximum chance for containing a diversity of rocks within a few tens of meters of the lander, which resulted in the selection of a "grab bag" site.
The Controller-Pilot Data Link Communications (CPDLC) and Air Traffic Control workstation research was conducted as part of the 1997 NASA Low Visibility Landing and Surface Operations (LVLASO) demonstration program at Atlanta Hartsfield airport. Research activity under this grant increased the sophistication of the Controllers' Communication and Situational Awareness Terminal (C-CAST) and developed a VHF Data Link -Mode 2 communications platform. The research culminated with participation in the 2000 NASA Aviation Safety Program's Synthetic Vision System (SVS) / Runway Incursion Prevention System (RIPS) flight demonstration at Dallas-Fort Worth Airport.
The Runway Safety Monitor (RSM) is an algorithm for runway incursion detection and alerting that was developed in support of NASA's Runway Incursion Prevention System (RIPS) research conducted under the NASA Aviation Safety Program's Synthetic Vision System element. The RSM algorithm provides pilots with enhanced situational awareness and warnings of runway incursions in sufficient time to take evasive action and avoid accidents during landings, takeoffs, or taxiing on the runway. The RSM currently runs as a component of the NASA Integrated Display System, an experimental avionics software system for terminal area and surface operations. However, the RSM algorithm can be implemented as a separate program to run on any aircraft with traffic data link capability. The report documents the RSM software and describes in detail how RSM performs runway incursion detection and alerting functions for NASA RIPS. The report also describes the RIPS flight tests conducted at the Dallas-Ft Worth International Airport (DFW) during September and October of 2000, and the RSM performance results and lessons learned from those flight tests.
Astrology has long argued that the alignment of the planets governs human affairs. Science usually scoffs at this. There is, however, an important exception: sending spacecraft for planetary exploration. In late May and early June, 2003, Mars will be in position for Earth launch. Two Mars Exploration Rovers (MER) will rocket towards the red planet. The rovers will perform a series of geological and meteorological experiments, seeking to examine geological evidence for water and conditions once favorable for life. Back on earth, a small army of surface operations staff will work to keep the rovers running, sending directions for each day's operations and receiving the files encoding the outputs of the Rover's six instruments. (Mars is twenty light minutes from Earth. The rovers must be robots.) The fundamental purpose of the project is, after all, Science. Scientists have experiments they want to run. Ideally, scientists want to be immediately notified when the data products of their experiments have been received, so that they can examine their data and (collaboratively) deduce results. Mars is an unpredictable environment. We may issue commands to the rovers but there is considerable uncertainty in how the commands will be executed and whether what the rovers sense will be worthy of further pursuit. The steps of what is, to a scientist, conceptually an individual experiment may be scattered over a large number of activities. While the scientific staff has an overall strategic idea of what it would like to accomplish, activities are planned daily. The data and surprises of the previous day need to be integrated into the negotiations for the next day's activities, all synchronized to a schedule of transmission windows . Negotiations is the operative term, as different scientists want the resources to run possibly incompatible experiments. Many meetings plan each day's activities.
As part of the NASA/USRA program, nineteen West Virginia University students conducted a preliminary design of a manned Universal Martian Lander (UML). The WVU design considers descent to Mars from polar orbit, a six month surface stay, and ascent for rendezvous. The design begins with an unmanned UML landing at Elysium Mons followed by the manned UML landing nearby. During the six month surface stay, the eight modules are assembled to form a Martian base where scientific experiments are performed. The mission also incorporates hydroponic plant growth into a Controlled Ecological Life Support System (CELSS) for water recycling, food production, and to counteract psycho-logical effects of living on Mars. In situ fuel production for the Martian Ascent and Rendezvous Vehicle (MARV) is produced From gases in the Martian atmosphere. Following surface operations, the eight member crew uses the MARV to return to the Martian Transfer Vehicle (MTV) for the journey home to Earth.
We have developed a model-based, distributed architecture that integrates diverse components in a system designed for lunar and planetary surface operations: an astronaut's space suit, cameras, rover/All-Terrain Vehicle (ATV), robotic assistant, other personnel in a local habitat, and a remote mission support team (with time delay). Software processes, called agents, implemented in the Brahms language, run on multiple, mobile platforms. These mobile agents interpret and transform available data to help people and robotic systems coordinate their actions to make operations more safe and efficient. The Brahms-based mobile agent architecture (MAA) uses a novel combination of agent types so the software agents may understand and facilitate communications between people and between system components. A state-of-the-art spoken dialogue interface is integrated with Brahms models, supporting a speech-driven field observation record and rover command system (e.g., return here later and bring this back to the habitat ). This combination of agents, rover, and model-based spoken dialogue interface constitutes a personal assistant. An important aspect of the methodology involves first simulating the entire system in Brahms, then configuring the agents into a run-time system.
We have developed a model-based, distributed architecture that integrates diverse components in a system designed for lunar and planetary surface operations: an astronaut's space suit, cameras, all-terrain vehicles, robotic assistant, crew in a local habitat, and mission support team. Software processes ('agents') implemented in the Brahms language, run on multiple, mobile platforms. These mobile agents interpret and transform available data to help people and robotic systems coordinate their actions to make operations more safe and efficient. The Brahms-based mobile agent architecture (MAA) uses a novel combination of agent types so the software agents may understand and facilitate communications between people and between system components. A state-of-the-art spoken dialogue interface is integrated with Brahms models, supporting a speech-driven field observation record and rover command system. An important aspect of the methodology involves first simulating the entire system in Brahms, then configuring the agents into a runtime system Thus, Brahms provides a language, engine, and system builder's toolkit for specifying and implementing multiagent systems.
This chapter describes the ongoing process by which a multidisciplinary group at NASA's Ames Research Center is designing and implementing a large interactive work surface called the MERBoard Collaborative Workspace. A MERBoard system involves several distributed, large, touch-enabled, plasma display systems with custom MERBoard software. A centralized server and database back the system. We are continually tuning MERBoard to support over two hundred scientists and engineers during the surface operations of the Mars Exploration Rover Missions. These scientists and engineers come from various disciplines and are working both in small and large groups over a span of space and time. We describe the multidisciplinary, human-centered process by which this h4ERBoard system is being designed, the usage patterns and social interactions that we have observed, and issues we are currently facing.