Search NASA⌕ Search

SEARCH · Search NASA

Results for “FLEET”

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 469 records · Page 26

The Second Joint NASA/FAA/DOD Conference on Aging Aircraft

The purpose of the Conference was to bring together world leaders in aviation safety research, aircraft design and manufacturing, fleet operation and aviation maintenance to disseminate information on current practices and advanced technologies that will assure the continued airworthiness of the aging aircraft in the military and commercial fleets. The Conference included reviews of current industry practices, assessments of future technology requirements, and status of aviation safety research. The Conference provided an opportunity for interactions among the key personnel in the research and technology development community, the original equipment manufacturers, commercial airline operators, military fleet operators, aviation maintenance, and aircraft certification and regulatory authorities. Conference participation was unrestricted and open to the international aviation community.

Harris, Charles E.↗

Transition to Glass: Pilot Training for High-Technology Transport Aircraft

This report examines the activities of a major commercial air carrier between 1993 and late 1996 as it acquired an advanced fleet of high-technology aircraft (Boeing 757). Previously, the airline's fleet consisted of traditional (non-glass) aircraft, and this report examines the transition from a traditional fleet to a glass one. A total of 150 pilots who were entering the B-757 transition training volunteered for the study, which consisted of three query phases: (1) first day of transition training, (2) 3 to 4 months after transition training, and (3) 12 to 14 months after initial operating experience. Of these initial 150 pilots, 99 completed all three phases of the study, with each phase consisting of probes on attitudes and experiences associated with their training and eventual transition to flying the line. In addition to the three questionnaires, 20 in-depth interviews were conducted. Although the primary focus of this study was on the flight training program, additional factors such as technical support, documentation, and training aids were investigated as well. The findings generally indicate that the pilot volunteers were highly motivated and very enthusiastic about their training program. In addition, the group had low levels of apprehension toward automation and expressed a high degree of satisfaction toward their training. However, there were some concerns expressed regarding the deficiencies in some of the training aids and lack of a free-play flight management system training device.

Wiener, Earl L.↗

Autonomy Architectures for a Constellation of Spacecraft

Until the past few years, missions typically involved fairly large expensive spacecraft. Such missions have primarily favored using older proven technologies over more recently developed ones, and humans controlled spacecraft by manually generating detailed command sequences with low-level tools and then transmitting the sequences for subsequent execution on a spacecraft controller. This approach toward controlling a spacecraft has worked spectacularly on previous missions, but it has limitations deriving from communications restrictions - scheduling time to communicate with a particular spacecraft involves competing with other projects due to the limited number of deep space network antennae. This implies that a spacecraft can spend a long time just waiting whenever a command sequence fails. This is one reason why the New Millennium program has an objective to migrate parts of mission control tasks onboard a spacecraft to reduce wait time by making spacecraft more robust. The migrated software is called a "remote agent" and has 4 components: a mission manager to generate the high level goals, a planner/scheduler to turn goals into activities while reasoning about future expected situations, an executive/diagnostics engine to initiate and maintain activities while interpreting sensed events by reasoning about past and present situations, and a conventional real-time subsystem to interface with the spacecraft to implement an activity's primitive actions. In addition to needing remote planning and execution for isolated spacecraft, a trend toward multiple-spacecraft missions points to the need for remote distributed planning and execution. The past few years have seen missions with growing numbers of probes. Pathfinder has its rover (Sojourner), Cassini has its lander (Huygens), and the New Millenium Deep Space 3 (DS3) proposal involves a constellation of 3 spacecraft for interferometric mapping. This trend is expected to continue to progressively larger fleets. For example, one mission proposed to succeed DS3 would have 18 spacecraft flying in formation in order to detect earth-sized planets orbiting other stars. A proposed magnetospheric constellation would involve 5 to 500 spacecraft in Earth orbit to measure global phenomena within the magnetosphere. This work describes and compares three autonomy architectures for a system that continuously plans to control a fleet of spacecraft using collective mission goals instead of goals or command sequences for each spacecraft. A fleet of self-commanding spacecraft would autonomously coordinate itself to satisfy high level science and engineering goals in a changing partially-understood environment making feasible the operation of tens or even a hundred spacecraft (such as for interferometry or plasma physics missions). The easiest way to adapt autonomous spacecraft research to controlling constellations involves treating the constellation as a single spacecraft. Here one spacecraft directly controls the others as if they were connected. The controlling "master" spacecraft performs all autonomy reasoning, and the slaves only have real-time subsystems to execute the master's commands and transmit local telemetry/observations. The executive/diagnostics module starts actions and the master's real-time subsystem controls the action either locally or remotely through a slave. While the master/slave approach benefits from conceptual simplicity, it relies on an assumption that the master spacecraft's executive can continuously monitor the slaves' real-time subsystems, and this relies on high-bandwidth highly-reliable communications. Since unintended results occur fairly rarely, one way to relax the bandwidth requirements involves only monitoring unexpected events in spacecraft. Unfortunately, this disables the ability to monitor for unexpected events between spacecraft and leads to a host of coordination problems among the slaves. Also, failures in the communications system can result in losing slaves. The other two architectures improve robustness while reducing communications by progressively distributing more of the other three remote agent components across the constellation. In a teamwork architecture, all spacecraft have executives and real-time subsystems - only the leader has the planner/scheduler and mission manager. Finally, distributing all remote agent components leads to a peer-to-peer approach toward constellation control.

