Data acquisition support of NASA lunar and planetary flight missions.
Telecommunication system for lunar, planetary and deep space flight mission control and data acquisition
Hynes, R. T.↗
SEARCH · Engineering Papers
Results for “Mission Control”
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.
An analysis of the telecommunication performance of a data-relay satellite system.
Data relay satellite system to provide communication capability between earth orbiting space vehicles and Mission Control Center
Arndt, G. D.↗
Data relay satellites for support of NASA R and D missions.
Data relay satellite systems for support of NASA R and D missions, discussing communications between satellites and to mission control
Barritt, P. F.↗
Tracking and data relay satellite system.
Tracking and Data Relay Satellite System with synchronous orbit satellites to relay data between low altitude earth orbital spacecraft and mission control centers
Andrus, A. M. G.↗
Evaluation of nine lunar models for Apollo
Evaluating various lunar gravitational models for Apollo mission control
Barrow, G. D.↗
Discussion of several problem areas during the Apollo 13 operation
Apollo 13 flight rescue operation as function of flight crew performance and Mission Control Center
Lunney, G. S.↗
A method for lunar roving vehicle position determination from three landmark observations with a sun compass
A simplified method is described for determining the position of the lunar roving vehicle on the lunar surface during Apollo 15. The method is based upon sun compass azimuth measurements of three lunar landmarks. The difference between the landmark azimuth and the sun azimuth is measured and the resulting data are voice relayed to the Mission Control Center for processing.
Blucker, T. J.↗
Mars lander position estimation in the presence of ephemeris biases.
The process of estimating the location of a spacecraft landed on the surface of Mars is investigated through the application of statistical estimation techniques to earth-based radio tracking data. The spacecraft location and the tracking geometry and schedule are consistent with Viking-type mission constraints. With mission control requirements in mind, the investigation is restricted to analysis of a short data arc (approximately 3 days). Statistics of the spacecraft location are obtained through analysis of (direct-link) tracking data for the landed spacecraft and through simultaneous analysis of tracking data for both a landed and an orbiting spacecraft. These estimates include the effects of model uncertainties in the ephemeris of Mars, tracking station locations, the Mars rotational period, the Mars gravity field, and the orientation of Mars axis of rotation. The most significant of these effects is shown to be due to the Mars ephemeris uncertainty. A dual spacecraft tracking technique is presented for substantially reducing these ephemeris effects.
Blackshear, W. T.↗
Apollo 15 mission. Temporary loss of command module television picture
An investigation was made into the temporary loss of command module color television picture by the ground station converter at Mission Control Center. Results show the picture loss was caused by a false synchronization pulse that resulted from the inability of the black level clipping circuit to respond adequately to the video signal when bright sunlight suddenly entered the camera's field of view.
Source record↗
Programmer's manual for the Mission Analysis Evaluation and Space Trajectory Operations program (MAESTRO)
The Mission Analysis Evaluation and Space Trajectory Operations program known as MAESTRO is described. MAESTRO is an all FORTRAN, block style, computer program designed to perform various mission control tasks. This manual is a guide to MAESTRO, providing individuals the capability of modifying the program to suit their needs. Descriptions are presented of each of the subroutines descriptions consist of input/output description, theory, subroutine description, and a flow chart where applicable. The programmer's manual also contains a detailed description of the common blocks, a subroutine cross reference map, and a general description of the program structure.
Lutzky, D.↗
Natural environment support guidelines for space shuttle tests and operations
All space shuttle events from launch through solid rocket booster recovery and orbiter landing are considered in terms of constraints placed on those operations by the natural environment. Thunderstorm activity is discussed as an example of a possible hazard. The activities most likely to require advanced detection and monitoring techniques are identified as those from deorbit decision to Orbiter landing. The inflexible flight plan will require the transmission of real time wind profile information below 24 km and warnings of thunderstorms or turbulence in the Orbiter flight path. Extensive aerial reconnaissance and communication facilities and procedures to permit immediate transmission of aircraft reports to the mission control authority and to the Orbiter will also be required.
Carter, E. A.↗
Rhythmic variation in heart rate and respiration rate during space flight - Apollo 15
As part of the operational biomedical monitoring for Apollo manned missions, ECG and respiration rate are telemetered at selected intervals to mission control. The data were collected as part of this monitoring program. These data were evaluated for circadian and ultradian rhythmicity because of their uniqueness. The ability to detect and quantitate biorhythms in living systems during space flight is an important aspect of evaluating hypotheses concerning the underlying mechanisms of these phenomena. Circadian variation in heart rate during space flight is demonstrated here. In analyzing generated time series data it has been found that period discrimination is much better than the theoretical limit.
Rummel, J. A.↗
Operational aspects of Skylab Student Project experiments
The activities associated with the operational aspects ot the Skylab Student Project experiments began with the participation of flight operations personnel on the National Science Teachers Association Selection Board and ended with the performance of the student experiments by the Skylab flightcrews. The operational criteria used during the compatibility analysis to determine which of the 25 national winners could be flown on board the Skylab vehicle are reviewed, the factors involved in the assignment of the experiments to Skylab missions are discussed, the activities associated with training the flightcrews in the operation of the student experiments are described, and the actual performance of the experiments during the mission and the associated ground operations in the Mission Control Center are detailed.
Macleod, J. B.↗
Viking Mars launch set for August 11
The 1975-1976 Viking Mars Mission is described in detail, from launch phase through landing and communications relay phase. The mission's scientific goals are outlined and the various Martian investigations are discussed. These investigations include: geological photomapping and seismology; high-resolution, stereoscopic horizon scanning; water vapor and thermal mapping; entry science; meteorology; atmospheric composition and atmospheric density; and, search for biological products. The configurations of the Titan 3/Centaur combined launch vehicles, the Viking orbiters, and the Viking landers are described; their subsystems and performance characteristics are discussed. Preflight operations, launch window, mission control, and the deep space tracking network are also presented.
Panagakos, N.↗
A scientific operations plan for the NASA space telescope
A ground system is described which is compatible with the operational requirements of the space telescope. The goal of the ground system is to minimize the cost of post launch operations without seriously compromising the quality and total throughput of space telescope science, or jeopardizing the safety of the space telescope in orbit. The resulting system is able to accomplish this goal through optimum use of existing and planned resources and institutional facilities. Cost is also reduced and efficiency in operation increased by drawing on existing experience in interfacing guest astronomers with spacecraft as well as mission control experience obtained in the operation of present astronomical spacecraft.
West, D. K.↗
Apollo Soyuz mission planning and operations
The paper describes the Apollo Soyuz project from the points of view of working group organization, mission plan definition, joint operations concept, and mission preparation. The concept for joint operations considered contingency situations as well as nominal operations. Preparations for the joint flight included cooperative tracking tests and combined training of the flight crews and mission control personnel.
Frank, M. P., III↗
MCC/shuttle test plan. Volume 1: Philosophy and guidelines
The Mission Control Center/Shuttle Test Plan is defined from development through operations to a level of detail which will support the National Aeronautics and Space Administration and contractor management in the following areas: test management, test tool development, and resource and schedule planning.
Source record↗
Space shuttle engineering and operations support: Study of the effects of multiple ground updates on the accuracy of the onboard state vector with IMU only navigation
There are six cases considered: (1) no updates made during the flight, (2) one ground update in the vertical components only at the first practice separation minus 15 minutes, (3) one ground update in all components at the first practice separation minus 5 minutes, (4) updates 2 and 3 applied successively, (5) Case 4 plus an update in all components at the second separation attempt minus 3 minutes, and (6) one ground update at first separation attempt minus 5 minutes and a second update at second separation minus two minutes. The mission control simulation program, GROPER, was run using as radar input a tape containing radar derived state vectors for the trajectory.
Killen, R.↗