Search NASA⌕ Search

SEARCH · Search NASA

Results for “Launch operations”

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 145 records · Page 8

Analysis of Launch Vehicle Liftoff Debris: Historical Perspective from Space Shuttle and Application to Artemis I

Human exploration-class launch vehicles are inherently prone to debris due to the extreme environments generated during pre-launch operations, liftoff, and flight. The use of cryogenic propellants often requires thermal protection system (TPS) coatings, typically foam, to maintain the propellant conditions in the tank and prevent an accumulation ice on the external surface of the vehicle. Some ice growth is to be expected at umbilical interfaces, vents, flanges, or brackets where it is difficult to apply TPS. This ice may come loose at any time due to wind on the launch pad, structural vibration and acoustics after rocket ignition, or aerodynamic forces during flight. This phenomena is especially apparent on vehicles with no TPS, such as the Saturn V rockets used in the Apollo Program, see Figure 1. During propellant tanking, the thermal contraction of the underlying substrate may generate cracks in the TPS (Figure 1). Chunks of TPS can release due to the expansion of ingested gas from cryopumping or from aerodynamic forces if the crack creates an offset surface. Most foams will also have a certain amount of “popcorning” where small pieces of foam will pop off during flight because of the differential between the static surface pressure and the pressure of the gas trapped in the foam cell structure. There are a number of other coating or closeout materials that may be shed from the vehicle and become debris. During pre-launch operations and liftoff, the vehicle may also be exposed to debris originating from the launch pad or ground support equipment. This debris is separate from foreign object debris, or FOD, which is not intended to be present and is strictly controlled through operations and maintenance procedures. In this case, debris is generated from hardware and materials that are necessary for launch and are subject to the intense vibration, acoustics, and direct plume impingement of the launch environment. Examples include ice from umbilicals, tape and tie wraps that protect cables, and rust or corrosion from the launch platform. While NASA has historically been aware of debris as a potential issue that could cause a failure resulting in loss of mission, loss of vehicle, or loss of crew, the likelihood and severity of that risk was not always well understood or given sufficient weight in program and flight decisions. After the Space Shuttle Columbia accident (STS-107), the investigation found that foam TPS debris shed from the external tank was the proximate cause of the damage to the orbiter wing. Six previous observations of debris released from the foam ramp that covered the bipod connecting the forward end of the orbiter to the external tank resulted in minor changes or were determined to be accepted flight risks. Two occurrences of bipod ramp foam loss were not identified until the STS-107 investigation. Despite the damage inflicted by these debris strikes, the Shuttle Program Requirements Control Board deemed the vehicle safe to fly. During the Return to Flight effort following the Columbia disaster, NASA Engineering developed a process for the assessment of debris transport, impact, and damage tolerance to support independent assessments of risk by NASA Safety and Mission Assurance (S&MA). Under this system, each element (vehicle or ground system) defines a catalog of all expected debris based on launch history, component testing, or analysis. Debris transport analysis (DTA) is conducted using the debris catalog characteristics and potential flow transport mechanisms (e.g., vehicle aerodynamics, gravity, wind, plume-driven). The predicted debris impact locations and velocities are provided to the hardware owners, who use available test data and analysis to determine whether each component can withstand the impacts. In cases where the element hardware may be severely damaged or fail, the options are to mitigate the debris source through some change in design or operation, or to work with S&MA to try to characterize the probability of the impact and damage for program risk acceptance. Because of the differences in debris characteristics and transport, the DTA has been divided between the Liftoff and Ascent regimes. The development and application of Liftoff DTA methodology from the Shuttle Program to the current Artemis Program is the subject of this paper. Liftoff DTA covers the time from the start of pre-launch operations at the launch pad, up until the vehicle clears the launch tower and there is no longer any interaction with ground systems. Debris transport during this period is broadly classified as either gravity, wind, and plume-entrained (GWPE) or plume driven (PD). GWPE debris is generally lower speed, travelling in a forward-to-aft direction. PD transport includes flow features from the rocket ignition transient, as well as plume impingement and recirculation that occur as the vehicle lifts off the launch platform. In these cases, the debris typically moves in an aft-to-forward direction at higher speeds. The applicable transport mechanisms must be considered for each piece of debris depending on the material, and release location and time. For example, rust or metallic debris from the tower could fall (GWPE) and impact the vehicle before landing on the launch platform deck where it could be also be transported by plume impingement (PD). However, falling ice (GWPE) from an umbilical is unlikely to survive impact with the vehicle or launch platform and be available for PD transport. Modeling of debris transport is accomplished using a set of DTA tools which simulate debris trajectories subject to a reference frame acceleration (i.e., gravity) and aerodynamic drag. Where the trajectory encounters a solid surface, the debris is allowed to rebound with a specified coefficient of restitution. The drag is calculated by interpolating the fluid state at each point in the debris trajectory from high-fidelity computational fluid dynamics (CFD) simulations of the launch vehicle and pad. The CFD data may either be static (steady state or time averaged), typically for GWPE transport, or dynamic (time-accurate) for PD flow features like the ignition transient. Examples of the CFD flow field solutions for the Space Launch System (SLS) rocket and launch pad are shown in Figure 2. Typical SLS debris trajectory predictions from DTA are illustrated in Figure 3. The final version of this paper will include a more detailed examination of the Liftoff DTA process developed during the Shuttle Program, and how it has been augmented and applied to the SLS rocket under the Artemis Program. Comparisons with debris observations from the Artemis I launch will demonstrate validation of the tools and methodology.

