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.
Solar electric propulsion performance and trajectory data for indirect solar probes, extra-ecliptic missions, and rendezvous with Ceres, D-Arrest, and Encke
Constants and related data used in trajectory calculations at jet propulsion laboratory
Computational techniques were developed and assimilated for the design optimization. The resulting computer program was then used to perform initial optimization and sensitivity studies on a typical thermal protection system (TPS) to demonstrate its application to the space shuttle TPS design. The program was developed in Fortran IV for the CDC 6400 but was subsequently converted to the Fortran V language to be used on the Univac 1108. The program allows for improvement and update of the performance prediction techniques. The program logic involves subroutines which handle the following basic functions: (1) a driver which calls for input, output, and communication between program and user and between the subroutines themselves; (2) thermodynamic analysis; (3) thermal stress analysis; (4) acoustic fatigue analysis; and (5) weights/cost analysis. In addition, a system total cost is predicted based on system weight and historical cost data of similar systems. Two basic types of input are provided, both of which are based on trajectory data. These are vehicle attitude (altitude, velocity, and angles of attack and sideslip), for external heat and pressure loads calculation, and heating rates and pressure loads as a function of time.
A method and a computer system with a specialized graphic user interface for processing trajectory data of a spacecraft and planets. The preferred graphic user interface is capable of representing the orbital trajectory of the spacecraft traveling from one planet to another in 3D and providing user interactions to display the orbit information at any time and position.
Instructions are presented on the use of ADMAP, (automatic data manipulation program) an aerospace data manipulation computer program. The program was developed to aid in processing, reducing, plotting, and publishing electric propulsion trajectory data generated by the low thrust optimization program, HILTOP. The program has the option of generating SC4020 electric plots, and therefore requires the SC4020 routines to be available at excution time (even if not used). Several general routines are present, including a cubic spline interpolation routine, electric plotter dash line drawing routine, and single parameter and double parameter sorting routines. Many routines are tailored for the manipulation and plotting of electric propulsion data, including an automatic scale selection routine, an automatic curve labelling routine, and an automatic graph titling routine. Data are accepted from either punched cards or magnetic tape.
In the past few years much of the global ATM research community has proposed advanced systems based on Trajectory-Based Operations (TBO). The concept of TBO uses four-dimensional aircraft trajectories as the base information for managing safety and capacity. Both the US and European advanced ATM programs call for the sharing of trajectory data across different decision support tools for successful operations. However, the actual integration of TBO systems presents many challenges. Trajectory predictors are built to meet the specific needs of a particular system and are not always compatible with others. Two case studies are presented which examine the challenges of introducing a new concept into two legacy systems in regards to their trajectory prediction software. The first case describes the issues with integrating a new decision support tool with a legacy operational system which overlap in domain space. These tools perform similar functions but are driven by different requirements. The difference in the resulting trajectories can lead to conflicting advisories. The second case looks at integrating this same new tool with a legacy system originally developed as an integrated system, but diverged many years ago. Both cases illustrate how the lack of common architecture concepts for the trajectory predictors added cost and complexity to the integration efforts.
Handbook of trajectory data for flights to Jupiter and the asteroids Ceres and Vesta
In the present-day National Airspace System, the air traffic management system attempts to predict the trajectory for each flight based on the flight plan and scheduled or controlled departure time. However, gaps in trajectory data and models, coupled with tactical control actions that are not communicated to automation systems or other stakeholders, lead to trajectory predictions that are less accurate than they could be. This affects traffic flow management performance. Management by Trajectory (MBT) is a NASA concept for air traffic management in which every flight operates in accordance with a 4D trajectory that is negotiated between the airspace user and the FAA to account for the airspace user’s goals while complying with NAS constraints. The primary benefit of MBT is an improvement in system performance due to increased trajectory predictability and stability, which result from managing traffic in all four dimensions (2D route, vertical, and time), ensuring that changes to the flight’s trajectory are incorporated into the assigned trajectory, and utilizing improved time or arrival control standards. Importantly, the performance improvements support increasing efficiency without increasing collision risk. This paper provides an overview of MBT and describes fast-time simulation results evaluating the safety, performance, and efficiency effects of MBT.
An earlier analysis of Prairie Network fireball trajectory data failed to discriminate between the varieties of meteoric materials that are thought to be present. The Lost City meteorite event offers another calibration of the fireball data and prompts a reanalysis intended to distinguish between ordinary chondritic meteorites and the more fragile early-type carbonaceous chondrites. The carbonaceous material is expected to ablate more readily and have shorter trajectories or higher end heights. Observational error and natural dispersion in the structures produce severe smoothing effects, and the end-height diagnostic is, in itself, not entirely convincing. However, after making a tentative division of the data, one can discern differences in orbits and beginning heights among the three end-height groups. These are consistent with expectations of the behavior of chondritic stones (group I), weak carbonaceous chondrites (group II), and still more fragile cometary material (group III). It is concluded that if the carbonaceous material occurs in reasonable abundance among the fireballs, it has been properly identified by this analysis.
The application of using the mission planning and analysis division (MPAD) common format trajectory data tape to predict temperatures for preflight and post flight mission analysis is presented and evaluated. All of the analyses utilized the latest Space Transportation System 1 flight (STS-1) MPAD trajectory tape, and the simplified '136 note' midsection/payload bay thermal math model. For the first 6.7 hours of the STS-1 flight profile, transient temperatures are presented for selected nodal locations with the current standard method, and the trajectory tape method. Whether the differences are considered significant or not depends upon the view point. Other transient temperature predictions are also presented. These results were obtained to investigate an initial concern that perhaps the predicted temperature differences between the two methods would not only be caused by the inaccuracies of the current method's assumed nominal attitude profile but also be affected by a lack of a sufficient number of orbit points in the current method. Comparison between 6, 12, and 24 orbit point parameters showed a surprising insensitivity to the number of orbit points.
This paper examines the lunar lander stages that will be necessary for the future exploration and development of the Moon. Lunar lander stage sizing is discussed based on the projected lunar payloads listed in the Civil Needs Data Base. Factors that will influence the lander stage design are identified and discussed. Some of these factors are (1) lunar orbiting and lunar surface lander bases; (2) implications of direct landing trajectories and landing from a parking orbit; (3) implications of landing site and parking orbit; (4) implications of landing site and parking orbit selection; (5) the use of expendable and reusable lander stages; and (6) the descent/ascent trajectories. Data relating the lunar lander stage design requirements to each of the above factors and others are presented in parametric form. These data will provide useful design data that will be applicable to future mission model modifications and design studies.
Recent developments in automated processing of digital SEASAT SAR imagery have made feasible the generation of large-scale high-resolution maps. Standard preprocessing of raw data into digital images results in geometrically distorted imagery. Computer algorithms have been developed for unsupervised pixel location, geometric rectification, and mosaicking of multiple-image frames without ground control points. These algorithms utilize knowledge of the spacecraft trajectory data, the imaging geometry, and the coherent properties of the sensor to generate the required processing parameters. This paper discusses the advantages as well as the inherent limitations of this technique, analyzes the associated errors, and presents results using SEASAT SAR imagery. Also discussed are the results of the recent shuttle imaging radar (SIR-A) experiment as well as a follow-on experiment (SIR-B) planned for 1984.
On June 13th, 2010, the Hayabusa sample return capsule successfully re-entered Earth s atmosphere over the Woomera Prohibited Area in southern Australia in its quest to return fragments from the asteroid 1998 SF36 Itokawa . The sample return capsule entered at a super-orbital velocity of 12.04 km/sec (inertial), making it the second fastest human-made object to traverse the atmosphere. The NASA DC-8 airborne observatory was utilized as an instrument platform to record the luminous portion of the sample return capsule re-entry (~60 sec) with a variety of on-board spectroscopic imaging instruments. The predicted sample return capsule s entry state information at ~200 km altitude was propagated through the atmosphere to generate aerothermodynamic and trajectory data used for initial observation flight path design and planning. The DC- 8 flight path was designed by considering safety, optimal sample return capsule viewing geometry and aircraft capabilities in concert with key aerothermodynamic events along the predicted trajectory. Subsequent entry state vector updates provided by the Deep Space Network team at NASA s Jet Propulsion Laboratory were analyzed after the planned trajectory correction maneuvers to further refine the DC-8 observation flight path. Primary and alternate observation flight paths were generated during the mission planning phase which required coordination with Australian authorities for pre-mission approval. The final observation flight path was chosen based upon trade-offs between optimal viewing requirements, ground based observer locations (to facilitate post-flight trajectory reconstruction), predicted weather in the Woomera Prohibited Area and constraints imposed by flight path filing deadlines. To facilitate sample return capsule tracking by the instrument operators, a series of two racetrack flight path patterns were performed prior to the observation leg so the instruments could be pointed towards the region in the star background where the sample return capsule was expected to become visible. An overview of the design methodologies and trade-offs used in the Hayabusa re-entry observation campaign are presented.
I. During each nine-hour shift (or upon request), the Orbital Safety Analyst (OSA) at JSpOC updates the entire tracked catalog with the latest tracking data from the SSN and screens this catalog against NASA s assets. a) For ISS operations, a 72-hour advance screening is performed. b) For Shuttle orbit operations, a 36-hour advance screening is performed. c) If a vehicle is performing a maneuver during the screening period, OSA uses post-reboost-trajectory data supplied by Mission Control Center-Houston (MCC-H) for screening. II. An automated process is used to detect any conjunctions within 10 x 40 x 40 km box (centered on the vehicle) using Special Perturbation (SP) processing: a) Box dimensions are Radial x Downtrack x Crosstrack. b) Any object found within this box has the tracking tasking level increased to improve (hopefully) its uncertainty in its current and predicted orbital trajectory. c) OSA informs NASA if any object is found inside a 2 x 25 x 25 km box then creates and sends an Orbital Conjunction Message (OCM) to NASA which contains detailed information about the conjunction. d) For Shuttle, the box size used for screening and reporting is altered for special operations (day of rendezvous, launch screening, etc.).
Methods of controlling the trajectories of high-drag-low-lift vehicles entering the earth's atmosphere at angles of attack near 90 deg and at initial entry angles up to 3 deg are studied. The trajectories are calculated for vehicles whose angle of attack can be held constant at some specified value or can be perfectly controlled as a function of some measured quantity along the trajectory. The results might be applied in the design of automatic control systems or in the design of instruments which will give the human pilot sufficient information to control his trajectory properly during an atmospheric entry. Trajectory data are compared on the basis of the deceleration, range, angle of attack, and, in some cases, the rate of descent. The aerodynamic heat-transfer rate and skin temperature of a vehicle with a simple heat-sink type of structure are calculated for trajectories made with several types of control functions. For the range of entry angles considered, it is found that the angle of attack can be controlled to restrict the deceleration down to an arbitrarily chosen level of 3g. All the control functions tried are successful in reducing the maximum deceleration to the desired level. However, in order to avoid a tendency for the deceleration to reach an initial peak decrease, and then reach a second peak, some anticipation is required in the control function so that the change in angle of attack will lead the change in deceleration. When the angle of attack is controlled in the aforementioned manner, the maximum rate of aerodynamic heat transfer to the skin is reduced, the maximum skin temperature of the vehicle is virtually unaffected, and the total heat absorbed is slightly increased. The increase in total heat can be minimized, however, by maintaining the maximum desired deceleration for as much of the trajectory as possible. From an initial angle of attack of 90 deg, the angle-of-attack requirements necessary to maintain constant values of deceleration (1g to 4g) and constant values of rate of descent (450 to 1,130 ft/sec) as long as it is aerodynamically practical are calculated and are found to be moderate in both magnitude and rate. Entry trajectories made with these types of control are presented and discussed.
Preliminary Apollo 14 (Mission H-3) trajectory data for the July 1970 launch window are presented in this document. A general mission profile is presented, and approximate variations of selected mission parameters are indicated. Note that the information in this document is preliminary and will be updated in the Apollo 14 (Mission H-3) operational trajectory documents.
A postflight trajectory reconstruction and analysis were conducted in order to determine the effects of unmodeled thrusting on the Space Shuttle Orbiter, to generate representative thrusting uncertainties for input to error analyses, and to evaluate the accuracy of the Ancillary trajectory data product and real-time vectors. The methods of selecting appropriate data arcs, time placement of compensation forces, limitations of the orbit determination process, and methods of evaluating solutions obtained from various force combinations are presented. It is shown that the estimation of forces to compensate for uncoupled attitude maneuvers and attitude hold maintenance thrusting significantly improves the postflight reconstruction of Space Shuttle Orbiter trajectories. A reduction of measurement residual statistics due to dynamic model uncertainties yields improved accuracy for postflight orbit determination.
The trajectory data are presented chronologically and are organized by holding the arrival date constant while varying the Earth departure date in increments of 10 days. Upon completion of the specified range of Earth departure dates, the arrival date is incremented and the range of departure dates is repeated. For long trip times, where the variation of the trajectory parameters is relatively small, the size of the increment of the arrival date is increased. The range of departure and arrival dates and their corresponding increments are given i n Table 4-1 for each launch opportunity. The criterion for the selection of these dates is that they encompass the region in which the Earth departure hyperbolic excess speed is less than or equal to 0.65 EMOS.