Barrett, Anthony↗

Pole-to-Pole Distribution of Stratospheric Black Carbon (Soot) Aerosol from Aircraft

The distribution of black carbon (soot) aerosol (BCA) in the atmosphere is of interest for several reasons: (1) Because BCA has the highest absorption cross section of any compound known, it can absorb solar radiation to cause atmospheric warming. (2) Because it is a strong adsorber of gases, it can catalyze heterogeneous reactions to change the chemical composition of the atmosphere.(3) If aircraft are a major source of BCA, it is an important tracer of aircraft emissions. Analysis for BCA of impactor samples from Arctic and Antarctic deployments, utilizing particle morphology of scanning electron microscopy images, permits the following conclusions: (1) The BCA concentration in the northern stratosphere varies between 0 and 2.6 ng m-3 averaging 0.6 ng/cu m. (2) This BCA loading is commensurate with estimated fuel consumptions in the stratosphere by the current commercial fleet and an emission index E=0.03 g BCA per kg fuel burnt which was measured in jet exhaust at al titude.Thus, most stratospheric BCA in the northern stratosphere results from aircraft emissions. The background BCA concentration in the southern stratosphere varies between 0 and 0.6 ng cu m averaging 0.1 ng/cu m. This strong meridional gradient implies that stratospheric BCA residence time- is shorter than are mixing times between hemispheres. Projected annual fuel consumption of a future supersonic commercial fleet is 7E13 g. This fleet would increase stratospheric BCA loadings by a factor of 2-3, because almost all fuel would be burnt above the tropopause. An improved EI(BCA) by a factor of ten would result in an increase of stratospheric BCA loadings by approximately 50 %.

Pueschel, R. F.↗

Material Issues in Space Shuttle Composite Overwrapped Pressure Vessels

Composite Overwrapped Pressure Vessels (COPV) store gases used in four subsystems for NASA's Space Shuttle Fleet. While there are 24 COPV on each Orbiter ranging in size from 19-40", stress rupture failure of a pressurized Orbiter COPV on the ground or in flight is a catastrophic hazard and would likely lead to significant damage/loss of vehicle and/or life and is categorized as a Crit 1 failure. These vessels were manufactured during the late 1970's and into the early 1980's using Titanium liners, Kevlar 49 fiber, epoxy matrix resin, and polyurethane coating. The COPVs are pressurized periodically to 3-5ksi and therefore experience significant strain in the composite overwrap. Similar composite vessels were developed in a variety of DOE Programs (primarily at Lawrence Livermore National Laboratories or LLNL), as well as for NASA Space Shuttle Fleet Leader COPV program. The NASA Engineering Safety Center (NESC) formed an Independent Technical Assessment (ITA) team whose primary focus was to investigate whether or not enough composite life remained in the Shuttle COPV in order to provide a strategic rationale for continued COPV use aboard the Space Shuttle Fleet with the existing 25-year-old vessels. Several material science issues were examined and will be discussed in this presentation including morphological changes to Kevlar 49 fiber under stress, manufacturing changes in Kevlar 49 and their effect on morphology and tensile strength, epoxy resin strain, composite creep, degradation of polyurethane coatings, and Titanium yield characteristics.