Debris↗

Expert system decision support for low-cost launch vehicle operations

Progress in assessing the feasibility, benefits, and risks associated with AI expert systems applied to low cost expendable launch vehicle systems is described. Part one identified potential application areas in vehicle operations and on-board functions, assessed measures of cost benefit, and identified key technologies to aid in the implementation of decision support systems in this environment. Part two of the program began the development of prototypes to demonstrate real-time vehicle checkout with controller and diagnostic/analysis intelligent systems and to gather true measures of cost savings vs. conventional software, verification and validation requirements, and maintainability improvement. The main objective of the expert advanced development projects was to provide a robust intelligent system for control/analysis that must be performed within a specified real-time window in order to meet the demands of the given application. The efforts to develop the two prototypes are described. Prime emphasis was on a controller expert system to show real-time performance in a cryogenic propellant loading application and safety validation implementation of this system experimentally, using commercial-off-the-shelf software tools and object oriented programming techniques. This smart ground support equipment prototype is based in C with imbedded expert system rules written in the CLIPS protocol. The relational database, ORACLE, provides non-real-time data support. The second demonstration develops the vehicle/ground intelligent automation concept, from phase one, to show cooperation between multiple expert systems. This automated test conductor (ATC) prototype utilizes a knowledge-bus approach for intelligent information processing by use of virtual sensors and blackboards to solve complex problems. It incorporates distributed processing of real-time data and object-oriented techniques for command, configuration control, and auto-code generation.

Szatkowski, G. P.↗

Lessons Learned and Process Improvement for Payload Operations at the Launch Site

For every space mission, there are challenges with the launch site/field operations process that are addressed too late in the development cycle. This potentially causes schedule delays, cost overruns, and adds risk to the mission success. This paper will discuss how a single interface, representing the payload at the launch site in all phases of development, will mitigate risk, and minimize or even alleviate potential problems later on. Experience has shown that a single interface between the project and the launch site allows for issues to be worked in a timely manner and bridges the gap between two diverse cultures.

Catena, John↗

ASTP (SA-210) Launch vehicle operational flight trajectory. Part 3: Final documentation

Trajectory data are presented for a nominal and two launch window trajectory simulations. These trajectories are designed to insert a manned Apollo spacecraft into a 150/167 km. (81/90 n. mi.) earth orbit inclined at 51.78 degrees for rendezvous with a Soyuz spacecraft, which will be orbiting at approximately 225 km. (121.5 n. mi.). The launch window allocation defined for this launch is 500 pounds of S-IVB stage propellant. The launch window opening trajectory simulation depicts the earliest launch time deviation from a planar flight launch which conforms to this constraint. The launch window closing trajectory simulation was developed for the more stringent Air Force Eastern Test Range (AFETR) flight azimuth restriction of 37.4 degrees east-of-north. These trajectories enclose a 12.09 minute launch window, pertinent features of which are provided in a tabulation. Planar flight data are included for mid-window reference.

Carter, A. B.↗

The Wallops Flight Facility Model for an Integrated Federal/Commercial Launch Range

