Amateur Astrometric Contributions in Support of Flight Projects
There are seven flight projects that will visit 13 different comets and asteroids in the next 13 years.
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.
There are seven flight projects that will visit 13 different comets and asteroids in the next 13 years.
Several principal aerodynamics flight projects of the NASA Dryden Flight Research Facility are discussed. Key vehicle technology areas from a wide range of flight vehicles are highlighted. These areas include flight research data obtained for ground facility and computation correlation, applied research in areas not well suited to ground facilities (wind tunnels), and concept demonstration.
Mariner and Viking flight projects for Mars exploration
Several principal aeronautics flight projects of the NASA Dryden Flight Research Facility are discussed. Key vehicle technology areas from a wide range of flight vehicles are highlighted. These areas include flight research data obtained for ground facility and computation correlation, applied research in areas not well suited to ground facilities (wind tunnels), and concept demonstration.
The Voyager Flight Project - DSN Telecommunications Compatibility Test Program consisted of three phases: Subsystem Design, System Design, and System Verification Tests. Subsystem Design Tests were performed during mid 1976. System Design Tests were performed during late 1976 and early 1977. System Verification Tests were performed during the spring and summer of 1977. This article describes the System Design Tests and test results that provided the basis for establishment of telecommunications design between the DSN and the Voyager Flight Project.
The Autonomous Formation Flight (AFF) project at the NASA Dryden Flight Research Center (Edwards, California) investigated performance benefits resulting from formation flight, such as reduced aerodynamic drag and fuel consumption. To obtain data on performance benefits, a trailing F/A-18 airplane flew within the wing tip-shed vortex of a leading F/A-18 airplane. The pilot of the trail airplane used advanced station-keeping technology to aid in positioning the trail airplane at precise locations behind the lead airplane. The specially instrumented trail airplane was able to obtain accurate fuel flow measurements and to calculate engine thrust and vehicle drag. A maneuver technique developed for this test provided a direct comparison of performance values while flying in and out of the vortex. Based on performance within the vortex as a function of changes in vertical, lateral, and longitudinal positioning, these tests explored design-drivers for autonomous stationkeeping control systems. Observations showed significant performance improvements over a large range of trail positions tested. Calculations revealed maximum drag reductions of over 20 percent, and demonstrated maximum reductions in fuel flow of just over 18 percent.
Viewgraphs on the Flight Projects Office Information Systems Testbed (FIST) are presented. The goal is to perform technology evaluation and prototyping of information systems to support SFOC and JPL flight projects in order to reduce risk in the development of operational data systems for such projects.
A highly integrated Concurrent Engineering Team (CET) within a flight project evolves in its function and has the potential to provide many benefits through the project lifecycle. The benefits include superior systems-oriented design products, as well as overall improved project efficiency and higher-performing interpersonal relationships within the project. If physically integrated, this can manifest as a Concurrent Engineering Center (CEC) centrally located within a project’s physical office space. Here we discuss the process to establish and maintain a tightly integrated engineering and design team for providing highly streamlined service to the project, including a cost/benefits analysis discussion.
A highly integrated Concurrent Engineering Team (CET) within a flight project evolves in its function and has the potential to provide many benefits through the project lifecycle. The benefits include superior systems-oriented design products, as well as overall improved project efficiency and higher-performing interpersonal relationships within the project. If physically integrated, this can manifest as a Concurrent Engineering Center (CEC) centrally located within a project’s physical office space. Here we discuss the process to establish and maintain a tightly integrated engineering and design team for providing highly streamlined service to the project, including a cost/benefits analysis discussion.
Mariner, and Voyager planetary-interplanetary flight projects, and Surveyor lunar program
A report on the utilization of the Deep Space Network during calendar year 1981 in support of all flight projects is presented. The network expended 63% of its total capability in support of Space Flight projects.
Lunar Orbiter, Pioneer space probe, and Apollo backup station - flight project support
Information is given in viewgraph form on the activities of the Flight Projects Division of NASA's Office of Aeronautics and Space Technology. Information is given on space research and technology strategy, current space flight experiments, the Long Duration Exposure Facility, the Orbiter Experiment Program, the Lidar In-Space Technology Experiment, the Ion Auxiliary Propulsion System, the Arcjet Flight Experiment, the Telerobotic Intelligent Interface Flight Experiment, the Cryogenic Fluid Management Flight Experiment, the Industry/University In-Space Flight Experiments, and the Aeroassist Flight Experiment.
Explore the source record for details and available documents.
A proof-of-concept (POC) aircraft is defined and the concept of interest described for each of the six aircraft developed by the Ames-Moffet Rotorcraft and Powered-Lift Flight Projects Division from 1970 through 1985; namely, the OV-10, the C-8A Augmentor Wing, the Quiet Short-Haul Research Aircraft (QSRA), the XV-15 Tilt Rotor Research Aircraft (TRRA), the Rotor Systems Research Aircraft (RSRA)-compound, and the yet-to-fly RSRA/X-Wing Aircraft. The program/project chronology and most noteworthy features of the concepts are reviewed. The paper discusses the significance of each concept and the project demonstrating it; it briefly looks at what concepts are on the horizon as potential POC research aircraft and emphasizes that no significant advanced concept in aviation technology has ever been accepted by civilian or military users without first completing a demonstration through flight testing.
Deep Space Stations flight support operations for Surveyor II, Lunar Orbiter I, Pioneer VI and VII, Mariner IV, and Atlas Centaur
This paper will discuss the drawbacks and risks of the current documentation paradigm, how Document QuickStart improves on that process and ultimately how this stream-lined approach will reduce risk and costs to the next generation of Flight Projects at JPL
The goal of interface management is to identify, define, control, and verify interfaces; ensure compatibility; provide an efficient system development; be on time and within budget; while meeting stakeholder requirements. This paper will present a successful seven-step approach to interface management used in several NASA flight projects. The seven-step approach using Model Based Systems Engineering will be illustrated by interface examples from the Materials International Space Station Experiment-X (MISSE-X) project. The MISSE-X was being developed as an International Space Station (ISS) external platform for space environmental studies, designed to advance the technology readiness of materials and devices critical for future space exploration. Emphasis will be given to best practices covering key areas such as interface definition, writing good interface requirements, utilizing interface working groups, developing and controlling interface documents, handling interface agreements, the use of shadow documents, the importance of interface requirement ownership, interface verification, and product transition.