Sutter, James K.↗

2010 JANNAF Abstract Propulsion System Status: Ares First Stage

In November 2005, NASA created the Constellation Program to develop an entirely new fleet of spacecraft to include the Ares I Crew Launch Vehicle and the Ares V Cargo Launch vehicles. The Ares I First Stage Team has made significant progress on the design of a propulsion system capable of lofting that new fleet. To minimize technical risks and development costs, the Solid Rocket Boosters (SRBs) of Shuttle served as a starting point in the design of a new motor that would meet the requirements of those new vehicles. By bringing in a fifth segment, this new propulsive element will provide greater total impulse to loft a safer, more powerful fleet of space flight vehicles. Additional modifications include the use of composite structures, new metallic forward structures, new parachutes, a new propellant grain design, and a new nozzle. Although still ongoing and in process, significant design, development and concept testing has already been conducted. This includes a full-scale motor firing, deceleration subsystem testing, and testing of several complete avionics line replaceable units. The suborbital development flight, Ares I-X, provided the opportunity to gather critical data about the flight dynamics of the integrated launch vehicle stack. The Ares I-X test flight has also informed our Ares First Stage design. It brought a more comprehensive understanding in a number of areas, which are now being analyzed. This paper will provide an overview of the design, development, challenges, and progress on the production of the new Ares First Stage propulsion system. Challenges and mitigation strategies will be addressed. An overview will also be included of testing to date.

Tiller, Bruce K.↗

2010 JPC Abstract: Ares I First Stage Propulsion System Status

In November 2005, NASA created the Constellation Program to develop an entirely new fleet of spacecraft to include the Ares I Crew Launch Vehicle and Ares V Cargo Launch vehicles. This mission architecture included the Orion capsule (which would be used to transport astronauts to low-Earth orbit and beyond), the Altair lunar lander, and an Earth departure stage. The Ares First Stage Team has made significant progress on the design of a propulsion system to meet the objectives of the Constellation Program. Work on a first stage element propulsion system capable of lofting a new fleet of spacecraft is well underway. To minimize technical risks and development costs, the Solid Rocket Boosters (SRBs) of Shuttle served as a starting point in the design of a new motor that would meet the requirements of those new vehicles. This new propulsive element will provide greater total impulse utilizing a fifth segment to loft a safer, more powerful fleet of space flight vehicles. Performance requirements, basic architecture, and obsolescence issues were all factors in determining the new first stage element design and configuration. Early efforts focused on creating designs that would be capable of supporting the requisite loads and environments. While the motor casings are Shuttle legacy, because of Ares I s unique in-line configuration, the first stage will require entirely new forward structures (forward skirt, forward skirt extension, aeroshell, and frustum) and a modified systems tunnel. The use of composites facilitated a change in the geometry, which in turn afforded the ability to focus strength where it was needed without additional mass. The Ares First Stage rocket motor casting tooling was designed and built to achieve a propellant grain geometry that produces the specific required ballistic profile. The new propellant formulation is a polybutadiene acrylonitrile (PBAN) copolymer, which has been modified to attain the desired burn rate and retain adequate tailoring capability.

Priskos, Alex S.↗

Potential Future Shuttle Improvements

NASA has just recently completed the 104th flight of the Space Shuttle. Each of the four Orbiters in the Shuttle fleet have a design life of 100 flights each. Thus the fleet is capable of almost 300 more flights, and at current flight rates could potentially operate well past 2020 if necessary. This paper addresses some of the potential Shuttle system improvements that could be considered if the decision is made to continue operations of this vehicle for such an extended period. The national space transportation policy envisions a decision around 2005-2006 concerning readiness to start development of a Shuttle replacement system. Leading up to that decision point NASA is investing in the Space Launch Initiative (SLI) to reduce the development risks associated with key technologies needed for the next generation reusable launch vehicle (RLV). The Shuttle replacement could be a new design RLV or could be based on a Shuttle derived design: i.e., a vehicle based on the current Shuttle but with major design changes. The technology investment strategy of SLI is supportive of either approach. However, if NASA and industry are not ready to develop a replacement vehicle in the 2006-2012 timeframe, then another option would be to continue to make important, but evolutionary changes, to the existing Shuttle fleet. The overall strategy for next generation RLV planning, including possible Shuttle evolution, is captured in Figure 1.