Historically, the federal government has been the predominant purchaser of space launches in the United States. The government met its needs through purchase of hardware and services. It also provided the infrastructure necessary to conduct launch operations through federal launch ranges, both military and NASA. Under this model, the government had the complete ownership, responsibility, liability, and expense for launch activities. As the commercial space sector grew, there emerged a corresponding growth in demand for launch range services. However, the expense and complexity of activities has thus far deterred a rapid rise in the establishment of purely commercial launch sites. In this context, purely commercial is defined as "without benefit of capabilities provided by the federal government." Consistent with the Commercial Space Launch Act, in recent years NASA and the Air Force have supported commercial launches from government launch ranges on a cost-reimbursable, non-interference basis. In this mode the commercial launch service providers contract with the government to provide services including use of facilities, tracking and data services, and range safety. As the commercial market projections began to show significant opportunities for economic development, several states established spaceports to provide the services necessary to meet these projected commercial needs. In 1997, NASA agreed to the establishment of the Virginia Space Flight Center (VSFC) at the Wallops Flight Facility. Under this arrangement, NASA agreed to allow Virginia Commercial Space Flight Authority (VCSFA) to construct facilities on NASA property and agreed to provide services in accordance with the Space Act of 1958 and the Commercial Space Launch Act of 1984 (as amended) to support VSFC launch customers. The relationship between NASA and VCSFA, however, has evolved beyond a customer supplier relationship. A partnership relationship has emerged which pairs the strengths of the established NASA test range and the state-sponsored, commercial launch facility provider, in an attempt to satisfy the needs for flexible, low-cost access to space. Furthermore, the future of the NASA/Wallops Test Range is closely linked with the success of VCSFA in promoting commercial launches from Wallops. This paper will describe the changing paradigm of the federal launch range and the unique aspects of the NASA/Wallops Facility relationship with VCSFA. Discussion will include institutional cost-sharing, business development and marketing, joint educational programs, and strategic planning.

Underwood, Bruce E.↗

Generating Safety-Critical PLC Code From a High-Level Application Software Specification

The benefits of automatic-application code generation are widely accepted within the software engineering community. These benefits include raised abstraction level of application programming, shorter product development time, lower maintenance costs, and increased code quality and consistency. Surprisingly, code generation concepts have not yet found wide acceptance and use in the field of programmable logic controller (PLC) software development. Software engineers at Kennedy Space Center recognized the need for PLC code generation while developing the new ground checkout and launch processing system, called the Launch Control System (LCS). Engineers developed a process and a prototype software tool that automatically translates a high-level representation or specification of application software into ladder logic that executes on a PLC. All the computer hardware in the LCS is planned to be commercial off the shelf (COTS), including industrial controllers or PLCs that are connected to the sensors and end items out in the field. Most of the software in LCS is also planned to be COTS, with only small adapter software modules that must be developed in order to interface between the various COTS software products. A domain-specific language (DSL) is a programming language designed to perform tasks and to solve problems in a particular domain, such as ground processing of launch vehicles. The LCS engineers created a DSL for developing test sequences of ground checkout and launch operations of future launch vehicle and spacecraft elements, and they are developing a tabular specification format that uses the DSL keywords and functions familiar to the ground and flight system users. The tabular specification format, or tabular spec, allows most ground and flight system users to document how the application software is intended to function and requires little or no software programming knowledge or experience. A small sample from a prototype tabular spec application is shown.

Source record↗

Assessing Upper-Level Winds on Day-of-Launch

On the day-or-launch. the 45th Weather Squadron Launch Weather Officers (LWOS) monitor the upper-level winds for their launch customers to include NASA's Launch Services Program (LSP). During launch operations, the payload launch team sometimes asks the LWO if they expect the upper level winds to change during the countdown but the LWOs did not have the capability to quickly retrieve or display the upper-level observations and compare them to the numerical weather prediction model point forecasts. The LWOs requested the Applied Meteorology Unit (AMU) develop a capability in the form of a graphical user interface (GUI) that would allow them to plot upper-level wind speed and direction observations from the Kennedy Space Center Doppler Radar Wind Profilers and Cape Canaveral Air Force Station rawinsondes and then overlay model point forecast profiles on the observation profiles to assess the performance of these models and graphically display them to the launch team. The AMU developed an Excel-based capability for the LWOs to assess the model forecast upper-level winds and compare them to observations. They did so by creating a GUI in Excel that allows the LWOs to first initialize the models by comparing the O-hour model forecasts to the observations and then to display model forecasts in 3-hour intervals from the current time through 12 hours.

Bauman, William H., III↗

PSA: A program to streamline orbit determination for launch support operations

An interactive, menu driven computer program was written to streamline the orbit determination process during the critical launch support phase of a mission. Residing on a virtual memory minicomputer, this program retains the quantities in-core needed to obtain a least squares estimate of the spacecraft trajectory with interactive displays to assist in rapid radio metric data evaluation. Menu-driven displays allow real time filter and data strategy development. Graphical and tabular displays can be sent to a laser printer for analysis without exiting the program. Products generated by this program feed back to the main orbit determination program in order to further refine the estimate of the trajectory. The final estimate provides a spacecraft ephemeris which is transmitted to the mission control center and used for antenna pointing and frequency predict generation by the Deep Space Network. The development and implementation process of this program differs from that used for most other navigation software by allowing the users to check important operating features during development and have changes made as needed.

Legerton, V. N.↗

Integrated operations/payloads/fleet analysis. Volume 3: System costs. Appendix A: Program direct costs

Individualized program direct costs for each satellite program are presented. This breakdown provides the activity level dependent costs for each satellite program. The activity level dependent costs, or, more simply, program direct costs, are comprised of the total payload costs (as these costs are strictly program dependent) and the direct launch vehicle costs. Only those incremental launch vehicle costs associated directly with the satellite program are considered. For expendable launch vehicles the direct costs include the vehicle investment hardware costs and the launch operations costs. For the reusable STS vehicles the direct costs include only the launch operations, recovery operations, command and control, vehicle maintenance, and propellant support. The costs associated with amortization of reusable vehicle investment, RDT&E range support, etc., are not included.

Source record↗

Launch processing system transition from development to operation

The Launch Processing System has been under development at Kennedy Space Center since 1973. A prototype system was developed and delivered to Marshall Space Flight Center for Solid Rocket Booster checkout in July 1976. The first production hardware arrived in late 1976. The System uses a distributed computer network for command and monitoring and is supported by a dual large scale computer system for 'off line' processing. A high level of automation is anticipated for Shuttle and Payload testing and launch operations to gain the advantages of short turnaround capability, repeatability of operations, and minimization of operations and maintenance (O&M) manpower. Learning how to efficiently apply the system is our current problem. We are searching for more effective ways to convey LPS system performance characteristics from the designer to a large number of users. Once we have done this, we can realize the advantages of LPS system design.

Paul, H. C.↗

Design and Testing of Non-Toxic RCS Thrusters for Second Generation Reusable Launch Vehicle