Henderson, Edward↗

Maximizing Launch Vehicle and Payload Design Via Early Communications

The United States? current fleet of launch vehicles is largely derived from decades-old designs originally made for payloads that no longer exist. They were built primarily for national security or human exploration missions. Today that fleet can be divided roughly into small-, medium-, and large-payload classes based on mass and volume capability. But no vehicle in the U.S. fleet is designed to accommodate modern payloads. It is usually the payloads that must accommodate the capabilities of the launch vehicles. This is perhaps most true of science payloads. It was this paradigm that the organizers of two weekend workshops in 2008 at NASA's Ames Research Center sought to alter. The workshops brought together designers of NASA's Ares V cargo launch vehicle (CLV) with scientists and payload designers in the astronomy and planetary sciences communities. Ares V was still in a pre-concept development phase as part of NASA?s Constellation Program for exploration beyond low Earth orbit (LEO). The space science community was early in a Decadal Survey that would determine future priorities for research areas, observations, and notional missions to make those observations. The primary purpose of the meetings in April and August of 2008, including the novel format, was to bring vehicle designers together with space scientists to discuss the feasibility of using a heavy lift capability to launch large observatories and explore the Solar System. A key question put to the science community was whether this heavy lift capability enabled or enhanced breakthrough science. The meetings also raised the question of whether some trade-off between mass/volume and technical complexity existed that could reduce technical and programmatic risk. By engaging the scientific community early in the vehicle design process, vehicle engineers sought to better understand potential limitations and requirements that could be added to the Ares V from the mission planning community. From the vehicle standpoint, while the human exploration mission could not be compromised to accommodate other payloads, the design might otherwise be tailored to not exclude other payload requirements. This paper summarizes the findings of the workshops and discusses the benefits of bringing together the vehicle design and science communities early in their concept phases

Morris, Bruce↗

Preliminary Investigation of Civil Tiltrotor in NextGen Airspace

Presentation intro: Tiltrotor aircraft have long been envisioned as being a potentially viable means of commercial aviation transport. Preliminary results from an ongoing study into the operational and technological considerations of Civil Tiltrotor (CTR) operation in the Next Generation airspace, circa the 2025 time-frame, are presented and discussed. In particular, a fleet of CTR aircraft has been conceptually designed. The performance characteristics of this CTR fleet was subsequently translated into BADA (Base of Aircraft DAta) models that could be used as input to emulate CTR aircraft operations in the ACES and AvTerminal airspace and terminal area simulation tools. A network of nine North-Eastern corridor airports is the focus of the airspace simulation effort; the results from this airport network viII then be extrapolated to provide insights into systemic impact of CTRs on the National Airspace System (NAS). Future work will also be detailed as to attempts to model the systemic effects of noise and emissions from this fleet of new aircraft as well as assess their leveraged impact on public service missions, in time of need, such as major regional/national disaster relief efforts. The ideal outcome of this study is a set of results whereby Next Gen airspace CONOPs can be refined to reflect potential CTR capabilities and, conversely, CTR technology development efforts can be better informed as to key performance requirement thresholds needed to be met in order to successfully introduce these aircraft into civilian aviation operation.

Young, Larry A.↗

Electric Vehicles at Kennedy Space Center

The story of how the transportation office began by introducing low speed electric cars (LSEV) to the fleet managers and employees. This sparked and interest in purchasing some of these LSEV and the usage on KSC. Transportation was approached by a vender of High Speed Electric Vehicle (HSEV) we decided to test the HSEV to see if they would meet our fleet vehicle needs. Transportation wrote a Space Act Agreement (SAA) for the loan of three Lithium Powered Electric vehicles for a one year test. The vehicles have worked very well and we have extended the test for another year. The use of HSEV has pushed for an independent Electric Vehicle Study to be performed to consider ways to effectively optimize the use of electric vehicles in replacement of gasoline vehicles in the KSC vehicle fleet. This will help the center to move closer to meeting the Executive Order 13423.

Chesson, Bruce E.↗

Estimation of Airline Benefits from Avionics Upgrade under Preferential Merge Re-sequence Scheduling