The current NASA Space Shuttle auxiliary propulsion system utilizes nitrogen tetroxide (NTO) and monomethylhydrazine (MMH), hypergolic propellants. This use of these propellants has resulted in high levels of maintenance and precautions that contribute to costly launch operations. By employing alternate propellant combinations, those less toxic to humans, the hazards and time required between missions can be significantly reduced. Use of alternate propellants can thereby increase the efficiency and lower the cost in launch operations. In support of NASA's Space Launch Initiative (SLI), TRW proposed a three-phase project structured to significantly increase the technology readiness of a high-performance reaction control subsystem (RCS) thruster using non-toxic propellant for an operationally efficient and reusable auxiliary propulsion system (APS). The project enables the development of an integrated primary/vernier thruster capable of providing dual-thrust levels of both 1000-lbf class thrust and 25-lbf thrust. The intent of the project is to reduce the risk associated with the development of an improved RCS flight design that meets the primary NASA objectives of improved safety and reliability while reducing systems operations and maintenance costs. TRW proposed two non-toxic auxiliary propulsion engine designs, one using liquid oxygen and liquid hydrogen and the other using liquid oxygen and liquid ethanol, as candidates to meet the goals of reliability and affordability at the RCS level. Both of these propellant combinations offer the advantage of a safe environment for maintenance, while at the same time providing adequate to excellent performance for a conventional liquid propulsion systems. The key enabling technology incorporated in both TRW thrusters is the coaxial liquid on liquid pintle injector. This paper will concentrate on only the design and testing of one of the thrusters, the liquid oxygen (LOX) and liquid hydrogen (LH2) thruster. The LOX/LH2 thruster design includes a LOX-centered pintle injector, consisting of two rows of slots that create a radial spoke spray pattern in the combustion chamber. The main fuel injector creates a continuous sheet of LH2 originating upstream of the LOX pintle injector. The two propellants impinge at the pintle slots, where the resulting momentum ratio and spray pattern determines the combustion efficiency and thermal effects on the hardware. Another enabling technology used in the design of this thruster is fuel film cooling through a duct, lining the inner wall of the combustion chamber barrel section. The duct is also acts as a secondary fuel injection point. The variation in the amount of LH2 used for the duct allows for adjustments in the cooling capacity for the thruster. The Non-Toxic LOX-LH2 RCS Workhorse Thruster was tested at the NASA Marshall Space Flight Center's Test Stand 500. Hot-fire tests were conducted between March 08, 2002 and April 05, 2002. All testing during the program base period were performed at sea-level conditions. During the test program, 7 configurations were tested, including 2 combustion chambers, 3 LOX injector pintle tips, and 4 LH2 injector stroke settings. The operating conditions that were surveyed varied thrust levels, mixture ratio and LH2 duct cooling flow. The copper heat sink chamber was used for 16 burns, each burn lasting from 0.4 to 10 seconds, totaling 51.4 seconds, followed by Haynes chamber testing ranging from 0.9 to 120 seconds, totaling 300.9 seconds. The total accumulated burn time for the test program is 352.3 seconds. C* efficiency was calculated and found to be within expectable limits for most operating conditions. The temperature on the Haynes combustion chamber remained below established material limits, with the exception of one localized hot spot. The test results demonstrate that both the coaxial liquid-on-liquid pintle injector design and fuel duct concepts are viable for the intended application. The thruster head-e design maintained cryogenic injection temperatures while firing, which validates the concept for minimal heat soak back. By injecting fuel into the duct, the throat temperatures were manageable, yet the split of fuel through the cooling duct does not compromise the overall combustion efficiency, which indicates that, provided proper design refinement, such a concept can be applied to a high-performance version of the thruster. These hot fire tests demonstrate the robustness of the duct design concept and good capability to withstand off-nominal operating conditions without adversely impacting the thermal response of the engine, a key design feature for a cryogenic thruster.

Calvignac, Jacky↗

The Road to Launch and Operations of the Spitzer Space Telescope

Spitzer Space Telescope, the fourth and final of NASA's Great Observatories, and the cornerstone to NASA's Origins Program, launched on 25 August 2003 into an Earth-trailing solar orbit to acquire infrared observations from space. Spitzer has an 85cm diameter beryllium telescope, which operates near absolute zero utilizing a liquid helium cryostat for cooling the telescope. The helium cryostat, though designed for a 2.5 year lifetime, through creative planning now has an expected lifetime of 5.5 years. Spitzer has completed its in-orbit checkout/science verification phases and the first two years of nominal operations, becoming the first mission to execute astronomical observations from a solar orbit. Spitzer was designed to probe and explore the universe in the infrared utilizing three state of the art detector arrays providing imaging, photometry, and spectroscopy over the 3-160 micron wavelength range...

infrared↗

Evaluation of Anomaly Detection Capability for Ground-Based Pre-Launch Shuttle Operations