Modernization of the airline fleet avionics is essential to fully enable future technologies and procedures for increasing national airspace system capacity. However in the current national airspace system, system-wide benefits gained by avionics upgrade are not fully directed to aircraft/airlines that upgrade, resulting in slow fleet modernization rate. Preferential merge re-sequence scheduling is a best-equipped-best-served concept designed to incentivize avionics upgrade among airlines by allowing aircraft with new avionics (high-equipped) to be re-sequenced ahead of aircraft without the upgrades (low-equipped) at enroute merge waypoints. The goal of this study is to investigate the potential benefits gained or lost by airlines under a high or low-equipped fleet scenario if preferential merge resequence scheduling is implemented.

air traffic management↗

Virtualized Multi-Mission Operations Center (vMMOC) and its Cloud Services

His presentation will cover, the current and future, technical and organizational opportunities and challenges with virtualizing a multi-mission operations center. The full deployment of Goddard Space Flight Centers (GSFC) Virtualized Multi-Mission Operations Center (vMMOC) is nearly complete. The Space Science Mission Operations (SSMO) organizations spacecraft ACE, Fermi, LRO, MMS(4), OSIRIS-REx, SDO, SOHO, Swift, and Wind are in the process of being fully migrated to the vMMOC. The benefits of the vMMOC will be the normalization and the standardization of IT services, mission operations, maintenance, and development as well as ancillary services and policies such as collaboration tools, change management systems, and IT Security. The vMMOC will also provide operational efficiencies regarding hardware, IT domain expertise, training, maintenance and support.The presentation will also cover SSMO's secure Situational Awareness Dashboard in an integrated, fleet centric, cloud based web services fashion. Additionally the SSMO Telemetry as a Service (TaaS) will be covered, which allows authorized users and processes to access telemetry for the entire SSMO fleet, and for the entirety of each spacecrafts history. Both services leverage cloud services in a secure FISMA High and FedRamp environment, and also leverage distributed object stores in order to house and provide the telemetry. The services are also in the process of leveraging the cloud computing services elasticity and horizontal scalability. In the design phase is the Navigation as a Service (NaaS) which will provide a standardized, efficient, and normalized service for the fleet's space flight dynamics operations. Additional future services that may be considered are Ground Segment as a Service (GSaaS), Telemetry and Command as a Service (TCaaS), Flight Software Simulation as a Service, etc.

Ido, Haisam Kassim↗

Bootstrapping Multi-Agent Unmanned Aerial Vehicle (UAV) System Integration Using Ground-Based Assets: Lessons Learned

In support of the Autonomy Teaming and TRAjectories for Complex Trusted Operational Reliability (ATTRACTOR) project, a fleet of unmanned ground vehicles (UGVs) was developed as a test and evaluation (T\&E) platform to reduce system integration gaps between simulation and live flight hardware. While simulation and hardware-in-the-loop bench testing provide adequate environments for preliminary validation, differences in system deployment architecture, software interfaces, and hardware infrastructure increase the risks to safety, property, and the project. Given ATTRACTOR’s goal of establishing a basis of certification of trust and trustworthiness in multi-agent autonomous systems, bridging these gaps was critical to successful project execution and feasibility assessment. In this paper we present the UGV fleet and its role in speeding up system integration, smoothing the transition from simulation to flight, and providing researchers an easy-to-use hardware test bed. An overview of the hardware and software on-board the vehicles is provided along with supporting infrastructure. The system integration process is documented including results in supporting both the overarching design reference mission (DRM) of ATTRACTOR and individual research efforts conducted since the creation of the fleet. Finally, we discuss the practical lessons learned regarding the testing, deployment, and operation of multi-agent autonomous systems.

Matthew P. Vaughan↗

Fit2Fly Project

NASA’s Fit2Fly project wants to make future commercial drone fleet operations routine, safe, and boring. How can future operators of commercial drone fleets know without a doubt that their aircraft are fit to fly? It is a tough problem, because every flight will effectively break the chain of custody for their aircraft, and having technicians do detailed inspections after each flight is not viable for large, busy fleets.

airworthiness↗

Velocity Measurements in the Wake of the Swept Wing Flow Test Model at the National Transonic Facility