This chapter will provide a thorough end-to-end description of the process for evaluation of three different data-driven algorithms for anomaly detection to select the best candidate for deployment as part of a suite of IVHM (Integrated Vehicle Health Management) technologies. These algorithms were deemed to be sufficiently mature enough to be considered viable candidates for deployment in support of the maiden launch of Ares I-X, the successor to the Space Shuttle for NASA's Constellation program. Data-driven algorithms are just one of three different types being deployed. The other two types of algorithms being deployed include a "nile-based" expert system, and a "model-based" system. Within these two categories, the deployable candidates have already been selected based upon qualitative factors such as flight heritage. For the rule-based system, SHINE (Spacecraft High-speed Inference Engine) has been selected for deployment, which is a component of BEAM (Beacon-based Exception Analysis for Multimissions), a patented technology developed at NASA's JPL (Jet Propulsion Laboratory) and serves to aid in the management and identification of operational modes. For the "model-based" system, a commercially available package developed by QSI (Qualtech Systems, Inc.), TEAMS (Testability Engineering and Maintenance System) has been selected for deployment to aid in diagnosis. In the context of this particular deployment, distinctions among the use of the terms "data-driven," "rule-based," and "model-based," can be found in. Although there are three different categories of algorithms that have been selected for deployment, our main focus in this chapter will be on the evaluation of three candidates for data-driven anomaly detection. These algorithms will be evaluated upon their capability for robustly detecting incipient faults or failures in the ground-based phase of pre-launch space shuttle operations, rather than based oil heritage as performed in previous studies. Robust detection will allow for the achievement of pre-specified minimum false alarm and/or missed detection rates in the selection of alert thresholds. All algorithms will also be optimized with respect to an aggregation of these same criteria. Our study relies upon the use of Shuttle data to act as was a proxy for and in preparation for application to Ares I-X data, which uses a very similar hardware platform for the subsystems that are being targeted (TVC - Thrust Vector Control subsystem for the SRB (Solid Rocket Booster)).

Martin, Rodney Alexander↗

Near-term Horizontal Launch for Flexible Operations: Results of the DARPA/NASA Horizontal Launch Study

Horizontal launch has been investigated for 60 years by over 130 different studies. During this time only one concept, Pegasus, has ever been in operation. The attractiveness of horizontal launch is the capability to provide a "mobile launch pad" that can use existing aircraft runways, cruise above weather, loiter for mission instructions, and provide precise placement for orbital intercept, rendezvous, or reconnaissance. A jointly sponsored study by DARPA and NASA, completed in 2011, explored the trade space of horizontal launch system concepts which included an exhaustive literature review of the past 70 years. The Horizontal Launch Study identified potential near- and mid-term concepts capable of delivering 15,000 lb payloads to a 28.5 due East inclination, 100 nautical-mile low-Earth orbit. Results are presented for a range of near-term system concepts selected for their availability and relatively low design, development, test, and evaluation (DDT&E) costs. This study identified a viable low-cost development path forward to make a robust and resilient horizontal launch capability a reality.

Bartolotta, Paul A.↗

Moonport: A History of Apollo Launch Facilities and Operations

The development of the Apollo f launch facilities and launch operations is described from the beginning of design through the final launch. Management techniques, innovation in automation, and testing on the ground to avoid failures in space are among the topics covered. The impact of the Apollo program on the citrus groves and quiet beaches of Florida's east coast is included.

Benson, C. D.↗

Large Space Telescope external interfaces

Key interfaces are described for all LST mission phases: ground test and integration, prelaunch and launch operations, ascent, deployment, operations, on-orbit maintenance, retrieval, deorbit and landing, and refurbishment. These interfaces can be categorized as test and integration, launch operations, Shuttle, data, and mission operations. The interface with the Shuttle and the Shuttle crew is emphasized here because the Shuttle allows a new capability: on-orbit maintenance and ground return. The LST will communicate with the ground elements of the LST system through a space link by means of the Tracking Data Relay Satellite System or directly to the stations of the Space Tracking and Data Network.

Collart, R. E.↗

Application of System Operational Effectiveness Methodology to Space Launch Vehicle Development and Operations

The Department of Defense (DoD) defined System Operational Effectiveness (SOE) model provides an exceptional framework for an affordable approach to the development and operation of space launch vehicles and their supporting infrastructure. The SOE model provides a focal point from which to direct and measure technical effectiveness and process efficiencies of space launch vehicles. The application of the SOE model to a space launch vehicle's development and operation effort leads to very specific approaches and measures that require consideration during the design phase. This paper provides a mapping of the SOE model to the development of space launch vehicles for human exploration by addressing the SOE model key points of measurement including System Performance, System Availability, Technical Effectiveness, Process Efficiency, System Effectiveness, Life Cycle Cost, and Affordable Operational Effectiveness. In addition, the application of the SOE model to the launch vehicle development process is defined providing the unique aspects of space launch vehicle production and operations in lieu of the traditional broader SOE context that examines large quantities of fielded systems. The tailoring and application of the SOE model to space launch vehicles provides some key insights into the operational design drivers, capability phasing, and operational support systems.

Watson, Michael D.↗