Femtosecond laser electronic excitation tagging (FLEET) was applied to obtain flowfield velocity data for the Swept Wing Flow Test (SWiFT) at the NASA Langley Research Center National Transonic Facility (NTF). Despite numerous challenges associated with performing flow velocimetry measurements within a large-scale cryogenic wind tunnel facility, the experimental campaign was conducted under various conditions, including dry air at 320 K, cool nitrogen at 240 K, and Mach numbers of 0.2 and 0.8. FLEET velocimetry measurements were performed in the downstream wake of the SWiFT model, providing a quantitative dataset. This dataset includes one-dimensional velocity profiles and two-dimensional velocity maps acquired at different angles of attack and Reynolds numbers. The two-dimensional single component velocity maps indicate relatively uniform flow across the 120-mm wide wake flow survey suggesting that the main flow features can be represented by single-position linear velocity profiles. The measured instantaneous velocity profiles at variable angles of attack are compared to model lift coefficient information obtained at Mach 0.2. At high Reynolds numbers, a sudden velocity decrease was observed in the FLEET measurements at the same time as stall in lift coefficient was observed. At a low Reynolds number, both the velocity profiles and the lift coefficient show a smoother transition, without a sudden stall. Furthermore, the two-dimensional, one component velocity map reveals a velocity deficit region at Mach 0.8 at various angles of attack. Both single shot and mean velocity measurements were acquired allowing assessment of flowfield fluctuations and measurement precisions. The uncertainties are within 4 m/s in mean measurements based on repeatability data and about 5 m/s in instantaneous single-shot measurements. Measurements are reported with ~4.8 mm spatial resolution with 32-pixel averaging used to reduce measurement errors.

femtosecond↗

Initial Analysis of Digitally Enabled Cooperative Operations in Class D Terminal Airspace

The primary contribution of this paper is an initial analysis of integrating digitally enabled cooperative operations (or digital operations for short) with Visual Flight Rules (VFR) and Instrument Flight Rules (IFR) operations in the terminal airspace around a Class D airport, specifically around Fort Worth Alliance airport (KAFW). Enabled by connected digital technologies and automated information exchange, digital operations as envisioned would utilize cooperative practices and operator-responsible separation to ensure safety. In the present study, three conflict management configurations for digital operations were analyzed: 1) centralized with a single instance of a conflict management service to model a scenario with only one fleet operator conducting digital operations or all fleet operators utilizing the same service, 2) federated with two different instances to model a scenario with two different fleet operators conducting digital operations, and 3) fully distributed with a different instance for each digital operation. In simulations in which recorded tracks for VFR and IFR operations were played back and digital operations were modeled that would nominally arrive at KAFW once every 20 minutes (given no conflict resolution maneuvers), there were one or fewer losses of separation (LOS) across the three conflict management configurations. The same result was seen in simulations in which digital operations would nominally arrive at KAFW once every 10 minutes. However, in simulations in which digital operations would nominally arrive at KAFW once every 5 minutes, the number of LOS ranged between six and ten. This highlights the need for follow-on research to investigate the extent to which additional capabilities for digital operations, such as complexity management and/or flow organization, may be needed.

digitally enabled cooperative operations, digital ↗

Initial Analysis of Digitally Enabled Cooperative Operations in Class D Terminal Airspace

The primary contribution of this paper is an initial analysis of integrating digitally enabled cooperative operations (or digital operations for short) with Visual Flight Rules (VFR) and Instrument Flight Rules (IFR) operations in the terminal airspace around a Class D airport, specifically around Fort Worth Alliance airport (KAFW). Enabled by connected digital technologies and automated information exchange, digital operations as envisioned would utilize cooperative practices and operator-responsible separation to ensure safety. In the present study, three conflict management configurations for digital operations were analyzed: 1) centralized with a single instance of a conflict management service to model a scenario with only one fleet operator conducting digital operations or all fleet operators utilizing the same service, 2) federated with two different instances to model a scenario with two different fleet operators conducting digital operations, and 3) fully distributed with a different instance for each digital operation. In simulations in which recorded tracks for VFR and IFR operations were played back and digital operations were modeled that would nominally arrive at KAFW once every 20 minutes (given no conflict resolution maneuvers), there were one or fewer losses of separation (LOS) across the three conflict management configurations. The same result was seen in simulations in which digital operations would nominally arrive at KAFW once every 10 minutes. However, in simulations in which digital operations would nominally arrive at KAFW once every 5 minutes, the number of LOS ranged between six and ten. This highlights the need for follow-on research to investigate the extent to which additional capabilities for digital operations, such as complexity management and/or flow organization, may be needed.

digitally enabled cooperative operations↗